Guides & Frameworks
ISO 27001 Certification: What It Takes to Pass
Short answer
ISO/IEC 27001 certifies an Information Security Management System (ISMS) built around Annex A controls, risk assessment and continuous improvement. Certification runs through a two-stage external audit - Stage 1 documentation review, Stage 2 implementation audit - followed by annual surveillance audits to maintain it.
ISO/IEC 27001 is the international standard for an Information Security Management System (ISMS). Certification demonstrates to customers, partners and regulators that you run a mature, risk-based security program. This guide explains what certification involves and how to pass on the first attempt.
What is an ISMS?
An ISMS is a documented, risk-based system for managing information security - policies, processes, roles and controls that you continually monitor and improve. ISO 27001 defines the management-system requirements (Clauses 4-10) and references a catalogue of controls (Annex A). The distinction matters: Clauses 4-10 are mandatory for every certified organization, while Annex A controls are selected based on your own risk assessment - you don't implement all 93 of them by default, you justify which apply and which don't.
The 2022 revision of the standard reorganized Annex A into four themes - organizational, people, physical and technological controls - and added several new controls reflecting modern risk, including threat intelligence, cloud security, and data masking. If your reference material still cites the 2013 Annex A structure, it's out of date. The transition window closed on 31 October 2025 - any certificate still issued against ISO/IEC 27001:2013 has since expired or been withdrawn, so the current text is ISO/IEC 27001:2022 with Amendment 1:2024 (the climate-action changes), full stop.
The certification process
- Gap analysis against Clauses 4-10 and Annex A - an honest assessment of what you already have versus what the standard requires
- Risk assessment and risk treatment; author the Statement of Applicability (SoA), the document that explains which Annex A controls apply to you and why
- Implement policies and controls; operate the ISMS long enough to generate real evidence, not just write the policies
- Internal audit and management review (mandatory before certification) - these aren't formalities, they're where you catch non-conformities before an external auditor does
- Stage 1 audit (documentation review) then Stage 2 audit (implementation) by an accredited certification body
- Surveillance audits maintain certification over the 3-year cycle, typically annually
What auditors actually check for during Stage 2
Stage 1 confirms your documentation exists and is internally consistent - policies reference the right clauses, the SoA matches your risk assessment, roles are defined. Stage 2 is where it gets tested against reality: auditors sample evidence that controls are actually operating, not just documented. That means interviewing staff about their actual day-to-day practices, reviewing access logs against your stated access-control policy, and checking whether incidents were handled the way your incident-response procedure says they should be.
The most common Stage 2 failure isn't a missing control - it's a documented control that isn't actually being followed in practice, which auditors usually catch quickly once they start asking staff how something actually works.
How it maps to SOC 2, PCI DSS and DPDP
ISO 27001 is an excellent backbone: it establishes the management system that SOC 2, PCI DSS, DPDP and RBI/SEBI expectations then layer specific requirements on top of. A risk assessment process, an access-control policy, an incident-response procedure - these aren't ISO-specific artifacts, they're exactly what a SOC 2 auditor or a PCI DSS QSA will also ask to see, just mapped to a different framework's language.
Building the ISMS first makes every subsequent compliance easier and cheaper - organizations that pursue SOC 2 and ISO 27001 as two completely separate projects typically duplicate a large share of the underlying work.
Passing first time
- Scope tightly - don't over-scope the ISMS to cover systems or locations that don't need to be in scope, which only adds audit surface with no compliance benefit
- Make risk treatment real, not paperwork - a risk register that was filled out once and never revisited is exactly what an auditor is trained to spot
- Run a genuine internal audit and fix non-conformities before Stage 2, rather than hoping the external auditor doesn't find what your own internal audit already should have
- Keep evidence continuously, not in a pre-audit scramble - logs, meeting minutes, training records and incident reports accumulated as a byproduct of actually running the ISMS, not reconstructed the week before the audit
Need help with this in practice?
A5 Cyber Nexus audits, remediates and documents conformance against these frameworks.
Frequently asked questions
How long does ISO 27001 certification take?
Typically 4-6 months from kickoff to Stage 2, depending on scope, maturity and resourcing. We run the gap analysis, build the ISMS, and prepare you so the certification audit holds no surprises.
Who issues the certificate?
An independent, accredited certification body issues the certificate after a successful Stage 2 audit. We prepare you and liaise with them; we don't issue the certificate ourselves.
What's the difference between the 2013 and 2022 versions of the standard?
The 2022 revision reorganized Annex A into four themes and added controls for areas like threat intelligence, cloud security and data masking that weren't explicitly addressed in 2013 - organizations certified under 2013 had a transition deadline to move to the 2022 control set.
Make it accessible.
Make it attack-ready.
Prove both before launch.
Bring us your app, audit deadline, or security concern. We'll map the fastest path to WCAG conformance, VAPT coverage, and regulator-ready evidence.
