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

Requirement

§ 45: Sikker anskaffelse og udvikling af systemer

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

Virksomheder skal have procedurer for sikkerhed i forbindelse med erhvervelse, udvikling og vedligeholdelse af net- og informationssystemer. Procedurerne skal indeholde:

Krav til opretholdelse af et passende sikkerhedsniveau i net- og informationssystemer, som en virksomhed erhverver, udvikler og vedligeholder, herunder krav til sikkerheden i udviklings- og testmiljøer.
Metoder til at kontrollere, om de erhvervede eller udviklede net- og informationssystemer lever op til virksomhedens krav efter nr. 1.

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

§ 45: Sikker anskaffelse og udvikling af systemer

Best practices

How to implement:

§ 45: Sikker anskaffelse og udvikling af systemer

This policy on

§ 45: Sikker anskaffelse og udvikling af systemer

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 have procedurer for sikkerhed i forbindelse med erhvervelse, udvikling og vedligeholdelse af net- og informationssystemer. Procedurerne skal indeholde:

Krav til opretholdelse af et passende sikkerhedsniveau i net- og informationssystemer, som en virksomhed erhverver, udvikler og vedligeholder, herunder krav til sikkerheden i udviklings- og testmiljøer.
Metoder til at kontrollere, om de erhvervede eller udviklede net- og informationssystemer lever op til virksomhedens krav efter nr. 1.

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

§ 45: Sikker anskaffelse og udvikling af systemer

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

§ 45: Sikker anskaffelse og udvikling af systemer

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

Information security policy -report publishing, informing and maintenance

Critical

High

Normal

Low

Risk management and leadership

Cyber security management

Information security policy -report publishing, informing and maintenance

This task helps you comply with the following requirements

5.1.1: Policies for information security ISO 27001

5.1.2: Review of the policies for information security ISO 27001

T01: Turvallisuusperiaatteet Katakri

6.6: Yleiset Omavalvontasuunnitelma

ID.GV-1: Cybersecurity policy NIST

General rules for the procurement of data systems

Critical

High

Normal

Low

System management

Data system procurement

General rules for the procurement of data systems

This task helps you comply with the following requirements

14.1.1: Information security requirements analysis and specification ISO 27001

13 §: Tietoaineistojen ja tietojärjestelmien tietoturvallisuus TiHL

HAL-16: Hankintojen turvallisuus Julkri

5.23: Information security for use of cloud services ISO 27001

52: Tietoturva- ja tietousojavaatimukset hankintavaatimuksissa Digiturvan kokonaiskuvapalvelu

Separation of production, testing and development environments

Critical

High

Normal

Low

Development and cloud

Secure development

Separation of production, testing and development environments

This task helps you comply with the following requirements

12.1.4: Separation of development, testing and operational environments ISO 27001

12.5.1: Installation of software on operational systems ISO 27001

14.2.6: Secure development environment ISO 27001

PR.DS-7: The development and testing environments NIST

MWP-06: Safe running of unknown code Cyber Essentials

Security rules for the development and acquisition of data systems

Critical

High

Normal

Low

System management

Data system procurement

Security rules for the development and acquisition of data systems

This task helps you comply with the following requirements

14.1.1: Information security requirements analysis and specification ISO 27001

14.1.2: Securing application services on public networks ISO 27001

14.2.5: Secure system engineering principles ISO 27001

13 §: Tietoaineistojen ja tietojärjestelmien tietoturvallisuus TiHL

I13: Ohjelmistoilla toteutettavat pääsynhallintatoteutukset Katakri

Process for monitoring and tracking outsourced development work

Critical

High

Normal

Low

Development and cloud

Secure development

Process for monitoring and tracking outsourced development work

This task helps you comply with the following requirements

14.2.7: Outsourced development ISO 27001

DE.CM-6: External service provider activity monitoring NIST

8.28: Secure coding ISO 27001

8.30: Outsourced development ISO 27001

21.2.e: Secure system acquisition and development NIS2

Guidelines for secure development

Critical

High

Normal

Low

Development and cloud

Secure development

Guidelines for secure development

This task helps you comply with the following requirements

14.2.1: Secure development policy ISO 27001

14.2.5: Secure system engineering principles ISO 27001

TEK-14: Ohjelmistojen turvallisuuden varmistaminen Julkri

8.25: Secure development life cycle ISO 27001

8.27: Secure system architecture and engineering principles ISO 27001

Regular critical code identification and verification

Critical

High

Normal

Low

Development and cloud

Secure development

Regular critical code identification and verification

This task helps you comply with the following requirements

14.2.3: Technical review of applications after operating platform changes ISO 27001

14.2.5: Secure system engineering principles ISO 27001

14.2.9: System acceptance testing ISO 27001

8.27: Secure system architecture and engineering principles ISO 27001

21.2.e: Secure system acquisition and development NIS2

Requiring a system description from suppliers of important information systems to be acquired

Critical

High

Normal

Low

System management

Data system procurement

Requiring a system description from suppliers of important information systems to be acquired

This task helps you comply with the following requirements

HAL-16: Hankintojen turvallisuus Julkri

21.2.e: Secure system acquisition and development NIS2

2.1.1: Include security in the organisation’s procurement process NSM ICT-SP

2.1.10: Review the service provider’s security when outsourcing NSM ICT-SP

30 § 3.5°: L'acquisition, du développement et de la maintenance des réseaux et des systèmes d'information NIS2 Belgium

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