Bekendtgørelse om modstandsdygtighed og beredskab i energisektoren (Danmark)

Requirement

§ 27: Risikovurdering

Oh no! No description found. But not to worry. Read from Tasks below how to advance this topic.

Virksomheder skal gennemføre en risikovurdering i henhold til § 18, stk. 1 og 2 og stk. 4, i forbindelse med følgende projekter:

Erhvervelse og udvikling af forsyningskritiske net- og informationssystemer.
Etablering af nye anlæg eller opkøb af anlæg i klasse 3-5, jf. tærskelværdierne i bilag 2. Ændring af eksisterende anlæg i klasse 3-5, som forventes at medføre en ændring i et anlægs klassificering, jf. tærskelværdierne i bilag 2.
Outsourcing af udviklings-, drifts- og vedligeholdelsesopgaver, der kan påvirke leveringen af virksomhedens tjenester.

Stk. 2. Risikovurderinger efter stk. 1, hvor der indgår et leverandørforhold, skal inkludere en vurdering af risici som følger af leverandørforholdet, jf. procedurerne i § 29.

Stk. 3. Risikovurderinger efter stk. 1 skal udarbejdes ved projektets opstart og foreligge skriftligt, inden projektet påbegyndes. Risikovurderingen skal opdateres, når projektets omfang, tidsplan og delleverancer ændres i en sådan grad, at det ændrer forudsætningerne for risikovurderingen.

Fulfill this requirement by completing the tasks below ->

This requirement is part of the framework:

Bekendtgørelse om modstandsdygtighed og beredskab i energisektoren (Danmark)

Other requirements of the framework

§ 27: Risikovurdering

Best practices

How to implement:

§ 27: Risikovurdering

This policy on

§ 27: Risikovurdering

provides a set concrete tasks you can complete to secure this topic. Follow these best practices to ensure compliance and strengthen your overall security posture.

Virksomheder skal gennemføre en risikovurdering i henhold til § 18, stk. 1 og 2 og stk. 4, i forbindelse med følgende projekter:

Erhvervelse og udvikling af forsyningskritiske net- og informationssystemer.
Etablering af nye anlæg eller opkøb af anlæg i klasse 3-5, jf. tærskelværdierne i bilag 2. Ændring af eksisterende anlæg i klasse 3-5, som forventes at medføre en ændring i et anlægs klassificering, jf. tærskelværdierne i bilag 2.
Outsourcing af udviklings-, drifts- og vedligeholdelsesopgaver, der kan påvirke leveringen af virksomhedens tjenester.

Stk. 2. Risikovurderinger efter stk. 1, hvor der indgår et leverandørforhold, skal inkludere en vurdering af risici som følger af leverandørforholdet, jf. procedurerne i § 29.

Stk. 3. Risikovurderinger efter stk. 1 skal udarbejdes ved projektets opstart og foreligge skriftligt, inden projektet påbegyndes. Risikovurderingen skal opdateres, når projektets omfang, tidsplan og delleverancer ændres i en sådan grad, at det ændrer forudsætningerne for risikovurderingen.

Read below what concrete actions you can take to improve this ->

Frameworks that include requirements for this topic:

No items found.

How to improve security around this topic

In Cyberday, requirements and controls are mapped to universal tasks. A set of tasks in the same topic create a Policy, such as this one.

Here's a list of tasks that help you improve your information and cyber security related to

§ 27: Risikovurdering

Task name

Priority

Task completes

Complete these tasks to increase your compliance in this policy.

Critical

No other tasks found.

Complete these tasks in Cyberday ISMS ->

How to comply with this requirement

In Cyberday, requirements and controls are mapped to universal tasks. Each requirement is fulfilled with one or multiple tasks.

Here's a list of tasks that help you comply with the requirement

§ 27: Risikovurdering

of the framework

Bekendtgørelse om modstandsdygtighed og beredskab i energisektoren (Danmark)

Task name

Priority

Task completes

Complete these tasks to increase your compliance in this policy.

Critical

Risk management procedure -report publishing and maintenance

Critical

High

Normal

Low

Risk management and leadership

Risk management

Risk management procedure -report publishing and maintenance

This task helps you comply with the following requirements

Članak 30.1.a: Politike analize rizika i sigurnosti informacijskih sustava NIS2 Croatia

2.5: Riskienhallinta TiHL tietoturvavaatimukset

8 §: Kyberturvallisuutta koskeva riskienhallinnan toimintamalli Kyberturvallisuuslaki

1.4.1: Management of Information Security Risks TISAX

30 § 1°: Gestion des risques et maîtrise des incidents NIS2 Belgium

Documentation of risk assessment

Critical

High

Normal

Low

Risk management and leadership

Cyber security management

Documentation of risk assessment

This task helps you comply with the following requirements

Article 13.3: Documenting risk assessment CRA

11.7: Listei de active și riscuri NIS2 Romania

12.2: Risk assessment measures CER

§ 4-4: Krav til dokumentasjon Sikkerhetsloven

§ 13: Riskbedömning NIS2 Åland

Risk assessment for new acquisitions

Critical

High

Normal

Low

Risk management and leadership

Risk management

Risk assessment for new acquisitions

This task helps you comply with the following requirements

§ 9-4.1: Myndighet til å fatte vedtak ved anskaffelser til skjermingsverdig informasjonssystem, objekt og infrastruktur Sikkerhetsloven

§ 27: Risikovurdering Energisektor beredskabsbekendtgørelse

Creating and maintaining risk assessment framework

Critical

High

Normal

Low

Risk management and leadership

Risk management

Creating and maintaining risk assessment framework

This task helps you comply with the following requirements

1.1.3: Identify the organisation’s processes for ICT risk management NSM ICT-SP

§ 27: Risikovurdering Energisektor beredskabsbekendtgørelse

Supply chain cyber security risk management

Critical

High

Normal

Low

Partner management

Supplier security

Supply chain cyber security risk management

This task helps you comply with the following requirements

ID.SC-1: Cyber supply chain NIST

21.3: Defining and monitoring required supply chain security measures NIS2

CC3.2: Identification of risks related to objectives SOC 2

Article 28: General principles DORA

9.4 §: Toimitusketjun hallinta ja valvonta Kyberturvallisuuslaki

Consideration of critical functions in risk management

Critical

High

Normal

Low

Risk management and leadership

Risk management

Consideration of critical functions in risk management

This task helps you comply with the following requirements

74: Kriittisten palveluiden riskien arviointi ja hallinta Digiturvan kokonaiskuvapalvelu

ID.BE-4: Dependencies and critical functions for delivery of critical services are established.CyberFundamentals

31: Besondere Anforderungen an die Risikomanagementmaßnahmen von Betreibern kritischer Anlagen NIS2 Germany

12.1: Risk assessments CER

§ 13: Riskbedömning NIS2 Åland

Complete these tasks in Cyberday ISMS ->

The ISMS component hierachy

When building an ISMS, it's important to understand the different levels of information hierarchy. Here's how Cyberday is structured.

Framework

Sets the overall compliance standard or regulation your organization needs to follow.

Requirements

Break down the framework into specific obligations that must be met.

Tasks

Concrete actions and activities your team carries out to satisfy each requirement.

Policies

Documented rules and practices that are created and maintained as a result of completing tasks.

Never duplicate effort. Do it once - improve compliance across frameworks.

Reach multi-framework compliance in the simplest possible way‍

Security frameworks tend to share the same core requirements - like risk management, backup, malware, personnel awareness or access management.

Cyberday maps all frameworks’ requirements into shared tasks - one single plan that improves all frameworks’ compliance.

Do it once - we automatically apply it to all current and future frameworks.

Start free trial