OPS-07 · Vulnerability and patch management
Catalogue · Operate & Protect
Technical vulnerabilities are identified, prioritised and fixed within timeframes that reflect their risk.
Typical activities
- Scan systems for vulnerabilities at defined intervals and after major change
- Set remediation deadlines by severity and track compliance
- Receive and act on vulnerability disclosures from researchers and suppliers
- Run penetration tests on critical and internet-facing systems
Evidence an assessor would expect
- Vulnerability scan reports
- Patch compliance metrics
- Penetration test reports and remediation tracking
Capability scale
- 0 · Absent
- The practice is not performed, or happens so rarely that it produces no recognisable outcome.
- 1 · Initial
- The practice is performed informally and its results depend on the people involved.
- 2 · Repeatable
- The practice is planned, assigned and tracked, with basic records kept.
- 3 · Defined
- The practice follows a documented, organisation-wide approach with clear roles and measurable outputs.
- 4 · Measured
- The practice is managed with quantitative targets and its performance is monitored and reported.
- 5 · Optimising
- The practice is continuously improved using performance data, external comparison and automation.
Regulatory requirements
- primary DORA Art. 9 · Protection and prevention
- supporting DORA Art. 24 · Digital operational resilience testing programme
- primary DORA Art. 25 · Testing of ICT tools and systems
- primary DORA Art. 26 · Advanced threat-led penetration testing
- primary NIS 2 Art. 21(2)(e) · Security in acquisition, development and maintenance
- supporting NIS 2 Art. 21(2)(g) · Cyber hygiene and training
Cross-references
- COBIT® 2019 DSS05
- ISO/IEC 27001:2022 A.8.8
- NIST CSF 2.0 ID.RA
Identifiers only, for orientation. Consult the original publications for their content.