Name of Your Organization:
Beyond Security Ltd.
Web Site:
Adopting Capability:
AVDS
Capability home page:
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 Results Consumer — 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.
AVDS uses OVAL to import benchmarks from the OVAL repository and user-developed XML files and to export assessment results files.
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 OVAL version is indicated in the screen when a pre-defined OVAL Definition is selected or you select to import a new one.
The following questions apply to all capabilities.
Error Reporting <AR_2.1>
Indicate how a user who discovers an error in the capability’s use of OVAL can report the error.
Email to support@beyondsecurity.com
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 AVDS related bugs are sent to support@beyondsecurity.com. When an issue is confirmed a patch is issued and distributed to our customers that are affected.
The following questions apply to all capabilities.
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.
Under the AVDS GUI in the Admin, Scan Setting section under Authenticated Scans the credentials are entered which will authenticate with the device under test. Then the OVAL Definitions are selected or entered that are to be run against the target machine. At this location there is a button that provides additional instructions on how to use this.
Language Support<AR_3.2>
List each supported component schema and specific OVAL Tests in those component schemas that are supported.
The following are supported:
- apache-definitions-schema.xsd
- catos-definitions-schema.xsd
- freebsd-definitions-schema.xsd
- independent-definitions-schema.xsd
- linux-definitions-schema.xsd
- macos-definitions-schema.xsd
- pixos-definitions-schema.xsd
- solaris-definitions-schema.xsd
List any core constructs defined in the OVAL Language that are not supported.
- None
OVAL Assessment Method <AR_3.3>
List each supported assessment method if applicable.
- Query to a database of an endpoint's current configuration settings.
- Assessment of state by a remote-scanning sensor.
OVAL Content Error Reporting <AR_3.4>
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.
All our AVDS related bugs are sent to support@beyondsecurity.com, when an issue is discovered a patch is issued and distributed to our customers that are affected.
The following questions apply to all capabilities.
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.
All our AVDS related bugs are sent to support@beyondsecurity.com, when an issue is discovered a patch is issued and distributed to our customers that are affected.
The following questions apply to only Definition Evaluator capabilities.
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.
When a user wants to use his own custom OVAL Definitions, we import it into our server (database) and run it through OVALDI to provide a syntax matching and verification to the user. If OVALDI produces no errors, we run it through our remote-scanning collecting script to verify that we support all the elements found inside this OVAL object. Any errors produced are return to the user.
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.
All our AVDS feature requests are sent to support@beyondsecurity.com, depending on the complexity of the requirement they are added to our system and deployed to our customers.
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 endpoint.
OVAL Results are sent back inside our regular report and can be gathered through it. Several tests return the relevant output, one returns the OVAL System Characteristics, another the complete OVALDI result (unprocessed) while several other tests return compliance/patch/vulnerability/inventory results.
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 endpoint.
OVAL Results are sent back inside our regular report and can be gathered through it. Several tests return the relevant output, one returns the OVAL System Characteristics, another the complete OVALDI result (unprocessed) while several other tests return compliance/patch/vulnerability/inventory results.
The following questions apply to only Results Consumer capabilities.
Examine Imported Content <AR_9.1> <AR_9.2>
Indicate how users can review OVAL Results that are imported into the product and explain how users can determine which endpoint a particular set of results applies to.
OVAL Results are sent back inside our regular report and can be gathered through it. Several tests return the relevant output, one returns the OVAL System Characteristics, another the complete OVALDI result (unprocessed), while several other tests return compliance/patch/vulnerability/inventory results.
Content Import Process Explanation <AR_9.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.
All our AVDS feature requests are sent to support@beyondsecurity.com, depending on the complexity of the requirement they are added to our system and deployed to our customers.
The following questions apply to only System Characteristics Producer capabilities.
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.
uname_test, textfilecontent54_test, password_test, file_test, environmentvariable_test, variable_test, partition_test, runlevel_test, rpminfo_test, xmlfilecontent_test, dpkginfo_test
Content Export <AR_5.2> <AR_5.3>
Indicate how the product allows users to export OVAL System Characteristics documents.
AVDS stores the OVAL System Characteristics inside a record in the database that can be dumped by the user into a 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: Noam Rathaus
TITLE: Chief Technology Officer
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: Noam Rathaus
TITLE: Chief Technology Officer
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: Noam Rathaus
TITLE: Chief Technology Officer
Page Last Updated: September 25, 2013
