Art.18 Classification of ICT-related incidents and cyber threats
Financial entities shall classify ICT-related incidents and determine their impact based on criteria including the number/relevance of clients and transactions affected, geographical spread, data losses, criticality of s
1
artefacts
0
held by a system
0
at each review
hard
to go live
Policy repository / GRC workspace
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
none for this control
periodic reviewEvidence produced at each review
none for this control
governing documentDocuments that govern the control
- Incident classification methodology aligned to the DORA criteria/RTS thresholds · Policy repository / GRC workspace
First move
This control is evidenced by people and documents, not systems. Put the document under version control with an owner and review date, and log each review as a record with reviewer and date. Do not try to automate it.
Common gaps auditors find
- No incident classification against the prescribed criteria
Do this for your whole sheet
Paste the rows you run your controls from and get this mapping for every control at once, with the periodic-review ones flagged and a first move per row. No account for the first run.
Build my evidence sheetArt.17 ICT-related incident management process · Art.19 Reporting of major ICT-related incidents