Find and prioritise weaknesses
Short label: VULN
Meaning
Keep an inventory, assess weaknesses and decide which updates or mitigations matter most.
Why it matters
The priority depends on exposure, likely impact and the systems your organisation relies on.
What you can do
Identify affected components, assess exposure, patch or mitigate, then verify the result and record remaining work.
Services that can help
Custom Software supports component records and updates. Web App Shield can add filtering while an application weakness is addressed; available mitigations depend on the issue.
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.