Chapter 1. Overview
Red Hat Product Security is committed to providing tools and security data to help you better understand security threats. This data has been available on our Security Data
page and is now also available in a machine-consumable format with the Security Data API. This service allows customers to programmatically query the API for data that was previously exposed only through files on our Security Data page.
The data provided by the Security Data API is the same as what is found on the Security Data page: Common Security Advisory Framework (CSAF) documents, OVAL v2 (OVAL streams) and CVE data. Using the API the data can be fetched in JSON or XML format.
This effort is a part of Red Hat Product Security’s commitment to providing security data to customers in an easy-to-use format.
Please Note: Only one version will be maintained and any changes will be noted in the documentation.
The Security Data API is provided for information and metrics purposes. For any questions or concerns with the API or the data it provides, please contact Red Hat Product Security
.
Base URL
https://access.redhat.com/hydra/rest/securitydata
https://access.redhat.com/hydra/rest/securitydata
Supported Formats
The API supports JSON, XML, and HTML formats. The format can be specified as an extension to the url like .json or .xml.
Compressed 'gzip' Responses
By default, responses are returned in compressed 'gzip' format. Most browsers and download utilities will automatically unzip the response data. If uncompressed response data is required, the query parameter isCompressed=false
may be added to the query URL. (See the individual sections for parameter descriptions and sample query URLs.)
Deprecation Notices
The Common Vulnerability Reporting Framework (CVRF) format is now deprecated and no longer supported. See the CVRF compatibility FAQ. Users of this format should migrate to the Common Security Advisory Framework (CSAF) format.
OVAL v1 files are deprecated and no longer available. See the OVAL v1 deprecation announcement for more information. Users of this format should migrate to OVAL v2 (OVAL streams).