Requirement
The entity monitors system components and the operation of those components for anomalies indicative of malicious acts, natural disasters and errors, and analyses them to determine whether they represent security events.
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.
Finding any of these outranks coverage — a policy that admits the gap is worse than silence.
Equivalent controls elsewhere
Matched on shared topics. Satisfying this control usually moves these too.
| Framework | Control | Title | Shared topics |
|---|---|---|---|
| ISO 27001 | A.8.16 | Monitoring activities | monitoring siem |
| PCI DSS 4.0.1 | 10.4 | Audit logs are reviewed, using automated mechanisms | monitoring siem |
| HIPAA | 164.308(a)(1)(ii)(D) | Information system activity review (R) | logging monitoring |
| GLBA | 314.4(c)(8) | Monitoring and logging of authorised user activity | logging monitoring |
| NIST CSF 2.0 | DE.CM-09 | Computing hardware, software and services are monitored | monitoring siem |
| ISO 27001 | A.5.7 | Threat intelligence | monitoring |
| ISO 27001 | A.5.28 | Collection of evidence | logging |
| ISO 27001 | A.7.4 | Physical security monitoring | monitoring |