What Is ISO 27001 Certification: A Plain-English Guide
ISO/IEC 27001 is the international standard for an information security management system (ISMS), and certification is an independent audit that confirms a company runs one. The current edition was published in October 2022, it replaced the 2013 version, and it works from a catalogue of 93 reference controls rather than a fixed list of products you have to buy.
The advice you'll hear most often is to ask a vendor for their certificate and tick the box. That's half a test. The other half is what ISO 27001 certification covers, and that answer lives in a paragraph on the certificate most buyers never read: the scope.
Ask for the certificate by all means. Read the scope statement before you read the logo.
What ISO 27001 certification actually means
The National Standards Authority of Ireland's ISO/IEC 27001 overview frames it as a management system built around assessing and treating information security risk. It isn't a check that the organisation happens to own particular security products.
The analogy I keep coming back to is a food hygiene rating. The inspector doesn't grade one clean plate on the morning of the visit. They look at how the kitchen runs: who owns the temperature log, whether staff know what to do when something goes wrong, whether the place has a habit of keeping itself in order. Five stars doesn't promise your dinner is safe tonight. It tells you there's a system, and that someone independent has tested it.
Swap the kitchen for software and the parts line up. A certified company has to show a defined scope, identified information security risks, controls chosen through a documented risk-treatment process, named owners, performance monitoring, internal audits and evidence of continual improvement.
What the certificate proves is that an independent auditor tested how you decide what security you need, and whether you do it. What it leaves out is everything outside the scope.
The line the certificate stops at
It's issued by a certification body, ideally an accredited one, and the current version is the 2022 edition, so a certificate still citing the 2013 standard is worth questioning. Beyond that, certification isn't a promise that no breach will ever happen and it isn't a product badge. Those are different claims, and mixing them up is how security pages end up overstating what a piece of paper says.
What the certificate covers and what it doesn't
Almost every security questionnaire has a tick box for ISO 27001 and a free-text field nobody fills in. The tick box is the problem. Certification applies to the ISMS inside a declared scope, not to the whole company by default, and that scope is written down for anyone who asks.
The question most buyers mean when they search for what ISO 27001 certification is, is narrower: does this certificate cover the thing I'm buying?
For a hosted document platform, a credible scope usually names the application, the cloud infrastructure behind it, identity and access management, encryption key handling, logging and monitoring, incident response, backups and recovery, supplier management, and the privacy processes around customer data. The list of things that can sit outside is just as long: a separate product line, a marketing site, an office, an unrelated subsidiary, a legacy tool nobody has migrated off yet.
Say a document platform certifies its hosted application and the support operation that runs it, but not a consumer app it launched later. The certificate stands for the hosted service. It says nothing about the consumer app, and a buyer who reads only the badge will assume otherwise.
That gap is where real risk sits, because document uploads, viewer analytics, email capture and subprocessors are either inside the scope or they aren't. There's no partial credit.
- The scope statement: does it name the systems and services you're buying, in words, rather than broad categories?
- The Statement of Applicability: the control-by-control record of what the ISMS covers, and why anything is excluded.
- The validity dates: issue date, expiry, and whether surveillance audits are current.
None of that adds up to a guarantee of zero incidents, and it isn't compliance with every privacy law either. It's a tested answer to a much narrower question.
How the certification process runs, step by step
Work backwards from the audit and the order becomes obvious. Nothing in the process rewards writing policies first and working out the risks later, but that's the sequence most first-timers follow, and Stage 2 is where it shows.
- Define the scope in writing. Which processes, locations, systems and information assets are in, and which are out. This decision shapes everything downstream, including how many audit days you end up paying for.
- Run the risk assessment. Threats, vulnerabilities, likelihood and business impact, per asset or per process. It's a working document rather than a formality, because the next step depends entirely on it.
- Decide the treatments and write the Statement of Applicability. For each control: applicable or not, the reason, the status, and ideally where the evidence lives. Exclusions are allowed. Unexplained exclusions aren't.
- Build the management system around it. Policies, named owners, staff training, internal audits, and a management review with senior people in the room.
- Choose an accredited certification body and agree a timeline. Kiwa's guide to getting ISO 27001 certified describes the shape of it: a two-stage assessment, then a three-year cycle with two surveillance audits and a recertification audit.
- Stage 1. The auditor reads your documentation, checks the scope, and forms a view on readiness. Treat the findings as a to-do list rather than a verdict.
- Close the gaps, then Stage 2. The auditor tests whether controls operate in practice. Can the team show you the access review, the restore test, the incident log?
- Certificate, then maintenance. Surveillance audits in years one and two, recertification in year three, and a certification body that can suspend the certificate when serious nonconformities sit uncorrected.
| Stage | What happens | Timing |
|---|---|---|
| Stage 1 | Documentation, scope and readiness review | Before Stage 2 |
| Stage 2 | Testing whether controls operate in practice | After gaps are closed |
| Surveillance | Check that the system is still running | Years one and two |
| Recertification | Full reassessment before the certificate renews | Year three |
The trap that sinks Stage 2 is a policy nobody follows. If your written rule says access is reviewed quarterly and the last review was fourteen months ago, the auditor will find it, because they ask for the evidence rather than the document.
Your first action isn't a tool or a template. Write the scope in a paragraph, then list which of the required documents already exist in some form.
The controls and evidence auditors actually check
The document that decides your audit isn't the risk register. It's the Statement of Applicability, because it's the only place where your risk analysis and your actual controls meet.
The 2022 edition's Annex A sets out 93 reference controls grouped into organisational, people, physical and technological themes, as IBM's ISO 27001 compliance overview sets out. Read that as a catalogue, not a checklist. You aren't expected to implement all of them. You're expected to justify which ones you use and which you don't.
Every SoA entry needs four things: the control, whether it applies, the reason, and whether it's implemented. Noting where the evidence lives is not a formal requirement, but it makes the audit far smoother. The reason is where weak applications fall apart. Marking a control "not applicable" with no explanation is the fastest way to buy yourself an extra day of audit.
Take a fully cloud-hosted document platform with no server room of its own. Physical controls don't simply disappear. If they're necessary to your ISMS, they stay in the SoA even when the hosting provider performs them, with the provider's controls and the contract that backs them as the evidence. Only controls that aren't necessary at all, such as protection for a server room you don't have, can be excluded, and you say why. Encryption key management and logging stay firmly in scope, because those are yours whether or not someone else runs the building.
What the auditor will ask to see:
- Policies, signed and dated, matching how the work happens
- Risk assessments, current, with treatment decisions recorded
- Training and competence records for the people who touch the system
- Access reviews, showing joiners, movers and leavers handled properly
- Incident logs and the actions taken afterwards
- Backup restore tests, not just backups
- Supplier reviews covering subprocessors
- Internal audit results, management review minutes and corrective actions
Practical rule: a tidy policy proves nothing. Auditors test consistency over time, so a folder of documents with no activity behind them raises more questions than an honest gap with a plan attached.
External sharing is a control too, and one auditors increasingly probe. Secure file sharing for business covers the practical side, from link permissions to what happens when a recipient forwards something they shouldn't.
Build the evidence folder with one subfolder per SoA entry before the audit, not during it.
How ISO 27001 fits alongside SOC 2, GDPR and other frameworks
| Framework | What it is | How you prove it | Typical fit |
|---|---|---|---|
| ISO/IEC 27001 | Management standard for an information security management system | Accredited certificate after an independent audit | Organisations wanting a certifiable, international benchmark |
| ISO/IEC 27002 | Guidance on implementing the controls in ISO 27001 | Not certifiable, used as a reference | Teams building the controls behind ISO 27001 |
| SOC 2 | AICPA attestation over the trust services criteria | CPA firm issues an examination report | US-focused SaaS and service providers answering enterprise security reviews |
| GDPR and UK GDPR | Data protection law for personal data | Certification is voluntary and limited to specified processing under approved schemes; otherwise proven through accountability records and regulator oversight | Any business whose processing falls under UK or EU rules |
| HIPAA | US law covering protected health information | No certificate, proven through documented safeguards and self-assessment | Healthcare providers and their business associates |
| Cyber Essentials | UK government-backed baseline security scheme | Self-assessment independently marked before certification; Cyber Essentials Plus adds independent technical testing | UK organisations needing a cost-effective baseline |
Here's the practical reading, which most comparison posts skip because it's less tidy than a matrix.
ISO 27001 is a management certification. SOC 2 is an attestation report. One says an accredited body audited your system and issued a certificate. The other says a CPA firm examined your controls against the trust services criteria and wrote a report. A Type 1 report covers controls at a single date; a Type 2 report covers how they operated over a review period. US enterprise buyers often ask for SOC 2 by name, and the overlap in control areas means most vendors reuse one evidence set for both.
GDPR and UK GDPR are law, not certificates. An ISMS supports the accountability principle and gives you something concrete to point at, but it doesn't cover lawful basis, data subject rights or impact assessments on its own. Run privacy as its own workstream with its own owner; our GDPR security page covers how we handle that side.
HIPAA is a US law about protected health information. A healthcare buyer still needs its own safeguards and business associate terms, and no ISO certificate stands in for those.
Cyber Essentials is the UK government-backed baseline, and for a small firm selling into UK public sector procurement it's a sensible first step before the far larger ISMS project.
Privacy law doesn't ask whether you hold a certificate. It asks what you did with personal data and whether you can show your reasoning.
My view, stated plainly: go for ISO 27001 when you need a certificate that travels internationally, go for SOC 2 when your pipeline is US enterprise, and run privacy law as a separate track either way.
ISO 27001 certification is generally voluntary, though a regulator or a contract can require it. GDPR applies to you if you process personal data in the context of an EU or UK establishment, or if you target or monitor people there from outside, certificate or not. So the honest question isn't just whether you need ISO 27001, it's whether your buyers, your regulators or your contracts are asking loudly enough to pay for it.
Why document-sharing vendors pursue it, and the real cost
The certificate's value depends on what it covers. For document-sharing vendors, buyers should care whether the certified management system includes the services they plan to use, not just whether the vendor holds a certificate.
The 2025 ISO Survey recorded 125,622 valid accredited ISO/IEC 27001 certificates covering 226,262 sites as of December 2025, according to HEIC's write-up of the ISO Survey results. HEIC is a consultancy summarising ISO's own data. Those figures count certificates and sites rather than unique companies, so they show broad recognition of the standard, not how many businesses are certified. The same table puts the United Kingdom at 7,929 certificates.
A certificate can answer a recurring set of questions in enterprise security reviews and give legal and procurement teams a shared vocabulary. The work behind it also forces the company to document how security decisions are made, rather than leaving them informal.
The cost is mostly operational:
- Staff time from engineering, operations and whoever owns security, spread over months rather than weeks
- A named internal owner with the authority to coordinate work across departments
- Tooling to collect and refresh evidence without a manual scramble each quarter
- Audit fees to an accredited body, plus surveillance audits to maintain certification
The total varies with scope, headcount and how much of the required work is already in place.
The sequencing question: scope narrowly around the product customers actually use, run it for a year, then widen. A tight scope you can evidence beats a broad scope you can't.
Certification doesn't eliminate questionnaires or privacy reviews. It can shorten the security review, but buyers still need to check that the certificate's scope covers the service they're purchasing. Before committing, ask whether it could win or speed up deals that are currently delayed or lost.
Check the certificate before you trust a vendor
A certificate is a claim about a defined scope and a managed process. Check the scope statement first: it shows which services and activities the certification covers, and what falls outside it.
Ask the vendor for six things, in this order:
- The certificate itself. Request the document, with its certificate number and the certification body's name.
- The scope statement. Check that it covers the service you plan to use. For a document-sharing tool, look for the relevant service and the activities that support it.
- The edition. ISO/IEC 27001:2022 is the current edition. If a certificate cites the 2013 standard, ask the vendor to explain its status.
- The certification body and its accreditation. UKAS explains that accreditation demonstrates a certification body's technical competence to audit and certify against applicable standards. In the UK, only certificates issued by UKAS-accredited bodies carry the UKAS symbol. The phrase "ISO 27001 certified" doesn't tell you who conducted the assessment.
- Validity dates and surveillance status. Ask for the dates and confirm the certificate is current.
- The Statement of Applicability, or a summary. It describes the controls selected for the organisation's ISMS. If the vendor can't provide it or a summary, ask why.
Then ask about incident response, subprocessors, data retention and privacy terms. A certificate doesn't settle those on its own.
We list ISO 27001 and SOC 2 Type II on our security page, and I'd expect you to ask us for the certificate and its scope just like anyone else. Each credential supports a different assurance claim; one doesn't automatically establish the others.
Send these questions before signing, and keep them handy when reviewing your own certificate. Your buyers will want to know what your scope covers, too.
About the Author
Cameron JamesCameron is the founder of LiveDocument. He writes about sharing documents, PDFs, decks and contracts, and why pairing a video walkthrough with a document beats sending it cold.