A.8.16 Monitoring activities
Monitor networks, systems and applications for anomalies and act on potential incidents.
12
artefacts
8
held by a system
1
at each review
easy
to go live
SIEM / log platform
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
- IDS/IPS alert logs · SIEM / log platform
- Firewall anomaly detection logs · SIEM / log platform
- Host-based IDS alerts · SIEM / log platform
- File integrity monitoring change logs · SIEM / log platform
- OS security event logs · SIEM / log platform
- Web application firewall alerts · SIEM / log platform
- Application performance monitoring anomaly reports · SIEM / log platform
- Custom application log anomaly summaries · SIEM / log platform
periodic reviewEvidence produced at each review
- Post-incident review meeting minutes · Policy repository / GRC workspace
governing documentDocuments that govern the control
- NetFlow analysis reports · Policy repository / GRC workspace
- Incident ticketing system entries for detected anomalies · Policy repository / GRC workspace
- Root cause analysis reports for security events · Document repository
First move
Automate the pull from your SIEM / log platform. Retention and alert rules exported from the SIEM; review evidence is the closed-alert record with reviewer and time.
Common gaps auditors find
- alerts not correlated across sources
- lack of documented response procedures for anomalies
- insufficient retention of monitoring logs
- overreliance on manual review
Do this for your whole sheet
Paste the rows you run your controls from and get this mapping for every control at once, with the periodic-review ones flagged and a first move per row. No account for the first run.
Build my evidence sheet