DORA major ICT-related incident initial notification (Article 19(4))

sha256(raw catalogue entry JSON file bytes)

ActProof shows what a machine-readable profile claims and where it came from. It does not certify legal compliance and is not legal advice.


Commission Implementing Regulation (EU) 2025/302


The field is a direct institutional identifier in the reporting template and glossary instructions.


The field is a direct institutional identity field in the reporting template.


Regulation (EU) 2022/2554 (Digital Operational Resilience Act)


The field records the regulated-entity category using the template and glossary context; selection depends on the entity taxonomy.


The field identifies the reporting stage in the DORA incident-reporting sequence.


The field normalises the institution’s incident reference into the reporting-template identifier field.


Commission Delegated Regulation (EU) 2025/301


The field normalises the detection timestamp for time-limit and reporting-template purposes.


The field reconciles the classification timestamp with the reporting sequence and timing rules.


Commission Delegated Regulation (EU) 2024/1772


The field records which classification criteria were triggered. The template carries the field; the classification RTS supplies the substantive criteria; the initial-notification RTS supplies the content context.


The field reconciles template reporting with operational analysis of affected jurisdictions.


The field transforms operational detection context into the reporting-template discovery-method field.


The field normalises business-continuity activation evidence into a boolean reporting field.


The field models a provisional narrative impact description from the initial-notification content requirement and reporting template.


The field is a direct contact-information field in the reporting template.


The field is a direct contact-email field in the reporting template.


The field links the reporting channel and competent-authority context to the operational recipient field.


Secondary contact information is optional support for report contact details. [experimental_optional: bound to existing section/obligation atoms, not a distinct reviewed template cell]


Secondary contact email is optional support for report contact details. [experimental_optional: bound to existing section/obligation atoms, not a distinct reviewed template cell]


First disruption time may be known at initial-notification stage but is associated with more detailed or later reporting. [experimental_optional: bound to existing section/obligation atoms, not a distinct reviewed template cell]


Affected functions/services may be known early and are relevant to incident impact, but are treated as optional in this profile. [experimental_optional: bound to existing section/obligation atoms, not a distinct reviewed template cell]


Preliminary affected-client estimate may be known early but is treated as optional in this profile. [experimental_optional: bound to existing section/obligation atoms, not a distinct reviewed template cell]


Preliminary financial amount may be known early and needs separate currency handling. [experimental_optional: bound to existing section/obligation atoms, not a distinct reviewed template cell]


Reporting currency is modelled separately from amount fields to avoid hard-coded assumptions. [experimental_optional: bound to existing section/obligation atoms, not a distinct reviewed template cell]


Third-party involvement can matter to the DORA reporting context and reporting-on-behalf arrangements. [experimental_optional: bound to existing section/obligation atoms, not a distinct reviewed template cell]


Outsourcing reference supports third-party reporting context where relevant. [experimental_optional: bound to existing section/obligation atoms, not a distinct reviewed template cell]


Optional cross-reference to a related threat notification when such record exists. [experimental_optional: bound to existing section/obligation atoms, not a distinct reviewed template cell]


Optional cross-reference to a related NIS2 notification when such record exists. [experimental_optional: bound to existing section/obligation atoms, not a distinct reviewed template cell]


Optional cross-reference to a related GDPR breach notification when such record exists. [experimental_optional: bound to existing section/obligation atoms, not a distinct reviewed template cell]


ActProof operates a native MCP runtime today