Logging and monitoring standard
Which events are logged on which systems, how long logs are kept, who may read and alter them, and what is monitored and alerted.
How the register reads it
| Also called | log management, security monitoring, SIEM standard |
|---|---|
| Family | Operations and technology |
| Document type | Standard. The regimes ask for the content, not the label; a line pasted as a standard, procedure, plan or schedule is placed here with the label noted. |
| Expected owner | The head of IT operations. |
| Review cadence | Annual (the register's default: the clauses say planned intervals and on significant change, and do not fix a period). |
| On the gap list when | ISO 27001 or DORA is ticked and no line resolves to it (ISO 27701, ISO 42001 require it too, inside a parent document, so they do not list it separately). |
| Template | Security monitoring and logging policy. |
Which standards require it, and what each expects it to contain
5 requiring clauses, 4 regimesShown on a register for the regimes you tick; with none ticked, ISO 27001 is applied. Requirement text is our own statement of each clause, read from the published text and cited so you can check it against the official text; it is not the instrument verbatim.
ISO/IEC 27001:2022
ISO 27001 8.15 LoggingProduce, store, protect and analyse logs of activities, exceptions and faults.
What the ISO 27002 guidance expects the document to say: Requires logs to be produced, stored, protected and analysed, covering activities, exceptions, faults and any other event of relevance. Older source material adds that records of user activity, exceptions and security events should be retained for an agreed period to support later investigation and access control monitoring, and that faults should be logged, analysed and acted on.
Common gap: Inconsistent log collection across systems
Source: ISO/IEC 27001:2022; guidance ISO/IEC 27002:2022
ISO 27001 8.16 Monitoring activitiesMonitor networks, systems and applications for anomalies and act on potential incidents.
What the ISO 27002 guidance expects the document to say: Requires networks, systems and applications to be monitored for anomalous behaviour, with appropriate action taken to evaluate whether what is observed constitutes an information security incident. Secondary commentary notes the deliberate shift to anomalous behaviour as the trigger, responding to cloud era risk.
Common gap: alerts not correlated across sources
Source: ISO/IEC 27001:2022; guidance ISO/IEC 27002:2022
ISO/IEC 27701:2025
ISO 27701 A.3.25 LoggingA process shall be in place to review event logs, by continuous automated monitoring and alerting or by manual review at a specified, documented periodicity, to identify irregularities and propose remediation; where possible event logs shall record access to PII including by whom, when, which PII principal's PII was accessed and what additions, modifications or deletions were made; where several service providers share roles in logging, the roles and any agreement on log access shall be defined and documented. Log information can itself contain PII, so access to it shall be controlled to ensure it is used only as intended, and a procedure, preferably automatic, shall delete or de-identify logged information as the retention schedule specifies. A PII processor shall define and make available to customers the criteria for if, when and how log information is made available to them, and where customers can access logs the processor controls it shall ensure each customer can access only records of its own activities and cannot amend the logs.
Common gap: Logs collected and never reviewed
Source: ISO/IEC 27701:2025
ISO/IEC 42001:2023
ISO 42001 A.6.2.8 AI system event loggingEvent logs shall be generated and recorded during AI system operations to enable monitoring, accountability, and incident investigation.
Common gap: Are logs sufficient to reconstruct an incident or audit a decision?
Source: ISO/IEC 42001:2023
DORA (Regulation (EU) 2022/2554)
DORA Art. 10 DetectionFinancial entities have mechanisms, aligned with the Article 17 incident process, that promptly detect anomalous activity, network performance problems and ICT-related incidents and flag possible material single points of failure; the mechanisms provide multiple control layers, alert thresholds and criteria that start incident response, automatic alerts to response staff, and are tested regularly under Article 25. Sufficient resources monitor user activity, anomalies and cyber-attacks. Data reporting service providers, where the entity is one, additionally check trade reports for completeness, omissions and obvious errors and ask for re-transmission (Art. 10(4)). Entities listed in Article 16(1) are outside this Article and follow the simplified framework of Article 16 instead.
Common gap: Alert thresholds set once and never tuned or tested
Source: DORA (Regulation (EU) 2022/2554)
Customizable template
11 sections, 5 cited to requiring clausesWith every regime ticked. Each clause section carries our statement of the clause, guidance beside it and starter wording to adapt; enter your organisation once, edit any section, export to Word, print or text. Every template is a draft to adapt and approve.
- Purpose
- Scope
- Roles and responsibilities
- Logging ISO 27001 A.8.15
- Monitoring activities ISO 27001 A.8.16
- Logging ISO 27701 A.3.25
- AI system event logging ISO 42001 A.6.2.8
- Detection DORA Art. 10
- Exceptions
- Related documents
- Review and approval
Customise this template The template document on the compliance platform
Do this for every document on your list
Paste the list and get this reading for every document at once, with the owner and cadence against each, the clauses quoted, and the documents the regimes expect that the list does not carry. Eight documents free, no account.
Build a register