nrdblg

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.

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:

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.

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:

Enterprise customers usually want Type II.

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:

Products and processes can be certified (e.g. via ISASecure or testing bodies like TÜV).

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).


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.

In 2007, ISO/IEC 17799:2005 was renumbered to ISO/IEC 27002. If someone talks about the 'best practice controls' today, they mean ISO 27002, the companion to ISO 27001.

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.

The series has been withdrawn. The risk management parts (3 and 4) went into ISO/IEC 27005, the network security part (5) into ISO/IEC 18028, today ISO/IEC 27033.

Comparison

StandardFocusNatureWho implements itWho asks for it
ISO 27001Company-wide ISMSCertifiable standard (voluntary, but often required by customers)Organizations of all industriesB2B customers & management
NIS2Cybersecurity & resilience of critical sectorsEU lawMedium & large companies in critical/important sectorsEU & national authorities (BSI)
SOC 2Data security at cloud & SaaS providersAttestation report by a CPA firmCloud & SaaS providersEnterprise customers
IEC 62443Industrial control systems (OT / IoT)Standard series (certifiable)Asset owners, integrators, manufacturersIndustrial customers & KRITIS operators
PCI DSSCard data protectionIndustry standard (contractually binding)Merchants & payment service providersCard brands & acquiring banks
ISO 17799Security controls catalogWithdrawn, now ISO 27002--
ISO 13335IT security & risk management methodologyWithdrawn, now ISO 27005 & 27033--

Honorable Mentions

A few more that show up regularly, especially in Germany:


That’s the map. Next time a questionnaire asks for “your NIS2 status and SOC 2 report”, at least you know who wants what. 🎯

#Security #IT #Administration