Requirement
Networks, systems and applications shall be monitored for anomalous behaviour and appropriate actions taken to evaluate potential information security incidents.
What the engine looks for
Every group below must be satisfied — by an affirmative statement, not a plan, a hedge or a denial — for the control to count as covered. A term ending in … matches any word it begins. Supporting terms do not change the verdict — they raise confidence and distinguish a policy that names a mechanism from one that gestures at a category.
Required element 1 — any one of
monitormonitoringalertdetection
Required element 2 — any one of
anomal…suspiciousthresholdrulebaseline
Supporting terms — specificity signals
siemon-call24/7runbooktuningfalse positive
Equivalent controls elsewhere
Matched on shared topics. Satisfying this control usually moves these too.
| Framework | Control | Title | Shared topics |
|---|---|---|---|
| PCI DSS 4.0.1 | 10.4 | Audit logs are reviewed, using automated mechanisms | monitoring siem |
| SOC 2 | CC7.2 | Monitoring for anomalies | monitoring siem |
| NIST CSF 2.0 | DE.CM-09 | Computing hardware, software and services are monitored | monitoring siem |
| SOC 2 | CC4.1 | Ongoing and separate evaluations | monitoring |
| PCI DSS 4.0.1 | 10.7 | Failures of critical security controls are detected and addressed | monitoring |
| PCI DSS 4.0.1 | 11.5 | Intrusion detection and change detection | monitoring |
| PCI DSS 4.0.1 | 11.6.1 | Payment page change and tamper detection | monitoring |
| GLBA | 314.4(c)(8) | Monitoring and logging of authorised user activity | monitoring |