Annex A 5.1
Policies for information security
A defined set of security policies exists, is approved at the right level, is communicated to the people it binds, and is reviewed on a schedule.
What an assessor looks for
Expect to show the approval record, evidence that staff have seen the policy, and the last review with its outcome. A policy nobody can produce evidence of reading is a finding regardless of how well it is written.
Where it usually fails
The policy set exists but has not been reviewed since certification, or the review is minuted with no substantive change considered.
Classification
- Theme
- A.5 Organisational
- Control type
- Preventive
- Security properties
- Confidentiality, Integrity, Availability
- Cybersecurity concepts
- Identify, Protect
- ISO 27001:2013 equivalent
- 5.1.1, 5.1.2
Control number and title are identifiers used as references. The classification above is our own analysis, aligned to the shape of the ISO 27002 attribute model rather than reproduced from it, and no text from the standard appears on this page. Last reviewed 2026-08-03.
Building the Statement of Applicability?
Record your applicability decision for this control and the other 92 in the browser-based builder. Nothing is transmitted, and you export the file at the end.
Open the SoA builder