Account Links: Cart | Register | Log In

Skip to content

Security Measurement

The Red Hat Security Response Team are committed to providing tools and data to help security measurement. Part of this commitment is our participation at board level in the Mitre CVE and OVAL projects. We also provide reports and metrics, but more importantly we also provide the raw data so that customers and researchers can produce their own metrics for their own unique situations and hold us accountable.

OVAL Definitions

OVAL definitions are available for all vulnerabilities that affect Red Hat Enterprise Linux 3, 4, 5

Vulnerability Statements

The Red Hat Security response team publish official statements for vulnerabilities currently under investigation and for vulnerabilities that do not affect us. These are also available directly from the National Vulnerability Database

Vulnerability Data

CVE to date and CVE to severity mapping

This data source is a mapping of the CVE name to the date that the issue was first known to the public. This can help generate statistics based on "days of risk". We also use this data source to capture the severity of issues and how we found out about the issue (date and source). Although the dates may come from third parties, the severity classifications are given by the Red Hat Security Response team and are specific to Red Hat and will vary for other distributions and vendors). This file is created manually and we update it every week or two (or by request by contacting secalert@redhat.com).

RHSA to date mapping

This data source is a mapping of Red Hat Security Advisories to the date and time the advisory was issued. Most of this data comes automatically from the Red Hat Network, but we've annotated a few entries which needed manual adjustment

RHSA to CVE and CPE mapping

This data source is a mapping of Red Hat Security Advisories to the vulnerabilities fixed, identified by CVE name. The file contains the product names affected in CPE format (with package name appended) so the file can be filtered by a product or package subset.

CPE list for default installations

Red Hat Enterprise Linux ships with a large number of packages, but they are not all installed by default. These files give lists of packages in default installations which can be used to filter the metrics (format is CPE name with package name appended)

CPE Dictionary

CPE is a structured naming scheme for information technology systems, software, and packages. For reference we provide a dictionary mapping official CPE names to Red Hat product descriptions

Data Analysis

This Perl script is designed to run reports based on the data sources cve_dates, release_date, and rhsamapcpe above. For a given product, such as Red Hat Enterprise Linux, and date range it can list all the issues fixed by severity and give a "days of risk" metric as well as vulnerability workflow statistics. For example, run

perl daysofrisk.pl --cpe enterprise_linux:5 --severity C

Sample Reports

Based on the above data sets and using daysofrisk.pl you can run sample reports. Here are some pre-generated examples:

DistributionDatesSeverityMetrics
Red Hat Enterprise Linux 3 (all packages)20031204-20090105all dates
Critical flaws
126 vulnerabilities
Average is 2.6 days
Median is 1 days
83% were within 1 day
Red Hat Enterprise Linux 4 (all packages)20050215-20090105all dates
For all flaws regardless of severity
1243 vulnerabilities
Average is 71.1 days
Median is 15 days
31% were within 1 day
Red Hat Enterprise Linux 4 AS (default installation packages) 20050215-20090105all dates
Critical flaws
11 vulnerabilities
Average is 1.8 days
Median is 0 days
90% were within 1 day
Red Hat Enterprise Linux 5 Server (default installation packages) 20070314-20090105all dates
For all flaws regardless of severity
373 vulnerabilities
Average is 60.3 days
Median is 1 days
50% were within 1 day
Red Hat Enterprise Linux 5 (all packages)20070314-20090105all dates
Critical flaws
64 vulnerabilities
Average is 0.5 days
Median is 1 days
100% were within 1 day

Other Analysis

Risk Report: Three years of Red Hat Enterprise Linux 4

Red Hat Magazine looks at the state of security for the first three years from release on Feb 15th 2005, including metrics, key vulnerabilities, and the most common ways users were affected by security issues.

Mark Cox metrics weblog

Security Response Director Mark Cox publishes a weblog with insight into security measurement and metrics for Red Hat products.