Compatibility Questionnaire: Opsware (Server Automation System (SAS)) — Archive

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.

Organizational Information

Name of Your Organization:

Opsware, Inc.

Web Site:

Product Information

Product/Service Name:

Opsware (Server Automation System (SAS))

Compatible Categories:

OVAL Definition Consumer

Product/Service Home Page:

General Capability Questions

Product Accessibility

Provide a short description of how and where your capability is made available to your customers and the public:

The product can be obtained by contacting the Opsware sales force:

For sales inquiries, please contact:

United States:
Western Region: Deirdre Boyle - (408) 744-7514
Central Region: Peter Kern - (408) 744-7310
Eastern Region: Victor Espino - (408) 744-7318
Federal: Milan Hemrajani - (814) 404-2509

For EMEA and APAC inquiries please send requests for contact or information to

Accuracy Questions

Language Version Indication

Describe how and where the capability indicates the version of the OVAL Language used to validate, create, or update its content:

Each OVAL Definition used will be tagged with the version of OVAL used to generate it. So, this information will be in the product associated with each end-result object.

Approach for Correction of Errors

Indicate how a user who discovers an error in the capability's use of OVAL can report the error:

Contact Opsware Customer Support ( referencing the TON Subscription Service.

Describe the approach to responding to the above error reports and how applicable fixes will be applied:

Support will provide a trouble ticket for the issue; this ticket will be escalated through the TON Engineering team and incorporated in a future release of the content.

Documentation Questions

Compatibility Documentation

Provide a copy, or directions to the location, of where the documentation describes OVAL and OVAL Compatibility for any customers:

None; this is still under generation.

Language Support

Indicate the component schemas and/or individual OVAL Tests that the capability does not support for each category of OVAL Compatibility being applied for:

In the windows File Object, SAS doesn't support the 'development-class' attribute. We have an open issue to address it going forward in a later release of the product.

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:

In the Opsware Server Automation System, customers browse vulnerability checks in a tree structure. The CVE ID of each vulnerability is listed in the vulnerability's name.

The OVAL Test ID is referenced inside the individual check source code.

OVAL Content Importation Process Explanation

If the capability does not support consuming OVAL content at runtime, explain the documented process by which users can submit OVAL content for interpretation by the capability, including how quickly submitted content is made available to the capability:

Opsware Support can create a content request ticket for content requests; these requests can be released within 6 weeks of the request.


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."

Name:   Alex Quilter
Title:   Sr. Engineering Manager

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."

Name:   Alex Quilter
Title:   Sr. Engineering Manager

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."

Name:   Alex Quilter
Title:   Sr. Engineering Manager

Page Last Updated: December 17, 2009