Catalog
[non-validated] DORA SFS 5 / SF C: Continuous monitoring operations

[non-validated] DORA SFS 5 / SF C: Continuous monitoring operations

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 implemented continuous monitoring operations to detect anomalous activity, performance issues, and ICT-related incidents as specified in the repository topic allocation documentation for SFS 5?

Explanation

[non-validated] Does the entity implement continuous monitoring operations to detect anomalous activity, performance issues, and ICT-related incidents as described in the repository topic allocation for SFS 5?

Criterion and evidence

Implement continuous monitoring operations as defined in repository topic allocation for SFS 5 (keyDescription passage), covering 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.

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 sufficient evidence for this condition?

Repository-documented evidence confirming continuous monitoring for anomalous activity, performance issues, and ICT incidents as specified in keyDescription passage. Missing repository-described parameters result in pending verification.

How should missing monitoring evidence be handled?

Pending verification when required repository-described continuous monitoring evidence parameters are unavailable. Absence of documented evidence indicates failure per repository description.

References

DORA: Monitoring and anomalous activity detection

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