Name of Your Organization:
eEye Digital Security
Web Site:
Adopting Capability:
Retina
Capability home page:
http://www.eeye.com/products/retina
Adoption Capabilities
If the functionality is available now, indicate "Yes." If it has been implemented but not released, indicate "Beta". If planned but not currently available, indicate "Planned". If there are no plans for a specific category, that section(s) is not included as part of the questionnaire below.
OVAL Definition Evaluator — Yes
OVAL Systems Characteristics Producer — Yes
Product Accessibility <AR_1.9>
Provide a short description of how and where your capability is made available to your customers and the public.
The product is available via a commercial license, and can be downloaded from our client web site.
Language Version Indication <AR_1.10>
Describe how and where the capability indicates the version of the OVAL Language used to validate, create, or update its content.
The product supports OVAL Versions 5.3, 5.4, 5.5, 5.6, 5.7, and 5.8.
Error Reporting <AR_2.1>
Indicate how a user who discovers an error in the capability’s use of OVAL can report the error.
Customers who discover an error in the use of OVAL can open a support helpdesk ticket. The product also contains a "Package Support Files" option which allows the customer to easily submit information relevant to the issue.
Responding to Error Reports <AR_2.2>
Describe the approach to responding to the above error reports and how applicable fixes will be applied.
All potential errors are investigated by the technical support department. If a defect is confirmed, it is submitted to development team to be evaluated and fixed. Upon release of the fix, the customer can use the products built in auto-update functionality to apply the latest version.
Adoption Documentation <AR_3.1>
Provide a copy, or directions to the location, of where the documentation describes OVAL and OVAL Adoption for any customers.
The Retina User’s Guide covers OVAL and other SCAP related functionality within Chapter 13 "SCAP Scanning".
Language Support <AR_3.2>
List each supported component schema and specific OVAL Tests in those component schemas that are supported. (AR_3.2)
The following independent tests are not supported: filehash_test, environmentvariable_test, ldap_test, sql_test, textfilecontent_test, xmlfilecontent_test.
Tests, Objects, States, and Variables not used by Windows Platform are currently not supported.
OVAL Content Error Reporting <AR_3.3>
Provide a copy, or directions to the location, of where the documentation describes the procedure by which errors in OVAL content may be reported for any OVAL content that is produced by the product.
Customers who discover an error in the OVAL output content can open a support helpdesk ticket.
Syntax Error Detection and Reporting <AR_4.1> <AR_4.2> <AR_4.3> <AR_4.4>
Indicate how the product or repository detects and reports syntax errors in any OVAL content that is consumed by the product or repository.
An in-product warning is displayed when selecting any OVAL content that does not pass XML Schema or Schematron validation. The user can then view syntax error details within an output log file.
Type-Specific Capability Questions
Content Transparency <AR_8.1> <AR_8.2>
Indicate how the product allows users to determine which OVAL Definitions are being evaluated and examine the details of those definitions.
Each scanned target has an associated OVAL Results Document. Details on all OVAL Definitions are included under <oval-def:definitions /> node in the OVAL Results Document. Users can also view human readable reports based off of the OVAL Results Document.
Content Import Process Explanation <AR_8.3>
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.
The product allows for OVAL content to be consumed at runtime. This is achieved by the end user placing OVAL content directly into a specified directory. The OVAL content must be associated with an XCCDF benchmark file.
Content Evaluation <AR_8.4> <AR_8.5> <AR_8.6> <AR_8.7>
Indicate how users can review the detailed results of evaluating an OVAL Definition on a target system.
Each scanned target has an OVAL Results Document. Users can refer to data within the <results /> node for detailed results of OVAL Definition on the target system. Users can also view human readable reports based off of the OVAL Results Document.
Full OVAL Results <AR_8.8>
Indicate how users can review the full OVAL Results of the evaluation of an OVAL Definition on a target system.
Each scanned target has an OVAL Results Document. OVAL definition results are stored under results/system/definitions node within the OVAL Results Document. OVAL output includes one result per definition and also covers detailed criteria results for each definition. Users can also view human readable reports based off of the OVAL Results Document.
Collecting System Data <AR_5.2> <AR_5.3>
Explain the criteria used to collect system data that is included in an OVAL System Characteristics document.
Each scanned target generates an OVAL output xml file. System data is included under <oval-sc:oval_system_characteristics /> node in the OVAL output file. Users can also view human readable reports based off of the OVAL output xml file.
Content Export <AR_5.2> <AR_5.3>
Indicate how the product allows users to export OVAL System Characteristics documents.
Each scanned target generates an OVAL output xml file. The user can import system information and collected OVAL objects data from the OVAL output xml file.
Adoption Signature
Statement of Adoption <AR_1.2>
"As an authorized representative of my organization I agree that we will abide by all of the mandatory adoption requirements as well as all of the additional mandatory adoption requirements that are appropriate for our specific type of capability."
NAME: Chris Silva
TITLE: Chief Architect
Statement of Accuracy <AR_1.2>
"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: Chris Silva
TITLE: Chief Architect
Statement on Follow-On Correctness Testing Support <AR_1.7>
"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: Chris Silva
TITLE: Chief Architect
Page Last Updated: May 04, 2011
