ISO/IEC 27002:2022, 0.5
Developing organization-specific guidelines
The structural clause 0.5, 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 0.5 presents the document as a starting point for an organization's own guidelines: not every control or piece of guidance will apply, and further controls and guidance may be needed for the organization's particular needs and identified risks. Cross-referencing organization-specific documents to the clauses of this document helps later reference.
What it means when you fill the register
The catalogue is generic; an organisation adds its own guidance where its context, technology, sector or regulation demands it. The introduction encourages written organisation-specific guidance beside the generic control, and warns that guidance written once and never reviewed becomes a source of drift. The attribute view is one way to decide where that guidance is needed: a control with an unusual combination of values, or with no detective or corrective value, is a candidate for a closer look. This is our reading, not a requirement in the text. The page states the reading as ours because a buyer should be able to disagree with it. The register can carry a column for the organisation's own guidance, which is usually where the real local knowledge sits. The test of local guidance is whether a new joiner could follow it without asking the author. If not, the attribute value it supports is probably resting on one person's memory. A short review note in the register, naming the author and the date, is usually enough to keep it honest.
Local guidance is where sector rules, technology choices and contractual terms land. A bank, a hospital and a software supplier can all use the same 93 controls and still need different local guidance for the same control. The attribute view helps a reviewer see where the local guidance is doing real work, because a control with an unusual combination of values is usually the one with a local story. The page should not claim that the standard asks for this review; it is our method, and it is offered as one.
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.