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.

See how Cyberday guides you to fulfill this requirement:

Start free trial

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

Članak 29.a: Upravljanje NIS2 Croatia

10 §: Johdon vastuu Kyberturvallisuuslaki

9.2 §: Kyberturvallisuuden toimintaperiaatteet Kyberturvallisuuslaki

1.1.1: Availability of information security policies TISAX

31 § 1°: Approbation des mesures de gestion des risques de cybersécurité NIS2 Belgium

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

Članak 30.1.e: Sigurnost u nabavi, razvoju i održavanju mrežnih i informacijskih sustava NIS2 Croatia

4.2: Tietojärjestelmien hankinnat TiHL tietoturvavaatimukset

9.3 §: Tietojärjestelmien hankinta ja kehittäminen Kyberturvallisuuslaki

5.3.1: Information Security in new systems TISAX

13 §: Tietoaineistojen ja tietojärjestelmien tietoturvallisuus TiHL

Separation of production, testing and development environments

Critical

High

Normal

Low

Development and cloud

Secure development

Separation of production, testing and development environments

Članak 30.1.e: Sigurnost u nabavi, razvoju i održavanju mrežnih i informacijskih sustava NIS2 Croatia

9.3 §: Tietojärjestelmien hankinta ja kehittäminen Kyberturvallisuuslaki

5.2.2: Seperation of testing and development environments TISAX

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

2.1.6: Use separate environments for development, test and production NSM ICT-SP

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

Članak 30.1.e: Sigurnost u nabavi, razvoju i održavanju mrežnih i informacijskih sustava NIS2 Croatia

4.2: Tietojärjestelmien hankinnat TiHL tietoturvavaatimukset

9.3 §: Tietojärjestelmien hankinta ja kehittäminen Kyberturvallisuuslaki

5.3.1: Information Security in new systems TISAX

13 §: Tietoaineistojen ja tietojärjestelmien tietoturvallisuus TiHL

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

Članak 30.1.e: Sigurnost u nabavi, razvoju i održavanju mrežnih i informacijskih sustava NIS2 Croatia

9.3 §: Tietojärjestelmien hankinta ja kehittäminen Kyberturvallisuuslaki

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

2.1.9: Maintain security responsibility during outsourcing NSM ICT-SP

DE.CM-6: External service provider activity is monitored to detect potential cybersecurity events.CyberFundamentals

Guidelines for secure development

Critical

High

Normal

Low

Development and cloud

Secure development

Guidelines for secure development

Članak 30.1.e: Sigurnost u nabavi, razvoju i održavanju mrežnih i informacijskih sustava NIS2 Croatia

9.3 §: Tietojärjestelmien hankinta ja kehittäminen Kyberturvallisuuslaki

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

2.1.5: Use a secure software development method NSM ICT-SP

2.1.8: Maintain the software code developed/used by the organisation NSM ICT-SP

Regular critical code identification and verification

Critical

High

Normal

Low

Development and cloud

Secure development

Regular critical code identification and verification

Članak 30.1.e: Sigurnost u nabavi, razvoju i održavanju mrežnih i informacijskih sustava NIS2 Croatia

9.3 §: Tietojärjestelmien hankinta ja kehittäminen Kyberturvallisuuslaki

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

2.1.5: Use a secure software development method NSM ICT-SP

2.1.8: Maintain the software code developed/used by the organisation NSM ICT-SP

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

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