Here's something that doesn't get said enough: holding an ISO 27001 certificate and actually having security embedded in your technology are two very different things. A lot of EU companies have the certificate. Fewer have the security. The gap between those two states is where breaches live.
ISO 27001 is an Information Security Management System (ISMS) standard. It defines a framework for managing security: risk assessments, policies, access controls, incident management, awareness training, supplier relationships. It's a management standard, not a technical one.
That distinction matters more than people realise. The standard says you must have controls. It doesn't say what those controls must do technically. Annex A lists 93 controls across 4 themes (organizational, people, physical, technological). But the implementation of each control is up to you.
An ISO 27001 audit checks documentation. Policies exist. Risk registers exist. Access control procedures are documented. Incident response plans are written down. Training records are maintained. The auditor reviews evidence that the ISMS exists as a management system.
What the auditor typically does not check:
The audit verifies that you said you'd do security. It doesn't verify that the security works.
The certificate proves you have a security management system. It does not prove that the system is technically effective. A company can be fully ISO 27001 certified and still get breached through a misconfigured S3 bucket that the auditor never looked at.
Here's what happens in practice. A company decides to get ISO 27001 certified. They hire a consultant. The consultant writes policies, risk registers, procedures. The auditor reviews the documentation. The certificate is issued. Everyone is happy.
Six months later: a developer commits an API key to a public GitHub repo. A phishing email gets through because the email filter rules were never tested against actual phishing campaigns. A supplier compromise spreads because no one checked whether the supplier's security claims were true. The ISO 27001 certificate is on the wall. The breach is in the logs.
Technologically certified means the controls in the ISMS are actually implemented in the technology, not just described in documents. Specifically:
NIS2 doesn't accept "we have ISO 27001" as evidence of compliance. It wants evidence that your security measures are effective, not just documented. DORA goes further: it wants operational resilience demonstrated through testing, not just described in a plan.
The regulators have figured this out. They know the gap exists. When they ask for evidence, they want to see detection rules, alerting thresholds, incident response times, patch verification. They don't want to see your certificate.
Under NIS2, the question isn't "are you certified?" — it's "can you demonstrate that your controls work?" An ISO 27001 certificate alone is not sufficient evidence. And regulators know this.
If you have ISO 27001 on paper and want it to be real in practice:
This is the difference between a security management system and actual security. Both matter. Only one of them stops breaches.
ISO 27001 is worth having. The management framework is genuinely useful. But the certificate is a starting point, not an endpoint. The endpoint is security that works in the technology, verified through testing, not just documented in a binder.
If your company is in scope for NIS2 or DORA, regulators will ask for the second kind of evidence. Not the certificate. The controls working.
Get in touch. We can help map your controls to technical verification.
Get in touch