Important: The OVAL Compatibility Program was moved to "archive" status in December 2009, and replaced with the "OVAL Adoption Program." Under the OVAL Adoption Program product validation is performed by an external organization, allowing the OVAL Team to focus on educating vendors on best practices regarding the use and implementation OVAL and on how OVAL can continue to evolve as needed by the community.
Refer to the OVAL Adoption Program section for addition information and to review all products and services listed.
Name of Your Organization:
Red Hat, Inc
Red Hat Security Advisories
OVAL Definition Producer
Product/Service Home Page:
General Capability Questions
Provide a short description of how and where your capability is made available to your customers and the public (required):
OVAL definitions for Red Hat Enterprise Linux 3 and 4 errata are
available individually and as a complete archive, updated within
an hour of each new security advisory being made available on the
Red Hat Network. The URL is currently
Language Version Indication
Describe how and where the capability indicates the version of the OVAL Language used to validate, create, or update its content. (required):
Approach for Correction of Errors
Indicate how a user who discovers an error in the capability's use of OVAL can report the error. (required):
Describe the approach to responding to the above error reports and how applicable fixes will be applied. (required):
Definitions are automatically created. Any flaws in our creation scripts can be made and definitions repushed. If necessary we can cause all definitions to be regenerated (this will automatically increment the version of each definition)
Provide a copy, or directions to its location, of where the documentation describes OVAL, OVAL compatibility and/or OVAL-ID compatibility for your customers (required):
Capability Specific Questions
Finding Elements Using OVAL
Provide details regarding how users can identify and find individual OVAL content (through OVAL-IDs) that is being consumed by the capability. For example, how can a user determine which definitions have been consumed and what the result of each definition is. (required):
Each OVAL-ID maps directly to a Red Hat Security Advisory. For example a Red Hat Security advisory RHSA-2006:0425 would have the OVAL-ID oval:com.redhat.rhsa:def:20060425 and hence the filename com.redhat.rhsa-20060425.xml
Questions for Signature
Statement of Compatibility
Have an authorized individual sign and date the following Compatibility Statement (required):
"As an authorized representative of my organization I agree that we will abide by all of the mandatory compatibility requirements as well as all of the additional mandatory compatibility requirements that are appropriate for our specific type of capability."
||Mark J. Cox
Statement of Accuracy
Have an authorized individual sign and date the following accuracy Statement (recommended):
"As an authorized representative of my organization and to the best of my knowledge, there are no errors in the correctness of our capability's use of the OVAL Language and the interpretation of the logic."
||Mark J. Cox
Statement on Follow-on Correctness Testing Support
Have an authorized individual sign and date the following statement about your organizations willingness to support correctness testing of other capabilities, which will be managed by the Reviewing Authority and kept to reasonable levels of effort for all involved. (required):
"As an authorized representative of my organization, we agree to support the Review Authority in follow-on correctness testing activities, where appropriate types of OVAL documents might need to be exchanged with other organizations attempting to prove the correctness of their capabilities."
||Mark J. Cox