Security standards cheat sheet: ISO 27001, NIS2, SOC 2 & co.
Every customer questionnaire, tender or audit seems to throw a different acronym at you. ISO 27001, NIS2, SOC 2, IEC 62443, PCI DSS… 🤯
They all sound alike, but they aim at different things, apply to different industries and have very different teeth: some are law, some are contracts, some are “voluntary” until your biggest customer asks for them.
For each one: what it is, who has to implement it and who actually asks for it. Plus two historic ones that still pop up in old docs.
ISO/IEC 27001
The best-known standard for building, running and continuously improving an Information Security Management System (ISMS). It covers people, processes and technology: risk management, policies, physical security, access control. The current version is ISO/IEC 27001:2022, with 93 controls in Annex A.
It’s certifiable. A certificate is valid for three years, with surveillance audits every year in between.
- Who implements it - organizations of any size and industry: startups, IT service providers, banks, public authorities, large corporations.
- Who asks for it - B2B customers, as a prerequisite in contracts and tenders (vendor due diligence). And management, to show they take their duty of care seriously.
NIS2
Not a standard but EU law: Directive (EU) 2022/2555. It requires risk management measures, a fixed incident reporting process and makes management accountable: the management body has to approve and oversee the security measures and can be held liable for violations.
The reporting deadlines are tight:
- 24 hours - early warning after becoming aware of a significant incident
- 72 hours - incident notification with a first assessment
- 1 month - final report
Being a directive, it has to be transposed into national law. In Germany that’s the NIS2 Implementation Act (NIS2UmsuCG), which amends the BSI Act. Affected companies have to register with the BSI themselves.
Fines go up to €10M or 2% of global annual turnover for essential entities and €7M or 1.4% for important entities.
- Who implements it - medium and large companies (roughly 50+ employees or more than €10M turnover) in critical and important sectors: energy, transport, banking, health, digital infrastructure, public administration, but also manufacturing, food production and more. Some entities like DNS providers or trust service providers are in scope regardless of size.
- Who asks for it - the EU and the national authorities, in Germany the BSI (Federal Office for Information Security). Compliance is supervised by the state.
SOC 2
A US audit framework by the AICPA, built for service providers, cloud and SaaS companies. It’s based on the Trust Services Criteria: Security, Availability, Processing Integrity, Confidentiality and Privacy. Security is mandatory, the others are picked depending on the service.
The result is not a certificate but an attestation report signed by a licensed CPA firm. There are two flavors:
- Type I - are the controls designed properly at a given point in time?
- Type II - did the controls actually work over a period, usually 6-12 months?
Enterprise customers usually want Type II.
- Who implements it - SaaS vendors, cloud and hosting providers, data centers, managed service providers, especially with US or international customers.
- Who asks for it - enterprise customers. Before a corporation puts its data into your cloud software, it will almost always ask for a current SOC 2 report.
IEC 62443
Classic IT standards are about office PCs and servers. IEC 62443 is about Operational Technology (OT): industrial control systems (ICS), PLCs, factory robots, power plants, industrial IoT. It covers the whole lifecycle of plants, components and their integration.
It’s a whole series of documents, a few of the important parts:
- 62443-2-1 - security program for asset owners
- 62443-3-3 - system requirements and the Security Levels SL 1-4
- 62443-4-1 - secure development lifecycle for product suppliers
- 62443-4-2 - technical requirements for components
Products and processes can be certified (e.g. via ISASecure or testing bodies like TÜV).
- Who implements it - asset owners (utilities, chemical plants, car factories), system integrators and manufacturers (OEMs) that need to build their controllers and devices “cybersecurity-ready”.
- Who asks for it - industrial customers and operators of critical infrastructure (KRITIS), who need to make sure a machine doesn’t become the entry point for ransomware on the production floor. The EU Cyber Resilience Act will add more pressure on manufacturers here.
PCI DSS
The Payment Card Industry Data Security Standard. A strict, industry-specific standard for protecting card data, with very concrete technical and organizational requirements on how the card number (PAN) may be stored, processed and transmitted. Sensitive authentication data like the CVV/CVC, full magnetic stripe data or PINs must never be stored after authorization.
The current version is PCI DSS 4.0.1. The “future-dated” requirements of v4.0 are mandatory since 31 March 2025.
Depending on transaction volume, merchants validate compliance with a Self-Assessment Questionnaire (SAQ) or a full audit by a Qualified Security Assessor (QSA).
- Who implements it - everyone who accepts, processes, stores or transmits card data: online shops, retailers, payment service providers.
- Who asks for it - the card brands (Visa, Mastercard, American Express, Discover, JCB) through the PCI Security Standards Council, enforced via the acquiring banks. Non-compliance can mean fines, higher fees or losing the ability to accept cards at all.
Historic: ISO/IEC 17799
You’ll still find this one in older security policies.
ISO/IEC 17799 was the first international code of practice for information security, based on the British BS 7799-1. While ISO 27001 defines the requirements for a management system (the “what” and “how to organize it”), 17799 was a catalog of concrete security controls: password policies, physical security, access control, HR security.
It was not certifiable. Certification was done against BS 7799-2, which later became ISO/IEC 27001:2005.
- Who implemented it - IT managers, security officers and organizations that wanted practical guidance to close technical and organizational gaps without building a formal, certifiable management system.
- Who asked for it - internal management and auditors, purely as a guideline and reference.
Historic: ISO/IEC 13335 (GMITS)
Guidelines for the Management of IT Security, a multi-part series. It provided the methodology for the whole IT security process: concepts and models, risk analysis and risk management, selection of safeguards and network security.
- Who implemented it - risk managers, IT architects and security officers in larger companies and public authorities that needed a structured way to assess IT risks.
- Who asked for it - management and public institutions that wanted standardized processes for identifying and reducing risks in IT projects and infrastructure.
Comparison
| Standard | Focus | Nature | Who implements it | Who asks for it |
|---|---|---|---|---|
| ISO 27001 | Company-wide ISMS | Certifiable standard (voluntary, but often required by customers) | Organizations of all industries | B2B customers & management |
| NIS2 | Cybersecurity & resilience of critical sectors | EU law | Medium & large companies in critical/important sectors | EU & national authorities (BSI) |
| SOC 2 | Data security at cloud & SaaS providers | Attestation report by a CPA firm | Cloud & SaaS providers | Enterprise customers |
| IEC 62443 | Industrial control systems (OT / IoT) | Standard series (certifiable) | Asset owners, integrators, manufacturers | Industrial customers & KRITIS operators |
| PCI DSS | Card data protection | Industry standard (contractually binding) | Merchants & payment service providers | Card brands & acquiring banks |
| ISO 17799 | Security controls catalog | Withdrawn, now ISO 27002 | - | - |
| ISO 13335 | IT security & risk management methodology | Withdrawn, now ISO 27005 & 27033 | - | - |
Honorable Mentions
A few more that show up regularly, especially in Germany:
- BSI IT-Grundschutz - the BSI’s own methodology with a huge catalog of modules, can be certified as “ISO 27001 based on IT-Grundschutz”.
- BSI C5 - the Cloud Computing Compliance Criteria Catalogue, the German counterpart to SOC 2 for cloud providers.
- TISAX - information security assessment for the automotive supply chain, based on the VDA ISA catalog.
- DORA - EU regulation on digital operational resilience for the financial sector, applies since 17 January 2025.
That’s the map. Next time a questionnaire asks for “your NIS2 status and SOC 2 report”, at least you know who wants what. 🎯