Common vulnerabilities & exposures database (CVE)

Centralised and standardized for hardware & software products

Request demo Free trial White paper
Versio.io offers enterprise customers common vulnerabilities & exposures database (CVE) for hardware and software products. This provides them with a central and standardised source of information for product release management.
In combination with the goverance & compliance module, compliance with customer-specific collection of CVEs can be monitored and verified automatically.

Consolidated and centralised access to hardware and software product release information on enterprise level

Consolidated and centralised access to hardware and software product release information on enterprise level
X

Consolidated and centralised access to hardware and software product release information on enterprise level

Versio.io offers enterprise customers a common vulnerabilities & exposures database for hardware and software products.

Here, Versio.io imports new or changing CVEs from various CVE vendors and manufacturers on a daily basis.

The following advantages result for customers by using the Versio.io CVE database:

  • Centralized and daily updated database
  • Harmonized and standardized data
  • Alerting possibility for specific CVE (e.g. Red Hat Kernel or Tomcat security vulnerability)
  • Generation of compliance rulesets for automated verification
  • Change history over the entire lifecycle of a CVE

 

Set up a security monitoring & alerting for specific CVE collection in a minute

Set up a security monitoring & alerting for specific CVE collection in a minute
X

Set up a security monitoring & alerting for specific CVE collection in a minute

Based on the imported common vulnerabilities & exposures information, customers can select individual groups of CVE and generate a compliance rule set for them.

This allows any future change in vulnerabilities & exposures compliance to be verified. A violation leads to an event and can be alerted.

Reaching a secure security state closes the open event again. This provides a fully automated audit-proof documentation.

 

Traceability of the creation and modification of CVEs

Traceability of the creation and modification of CVEs
X

Traceability of the creation and modification of CVEs

Common vulnerabilities and exposures of hardware and software vendors are usually extended and specified several times.

Versio.io's change detection allows us to record these changes in an audit-proof manner, giving our customers the ability to track and respond to the lifecycle of a CVE.

 

An example of a change history to a CVE

The following screenshot shows the recorded history of CVE-2020-11996. Blue texts indicate changes, green texts are new and red texts are deleted attributes.

Related solutions


Keywords

Common vulnerabilities & exposures database

 

CVE

 

History

 

Topology

 

Database

 

Repository

 

Security

 

Hardware

 

Software

 

Version

 

We use cookies to ensure that we give you the best experience on our website. Click here for more information.