ISO 42001 & EU AI Act: The guide to a legally sound AI management system
Whether automated customer communication, predictive maintenance or generative AI in development processes: artificial intelligence is long…
Read articleInnovation, IT Security and Artificial Intelligence
Ransomware attacks, compromised supply chains and daily waves of phishing: the threat landscape in the digital space has reached a historic high. At the same time, lawmakers are tightening the screws. With the European NIS-2 Directive, cybersecurity duties have been drastically expanded – and now affect tens of thousands of organisations that previously did not see themselves as “critical infrastructure”.
What makes this especially sensitive: in future, managing directors will in some cases be personally liable with their private assets if they breach their duties.
Against this background, the international standard ISO/IEC 27001 has moved, for many organisations, from a pure IT status symbol to an existential insurance policy. But how do ISO 27001 and NIS-2 fit together? And how can an information security management system (ISMS) be established that does not exist only on paper, but stands up to the audit and to reality?
ISO/IEC 27001 is the world’s leading standard for information security management systems. The aim of the standard is to protect the three fundamental values of information security (the so-called CIA triad):
What matters is this: ISO 27001 is not a pure IT standard. It looks at information security holistically. That includes physical security (access controls), organisational processes (emergency manuals, employee offboarding) and personnel measures (awareness training, security guidelines).
Many organisations ask themselves: “If we are certified to ISO 27001, have we automatically fulfilled NIS-2 as well?”
The honest answer is: yes, to 80 to 90 per cent.
The NIS-2 Directive sets binding minimum requirements in areas such as:
Exactly these areas are covered in a structured way by Annex A of ISO/IEC 27001 (in the current edition, with its 93 controls in 4 theme areas). Anyone who can demonstrate a lived ISMS in line with ISO 27001 has already documented, operationalised and had audited the technical and organisational measures (TOMs) for NIS-2. Only specific statutory reporting routes to national authorities still need to be added operationally.
A successful ISMS does not appear overnight, but it can be implemented efficiently with a clear focus:
Set out precisely which parts of the organisation, sites, products or services are to be covered by the ISMS. For many IT service providers this initially covers the cloud infrastructure and the core applications.
Identify your most important assets (information assets): customer data, source code, production plans. Which threats and vulnerabilities exist? Which risks are reduced by technical measures (for example multi-factor authentication, segmentation), and which are accepted or insured?
In the SoA you document which of the 93 Annex A controls are relevant to your organisation and how they have been implemented. If controls are excluded, this must be justified in a coherent way.
Security fails most often because of the human factor. Establish understandable policies (clean desk, password rules, handling of mobile devices) and run regular training and simulated phishing tests.
Before the external auditor arrives, internal auditors put the system through its paces. Top management reviews the metrics and releases resources for corrective action.
Beyond legal duties, ISO 27001 has enormous commercial leverage:
ISO 27001 is today the foundation for every organisation that creates value digitally. It turns vague security fears into measurable processes and protects the leadership team from liability risks.
Planning your ISO 27001 certification?
At cert-authority.com we guide you through the audit process transparently and as a partner, with experienced specialist auditors. Get an overview of our prices and packages.