Vulnerability Database
What is Vulnerability Database?
A repository of known security vulnerabilities with details including severity ratings, affected systems, and available patches or workarounds.
Terms that appear alongside vulnerability database
Each of these is named in at least one of the same controls as vulnerability database. The number is how many controls name both.
- vulnerability 6 shared controls
- enisa 3 shared controls
- vulnerability disclosure 2 shared controls
- asset discovery 2 shared controls
- vulnerability scanning 2 shared controls
Frameworks that govern vulnerability database
What the standards actually require on vulnerability database
Requirements naming vulnerability database across 6 standards, quoted from the control text.
A vulnerability scanner with an up-to-date vulnerability database is used for vulnerability scanning activities. Required at Maturity Levels One, Two and Three of the Patch applications mitigation strategy (Appendices A, B and C);
acsc-essential-eight::E8-PATCHAPP-ISM-1808 · Patch applications (ISM-1808): A vulnerability scanner with an up-to-date vulnerability database is used for vulnerability scanning activities →A vulnerability scanner with an up-to-date vulnerability database is used for vulnerability scanning activities.
ISM-1808 · Up-to-date vulnerability database for scanning →The advisory should reference related information: other vendors' advisories, coordinator publications, vulnerability database entries and the vendor's knowledge base.
iso-iec-29147-2018::7.4.13 · 7.4.13 References →For each zone and conduit, vulnerabilities are identified from vulnerability assessments, prior audits and vulnerability databases, including the assumption that unknown and unpatched vulnerabilities exist in the attack surface the zone exposes.
iec-62443::ZCR 5.2 · ZCR 5.2 Identify vulnerabilities →A PSIRT should watch the public sources where vulnerability information is known to appear (mailing lists, social media, discussion forums, vulnerability databases) for disclosures or discussion that concern the vendor's products or services.
iso-iec-30111-2019::6.5.3.2 · 6.5.3.2 Public vulnerability monitoring →Two duties travel together in this point. The first is that security is built into how systems are acquired, developed and maintained: security requirements set before purchase or build, secure development practice, change control, and maintenance that does no...
nis2-directive::Art.21.2.e · Security in acquisition, development and maintenance, including vulnerability handling and disclosure →Questions people ask about vulnerability database
What is Vulnerability Database?
Why is Vulnerability Database important for compliance?
Which compliance frameworks address Vulnerability Database?
Where can I learn more about Vulnerability Database?
See how Vulnerability Database applies across compliance frameworks
Our platform maps 1,016 frameworks with 316K cross-framework control mappings. Explore how this concept is addressed across standards.