Catalog
[non-validated] DORA SFS 7 / SF F: Verification of Current Incident Reporting Templates (Repository Draft)

[non-validated] DORA SFS 7 / SF F: Verification of Current Incident Reporting Templates (Repository Draft)

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 documented verification evidence confirming the use of current competent-authority templates and timing specifications for incident reporting as specified in the DORA topic allocation documentation?

Explanation

[non-validated] Does the financial entity maintain documented verification evidence confirming use of current competent-authority templates and timing specifications for incident reporting as specified in the repository topic allocation documentation (draft taxonomy)? This draft reflects repository-prose guidance; no external legal verification performed.

Criterion and evidence

Actor: Financial entity under DORA topic allocation framework (draft taxonomy). Scope: Verification of current competent-authority templates/timing for incident reporting per repository topic allocation documentation. Evidence period: Current review period with evidence dated after repository publication. Positive criterion: Documented verification evidence confirming current templates/timing per repository requirement. Negative criterion: Evidence shows outdated templates/timing or absence of verification documentation as specified in repository. Missing evidence: Pending until verification evidence is provided; never presumed negative. Alternatives: No valid alternatives satisfy the requirement per repository topic allocation.

AI assistance prompt

Develop sixteen bounded yes/no factors for DORA: Incident reporting and communications. Notify and report applicable incidents using current competent-authority requirements and communication plans. Cover initial/intermediate/final reports, voluntary significant-threat notifications, delegated reporting responsibilities, client/stakeholder communication and applicable operational/payment-security incidents. Verify current RTS/ITS timing and templates from sources; do not invent deadlines or assume one authority for every entity. DORA article references: 14, 19, 20, 21, 22, 23. Verify entity-role applicability and current primary sources. Missing evidence stays pending; no compliance or assessment is implied.

Clarifications

What evidence qualifies as sufficient verification?

Documented verification reports (e.g., internal assessments dated after repository publication) confirming use of current competent-authority templates/timing specifications per repository topic allocation keyDescription. Must reference specific templates/versions applicable during review period. Generic assertions without version details are insufficient. Repository templates are unverified draft guidance, not statutory evidence.

References

DORA: Incident reporting and communications

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