Security Questionnaire Mapper

Logging and monitoring: the clause the question tests

What is logged, how long it is kept and who watches it.

How the customer usually asks it

example

"Do you centrally log and monitor security events?"

Read this question

Anchor clauses

7 frameworks
FrameworkAnchor clause
ISO/IEC 27001:20228.15 Logging · 8.16 Monitoring activities
SOC 2 (Trust Services Criteria)CC7.2 CC7.2 Monitoring system components for anomalies
SIG (Shared Assessments)domain G IT Operations Management
NIST Cybersecurity Framework 2.0DE.CM-01 Networks and network services are monitored to find potentially adverse events
NIST SP 800-53 Rev 5AU-6 Audit record review, analysis, and reporting
PCI DSS v4.0.110.4.1 Daily review of security-relevant logs
HIPAA Security Rule (45 CFR 164)164.312(b) Audit Controls (Standard)

Every framework that anchors this family is listed here; a register shows the ones ticked for the customer.

Evidence expected

The logging standard naming what is logged and for how long, the monitoring and alerting set-up, and a sample of the review record.

The clauses, with what an assessor asks for

ISO 27001 8.15 Logging

Produce, store, protect and analyse logs of activities, exceptions and faults.

Evidence an assessor expects: Log collection policy; Log storage and protection; Log review and analysis; Log retention and disposal
Where answers usually fall short: Inconsistent log collection across systems; Insufficient protection of log integrity
Source: ISO/IEC 27001:2022
ISO 27001 8.16 Monitoring activities

Monitor networks, systems and applications for anomalies and act on potential incidents.

Evidence an assessor expects: Network anomaly detection logs; System integrity monitoring reports; Application behavior alerts; Incident response records
Where answers usually fall short: Alerts not correlated across sources; Lack of documented response procedures for anomalies
Source: ISO/IEC 27001:2022
SOC 2 CC7.2 CC7.2 Monitoring system components for anomalies

Named only: the criteria are not stated here; see the official text.

Evidence an assessor expects: Logging standard and SIEM or log platform coverage of in-scope systems; Alert rules and sample of triaged alerts; Threat intelligence sources in use; Evidence detection tools are health-checked (for example log source outage alerts)
Where answers usually fall short: Key systems not sending logs to the monitoring platform; Alerts with no triage record
Source: SOC 2 (Trust Services Criteria)
SIG domain G IT Operations Management

What it asks for, in one line (the standard's own text is not quoted here):

Document and follow operational procedures for change management, capacity management, system hardening, backup, and operational monitoring for production systems.

Evidence an assessor expects: Operations procedure manual; Change advisory board minutes and tickets; Backup completion and restore test logs; Capacity reports
Where answers usually fall short: Backup restore not tested; Emergency changes routinely used to bypass CAB
Source: SIG (Shared Assessments)
NIST CSF DE.CM-01 Networks and network services are monitored to find potentially adverse events

Networks and network services are monitored to find potentially adverse events.

Evidence an assessor expects: Network flow telemetry coverage map by segment; IDS or NDR sensor inventory with placement diagram; DNS query analytics pipeline configuration; East-west traffic monitoring sample alerts; Egress monitoring policy and exception register
Where answers usually fall short: Encrypted traffic not inspected at chokepoints; Container and service mesh traffic invisible
Source: NIST Cybersecurity Framework 2.0
SP 800-53 AU-6 Audit record review, analysis, and reporting

Requires audit records to be reviewed and analysed on a defined frequency for indications of organization-defined inappropriate or unusual activity and its likely impact, findings to be reported to defined personnel, and the depth of review to be increased when credible information changes the risk.

Evidence an assessor expects: Defined review frequency and the activity indicators being looked for; Completed review records with reviewer, date and findings; Reports issued to the defined recipients and evidence of follow-up; Record of a review level adjustment made in response to changed risk
Where answers usually fall short: Review is automated alerting only, with no periodic analytical review for slow patterns; Findings recorded but never reported to anyone able to act
Source: NIST SP 800-53 Rev 5
PCI DSS 10.4.1 Daily review of security-relevant logs

What it asks for, in one line (the standard's own text is not quoted here):

Every day, at a minimum, the entity must review: all security events; the logs of each critical system component; the logs of each system component that stores, processes or transmits CHD and/or SAD; and the logs of each server and system component with a security function (such as authentication servers, IDS/IPS and network security controls). Applies to all entities. Objective under the customized approach: activity that may be suspicious or anomalous is found fast, keeping its impact low.

Evidence an assessor expects: Daily log review procedure naming the four log categories; SIEM dashboards or review tickets showing a review for every calendar day, including weekends and holidays; List of critical system components and security function systems covered by review; Reports or sign-offs from an outsourced SOC, if used; Interview records with analysts performing the review
Where answers usually fall short: No review evidence for weekends or public holidays; Security function devices such as authentication servers not included in the review scope
Source: PCI DSS v4.0.1
HIPAA 164.312(b) Audit Controls (Standard)

Implement hardware, software, and procedural mechanisms that record and examine activity in information systems that contain or use ePHI. NIST recommends central log management aligned to SP 800-92.

Evidence an assessor expects: Logging standard; Central log management deployment; Log retention configuration; SIEM use case catalog
Where answers usually fall short: Application-level audit logs missing; Logs retained less than six years where applicable
Source: HIPAA Security Rule (45 CFR 164)

Other families in operations, logging and vulnerability