Directive (EU) 2022/2555 — NIS 2 Directive
NIS2 establishes cybersecurity risk-management, reporting, governance, supervision, and supply-chain requirements across essential and important entities.
What the authority record establishes
NIS2 establishes cybersecurity risk-management, reporting, governance, supervision, and supply-chain requirements across essential and important entities.
Obligations arise through the directive and national implementing law within scope
The exact official title, issuing body, jurisdiction, version or application record, and linked source define the scope of this page. Readers should not transfer the authority's status to a commercial product or infer transaction-, patient-, system-, site-, or organization-specific applicability from this summary.
Why it matters to this market
OT operators need jurisdiction-specific mappings from legal requirements to accountable controls, reporting, supplier, and evidence workflows.
Affected operating stages
- Governance
- Risk Management
- Supply Chain
- Incident Reporting
- Continuity
- Supervision
Capabilities to examine
Compliance Mapping And Control Evidence
Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for compliance mapping and control evidence.
Incident Response And Recovery Support
Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for incident response and recovery support.
Cyber-Risk Quantification And Executive Reporting
Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for cyber-risk quantification and executive reporting.
Multi-Site Sensor, Data, And Policy Management
Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for multi-site sensor, data, and policy management.
Device And Product Software-Supply-Chain Risk
Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for device and product software-supply-chain risk.
Affected buyer audiences
- essential and important entities
- management bodies
- security leaders
- suppliers
Implementation questions
- Which entities, products, populations, transactions, systems, sites, or jurisdictions are actually within scope?
- What is binding, what is guidance, and what is a technical or consensus standard?
- Which publication, adoption, effective, application, transition, and enforcement dates differ?
- Who owns legal, clinical, quality, regulatory, policy, or operational interpretation?
- How will a source revision affect open work and historical decisions?
Interpretation boundary
The directive page does not determine an entity's national-law scope, supervisory authority, deadline, or compliance.