Catalog
[non-validated] DORA SFS 6 / SF 1: Incident management and classification

[non-validated] DORA SFS 6 / SF 1: Incident management and classification

Generated catalog draft. No operational assessment or human approval is claimed.

[non-validated] This question has unresolved selected work.

Question

[non-validated] Has the financial entity established a documented process to classify ICT-related incidents and significant cyber threats according to DORA Articles 17 and 18?

Explanation

[non-validated] Has the financial entity established a documented process to classify ICT-related incidents and significant cyber threats according to DORA Articles 17 and 18?

Criterion and evidence

Applies to financial entities under DORA Article 2(1-33). Verify documented incident classification methodology meeting repository-defined scope (keyDescription), covering workflows, ownership, tracking, prioritization, root cause analysis, and distinction between ordinary/major incidents/significant cyber threats during current compliance period. Evidence requires implemented process showing real-incident application per SFS 6 boundaries. No alternatives satisfy requirement.

AI assistance prompt

Develop sixteen bounded yes/no factors for DORA: Incident management and classification. Record, handle and classify ICT-related incidents and significant cyber threats using an accountable process. Cover incident handling workflows, ownership, tracking, prioritisation, root cause and classification criteria. Distinguish ordinary incidents, major ICT-related incidents and significant cyber threats. SFS 7 owns reporting deadlines, forms and recipients. DORA article references: 17, 18. Verify entity-role applicability and current primary sources. Missing evidence stays pending; no compliance or assessment is implied.

Clarifications

What constitutes sufficient evidence for this requirement?

Documented classification process aligned with repository topic boundaries (keyDescription) showing implementation evidence through real-incident logs. Pending when documentation or implementation records are absent per evidencePeriod.

Are alternative classification approaches permitted?

No alternatives satisfy the requirement per repository-defined scope; compliance necessitates adherence to DORA Article 18 criteria as implemented through accountable processes within current evidence period.

References

DORA: Incident management and classification

https://github.com/stefanospetsios/uniq2me/blob/1c70a85c3c2e074619c17aef2fd08be79a7e633d/json/en/6.json (opens in a new tab)