This sheet is past its review date. Deadlines or advice may have changed since 5 Nov 2026.
ISMS and ISO 27001: which certificate do you need, and will the system run your security?
Decide this quarter which evidence your customers and regulators actually ask for, such as an ISO/IEC 27001:2022 certificate or a TISAX label, because NIS2 and the German BSIG require documented measures, not a certificate1. Then scope the ISMS to all the regulated entity's relevant operations, let your risk register choose the controls and have management decide on the remaining risks at least once a year.
If you only do five things
List who asks for which evidence.
Write down what key customers, regulators and insurers require. The BSI calls an ISO 27001 certificate a good foundation for the BSIG but no proof of NIS2 compliance1.
Scope the whole regulated entity.
ISO 27001 lets you limit the scope; the BSIG requires measures for all relevant operations of the entity1. Include IT operations, cloud services and outsourced process steps.
Make management own the remaining risks.
ISMS responsibility can't be delegated, and management signs off residual risks4. Give every accepted risk an owner and an end date.
Audit whether controls work.
Give internal auditors time to test the controls for your biggest risks4: restore a backup, sample leavers' accounts, trigger an alert.
Choose what to certify against
Does a regulator name a scheme?
German power and gas grid operators need an ISMS certified against the Bundesnetzagentur's 2015 IT security catalog, now under revision; an ISO or IT-Grundschutz certificate alone isn't enough16. Other KRITIS operators prove their measures to the BSI every 3 years3.
Do automotive customers ask for TISAX?
More than ten vehicle makers and thousands of suppliers use TISAX results to judge partners12. Register the sites and objectives your customer names.
Do customers or tenders ask for ISO 27001?
Get an accredited ISO/IEC 27001:2022 certificate, which can be recognized worldwide8.
Do you want the BSI's catalog behind it?
ISO 27001 on the basis of IT-Grundschutz needs a BSI-certified lead auditor; the BSI checks the report and issues the certificate7.
Does nobody ask for a certificate?
Build to ISO 27001 anyway and certify when asked. NIST CSF 2.0 helps report outcomes to the board, but NIST offers no certification15.
The certifiable options side by side
ENISA maps each requirement of NIS2 Implementing Regulation 2024/2690 to ISO 27001 and NIST CSF 2.0, without judging equivalence or full coverage11.
ISO/IEC 27001:2022
- Current edition. The 2022 text with Amendment 1:20249, which asks you to decide whether climate change is relevant; no new certificate is needed10.
- Controls. Annex A refers to the 93 controls of ISO/IEC 27002:20228. You select them by risk and list them in the statement of applicability (SoA).
- 2013 is gone. Certificates to the 2013 edition expired or were withdrawn by 31 October 20258.
IT-Grundschutz and Grundschutz++
- Classic. Audited against BSI-Standard 200-2 and the Kompendium Edition 20236, for 3 years with yearly surveillance7. Certifiable until 30 November 20315.
- Grundschutz++. BSI-Standard 300-1 sets the method and a machine-readable catalog replaces the Kompendium. Certification applications open on 1 January 20275.
- Less risk work. For normal protection needs the BSI did the risk analysis; you cover high needs and gaps4.
TISAX
- Objectives set the depth. AL2 checks evidence and interviews the security lead, usually by video call. AL3, for example for strictly confidential data and prototype parts, checks everything, generally on site14.
- Catalog. VDA ISA2027 applies to assessments ordered from 1 January 202712; initial ISA6 assessments can be opened until March 202713.
- Validity. Labels last up to 3 years12.
What NIS2 and the BSIG require
- No certificate. The BSI says ISO 27001 certification is no precondition for meeting the BSIG1, and IT-Grundschutz isn't mandatory for all entities2.
- Documented measures. You must document how you meet the risk management duties3 and show proof when the BSI orders it, for example audit reports. KRITIS operators submit it unasked2.
- Gaps to close. Registration, reporting deadlines and management training aren't part of ISO 270011; see the EU security laws sheet. Energy and telecom operators follow their sector law instead3.
- Mappings are gap lists. The BSI maps each § 30 BSIG measure to ISO 27001 clauses and controls1. ENX, which runs TISAX, argues that a label covering all affected sites meets NIS2 apart from reporting14; the BSI says no company certificate alone meets every BSIG requirement2.
Scope and SoA, done honestly
- Scope by business process. Name the processes, sites, applications, IT systems and service providers, and include each process completely4.
- Mark each control's real state. Implemented with evidence, planned with a date, or not applicable. Grundschutz++ allows that only if a requirement can't functionally be met or the component is absent, with a reason4.
- Explain every choice. ISA2027 requires each listed aspect to be consciously considered and the decision explainable12. Hold your SoA to that.
- Keep the documents few. Scope, policy, objectives, risk register, SoA, treatment plan, audit and corrective action records and review minutes. Management approves the policy; every employee gets it4.
Run a risk assessment that changes decisions
- Management sets the limits. It approves the method, acceptance criteria and risk appetite4. Write criteria in euros, days of downtime and records exposed.
- Start with the crown jewels. Rate each business process for confidentiality, integrity and availability; Grundschutz++ advises starting with the most important one in the highest category4.
- Process owners own risks. That is the default unless you decide otherwise4. Link each risk to measures with an owner and a due date.
- Sign off and repeat. Risk owners approve the plan and management the residual risks. Review at least yearly and after significant changes4 or serious incidents.
Audits and reviews that change things
- Aim audits at your risks. Plan the program around the top risks, detection and incident handling, and earlier findings4. Test real samples.
- Look for improvements. Grundschutz++ sees internal audit as a way to find improvements, not just nonconformities4.
- Keep it impartial. Pick an objective audit team and keep the security officer role apart from IT management4.
- End the review with decisions. Cover audit results, performance, incidents, risk treatment, threat changes and earlier decisions4. Record decisions on budget, scope and accepted risks.
What changed in 2026
- Grundschutz++ arrived. BSI-Standard 300-1 version 1.0, dated 20 October 2026, targets experienced early adopters4. Certification applications on its basis open on 1 January 2027; classic IT-Grundschutz stays certifiable until 30 November 20315.
- TISAX moved to yearly catalogs. Under ISA2027, published on 1 July 2026, suppliers to organizations with very high protection needs are expected to show a TISAX label, an equivalent assessment or a supplier audit. New catalogs follow each summer12.
What you can skip
- A policy for every Annex A control. Write rules where people need them; for technical controls, configuration exports are better evidence.
- A GRC tool before the first cycle. A spreadsheet register and your ticket system will do.
- Separate programs for ISO, TISAX and NIS2. Keep one register and one SoA with a column for each mapping.
- Waiting for Grundschutz++. Its method requirements mirror ISO 27001 clauses 4 to 104, so scope, risk and audit work carries over.
- A climate change study. Record whether it is relevant and why; IAF treated the amendment as a clarification10.
Mistakes that cost the most
- A scope too narrow to matter. A certificate for the IT department alone misses what customers and the BSI care about. The BSI tells certified entities to check whether NIS2 needs a wider scope1.
- Controls copied from a template. An SoA with every control implemented and no evidence falls apart in the first customer audit.
- An ISMS run only by consultants. Management can't hand over responsibility, and a security role must be involved in security-relevant projects such as new systems4. Let consultants coach the process owners.
- Trusting a supplier's logo. Ask for the certificate's scope and SoA; see the third-party risk sheet.
What this looks like at your size
Small team, no security staff
- Build to ISO 27001 without certifying until a customer asks.
- Name a security officer with budgeted time and a deputy.
- Hold the risk review and management review in one half-day meeting a year.