Zum Hauptinhalt springen
Starter Kit · Register

Vulnerability Register

Updated on 2 min Reviewed by: Cenedril-Redaktion
A.8.8 ISO 27001BSI IT-Grundschutz

The vulnerability register documents all known technical vulnerabilities in your IT infrastructure. From unpatched operating systems to misconfigured firewalls to outdated libraries — every vulnerability is captured, assessed, and tracked to resolution.

ISO 27001 Control A.8.8 requires structured management of technical vulnerabilities. Information about vulnerabilities must be obtained in a timely manner, assessed, and addressed through appropriate measures. The register is the operational tool for this.

What does it contain?

The CSV template covers the lifecycle of a vulnerability from discovery to remediation:

  • Vulnerability ID and CVE reference — unique identifier, optionally linking to the public CVE database
  • Description — what is the vulnerability and how can it be exploited?
  • Severity — critical, high, medium, low (e.g. based on CVSS)
  • Affected assets — which systems are impacted?
  • Owner — who coordinates remediation?
  • Remediation action and deadline — what is being done, by when?
  • Status — open, in progress, remediated, accepted (with justification)

How to use it

Automated discovery as a foundation. Vulnerability scanners (Nessus, OpenVAS, Qualys, or cloud-native services) provide the baseline. Their results flow into the register regularly — ideally automated. Supplement with manually discovered vulnerabilities and penetration test findings.

Assessment and deadline assignment. Every new vulnerability is assessed and assigned a remediation deadline. Define clear SLAs upfront: e.g. critical within 72 hours, high within 14 days, medium within 30 days. These SLAs belong in your vulnerability management policy and are tracked in the register.

Handle exceptions deliberately. Sometimes a patch is not feasible in the short term — the legacy system has no vendor support, or the patch breaks a critical application. In these cases, document a compensating control (network segmentation, additional monitoring, access restriction) and a review date.

Register Template

Vulnerability Register

IDCVETitleProductAffected AssetCVSS v3.1EPSSSeverityDiscoveredSourcePatch AvailableRemediation DeadlineStatusOwnerNotes
VUL-2025-001CVE-2025-21293Windows Kernel Elevation of PrivilegeMicrosoft Windows 10/11 Server 2019/2022AST-005 AST-0047.80.08High2025-01-14MS Patch TuesdayYes2025-02-14ClosedIT Operations LeadPatched via WSUS 2025-01-18
VUL-2025-002CVE-2025-29813Azure DevOps privilege escalation variable groupsAzure DevOps ServicesAST-013 (GitLab CI but Azure DevOps used for one legacy project)10.00.12Critical2025-05-08MSRC advisoryYes2025-05-15ClosedHead of EngineeringMicrosoft hosted patched - verified tenant
VUL-2024-210CVE-2024-38200Microsoft Office NTLM hash disclosureMicrosoft Office 2019/2021/365AST-003 AST-0067.50.21High2024-08-13MS Patch TuesdayYes2024-09-13ClosedIT Operations LeadPatched fleet via Intune
VUL-2025-003CVE-2025-24989Microsoft Power Pages auth bypassMicrosoft Power PagesCustomer portal (Power Pages)8.20.35High2025-02-19MSRC KEVYes (vendor side)N/AClosedHead of EngineeringVendor patched - verified
VUL-2025-004CVE-2025-22224VMware ESXi heap overflowVMware ESXi 7.0/8.0AST-004 AST-005 (hypervisor)9.30.28Critical2025-03-04CISA KEVYes2025-03-18ClosedIT Operations LeadEmergency change EC-2025-003
VUL-2025-005CVE-2025-30397Microsoft Scripting Engine RCE (Edge/Chakra)Microsoft Edge legacyAST-0068.80.15High2025-05-13MS Patch TuesdayYes2025-06-13ClosedIT Operations LeadAuto-update
VUL-2025-006CVE-2024-7971Google Chrome V8 type confusionGoogle ChromeAST-0068.80.88Critical2024-08-21Chrome releaseYes2024-08-28ClosedIT Operations LeadChrome auto-update enforced
VUL-2025-007CVE-2025-20281Cisco IOS XE privilege escalationCisco IOS XEAST-010 (if Cisco - check applicability)6.70.03Medium2025-06-25Cisco PSIRTYes2025-07-25N/AIT Operations LeadNot applicable - Fortinet stack
VUL-2025-008CVE-2025-26633Microsoft Management Console bypassMicrosoft WindowsAST-005 AST-004 AST-0067.00.42High2025-03-11CISA KEVYes2025-04-11ClosedIT Operations LeadPatched via WSUS
VUL-2025-009CVE-2024-3094XZ Utils backdoor (liblzma)xz-utils 5.6.0-5.6.1Internal Linux build servers (2x)10.00.62Critical2024-03-29Debian advisoryYes (downgrade)2024-03-30ClosedIT Operations LeadRolled back to 5.4.6 within hours
VUL-2025-010CVE-2025-32756Fortinet FortiOS stack overflowFortinet FortiOS 7.2/7.4AST-0109.80.71Critical2025-05-13CISA KEVYes2025-05-20ClosedIT Operations LeadEmergency change EC-2025-011
VUL-2025-011CVE-2025-24201Apple WebKit out-of-bounds writemacOS/iOS SafariAST-006 AST-0148.10.11High2025-03-11Apple advisoryYes2025-04-11ClosedIT Operations LeadMDM enforced update
VUL-2025-012CVE-2025-22457Ivanti Connect Secure stack overflowIvanti Connect SecureAST-011 (if Ivanti - check)9.00.55Critical2025-04-03CISA KEVYes2025-04-10N/AIT Operations LeadNot applicable - Fortinet VPN used
VUL-2025-013CVE-2025-29824Windows CLFS driver privilege escalationMicrosoft WindowsAST-005 AST-0047.80.25High2025-04-08MS Patch TuesdayYes2025-05-08ClosedIT Operations LeadPatched via WSUS
VUL-2025-014CVE-2025-3248Langflow missing authentication remote code executionLangflow (internal POC)Internal POC environment9.80.47Critical2025-04-07Horizon3 advisoryYes2025-04-10ClosedHead of EngineeringDecommissioned POC

Sources

ISO 27001 Controls Covered

A.8.8 Management of technical vulnerabilities

Frequently asked questions

What is the difference between a vulnerability and a threat?

A vulnerability is a property of a system that can be exploited (e.g. an unpatched web server, a weak password, a missing firewall rule). A threat is the potential cause of an incident — e.g. an attacker, malware, or a natural event. Only the combination of threat and vulnerability creates a risk.

Does every CVE need to go into the register?

Every CVE that affects a system within your scope belongs in the register — even if you decide not to patch. In that case, document the justification (e.g. compensating control, isolated system, exploitation unlikely). Auditors check whether the decision was conscious and traceable.

How often should I scan for new vulnerabilities?

Continuously. Automated vulnerability scanners deliver regular results. Additionally, subscribe to security advisories from your software vendors and public CVE feeds. Penetration tests complement automated detection — typically at least once a year.