Why should NIS2 measures be integrated across governance, process and technology?
Article 21(2) of NIS2 lists ten measures, (a) to (j). The most common mistake is to treat them as ten separate to-do lists handed to ten different owners. Policies get written and tools get bought, yet when an incident hits nobody can connect the board decision, the SOC alert and the supplier contract into one coherent account.
We look at NIS2 in three layers:
- Governance: who approves the measures, who decides whether an incident is significant, who answers to the competent authority. These belong in your existing security and corporate governance framework.
- Process: IT operations, the SOC, procurement, HR and business continuity already run every day; each one takes on the measures that naturally land on it.
- Technology: MFA, logging, backup and vulnerability management keep producing records you can trace.
Integration means each piece of evidence is produced once and answers NIS2, customer audits and your existing ISO certifications at the same time. We start from the management system you already operate and build the NIS2 requirements into it rather than creating a parallel one, cutting duplicated effort now and maintenance cost later. VP- and director-level consultants lead the engagement end to end, never outsourced. For how each measure is implemented, see NIS2 technical integration.
How does Ahura keep NIS2 evidence reusable across ISO 27001 and ISO 22301?
NIS2 evidence overlaps heavily with ISO 27001 control records and ISO 22301 exercise reports. Continuous integration starts from one principle: a single evidence record and a single sign-off chain should be referenced by every framework that needs it, instead of each framework keeping its own copy.
The Ahura enterprise risk management platform is currently at proof-of-concept (POC) stage, and everything below refers to the POC version. In a NIS2 programme it is the evidence and sign-off layer; it does not replace your SIEM or SOC.
- Available in the POC: 100% on-premises deployment; an end-to-end evidence chain in which every sign-off is recorded and compatible with EU eIDAS certificates; a group-wide distributed architecture suited to groups operating in several Member States; EU multilingual interface; modular extension for EU regulations and international standards.
- In development, released as the POC progresses: cross-standard comparison, gap analysis on uploaded documents, regulatory version timelines and regulatory change tracking. There is no NIS2-specific module today.
Today, incident timelines, restore tests and supplier assessments can be signed off on one chain and cited in both NIS2 and ISO audits. Once the development features ship, the goal is to show which evidence needs a second look when a Member State's transposition law changes.
What does outsourcing your NIS2 internal audit to Winners Consulting deliver?
Article 21(2)(f) of NIS2 requires policies and procedures to assess the effectiveness of cybersecurity risk-management measures. An internal audit is the most direct way to meet it. Our internal audit outsourcing service typically covers how significant incidents are classified and reported, third-party remote access, backup restore testing, and whether management approval records keep pace with changes to the measures.
Objectivity comes first. Under ISO 9000:2015, 3.13.1, an internal (first-party) audit may be conducted by the organisation itself or on its behalf, and independence can be demonstrated by freedom from responsibility for the activity being audited. ISO/IEC 27001:2022, clause 9.2, likewise requires the audit process to be objective and impartial. Our principle follows directly: a consultant never audits a process they designed. The audit is performed by a consultant who had no part in that design.
After the audit we work through the findings with your management team and sort them into three horizons: fixes that cannot wait, items for the next budget year, and longer-term capability building. The result is a roadmap you can track. An internal audit is not third-party certification and does not stand in for a supervisory conclusion by the competent authority; Winners Consulting provides consulting only and does not issue certifications.
How do supplier audits put NIS2 Article 21(2)(d) supply chain security into practice?
Article 21(2)(d) covers supply chain security, including the security aspects of each entity's relationships with its direct suppliers and service providers. Article 21(3) asks entities to take into account the vulnerabilities specific to each direct supplier, the overall quality of their products and their cybersecurity practices. For digital infrastructure and certain other entity types, points 5.1 and 5.2 of the Annex to Implementing Regulation (EU) 2024/2690 add a supply chain security policy and a directory of suppliers.
Our NIS2 supplier audit service carries out those audits on your behalf. Under ISO 9000:2015, 3.13.1, that makes it a second-party audit. It is not certification: the findings belong to you and feed directly into supplier terms and corrective actions, giving you supply chain assurance you can evidence.
| Supplier type | Audit focus (NIS2 requirement) | Evidence retained |
|---|---|---|
| MSPs and MSSPs | Art. 21(3): cybersecurity practices, privileged access | Audit report, access list |
| Cloud and data centre providers | Art. 21(2)(d): security terms of the service relationship | Contract clauses, assessment record |
| Software development and maintenance vendors | Art. 21(3): secure development procedures | Development process review record |
| Remote equipment maintenance providers | Art. 21(2)(d): control of remote access | Access logs, MFA configuration |
| Network and security appliance vendors | Art. 21(3): overall product quality | Vulnerability handling records |
To scope a supplier audit programme, contact us.
Official sources
- Directive (EU) 2022/2555 (NIS 2 Directive) — EUR-Lex
- ENISA — Cybersecurity roles and skills for NIS2 essential and important entities (Article 21(2) text)
- ENISA — Technical implementation guidance on cybersecurity risk-management measures, v1.0 (June 2025)
- Commission Implementing Regulation (EU) 2024/2690 — EUR-Lex
- ISO/TC 176 — Terms and definitions in TC 176 standards (ISO 9000:2015, 3.13.1 audit, Notes 1–4)
- ISO CASCO — Conformity assessment techniques: Auditing (first-, second-, third-party audits)
