ISO/IEC 27002:2022, 1
Scope
The structural clause 1, with what it does in the catalogue, why it matters to the attribute record and what a buyer should keep. This page is our statement of the clause, not the text.
What this part of the catalogue does
Clause 1 describes the document as a catalogue of general-purpose security controls accompanied by guidance on implementing them, intended for use inside an ISMS that follows ISO/IEC 27001, for implementing controls based on internationally recognized good practice, and for developing an organization's own information security management guidelines.
What it means when you fill the register
The scope clause describes a reference set of generic controls with implementation guidance, for organisations that want to select and implement controls in an ISMS based on ISO/IEC 27001, and for organisations that want a common control reference without certification. It states that the document is not a management system standard and does not set management system requirements. For the attribute view the scope is the boundary: the attributes describe the controls in this catalogue, and adopting them does not extend the ISMS scope or create a new certification. A consultant who is asked to 'certify the attributes' should say this plainly. The site says it on the publication page, in the terms and in the free check result. The scope also answers a common consultancy question: can the attribute view be sold as a separate deliverable? It can be a useful one, provided the client understands that it is a view of the existing controls and not a new certification. Our kit prices it as a document set for that reason, and the terms say plainly that it does not certify anything.
Scope questions arrive as 'does this apply to us?'. The honest answer for the attribute guidance is that it applies if you use the control catalogue, and it does not create a certification duty. In practice the scope statement in the ISMS is unchanged, the control set is unchanged, and the only addition is a view. A consultant can say that in one sentence and then spend the time on the SoA, which is where the buyer's actual risk sits.
What to keep beside the register
- The clause reference and the edition you read, so a later reader can check it.
- The decision it supports, with an owner and a date.
- The link to the control rows it frames, so the clause is not an orphan page in the file.
This is a structural or introductory clause. It carries no control evidence of its own, and the site does not present it as a requirement.
Where this clause is used
Source for this page
- ISO/IEC 27002:2022, the control catalogue and Table A.1. The reference record of the 93 controls, their five attribute values, purpose, evidence and gaps. The published standard is at https://www.iso.org/standard/75652.html.
- ISO/IEC 27028, official record. Stage 60.00 under publication, edition 1, committee, abstract and the dated lifecycle. Retrieved 20 October 2026.
Retrieved 2026-10-20. The requirement above is our statement of the clause in our own words; the official text is linked so you can check it.