Compatibility > Compatibility Questionnaire: PatchLink Corporation (PatchLink OVAL Add-In (Special Edition), Version 6.3)

Compatibility Questionnaire: PatchLink Corporation (PatchLink OVAL Add-In (Special Edition), Version 6.3) — 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:

PatchLink Corporation

Web Site:

http://www.patchlink.com/

Product Information

Product/Service Name:

PatchLink OVAL Add-In (Special Edition), Version 6.3

Compatible Categories:

OVAL Systems Characteristics Producer
OVAL Systems Characteristics Consumer
OVAL Definition Consumer
OVAL Results Producer
OVAL Results Consumer

Product/Service Home Page:

http://www.patchlink.com/products
General Capability Questions

Product Accessibility

Provide a short description of how and where your capability is made available to your customers and the public:
OVAL Add-In (Special Edition, Version 6.3) will be available for free download from Patchlink's website (http://www.patchlink.com/downloads/index.html) with unlimited clients, unlimited private or commercial use for a minimum of 18 months with registeration of the product.
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:

By Navigating to /OVAL/MaintainanceSchema.aspx the schema used for validation is displayed.

By Navigating to /OVAL/ElementPedigree.aspx the import Schema Versions are displayed.

Definitions will be exported as the highest number schema version listed there. This assumes backward compatibility will occur with Schema changes.

Approach for Correction of Errors

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

The user report problems via either:

OVAL\ResultsProblemReports.aspx, or OVAL\ObjectsProblemReports.aspx

Describe the approach to responding to the above error reports and how applicable fixes will be applied:
The reports will be acted upon by the website administrator, or automatically forwarded to PatchLink Support (if under a service contact). The administrator may configure email contact information to have problems automatically forwarded to the definition's owner (i.e. interpreter or definition). Fixes are automatically incorporated from the definition's owner feed/drop site.
Documentation Questions

Compatibility Documentation

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

See attached PDF's
* PatchLink OVAL Add-In.Pdf
* OVAL Services Proposal.Pdf

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:
All schemas and tests are supported on the website and in the database. The client component schemas and/or individual OVAL Tests are aspects of the 3rd party clients that are selected by the user.
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:
The web page, OVAL/ClientDetail.aspx allows listing by definitiontype and state for individual computer. OVAL/ResultsSummary.aspx shows the overall state of all computers and allow a click-thru to OVAL/ResultsDetail.asp which can list the individual results and computers that have them.

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:
OVAL content(Definitions) may be uploaded by /OVAL/AutoUpdates.aspx. The definitions are consolidated with prior definitions (supports deltas). The new defintions (if valid) becomes immediately available from OVAL/OSDefinition.aspx.
Statements

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:   Ken Lassesen
Title:   Consulting Architect

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 OVAL schema and logic."

Name:   Ken Lassesen
Title:   Consulting Architect

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:   Ken Lassesen
Title:   Consulting Architect

Page Last Updated: December 17, 2009