BESScompliance logoBESScompliance
EUDirective 2022/2555

NIS2 — Network and Information Security Directive

83 cybersecurity requirements for BESS operators and their supply chain, organized by obligation category. Each requirement is tagged with the stakeholder primarily responsible for delivering it.

Entity classification

Essential entity
≥250 employees OR >€50M turnover — ex ante supervision, fines up to €10M
Important entity
≥50 employees OR >€10M turnover — ex post supervision, fines up to €7M
Asset OwnerEPCO&MManufacturerDeveloperAll

Scope and entity classification

6 requirements
Energy is classified as a sector of high criticality under Annex I. Entities providing electricity storage are explicitly in scope. Classification as essential or important determines the supervision regime and penalty ceiling.
RequirementDetailRole responsibilityRef
Electricity storage in scopeAnnex I, Sector 1 (Energy) — electricity undertakings performing storageAllArt. 2, Annex I
Essential entity thresholdLarge enterprise: ≥250 employees OR >€50M turnover and >€43M balance sheetAsset OwnerArt. 3(1)
Important entity thresholdMedium enterprise: ≥50 employees OR >€10M turnover and >€10M balance sheetAsset OwnerArt. 3(2)
Member state designationMember states may designate additional entities regardless of sizeAllArt. 2(2)(b)
Single market operatorIf entity provides services in multiple member states, each applies separatelyAsset OwnerArt. 26(1)
Registration obligationEssential and important entities must register with national competent authorityAsset OwnerArt. 3(4)

Governance and management liability

6 requirements
Management bodies must approve cybersecurity risk management measures and oversee implementation. They are personally liable. This is not delegable to the IT department.
RequirementDetailRole responsibilityRef
Management body approvalMust approve cybersecurity risk management measures adopted under Art. 21Asset OwnerArt. 20(1)
Management body oversightMust oversee implementation of Art. 21 measuresAsset OwnerArt. 20(1)
Personal liabilityManagement bodies can be held liable for infringements of Art. 21Asset OwnerArt. 20(1)
Cybersecurity training — managementMembers of management bodies must undertake trainingAsset OwnerArt. 20(2)
Cybersecurity training — employeesMust offer similar training to employees on a regular basisAsset OwnerArt. 20(2)
Risk identification skillsTraining must enable identification of risks and assessment of cybersecurity impactAsset OwnerArt. 20(2)

Article 21 — Risk management measures

16 requirements
10 mandatory cybersecurity risk management measures. These are minimum requirements — entities must implement measures proportionate to the risk, the size of the entity, the likelihood and severity of incidents, and the societal and economic impact.
RequirementDetailRole responsibilityRef
(a) Risk analysis and information system security policiesDocumented policies covering risk assessment methodology, asset inventory, and security baselinesAsset OwnerArt. 21(2)(a)
(b) Incident handlingProcedures for prevention, detection, response, and recovery from cybersecurity incidentsAsset OwnerArt. 21(2)(b)
(c) Business continuity and crisis managementBackup management, disaster recovery, crisis management proceduresAsset OwnerArt. 21(2)(c)
(d) Supply chain securitySecurity requirements for direct suppliers and service providers, including contractual arrangementsAsset OwnerArt. 21(2)(d)
(d) Supply chain — EPC contractsCybersecurity requirements must flow down into EPC contract specificationsEPCArt. 21(2)(d)
(d) Supply chain — O&M contractsRemote access, patch management, and incident notification requirements in O&M SLAsO&MArt. 21(2)(d)
(d) Supply chain — equipment procurementManufacturer security posture, firmware update commitments, vulnerability disclosure policiesManufacturerArt. 21(2)(d)
(e) Network and information system acquisition, development, maintenanceIncluding vulnerability handling and disclosureAsset OwnerArt. 21(2)(e)
(f) Policies and procedures for effectiveness assessmentRegular testing and auditing of cybersecurity risk management measuresAsset OwnerArt. 21(2)(f)
(g) Basic cyber hygiene practices and trainingAwareness programs, password policies, access management, secure configurationsAllArt. 21(2)(g)
(h) Cryptography and encryption policiesPolicies and procedures regarding the use of cryptography and, where appropriate, encryptionAllArt. 21(2)(h)
(i) Human resources security, access control, asset managementIdentity management, authentication, access rights — including for OT systemsAsset OwnerArt. 21(2)(i)
(j) Multi-factor authentication or continuous authenticationMFA, secured voice/video/text, secured emergency communication systemsAllArt. 21(2)(j)
Proportionality principleMeasures must be proportionate to risk exposure, entity size, incident likelihood, and societal impactAllArt. 21(1)
State of the artMeasures must take into account relevant European and international standardsAllArt. 21(1)
All-hazards approachMust protect against both cyber and physical threats to network and information systemsAsset OwnerArt. 21(2)

Incident reporting

9 requirements
Significant incidents must be reported in a strict timeline: early warning within 24 hours, incident notification within 72 hours, and a final report within one month. Failure to report is a separate violation.
RequirementDetailRole responsibilityRef
Significant incident definitionCaused or capable of causing severe operational disruption or financial loss, or affected or capable of affecting other persons by causing considerable damageAsset OwnerArt. 23(3)
Early warning — 24 hoursWithout undue delay, within 24 hours of becoming aware. Must indicate if suspected unlawful/malicious or cross-border impactAsset OwnerArt. 23(4)(a)
Incident notification — 72 hoursUpdate with initial assessment: severity, impact, and where available, indicators of compromiseAsset OwnerArt. 23(4)(b)
Intermediate reportUpon request of the CSIRT or competent authorityAsset OwnerArt. 23(4)(c)
Final report — 1 monthDetailed description: root cause, mitigation measures applied and ongoing, cross-border impact if applicableAsset OwnerArt. 23(4)(d)
Extended final — 1 month after handlingIf incident still ongoing at 1-month mark, interim report then; final report within 1 month of handlingAsset OwnerArt. 23(4)(d)
Report to CSIRTReports go to the national CSIRT (Computer Security Incident Response Team)Asset OwnerArt. 23(1)
Inform recipients of servicesMust inform recipients of services potentially affected by a significant cyber threatAsset OwnerArt. 23(1)
Remediation measures to recipientsMust disclose to service recipients any measures they can take in response to the threatAsset OwnerArt. 23(2)

Supply chain security for BESS

9 requirements
NIS2 makes the asset owner responsible for the cybersecurity of their supply chain. In practice, this means cybersecurity clauses must flow into EPC contracts, O&M SLAs, and equipment procurement specifications.
RequirementDetailRole responsibilityRef
Direct supplier assessmentAssess cybersecurity risk of direct suppliers and service providersAsset OwnerArt. 21(2)(d)
Contractual security requirementsInclude cybersecurity requirements in contractual arrangements with direct suppliersAsset OwnerArt. 21(2)(d)
EPC cybersecurity handoverEPC must deliver cybersecurity documentation: network architecture, access credentials, hardening recordsEPCArt. 21(2)(d)
PCS/BMS firmware securityManufacturer must provide firmware update policy, vulnerability disclosure process, SBOMManufacturerArt. 21(2)(d)
SCADA/EMS securityControl system providers must document security architecture and remote access proceduresManufacturerArt. 21(2)(d)
Remote access controls — O&MO&M provider remote OT access must use MFA, audit logging, and session recordingO&MArt. 21(2)(d),(j)
Patch management — O&MO&M provider must maintain patching schedule and document exceptionsO&MArt. 21(2)(e)
Incident notification — supply chainSuppliers and service providers must notify the entity of incidents affecting supplied servicesAllArt. 21(2)(d)
Coordinated risk assessmentsEU-level coordinated security risk assessments of critical supply chainsAllArt. 22

OT security — IEC 62443 alignment

8 requirements
NIS2 does not prescribe a specific standard, but IEC 62443 is the de facto framework for industrial OT security in the energy sector. Aligning with IEC 62443 is the most practical path to demonstrating compliance with Article 21.
RequirementDetailRole responsibilityRef
OT network segmentationSeparate IT and OT networks. Zone and conduit model per IEC 62443-3-3Asset OwnerArt. 21(2)(a),(e)
Security levels per zoneDefine target security levels (SL-T) for each zone based on risk assessmentAsset OwnerArt. 21(2)(a)
Component security — SL capabilityPCS, BMS, EMS components must meet required security level capability (SL-C)ManufacturerArt. 21(2)(e)
Secure development lifecycleManufacturers should follow IEC 62443-4-1 for product developmentManufacturerArt. 21(2)(e)
System integrator responsibilityEPC/SI must achieve target SL through integration: hardening, access control, monitoringEPCArt. 21(2)(e)
Periodic security assessmentRegular vulnerability scanning and penetration testing of OT systemsAsset OwnerArt. 21(2)(f)
Change management — OTDocumented change management process for all OT system modificationsO&MArt. 21(2)(e)
Backup and recovery — OTOT system configurations, firmware images, and control logic must be backed up and testedAsset OwnerArt. 21(2)(c)

National implementation — Nordics

8 requirements
RequirementDetailRole responsibilityRef
Sweden — CybersäkerhetslagenNational transposition law. Competent authority: MSB (Swedish Civil Contingencies Agency)AllNational
Sweden — registrationEntities must register with the competent authority. Energy sector supervised by EnergimyndighetenAsset OwnerNational
Denmark — national transpositionTransposed into Danish law. Competent authority: CFCS (Centre for Cyber Security)AllNational
Denmark — energy sectorEnergy sector supervised by Energistyrelsen (Danish Energy Agency)Asset OwnerNational
Finland — national transpositionTransposed into Finnish law. Competent authority: Traficom (Transport and Communications Agency)AllNational
Finland — energy sectorEnergy sector supervised by Energiavirasto (Energy Authority)Asset OwnerNational
Transposition deadline17 October 2024 — all member states must have transposed NIS2 into national lawAllArt. 41(1)
Application date18 October 2024 — measures apply from this dateAllArt. 41(2)

Supervision and enforcement

9 requirements
RequirementDetailRole responsibilityRef
Essential entities — ex ante supervisionProactive supervision: audits, security scans, on-site inspections at any timeAsset OwnerArt. 32(2)
Important entities — ex post supervisionReactive supervision: triggered by evidence of non-compliance or incidentAsset OwnerArt. 33(2)
On-site inspectionsCompetent authorities may conduct on-site inspections and off-site supervisionAsset OwnerArt. 32(2)(a)
Security auditsRegular and targeted security audits by independent body or competent authorityAsset OwnerArt. 32(2)(b)
Security scansAd hoc security scans based on objective, non-discriminatory risk assessment criteriaAsset OwnerArt. 32(2)(c)
Information requestsCompetent authority may request evidence of cybersecurity policies implementationAsset OwnerArt. 32(2)(d)
Compliance ordersAuthority may issue binding instructions and require remediation within a deadlineAsset OwnerArt. 32(4)
Suspend certificationAuthority may request suspension of entity certification or authorizationAsset OwnerArt. 32(5)(b)
Suspend managementFor essential entities: authority may request temporary ban of management body memberAsset OwnerArt. 32(5)(d)

Penalties

6 requirements
RequirementDetailRole responsibilityRef
Essential entities — maximum fine€10,000,000 or 2% of total worldwide annual turnover, whichever is higherAsset OwnerArt. 34(4)
Important entities — maximum fine€7,000,000 or 1.4% of total worldwide annual turnover, whichever is higherAsset OwnerArt. 34(5)
Periodic penalty paymentsCompetent authority may impose periodic penalties to compel complianceAsset OwnerArt. 34(6)
Penalties must be effectiveProportionate and dissuasive, taking into account circumstances of each caseAllArt. 34(1)
Factors consideredGravity, duration, previous infringements, damage caused, degree of intent or negligenceAllArt. 34(3)
Personal liability of managementNatural persons in management bodies can be held personally liableAsset OwnerArt. 20(1), Art. 32(6)

Key dates and deadlines

6 requirements
RequirementDetailRole responsibilityRef
Directive adopted14 December 2022AllDirective 2022/2555
Transposition deadline17 October 2024AllArt. 41(1)
Application date18 October 2024 — obligations apply from this dateAllArt. 41(2)
Entity registrationOngoing — register with national competent authorityAsset OwnerArt. 3(4)
Implementing acts — incident reportingBy 17 October 2024 — further specifying significant incidentsAllArt. 23(11)
Review of the DirectiveBy 17 October 2027 — Commission reviews functioning of the DirectiveAllArt. 40
Requirements based on Directive (EU) 2022/2555 of the European Parliament and of the Council (NIS2 Directive), published 14 December 2022.