[non-validated] DORA SFS 5 / SF 3: Monitoring Responsibilities and Escalation Triggers (Article 10)
Generated catalog draft. No operational assessment or human approval is claimed.
[non-validated] This question has unresolved selected work.
Question
[non-validated] Have documented monitoring responsibilities and escalation triggers been established for detecting anomalous activity, performance issues, and ICT-related incidents according to the repository topic allocation documentation?
Explanation
[non-validated] Have documented monitoring responsibilities and escalation triggers been established for detecting anomalous activity, performance issues, and ICT-related incidents according to the repository topic allocation documentation?
Criterion and evidence
Verify documented evidence of assigned monitoring responsibilities and defined escalation triggers per repository topic scope 5 description (DORA Article 10 reference), applicable to entities operating under topic boundaries. Evidence period aligns with current operational documentation.
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 evidence satisfies this requirement?
Repository-described protocols showing formally assigned monitoring duties and documented escalation paths for critical anomaly scenarios. Missing assignment fields or undefined triggers constitute insufficient evidence.
How are alternative implementations assessed?
No valid alternatives exist per repository definition; requirements mandate explicit documentation of both responsibilities and triggers as defined in topic allocation materials. Unstructured approaches fail verification.
References
DORA: Monitoring and anomalous activity detection