ISO information security standards are the ISO/IEC 27000 family: a set of international standards that describe how a company should protect its information and how to prove it. The core standard is ISO 27001, the only one in the family you can certify against. The others, such as 27002, 27005, 27017, 27018 and 27701, are guides that explain how to meet it in a specific area: controls, risk, cloud or personal data.
The confusion is common because they all start the same way and show up together in customer and insurer questionnaires. In this guide we explain what each one covers, which ones are certifiable, who is likely to ask you for them and how to tell which one your company needs.
What the ISO 27000 family is
ISO is the International Organization for Standardization, and the 27000 series is the one it dedicates to information security. The family contains two kinds of documents that are worth keeping apart:
The requirements standard. That is ISO 27001. It defines what a company must have in place to manage its security: policies, risk assessment, controls, reviews and continual improvement. Put together, all of that is called an ISMS, an information security management system. It is the only one a certification body audits and backs with a certificate.
The guides. These are all the others. You cannot be certified against them: they explain how to meet the 27001 requirements on a specific topic. 27002 details the controls, 27005 covers risk management, 27017 and 27018 cover the cloud, and 27701 covers personal data. When an auditor reviews your ISMS, they lean on these guides to judge whether you did it right.
ISO 27000 itself (with no suffix) is a vocabulary document: it defines the terms the other standards use. So when someone says "we are ISO 27000 certified," what they really mean is 27001.
The 7 ISO security standards that matter
Of the more than 40 standards in the family, these are the ones that appear in questionnaires from customers, insurers and auditors:
| Standard | What it covers | Certifiable? | Who asks for it |
|---|---|---|---|
| ISO 27001 | The full management system: policies, risks, controls and continual improvement. | Yes, it is the only certifiable standard in the family. | Corporate customers, banks, insurers and public tenders. |
| ISO 27002 | The catalog of security controls, with guidance on how to implement each one. | No. It is the guide to the 27001 controls. | Auditors and consultants, as a technical reference. |
| ISO 27005 | How to identify, analyze and treat information security risks. | No. | The 27001 auditor, who reviews your risk assessment. |
| ISO 27017 | Security controls for cloud services, for both the provider and the customer. | No, although cloud providers publish attestations against it. | Customers who want evidence of how you protect what you keep in the cloud. |
| ISO 27018 | Protection of personal data processed in the cloud. | No. | Customers and data protection regulators. |
| ISO 27701 | An extension of 27001 for privacy management: how to handle personal data. | Yes, as an extension of a 27001 certificate. | European customers and companies that handle data on many people. |
| ISO 27032 | Cybersecurity guidelines: how information, network, internet and application security relate to each other. | No. | Almost nobody directly; it works as a reference framework. |
Left off the list, but part of the same family, are standards that only appear in specific sectors, such as 27011 for telecommunications or 27799 for healthcare. And one is often confused with 27001 even though it is not in the family: TISAX, the security assessment required by the German automotive industry.
ISO 27001, 27002 and 27005: the trio everyone mixes up
All three are cited together in any certification project, which is why they get confused. Each one answers a different question:
ISO 27001: what do I need to have?
It is the list of requirements. It asks you to define the scope of your system, secure leadership commitment, run a risk assessment, choose controls to treat those risks, measure results and keep improving. Its Annex A lists the available controls, but it only names them and does not explain how to implement them. What certification involves, how long it takes and what it costs are covered in our ISO 27001 certification guide.
ISO 27002: how do I implement each control?
It takes the Annex A controls and develops them one by one: purpose, how to apply it and what evidence it leaves. In its 2022 version, ISO 27002 brings together 93 controls grouped into four themes: organizational, people, physical and technological. It is the working document for the team that has to carry out the project.
ISO 27005: how do I decide which controls I need?
27001 requires a risk assessment but does not say how to do it. 27005 does: how to identify assets, threats and vulnerabilities, how to estimate likelihood and impact, and how to decide which risks you treat, accept or transfer. It is the standard that turns security into business decisions backed by numbers.
In short: 27005 tells you which risks you have, 27002 tells you how to close them and 27001 certifies that the whole system works.
The ones that came with the cloud and personal data
Three newer standards in the family respond to the two changes that affect companies most today: information no longer lives in the office, and personal data laws now have teeth.
ISO 27017 adapts the 27002 controls to the cloud and adds the ones that were missing: who is responsible for what between provider and customer, how data from different customers is kept separate on the same server, and what happens to your information when you cancel the contract. The large cloud providers publish attestations against it; what almost nobody reviews is the part that falls on the customer.
ISO 27018 focuses on personal data processed in the cloud: consent, transparency about where data is stored, what the provider does if an authority requests access and how data is deleted when the service ends. It is the standard that answers the question "does my cloud provider comply with data protection rules?"
ISO 27701 is the most complete of the three: it extends 27001 with a privacy management system. It sets different obligations for whoever decides how data is used (the controller) and whoever processes it on their behalf (the processor), and it can be certified together with 27001. Its main value is giving you a structured, auditable way to show how you handle personal data, beyond simply saying you follow the law.
Outside the family: ISO 22301, PCI DSS, SOC 2 and privacy and sector regulations
The same questionnaire that asks for 27001 often lists other names that are not ISO security standards, or are not ISO at all. It helps to know where each one comes from:
| Standard or regulation | What it is | Who requires it |
|---|---|---|
| ISO 22301 | The ISO standard for business continuity: how to keep operating through a disruption. Certifiable, but not part of the 27000 family. | Customers who depend on your operation; banks and insurers with their critical suppliers. |
| PCI DSS | The card brands' standard for anyone who stores, processes or transmits payment card data. It is not an ISO standard. | Acquiring banks and the card brands, for any business that accepts card payments. |
| SOC 2 | A US audit report on a service provider's controls. It is a report, so it is neither a certificate nor an ISO standard. | US customers and technology companies that buy software or services. |
| Privacy laws (CCPA/CPRA, GDPR) | Laws that require companies to protect the personal data of customers and employees, such as California's privacy law or the European GDPR. | Any company that handles personal data covered by them; ISO 27701 helps show compliance. |
| GLBA Safeguards Rule | The US rule that requires financial institutions to protect customer information, which also reaches the technology vendors that serve them. | Banks, lenders, fintech companies and their IT service providers. |
| HIPAA | The US law that protects health information. | Healthcare providers, health insurers and the vendors that handle patient data for them. |
The good news is that almost all of them rely on the same controls. A company with a well-built ISO 27001 ISMS is already 60% to 80% of the way to PCI DSS or SOC 2; what changes is the evidence each auditor wants to see.
How to know which one your company needs
Nobody needs all seven. The choice comes down to four questions:
- Who is asking for it, and in what document? If it is a customer questionnaire, ISO 27001 is almost always accepted as an answer; if it is an acquiring bank, it will be PCI DSS; if it is a US customer, SOC 2. Start with what you are already being asked for.
- Do you handle personal data on many people? If your business runs on end-customer data, 27701 gives you the structure to comply with privacy laws and prove it.
- Does your information live in the cloud? Then 27017 and 27018 tell you what to check with your provider and what is on you. Certifying against them is unnecessary; applying them is what counts.
- Do you need the certificate, or do you need the controls? Certification takes time and money and is only worth it if someone is going to ask for it. Many companies get what they need by applying 27002 without certifying, and move to 27001 when a contract requires it.
Take an 80-person accounting firm that receives a security questionnaire from a banking client and finds three requirements: an ISO 27001 certificate, evidence of compliance with privacy law and controls aligned with the GLBA Safeguards Rule for vendors. The answer is not three projects but one: an ISMS under 27001 with the 27701 privacy extension, whose evidence covers all three. What the firm does need from day one is for every security action to be recorded, because all three auditors will ask for the same thing: proof.
That is where day-to-day operations matter more than the paperwork. In TecnetSOC Agentic, our agentic managed security operations service, every action is logged the moment it happens and the platform generates the evidence for ISO 27001 and SOC 2. And we run it under the same standards we help you meet: TecnetOne is ISO 27001 certified.
Frequently asked questions about ISO security standards
ISO is the International Organization for Standardization, and 27000 is the number of the series it dedicates to information security. The ISO 27000 standard itself is the family's vocabulary document; the one you get certified against is ISO 27001.
No. In the whole family, only ISO 27001 and, as an extension of it, ISO 27701 are certifiable. The others (27002, 27005, 27017, 27018, 27032) are guides you apply but that are not audited separately. If a vendor claims to be "ISO 27000 certified," ask for the certificate: it should say 27001.
27001 states what your management system must include and is certifiable; 27002 explains how to implement each of its controls and is not. One is the list of requirements and the other is the manual for meeting them.
Between six and twelve months for a midsize company, depending on how far it is from the requirements at the start. The certificate is valid for three years, with surveillance audits every year. We cover the steps and costs in our ISO 27001 certification guide.
It helps a lot, but it is not the same thing. Privacy laws require security measures for personal data, and 27001 is the most widely recognized way to show you have them. To cover privacy-specific matters, such as consent and individuals' rights, there is the ISO 27701 extension.
A consultant helps you design the system and prepare for the audit, and a security operations service helps you sustain it every day with evidence. That is how TecnetSOC Agentic works: it runs your security operations and produces the compliance evidence auditors ask for.