Which existing processes does NIS2 plug into: IT operations, the SOC, procurement or crisis communication?
NIS2 is an organisation-level directive that has applied through Member State law since 18 October 2024. It governs not a single product but how the whole organisation manages risk to its network and information systems. So we start by mapping the processes you already run and then assign the ten Article 21(2) measures to them:
- IT operations: change, configuration and patch management, covering (e) security in network and information systems acquisition, development and maintenance, including vulnerability handling and disclosure.
- Security monitoring and the SOC: alert triage and incident tickets, covering (b) incident handling and feeding the Article 23 deadlines.
- Business continuity and crisis communication: backup management, disaster recovery and crisis management under (c).
- Procurement and supplier management: supplier assessments and contract clauses under (d) supply chain security.
- HR and account management: joiners, movers, leavers and access rights under (i) human resources security, access control and asset management.
- Management reporting: management bodies must approve and oversee the Article 21 measures, and their members must follow training (Article 20(1) and (2)).
A Taiwanese company that is only a supplier to an in-scope EU entity is not directly in scope for that reason alone, but customers will write (d) supply chain requirements into contracts. In that case the process to connect is how sales, quality and security answer customers together. National transposition laws may add requirements; check the law in force on the day of assessment.
Which technologies implement the ten NIS2 Article 21 measures, and what evidence do they leave?
Article 21(2) lists ten measures, (a) to (j). The first column follows the official text; the implementation column is our good-practice recommendation, not legal wording.
| Requirement (article / control) | Implementation technology | Evidence left behind |
|---|---|---|
| Article 21(2)(a): policies on risk analysis and information system security | Risk register, asset and threat assessment method | Security policy, risk assessment and approval records |
| (b) incident handling; Article 23(4) | SIEM alerts, SOC triage rules, incident tickets with awareness timestamps | Incident records, early warning / notification / final report and timeline |
| (c) business continuity (backup management, disaster recovery) and crisis management | Offline or immutable backups, restore tests, disaster recovery drills | Restore-test records, drill reports, crisis communication logs |
| (d) supply chain security | Supplier register, security questionnaires, contractual security clauses, controls on third-party remote access | Supplier assessments, contract clauses, access logs |
| (e) security in acquisition, development and maintenance, including vulnerability handling and disclosure | Vulnerability scanning, patch management, configuration baselines, network segmentation | Scan reports, patch-time records, change records |
| (h) cryptography and encryption | Encryption in transit and at rest, key management | Encryption policy, key inventory |
| (i) human resources security, access control policies and asset management | IAM, privileged access management, asset inventory | Access review records, asset inventory |
| (j) multi-factor or continuous authentication, secured voice, video and text communications | MFA, encrypted communication tools | MFA coverage records, communication tool configuration records |
(f) assessing the effectiveness of the measures and (g) basic cyber hygiene and cybersecurity training are evidenced through internal audits, metric reviews and training records.
For DNS service providers, TLD name registries, cloud, data centre and CDN providers, MSPs, MSSPs, online marketplaces, search engines, social networks and trust service providers, Implementing Regulation (EU) 2024/2690 adds detailed technical requirements, for example Annex section 3.2 on monitoring and logging, section 6.8 on segmenting systems into networks or zones according to the risk assessment, and section 12.4 on a complete, accurate and up-to-date asset inventory. Other entities are not directly bound by it, but it works well as a technical benchmark.
For companies that already run ISO 27001, we first map existing controls against these ten measures and reuse what is there; the additional NIS2 elements, the reporting deadlines and supply chain security assessment, are usually where reinforcement is needed.
How does NIS2 risk management connect to legal requirements, technical controls and monitoring metrics?
A common scenario shows the chain:
- Risk identification: ransomware enters the internal network through a supplier’s remote maintenance account.
- Legal requirement: Article 21(2)(d) supply chain security, (i) access control, (j) multi-factor authentication and (c) backup and disaster recovery; once it is a significant incident, Article 23 reporting is triggered.
- Technical control: all third-party accounts go through a jump host with MFA, privileged accounts are reviewed regularly, and backups are isolated from production and restore-tested.
- Monitoring metric: MFA coverage of third-party accounts, restore-test success rate, and the time from becoming aware of a significant incident to sending the early warning.
The Article 23(4) clock starts when you become aware of a significant incident: an early warning within 24 hours, an incident notification within 72 hours, an intermediate report on request of the authority or CSIRT, and a final report within one month of the notification. The time of awareness and the significance assessment are therefore evidence in their own right.
Accountability also sits with management: management bodies can be held liable for the entity infringing Article 21 (Article 20(1)), and for infringements of Articles 21 or 23 essential entities face fines with a maximum of at least EUR 10 million or 2% of worldwide annual turnover, whichever is higher (Article 34).
At Winners, one team plans the legal scoping (essential or important entity, which Member State has jurisdiction), the processes and the technical controls together, so one set of evidence serves several regulations and customer requirements. VP- and director-level consultants lead the work end to end, never outsourced.
Which departments, systems, data and evidence must be integrated vertically for NIS2?
NIS2 evidence is scattered: incident records sit with the SOC, restore tests with IT, supplier assessments with procurement, approvals with the board secretary. Vertical integration puts them on one line, so that when an authority asks, you can trace from the management body’s decision down to the SIEM alert.
| Department | System | Data | Evidence |
|---|---|---|---|
| Management body / board | Meeting and reporting system | Approval of measures, risk acceptance decisions | Approval records, member training records |
| Security / SOC | SIEM, EDR, incident ticketing | Alerts, incidents, time of awareness | Incident timeline, three-stage reports |
| IT operations | ITSM, configuration and patch management, backup system | Changes, patches, backup and restore results | Change records, patch times, restore tests |
| Procurement / supplier management | Supplier master data, contract management | Supplier register, assessment results | Assessment records, contractual security clauses |
| HR | HR system, IAM | Joiners, movers, leavers | Access provisioning and revocation records, training records |
| Business continuity / communications | Continuity plan repository, emergency communication tools | Critical services, recovery objectives | Continuity plans, drill and crisis communication records |
| Compliance / legal | Document management, regulatory register | Transposition requirements, authority contacts | Applicability determination, registration data |
We recommend connecting the SOC, IT operations and compliance first, because the reporting deadlines are tightest; then procurement and HR; and finally putting management approvals and training records on the same evidence chain. Groups operating in several Member States also need to confirm each national law’s requirements on reporting contacts and registration.
The table is also our interview checklist at project start: for each row we find the counterpart, confirm what data the systems already hold, and fill only the gaps, so NIS2 does not spawn a parallel set of records. Each evidence item needs a named owner and storage location.
What does Ahura do in a NIS2 project, and how does the data flow?
The Ahura Enterprise Risk Management Platform is a Taiwan-born RegTech platform developed by Winners Consulting. It is currently at the POC (proof-of-concept) stage, and everything below describes the POC build. In a NIS2 project Ahura keeps and signs off evidence; it is not a SIEM and does not replace the SOC.
Data flow:
- SOC incident timelines, IT restore tests, procurement’s supplier assessments, management approvals, and our applicability determination and process documents go into Ahura, deployed on your premises.
- Every sign-off enters the evidence chain, compatible with EU eIDAS certificates.
- Auditors, certification bodies or authorities retrieve evidence from that same chain.
Deployment and architecture: 100% on-premises; incident and vulnerability data never go to the cloud or leave your environment. For groups operating in several Member States, a group-style distributed architecture keeps HQ policy uniform while each site stays locally compliant. The interface supports EU languages such as German, French, Dutch and Czech, plus Traditional Chinese and English. EU regulations, harmonised standards and international standards are added through a modular extension design.
To be clear: a NIS2-specific module is planned under that modular extension design. For now Ahura focuses on the evidence chain, sign-offs and on-premises storage; document upload with compliance gap analysis, cross-standard comparison and regulatory change tracking are in development and will be released as the POC progresses.
What governance, risk, efficiency and continuous-compliance results does NIS2 integration produce?
We describe results in ways that can be checked:
- Governance: the management body’s approval and oversight of the Article 21 measures, and members’ training, are recorded (Article 20); cybersecurity stops being an IT-only matter.
- Risk: significant-incident assessment and three-stage reporting follow a fixed path with timestamps; supplier risk is assessed at procurement, not after an incident sends someone digging through contracts.
- Efficiency: one set of controls and records answers NIS2, ISO 27001 certification and customer audits; backups, recovery and drills can be shared with ISO 22301.
- Continuous compliance: when national transposition laws or implementing rules change, there is a named owner and a review cycle, and the measures are updated accordingly.
We start from the management system you already run and build the NIS2 requirements into your existing security, IT operations and continuity arrangements instead of setting up a separate one, cutting duplicated effort now and maintenance cost later. Our consultants hold ISO Lead Auditor qualifications; Winners provides consulting only and does not issue certifications.
To check whether NIS2 applies to you and which measure to start with, contact us.
Continuous assurance & trusted supply chain: NIS2 Internal Audit Outsourcing & Supplier Audits
Technical integration for related services
Official sources
- Directive (EU) 2022/2555 (NIS 2 Directive) — EUR-Lex
- Commission Implementing Regulation (EU) 2024/2690 — technical and methodological requirements of cybersecurity risk-management measures — EUR-Lex
- ENISA — Technical implementation guidance on cybersecurity risk-management measures, v1.0 (June 2025)
- ENISA — Cybersecurity roles and skills for NIS2 essential and important entities (Article 21(2) and 23(4) text)
- European Commission — NIS2 Directive: securing network and information systems
