[non-validated] DORA SFS 5 / SF 1: Detection Thresholds Configuration
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 established documented detection thresholds for identifying anomalous activity and ICT-related incidents as specified in the repository topic allocation documentation for SFS 5?
Explanation
[non-validated] Has the entity established documented detection thresholds for identifying anomalous activity and ICT-related incidents as specified in DORA Article 10 implementation requirements?
Criterion and evidence
Applies to entities operating under DORA topic scope 5 boundaries. Evidence must document configured detection threshold parameters per repository topic description during current operational period. Absence of threshold configuration evidence = pending; default/unmodified settings = failed.
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 qualifies as sufficient threshold configuration documentation?
Repository-described evidence showing defined threshold values for anomalous traffic detection during operational period. Default/unmodified settings = failed. Missing configuration records = pending.
References
DORA: Monitoring and anomalous activity detection