NIS2 Directive

What the authority establishes

NIS2 establishes cybersecurity risk-management and incident-reporting obligations for covered entities. Article 21 expressly includes supply-chain security and security-related aspects of relationships with direct suppliers and service providers.

Covered organizations must treat supplier and service-provider relationships as part of cybersecurity risk management. The directive supports disciplined supplier scoping, security criteria, evidence, incident coordination, vulnerability handling, and monitoring while leaving implementation detail to national law and organizational risk decisions.

The record is written for operational interpretation, not legal advice. Applicability depends on entity type, jurisdiction, relationship, service, data, criticality, contractual commitments, and later authority guidance.

Who should read it

The primary audiences named in this review are essential and important entities in covered EU sectors, CISOs and cybersecurity governance leaders, procurement, legal, compliance, and third-party risk teams, digital and managed service providers in scope. Those roles may divide responsibility differently, but the operating record should still show scope, accountable ownership, evidence, review, exceptions, and the final decision.

Third-party lifecycle implications

Scope And Governance

Teams should determine what this authority expects at the scope and governance stage, which function owns the judgment, what evidence must be retained, and what later change would reopen the record.

Supplier Security Criteria

Teams should determine what this authority expects at the supplier security criteria stage, which function owns the judgment, what evidence must be retained, and what later change would reopen the record.

Due Diligence

Teams should determine what this authority expects at the due diligence stage, which function owns the judgment, what evidence must be retained, and what later change would reopen the record.

Contracting

Teams should determine what this authority expects at the contracting stage, which function owns the judgment, what evidence must be retained, and what later change would reopen the record.

Monitoring

Teams should determine what this authority expects at the monitoring stage, which function owns the judgment, what evidence must be retained, and what later change would reopen the record.

Vulnerability And Incident Coordination

Teams should determine what this authority expects at the vulnerability and incident coordination stage, which function owns the judgment, what evidence must be retained, and what later change would reopen the record.

Remediation

Teams should determine what this authority expects at the remediation stage, which function owns the judgment, what evidence must be retained, and what later change would reopen the record.

Relationship Change

Teams should determine what this authority expects at the relationship change stage, which function owns the judgment, what evidence must be retained, and what later change would reopen the record.

Capabilities that may support the work

These links identify relevant operating capabilities; they do not state that any product creates compliance.

Intake And Inventory

establishing an accountable record of relationships, products, owners, and critical services. Buyers should test the workflow against their own scope and evidence requirements.

Inherent Risk Tiering

using relationship context to determine proportional diligence and review. Buyers should test the workflow against their own scope and evidence requirements.

Due Diligence And Assessments

collecting and reviewing evidence before and during a relationship. Buyers should test the workflow against their own scope and evidence requirements.

Evidence Collection

preserving source material, responses, and reviewer context. Buyers should test the workflow against their own scope and evidence requirements.

Continuous Monitoring

bringing material external and internal change into an owned response workflow. Buyers should test the workflow against their own scope and evidence requirements.

Issue Remediation

assigning findings, deadlines, exceptions, and closure evidence. Buyers should test the workflow against their own scope and evidence requirements.

Fourth-Party Visibility

identifying and explaining important downstream dependencies. Buyers should test the workflow against their own scope and evidence requirements.

Regulatory Mapping

connecting program records to obligations and examination needs. Buyers should test the workflow against their own scope and evidence requirements.

Reporting

turning program activity into operator, executive, and board-ready information. Buyers should test the workflow against their own scope and evidence requirements.

What software cannot decide

Software can structure records, route work, preserve evidence, surface change, and support reporting. It cannot determine legal applicability, set risk appetite, negotiate accountable contract terms, validate every external claim, accept residual risk, or make management responsible for an outcome. Those remain organizational decisions.