Build software securely
Short label: SOFTWARE
Meaning
Use reviewed changes, component checks, controlled releases and a maintenance process when building software.
Why it matters
Clear records make it easier to understand what runs, assess a vulnerable component and recover from a failed change.
What you can do
Define review and testing steps, record components and responsibilities, and plan updates and recovery.
Services that can help
Custom Software follows an agreed delivery and operating process. Sovereign Code supports source control and credential checks; product obligations depend on scope and role.
Official reference — NIS2 Art. 21(2)(e)
2. The measures referred to in paragraph 1 shall be based on an all-hazards approach that aims to protect network and information systems and the physical environment of those systems from incidents, and shall include at least the following:
— Directive (EU) 2022/2555 (NIS2), Art. 21(2)
(e) security in network and information systems acquisition, development and maintenance, including vulnerability handling and disclosure;
— Directive (EU) 2022/2555 (NIS2), Art. 21(2)(e)
Security must be built in when you buy, build or maintain systems, and known vulnerabilities must be handled and disclosed.
Read the article on EUR-Lex → · Official text, quoted from the Official Journal of the EU
Acronyms used here: NIS2, GDPR, DORA, CRA
- NIS2 — Network and Information Systems Directive 2
- An EU cybersecurity directive with requirements for organisations covered by its scope.
- GDPR — General Data Protection Regulation
- The EU regulation on personal-data protection. RGPD is the French name and AVG the Dutch name.
- DORA — Digital Operational Resilience Act
- EU rules on digital operational resilience in the financial sector.
- CRA — Cyber Resilience Act
- EU cybersecurity rules for products with digital elements, including certain software and connected devices.