One page per clause
The duty in our words, the evidence a board or an auditor asks for, the common gaps and what to do before publication.
Open the registerIt applies to any organization of any size that governs the security of information, whether the security work sits inside an ISO/IEC 27001 management system or outside one. It is written for the governing body and top management, and for the people who evaluate, direct and monitor the management system. It is guidance, not a certifiable requirement.
Last updated: . Written from the published edition and the ISO record. Not legal advice; does not certify.
The standard is about the governance of information security, not about holding a certificate. An organization that runs a certified management system is inside its audience, and so is one that governs security outside any formal system. What matters is that a governing body sets direction, monitors performance and answers for the result.
The first is the governing body and top management. The second is the people who evaluate, direct and monitor a management system based on ISO/IEC 27001. The third is the people who manage security outside such a system but inside the reach of governance. A reader should place themselves in one of the three before applying a clause.
Very little, because the scope is governance itself. An organization with no governing body, no information to protect and no interested parties is hard to imagine. The practical question is not whether the guidance applies but which of its clauses is already covered by the management system and which is not.
Write the scope note and the role map, then run the free check. If the relationship between the entity and the management system is unclear, the check returns scope incomplete and names that question rather than guessing the lighter pathway.
No. It applies to all types and sizes. In a small organization the governing body and top management can be the same people, and the standard accepts that, but the record still has to show how policy setting is separated from execution.
Yes. The scope explicitly includes information security management outside an ISO/IEC 27001 management system but within the scope of governance.
No. It is guidance. A contract, a regulator or your own policy can make a practice binding, and that is a different kind of obligation.
Run the free check / Open the register / The kit and the watch
Every clause answer on this site points to the official rule behind it, so you can check any line yourself. The register holds 28 records, 110 evidence lines and 84 common failure lines. The dates come from the ISO record. The substance comes from the published 2020 edition, which is the baseline that edition 3 replaces.
The duty in our words, the evidence a board or an auditor asks for, the common gaps and what to do before publication.
Open the registerAnnexes A to C are informative. Each page says so, because a finding cannot rest on guidance alone.
Open the annexesStage 50.60 is recorded on 12 August 2026. The planning date is an estimate and is labelled wherever it appears.
Read the recordThe edition 3 text is not public and is not reproduced. Each record cites the published clause it comes from. Where the public record is silent, the page says so.