Catalog
[non-validated] DORA SFS 5 / SF A: Monitoring Handoff to Classification Team

[non-validated] DORA SFS 5 / SF A: Monitoring Handoff to Classification Team

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 evidence that detected anomalous activity, performance issues, or ICT-related incidents are handed off to the classification/handling team (SFS 6) as specified in the repository topic allocation documentation?

Explanation

[non-validated] Is there repository-documented evidence that detected anomalous activity, performance issues, or ICT-related incidents are handed off to the classification/handling team (SFS 6) as specified in current monitoring procedures?

Criterion and evidence

Verify repository-documented handoff protocols to SFS 6 during operational evidence period, including detection thresholds, logging, alert triggers, and monitoring responsibilities. Based on DORA Article 10 reference in repository implementation 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 constitutes sufficient evidence for this condition?

Documented procedures showing completed transfer to SFS 6 during operational period, including verification records of monitored evidence triggering handoff. Alternative: Test validation demonstrating successful handoff workflow execution per repository specifications.

How are missing handoff procedures evaluated?

Pending verification status when repository-described handoff evidence parameters are unavailable. Absence of documented procedures constitutes failure only when explicit repository requirements are verifiable and unmet.

References

DORA: Monitoring and anomalous activity detection

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