ISO 27001:2022 | Control 5.35 / A.18.2.1
Independent Review of Information Security
ISO 27001 Control 5.35 requires an independent, impartial review of your information security management system. Not a self-assessment. Not a checkbox. A skilled external review that tells you whether your ISMS is genuinely working.
Request an Independent ReviewWhat ISO 27001:2022 Control 5.35 (A.18.2.1) Actually Requires
ISO 27001:2022 Control 5.35 is the direct successor to the 2013 standard's Annex A control A.18.2.1. The requirement is unchanged in intent and reinforced in scope: an organisation's approach to managing information security — its controls, policies, processes, and procedures — must be reviewed independently at planned intervals.
The 2022 version goes further than its predecessor by explicitly naming the circumstances that trigger an ad-hoc review outside the planned schedule.
The purpose is clear. The ISMS must remain suitable, adequate, and effective — not just at certification, but continuously. An independent review is how you demonstrate that to management, your board, and external stakeholders.
The Standard's Core Requirement
The organisation's approach to managing information security and its implementation shall be reviewed independently at planned intervals or when significant changes occur, to ensure its continuing suitability, adequacy, and effectiveness.
ISO/IEC 27001:2022 — Control 5.35. Source: iso.org/standard/82875.html
Three Things an Independent Review Must Assess
Suitability
Does your ISMS reflect your current business context? Controls designed for a 50-person firm rarely remain suitable at 200. An independent reviewer tests whether the approach still fits the organisation it is meant to protect.
Adequacy
Are the controls comprehensive enough to address your real risk exposure? Adequacy goes to coverage. An independent review identifies the gaps between what the policy says and what is actually protecting you day to day.
Effectiveness
Are the controls actually working? A policy exists. Access reviews are scheduled. But are they happening? Are they producing the right outcomes? Effectiveness testing is where most self-assessments fall short.
Why Independence Is the Point
The standard is explicit: the review must be conducted by individuals independent of the area being assessed. You cannot mark your own homework and satisfy Control 5.35.
Internal staff from a separate department can satisfy the independence requirement in large organisations with genuinely siloed functions. For most mid-market organisations in Australia and New Zealand, that separation does not exist in practice. The security manager who built the ISMS cannot be the person who objectively assesses it.
An external qualified reviewer brings two things an internal review cannot: impartiality and comparative perspective. They have seen how other organisations implement similar controls. They know what good looks like. They know what an auditor from a certification body will look for — because they are, or have been, that auditor.
For Australian and New Zealand organisations operating under APRA CPS 234, ASIC governance obligations, the Privacy Act 1988 (Cth), or New Zealand's NZISM requirements, the independent review also serves a second function: it provides documented assurance that can be presented to regulators, boards, and audit committees as evidence of ongoing due diligence.
When a Review Is Required
Control 5.35 requires reviews at planned intervals and whenever significant changes occur. The 2022 version explicitly lists the circumstances that trigger an ad-hoc review. Any one of these is a reason to act.
Regulatory change
A new law, regulation, or guidance affecting your information security obligations. In 2025 and 2026, the Cyber Security Act 2024, APRA CPS 230, and updated NZISM guidance have each created this trigger for many ANZ organisations.
Significant security incident
A data breach, ransomware event, or material compromise. The incident reveals that something in your ISMS did not work. A review determines what and why, before the next event occurs.
Major business change
Merger, acquisition, new product line, expansion into a new market, or a significant change to your cloud or technology environment. Your risk profile has changed. Your controls need to reflect it.
New service or product
A new offering that processes customer data, uses AI systems, or relies on third-party suppliers not previously assessed. This includes adopting AI tools that were not in scope when the ISMS was last reviewed.
Material change to controls
Significant changes to existing security controls, policies, or processes. If the controls have been rebuilt, the review of the previous version is no longer valid evidence of the current state.
Annual planned review
Regardless of the above, most certified organisations conduct a full independent review at least annually, aligned to the three-year ISO 27001 certification cycle, to ensure all 93 Annex A controls are verified for operational effectiveness.
The ANZ Regulatory Context Makes This More Urgent
For Australian and New Zealand organisations, the independent review obligation does not exist in isolation. It sits inside a regulatory environment that is actively tightening, and where regulators are increasingly focused on the gap between documented compliance and operational reality.
APRA CPS 234 — Australia
APRA CPS 234 requires the internal audit function of APRA-regulated entities to include a review of the design and operating effectiveness of information security controls — including those maintained by third parties. This maps directly to the independent review obligation in ISO 27001 Control 5.35. Organisations holding ISO 27001 certification can use a well-structured 5.35 review process to satisfy core elements of this requirement, provided the reviewer is genuinely independent and the scope covers third-party controls. Source: APRA CPS 234, July 2019.
APRA CPS 230 — Operational Risk (effective 1 July 2025)
APRA CPS 230 came into force on 1 July 2025 and significantly expanded obligations around operational resilience and material service provider oversight. For organisations where third-party suppliers are part of the ISMS scope, CPS 230 creates an additional reason to ensure the independent review includes supply chain controls — not just internal ones. Source: apra.gov.au/operational-risk.
NZISM and New Zealand Obligations
The New Zealand Information Security Manual (NZISM) sets baseline controls for New Zealand government agencies and is increasingly referenced by private sector organisations, particularly those supplying government. NZISM controls can be mapped to ISO 27001 Annex A, meaning an ISO 27001 independent review can simultaneously provide assurance against NZISM obligations. For trans-Tasman organisations, a dual-jurisdiction review that addresses both frameworks eliminates duplication and strengthens the evidence trail for both Australian and New Zealand regulators. Source: nzism.gcsb.govt.nz.
Privacy Act 1988 (Cth) and Cyber Security Act 2024 — Australia
Australia's Privacy Act 1988 (Cth) requires APP entities to take reasonable steps to protect personal information from misuse, loss, and unauthorised access. The Cyber Security Act 2024, passed on 25 November 2024, introduced mandatory ransomware payment reporting and reinforced the obligation to maintain documented, tested security practices. An annual independent review of your ISMS provides directly relevant evidence of "reasonable steps" — the standard against which regulators and courts assess whether an organisation has met its obligations. Source: Privacy Act 1988 (Cth) | Cyber Security Act 2024.
Internal Audit vs Independent Review — What Is the Difference?
These two requirements sit alongside each other in ISO 27001:2022 but serve distinct purposes. Conflating them is one of the most common compliance errors we see in ANZ mid-market organisations.
| Internal Audit (Clause 9.2) | Independent Review (Control 5.35) | |
|---|---|---|
| Primary question | Does the ISMS conform to ISO 27001 requirements and the organisation's own requirements? | Is the overall approach to information security still suitable, adequate, and effective for the business? |
| Focus | Conformity with the standard | Strategic effectiveness and fitness for purpose |
| Scope | Specific requirements and controls | Broader ISMS strategy, governance, and operational context |
| Reviewer | Internal auditors or qualified external auditors | Must be independent of the area being reviewed — typically external |
| Output | Non-conformities, observations, and corrective actions | Assessment of strategic direction, identification of improvement opportunities, and management reporting |
Both are required. Neither replaces the other. Source: ISO/IEC 27001:2022 Clause 9.2 and Control 5.35 — iso.org/standard/82875.html
How Insicon Cyber Delivers the Independent Review
Insicon Cyber is an ISO 27001 certified organisation. Our Principal Cyber Consultants have deep experience across regulated sectors in Australia and New Zealand, including financial services, aged care, and healthcare — sectors where the regulatory stakes of an inadequate review are genuinely significant. Reviews are led by practitioners, not analysts, and delivered by the same people who will answer your questions at the end.
Scoping and evidence gathering
We establish the review scope, confirm the ISMS boundary, and gather the documentation and evidence base required to assess all 93 Annex A controls, your risk register, treatment plans, and management review outputs.
Control effectiveness testing
We go beyond document review. We test whether controls are operating as designed, through staff interviews, configuration review, and operational sampling — focused on the areas most likely to reveal the gap between policy and practice.
Regulatory alignment check
For Australian and New Zealand organisations, we map ISMS controls to your applicable regulatory obligations — CPS 234, CPS 230, Privacy Act, NZISM, Essential Eight — and identify where a single control satisfies multiple requirements, and where it does not.
Board-ready findings report
We deliver a written findings report suitable for presentation to your board and audit committee. Findings are rated by severity, linked to corrective action requirements, and expressed in plain language that translates technical risk into business impact.
What makes our review genuinely independent
We have no stake in the controls we are reviewing. We did not design your ISMS. We have no vendor relationship with the platforms it runs on. Our business model is advisory and managed services, not tool sales. That independence is structural, not just declared.
Who Needs an Independent Review
Any organisation holding ISO 27001 certification must satisfy Control 5.35. Beyond the certification requirement, an independent review is relevant to any of the following.
Financial services
APRA-regulated banks, insurers, and superannuation funds managing CPS 234 and CPS 230 obligations. The independent review provides documented evidence for APRA if queried on control effectiveness.
Aged care
Residential and home care providers under the Aged Care Act 2024, which strengthened governance and accountability obligations for providers handling sensitive health and personal data for vulnerable Australians.
Healthcare
Health service providers handling My Health Record data or subject to the My Health Records Act 2012, where the Office of the Australian Information Commissioner actively investigates compliance breaches.
Government suppliers
Australian and New Zealand organisations supplying services to government agencies, where ISO 27001 certification is either mandated or strongly preferred, and where an independent review supports contract retention and renewal.
Organisations pre-certification
Organisations preparing for initial ISO 27001 certification who want an independent assessment of their ISMS before the certification body arrives. An independent pre-audit review closes gaps before they become non-conformities.
Post-incident review
Organisations that have experienced a security incident and need to demonstrate to their board, regulators, or insurers that they have independently assessed what went wrong, why, and what has been corrected.
Frequently Asked Questions
Is A.18.2.1 the same as Control 5.35 in ISO 27001:2022?
Yes. ISO 27001:2022 restructured and renumbered the controls from the 2013 edition. Annex A control A.18.2.1 (Independent Review of Information Security) from the 2013 standard is directly mapped to Control 5.35 in the 2022 standard. The core requirement is the same. The 2022 version adds greater specificity about when ad-hoc reviews are required. If your organisation was certified under the 2013 standard, your transition to ISO 27001:2022 requires confirming that your existing review process meets the 2022 version's additional guidance. Source: iso.org/standard/82875.html
How often does the independent review need to happen?
The standard requires reviews at "planned intervals" and provides no specific minimum frequency. Most certified organisations and their certification bodies treat annual as the practical standard, aligned to the three-year ISO 27001 surveillance cycle. Beyond the annual planned review, the standard explicitly requires ad-hoc reviews when significant changes occur. In the current ANZ environment — with the Cyber Security Act 2024 now in force, CPS 230 effective from 1 July 2025, and frequent APRA and ASIC guidance updates — many organisations should consider whether recent regulatory changes have already triggered this obligation.
Can our internal IT team conduct the independent review?
Only if they are genuinely independent of the area being reviewed. The standard does not mandate an external reviewer, but it requires impartiality. If the team members who would conduct the review were involved in designing, implementing, or operating the controls being assessed, they cannot satisfy the independence requirement. For most mid-market organisations in Australia and New Zealand, an external reviewer is the only practical way to achieve the separation the standard requires.
Does an ISO 27001 independent review satisfy our APRA CPS 234 audit obligations?
A well-structured ISO 27001 Control 5.35 review can satisfy core elements of CPS 234's internal audit requirements, provided the scope covers third-party controls and the reviewer is independent of the controls being assessed. CPS 234 has additional APRA-specific requirements — including 72-hour incident notification obligations and board-level accountability provisions — that sit outside the ISO 27001 scope. We recommend a combined approach that treats the ISO 27001 independent review as the foundation and then maps CPS 234-specific gaps on top of it.
We operate in both Australia and New Zealand. Can one review cover both jurisdictions?
Yes. ISO 27001 controls can be mapped to both Australian (APRA, Privacy Act, Essential Eight) and New Zealand (NZISM, NZ Privacy Act 2020) obligations within a single review scope. Insicon Cyber operates across both jurisdictions and delivers reviews that address trans-Tasman compliance simultaneously. This eliminates the cost and duplication of separate reviews for each market and provides a single, unified evidence trail for both Australian and New Zealand regulators.
What do we receive at the end of the review?
A written independent review report, structured for presentation to your board and audit committee. The report covers: findings against each assessed control, severity ratings, corrective action requirements, improvement recommendations, and a regulatory alignment summary mapping findings to your applicable obligations. Where findings require corrective action, we provide clear guidance on remediation and can support implementation through our Managed Compliance or CISO-as-a-Service engagements.
Ready to Satisfy Control 5.35?
Insicon Cyber delivers independent ISMS reviews for mid-market organisations across Australia and New Zealand. Our reviewers are qualified, experienced, and genuinely independent of the controls they assess.
Contact us to discuss your review scope, timeline, and regulatory context.
Sources
- ISO/IEC 27001:2022 Information Security Management Systems — Requirements. iso.org/standard/82875.html
- APRA Prudential Standard CPS 234 Information Security, July 2019. apra.gov.au
- APRA Prudential Standard CPS 230 Operational Risk Management, effective 1 July 2025. apra.gov.au/operational-risk
- New Zealand Information Security Manual (NZISM), Government Communications Security Bureau. nzism.gcsb.govt.nz
- Privacy Act 1988 (Cth), Australian Government. legislation.gov.au
- Cyber Security Act 2024 (Cth), assented 25 November 2024. legislation.gov.au
- Hicomply — ISO 27001 Annex A Control 5.35 Guide (2022). hicomply.com
- Hightable — ISO 27001 Annex A 5.35 Lead Auditor Implementation Guide. hightable.io
Contact Insicon Cyber
Speak to one of our friendly folks