ISO/IEC 27001: security policies approved, communicated and acknowledged
For ISMS owners and security leads who hold or are working toward accredited ISO/IEC 27001 certification and must evidence policy, awareness and document control at every audit.
Checked against primary sources on 18 October 2026.
Who it applies to
Any organization that chooses to run an information security management system and seek accredited certification, typically because customers, tenders or contracts ask for the certificate.
Who checks
Auditors from accredited certification bodies; customers and partners then review the certificate, its scope and often the Statement of Applicability.
How often
Two-stage initial certification audit, surveillance audits each year, recertification every three years
Current edition
ISO/IEC 27001:2022 (Edition 3) with ISO/IEC 27001:2022/Amd 1:2024 Climate action changes, 2022-10-25 (Amd 1:2024 published 2024-02-23). Paid standard (CHF 155 for English PDF + ePub on the ISO Store; Amd 1:2024 listed at CHF 0).
Dates to know
Dates for ISO/IEC 27001
Date
What happens
Status
2025-10-31
Transition from ISO/IEC 27001:2013 ends; certification bodies must have moved all clients to the 2022 edition
Done
2026-01-01
Global Accreditation Cooperation Incorporated replaces IAF and ILAC as the international accreditation body
Done
What ISO/IEC 27001 asks you to write down
Each one needs an owner, an approval, and proof it reached the people it covers.
Clause 5.2
Information security policy
Top management sets a policy suited to the organization's purpose that frames security objectives, commits to meeting requirements and improvement, and is communicated internally.
Top management approval and date
Version in force and review history
Where interested parties can access it
Annex A 5.1
Topic-specific policies
Topic-specific policies sit beneath the main policy; management approves and publishes them, relevant people receive and acknowledge them, and they are reviewed at planned intervals.
Owner and management approval per policy
Acknowledgment by name for each relevant person
Planned review date and change triggers
Clauses 6.1.2 and 8.2
Risk assessment process and results
Documented criteria for assessing and accepting information security risk, applied consistently, with results retained each time the assessment runs.
Risk acceptance and assessment criteria
Dated assessment results and risk owners
Clause 6.1.3
Statement of Applicability and risk treatment plan
The SoA records which controls are necessary, why any are excluded and whether each is implemented; risk owners approve the treatment plan and residual risk.
Justification for each Annex A control
Implementation status per control
Risk owner approval of residual risk
Clause 7.3 and Annex A 6.3
Awareness, education and training
People working under the organization's control know the policy, their contribution to the ISMS and the consequences of not conforming, with training kept current.
Training completion by person and date
Policy version each session covered
Annex A 5.37
Documented operating procedures
Operating procedures for information processing facilities are documented and made available to the personnel who need them.
Procedure owner and current version
Distribution to the people who perform it
Citations are to the standard or regulation; wording is ours.
What gets asked for on the day
What reviewers sample about these documents and the people they cover.
Policy approval and acknowledgment
Auditors sample the main and topic-specific policies and ask for management approval, the published version and records showing staff and relevant third parties acknowledged them.
Document control under 7.5
They check that documented information is identified, reviewed, approved and versioned, that current versions are available where used and that obsolete versions are withdrawn.
Awareness in interviews
Staff interviews test whether people know where policies live, what applies to their role and what happens if they do not follow them.
Policies traced to the SoA
Auditors trace policies to the risk assessment and Statement of Applicability to confirm the documented controls match what is implemented.
The policy and acknowledgment layer for ISO/IEC 27001.
Write each policy, send it through approval, and send it to the people it covers. Each acknowledgment is recorded by name, with the version, the date and the time.
When a policy changes, the new version is approved, its Editor sends it out again, and everyone it applies to is asked again. Export the record as a PDF or CSV, or give a reviewer Viewer access to the documents their tags allow.
Approved before it goes outUp to four steps, with any or all approvers.
Acknowledged by nameName, email, date, time and version on every record.
Asked again on every changeEach new version goes out again to everyone it applies to.
The record on requestA PDF or CSV export, or Viewer access to the documents their tags allow.
Your region’s laws, the standards your customers ask for, and your own house rules. Write each one as a policy, approve it, and send it to the people it covers.
It added a requirement in clause 4.1 to determine whether climate change is a relevant issue, plus a note in 4.2 that interested parties can have climate-related requirements. IAF and ISO stated the intent of both clauses is unchanged, so no formal transition program applied.
Are certificates to the 2013 edition still valid?
The IAF MD 26 transition closed on 31 October 2025, and certification bodies had to move all clients to ISO/IEC 27001:2022 by then. Audits now run against the 2022 edition and its 93 Annex A controls.
Does the standard expect staff to acknowledge policies?
Annex A control 5.1 calls for relevant personnel and interested parties to receive and acknowledge the policies that apply to them. Certification bodies such as TÜV NORD look for records showing who acknowledged which version.
How often should policies be reviewed?
The standard asks for review at planned intervals and when significant changes occur, without fixing a period. TÜV NORD suggests at least annual review as a practical baseline.
What must be in place before the initial audit?
NQA asks for the management system to have run for at least three months, with a management review and a full internal audit cycle completed. Stage 1 then reviews ISMS design and Stage 2 tests operation and effectiveness.