In this lesson
After this lesson you can:
- State precisely what an ISO 27001 certificate asserts, and what it leaves open.
- Read a supplier’s certificate for its scope rather than its logo, and ask for the right additional evidence.
- Present your own certificate accurately, so a customer never discovers a gap you could have named.
Read first: What ISO 27001 is and what accreditation adds
Start with what it does certify.
The limits only make sense against the claim, and the claim is narrower than most buyers read it as. An ISO 27001 certificate says that an accredited certification body examined an information security management system, found it conformant with the standard, and that the system covers the activities described in the scope statement. The examination is conducted by sampling, which ISO/IEC 17021-1 sets as the basis of audit evidence, and every limit further down this page follows from those two words: sampling, and scope.
Unpack management system, because that is the load-bearing phrase. It means the organisation has a defined way of understanding its context, deciding what it is protecting, assessing risk against its own criteria, selecting and operating controls, training people, measuring whether any of it works, auditing itself, reviewing the results at senior level, and correcting what it finds. That is a real and useful thing to have established about a supplier. It is a statement about process capability.
What it is not is a statement about the current security condition of any system. Those are different kinds of claim, and conflating them is the source of nearly every disappointment people have with the standard.
| Proposition | Does the certificate establish it? | Why |
|---|---|---|
| A management system for information security exists and operates | Yes, this is the claim | Inside the declared scope only. |
| Risks were identified, assessed and treated by a defined method | Yes | Your method, your acceptance criteria. |
| The organisation audits and reviews itself | Yes | Clause 9 is much of what is examined. |
| Your product or application is secure | No | No product is tested. The system is examined. |
| Your code was reviewed or your systems tested | No | The auditor samples evidence, not vulnerabilities. |
| You comply with a data protection law | No | Different subject matter and different duties. |
| Controls operated throughout a historical period | No | That is what a SOC 2 Type 2 reports. |
| You will not suffer a breach | No | No standard makes that claim, and none can. |
The scope statement is the whole boundary.
If you remember one thing, remember this. Everything a certificate asserts is bounded by its scope statement, and the scope statement is written by the certified organisation.
Clause 4.3 requires an organisation to determine the boundaries and applicability of its ISMS, and gives it latitude in doing so. That latitude is legitimate and it is also the most common gap between what a certificate says and what a buyer assumes. A scope can name one legal entity in a group, one office, one product line, or the corporate IT function while excluding the production platform your data would actually live on.
None of those is deceptive. Each is published on the face of the certificate. The failure is a reading failure, and it happens because procurement checks whether a certificate exists and is current rather than what it covers. Read the scope statement first, then the dates, then the accreditation mark.
It is not a security score.
There is no grade. A certificate is binary, and two certified organisations may be in very different security conditions while both being fully conformant.
The mechanism that allows this is risk acceptance, and it is a feature rather than a loophole. Clause 6.1 requires you to assess risk against criteria you set and to decide how to treat each one, and accepting a risk is a valid treatment. So an organisation can identify a significant weakness, document it, have the right person accept it with reasons, and be conformant. The standard asks whether you decided deliberately, not whether you decided the way a third party would have.
This is why a certificate tells you about decision-making quality rather than control strength, and why a buyer who needs to know about control strength has to ask a different question.
It is not a penetration test.
An ISO 27001 auditor examines whether your management system operates. They do not attack your infrastructure, read your source code, or run a scanner. They sample evidence and interview people, which means an exploitable vulnerability can sit inside a certified environment without the audit being deficient.
The standard does require you to manage technical vulnerabilities, and for most organisations testing is how that requirement gets evidenced. So testing is usually necessary in practice while not being a prescribed certification activity with a mandated frequency, which is a distinction worth getting right in both directions. Whether ISO 27001 requires penetration testing sets out what the standard actually asks for.
For a buyer, the practical consequence is simple. If you need assurance about the security of a specific application, ask for a test report with a date and a scope. The certificate is not a substitute and was never meant to be.
It is not privacy law compliance.
This is the most consequential confusion, because it has legal rather than commercial outcomes.
A data protection law governs whether you may process personal data at all: on what basis, with what notice, for what purpose, for how long, with what rights for the individual, and with what duties when something goes wrong. ISO 27001 governs how you manage information security risk. The two meet on safeguards, and only on safeguards.
So a certified organisation can be comprehensively non-compliant with a privacy law while holding a perfectly valid certificate, because nothing in the audit examined lawful basis, notice content, consent mechanics, retention justification or how it handles a rights request. Our gap table for the DPDP Act sets out line by line what the standard does and does not reach, and the same shape applies to other privacy regimes.
If you are answering a customer questionnaire, do not attach the certificate against a data protection question. It is not a wrong document so much as an answer to a different question, and the mismatch is usually noticed.
It is not a SOC 2, and cannot be read as one.
These are different instruments from different traditions, and the difference that matters most is temporal. An ISO 27001 certificate says a system was found conformant at a point in time and is maintained under surveillance. A SOC 2 Type 2 report says named controls were tested and operated throughout a defined historical period, and it includes the detail of what was tested and what exceptions were found.
So a buyer who wants to know what your controls are and how they performed is asking for something the certificate structurally cannot provide, however valid it is. Conversely a buyer who wants evidence of a managed, internationally recognised system gets that from the certificate more cleanly than from a report. Which one to do first covers the sequencing decision, and it is decided by which deal is blocked rather than by which instrument is better.
It is not a promise you will not be breached.
Certified organisations suffer incidents. This is not evidence that the standard failed, and treating it that way misunderstands what any management system can do.
The standard’s own logic assumes incidents will happen. That is why it requires incident management, event reporting, learning from incidents, evidence collection and continuity planning as controls in their own right. An organisation that has never had an incident has not been tested, and an auditor reads a clean history with more suspicion than a well-handled incident.
What a buyer can reasonably infer from a certificate is that the organisation is more likely to notice an incident, respond in a defined way, and act on what it learns. That is worth having. It is not immunity, and nobody should present it as such.
If you are the buyer: what to ask for instead.
Match the evidence to the question. The certificate answers one of these, and the others each have their own document.
- Is there a managed security function? The certificate, read with its scope statement.
- Does it cover the service I am buying? The scope statement, checked against the entity and systems behind the service.
- How did specific controls perform over time? A SOC 2 Type 2 report, or your own questionnaire.
- Is this application secure? A penetration test report, with date and scope.
- Do they comply with data protection law? A data processing agreement, their privacy documentation, and specific answers.
- What happens when something goes wrong? Their incident response commitments and notification timelines, in the contract.
- Is the certificate real and current? The accreditation body’s directory and the certification body’s register.
Verifying a certificate covers item seven in detail.
If you hold one: how to present it honestly.
The commercial advice here is the same as the ethical advice, which is convenient. Describe the certificate accurately, because every overstatement is a landmine with your name on it.
Three habits worth adopting:
- Quote your scope statement when you cite the certificate, rather than saying only that you are ISO 27001 certified. If the scope does not cover what a customer is buying, say so before they find out.
- Never answer a question the certificate does not answer by attaching the certificate. Answer the question, then attach the certificate where it is relevant.
- If your scope is narrower than you would like, treat widening it as a roadmap item with a date rather than a thing to be vague about. Buyers are far more comfortable with a stated limit and a plan than with a discovered one.
A supplier who volunteers the limits of their own certificate is doing something unusual, and the unusual part reads as confidence. That is a better position than the one you occupy after a procurement team finds the gap for you.
Not sure what your certificate covers?
Send us the certificate and scope statement and tell us what your buyers are asking. We will tell you what it genuinely answers, where the gaps are, and whether widening the scope or adding a different instrument is the cheaper fix.
Key takeaways.
- The certificate asserts that a management system for information security exists and operates inside the scope on its face, as examined by sampling. That is the whole claim.
- The scope statement is the boundary, it is written by the certified organisation, and reading it first prevents most misunderstandings.
- There is no grade. Risk acceptance is a valid treatment, so two conformant organisations can be in very different security conditions.
- No product is tested and no code is read. For assurance about a specific application, ask for a test report with a date and a scope.
- Privacy law compliance is a different subject. A certified organisation can be non-compliant with a data protection law and still hold a valid certificate.
- A SOC 2 Type 2 reports on named controls across a past period. A certificate cannot do that, however valid it is.
- Certified organisations have incidents, and the standard assumes it. A spotless history reads as untested rather than safe.
- Stating the limits of your own certificate before a customer finds them is both the honest move and the stronger commercial one.
Quick check.
A supplier holds a valid, accredited ISO 27001 certificate. What has an independent body established?
- That the supplier’s product is secure
- That a management system for information security operates within a declared scope
- That the supplier has had no security incidents
- That the supplier complies with applicable data protection law
Check the answer
B. The certificate attests to the management system inside the scope statement, examined by sampling. It makes no claim about product security, incident history or legal compliance, each of which is a different subject with different evidence. ISO/IEC 17021-1
Which document tells you the real limits of any ISO 27001 certificate?
- The expiry date
- The certification body’s name
- The scope statement
- The accreditation mark
Check the answer
C. The scope statement defines what was examined. The expiry date tells you whether it is current and the accreditation mark tells you whether it counts, and neither tells you what it covers. Clause 4.3, determining the scope of the ISMS
Spot the mistake. A company answers a customer questionnaire item on data protection compliance by attaching its ISO 27001 certificate.
Check the answer
It answers a legal question with a security management answer.. Data protection compliance concerns lawful basis, notices, individual rights and specific statutory duties. ISO 27001 governs information security risk management. Attaching the certificate is not a lie and it does not answer the question, which is how the gap gets discovered later. Does ISO 27001 cover the DPDP Act?
Sources.
- ISO/IEC 17021-1, requirements for bodies providing audit and certification of management systemsISO catalogue entry 61651Used here: That certification rests on sampling within a defined scope, which is the source of every limit on this page
- ISO/IEC 27001:2022, Clause 4.3, determining the scope of the ISMSOur clause reference page, which carries the requirementUsed here: That the scope statement is the boundary of what a certificate asserts
- ISO/IEC 27001:2022, Clause 6.1, actions to address risks and opportunitiesOur clause reference page, which carries the requirementUsed here: That an organisation sets its own risk acceptance criteria, so an accepted risk is conformant
- Does ISO 27001 cover the DPDP Act? The gap tableOur own reference page, maintained against the Act and its RulesUsed here: The privacy-law section, and where the overlap genuinely is
Last checked against ISO’s catalogue entry for ISO/IEC 17021-1 and our own clause and gap-table reference pages on 9 November 2026.