Catalog
[non-validated] DORA SFS 5 / SF 7: External Incident Reporting Procedures

[non-validated] DORA SFS 5 / SF 7: External Incident Reporting Procedures

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

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

Question

[non-validated] Has the entity documented procedures for reporting detected anomalous activity, performance issues, or ICT-related incidents to external regulatory authorities as specified in the repository topic allocation documentation for SFS 7?

Explanation

[non-validated] Does the entity maintain documented procedures for reporting detected ICT incidents to external regulatory authorities as specified in the repository's DORA topic allocation for SFS 7?

Criterion and evidence

Verify repository-documented evidence of external incident reporting protocols with defined submission channels during current operational period for entities under DORA Topic 5 scope. Pending when repository-described parameters are unpopulated.

AI assistance prompt

Develop sixteen bounded yes/no factors for DORA: Monitoring and anomalous activity detection. Detect anomalous activity, performance issues and ICT-related incidents using monitored evidence. Cover detection thresholds, logging, alerting, monitoring responsibilities, escalation triggers and testing of detection capability. SFS 6 owns handling/classification after detection; SFS 7 owns external reporting. DORA article references: 10. Verify entity-role applicability and current primary sources. Missing evidence stays pending; no compliance or assessment is implied.

Clarifications

What constitutes valid evidence for compliant reporting procedures?

Repository-documented evidence showing completed regulatory notification fields in incident report templates within the operational period. Absence of specified submission channels constitutes failure per repository definition.

How are unpopulated reporting parameters treated?

Unpopulated external reporting verification fields in the repository-described incident response framework result in pending status until documented evidence becomes available under current operational parameters.

References

DORA: Monitoring and anomalous activity detection

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