Name of Your Organization:
Positive Technologies CJSC
Web Site:
Adopting Capability:
Positive Technologies OVAL Repository
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 Repository — 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.
Positive Technologies OVAL Repository can be accessed at http://oval.ptsecurity.com.
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 Definitions use version 5.10, and lower versions are supported for backward compatibility.
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 can open a support ticket using help desk system (https://support.ptsecurity.ru).
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 issues are investigated by the technical support team. If a defect is confirmed, it’ll be fixed by the development team. Customers will be informed through the support ticket, and the ticket is closed as far as the fix is satisfactory.
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.
http://oval.ptsecurity.com/about
Language Support <AR_3.2>
List each supported component schema and specific OVAL Tests in those component schemas that are supported. (AR_3.2)
Positive Technologies OVAL Repository is compliant to schema version 5.10, and all the schema’s Tests, Objects, States, Variables are supported.
- aix-definitions-schema.xsd (yes)
- interim_fix_test
- fileset_test
- fix_test
- apache-definitions-schema.xsd (yes)
- httpd_test
- catos-definitions-schema.xsd (yes)
- line_test
- module_test
- version55_test
- version_test
- esx-definitions-schema.xsd (yes)
- patch56_test
- patch_test
- version_test
- visdkmanagedobject_test
- freebsd-definitions-schema.xsd (yes)
- portinfo_test
- hpux-definitions-schema.xsd (yes)
- getconf_test
- ndd_test
- patch53_test
- patch_test
- swlist_test
- trusted_test
- independent-definitions-schema.xsd (yes)
- family_test
- filehash_test
- filehash58_test
- environmentvariable_test
- environmentvariable58_test
- ldap_test
- ldap57_test
- sql_test
- sql57_test
- textfilecontent54_test
- textfilecontent_test
- variable_test
- xmlfilecontent_test
- ios-definitions-schema.xsd (yes)
- global_test
- interface_test
- line_test
- snmp_test
- tclsh_test
- version55_test
- version_test
- linux-definitions-schema.xsd (yes)
- dpkginfo_test
- iflisteners_test
- inetlisteningservers_test
- partition_test
- rpminfo_test
- rpmverify_test
- rpmverifyfile_test
- rpmverifypackage_test
- selinuxboolean_test
- selinuxsecuritycontext_test
- slackwarepkginfo_test
- macos-definitions-schema.xsd (yes)
- accountinfo_test
- diskutil_test
- inetlisteningservers_test
- inetlisteningserver510_test
- nvram_test
- plist_test
- plist510_test
- pwpolicy_test
- pwpolicy59_test
- pixos-definitions-schema.xsd (yes)
- line_test
- version_test
- sharepoint-definitions-schema.xsd (yes)
- spwebapplication_test
- spgroup_test
- spweb_test
- splist_test
- spantivirussettings_test
- spsiteadministration_test
- spsite_test
- spcrawlrule_test
- spjobdefinition_test
- spjobdefinition510_test
- bestbet_test
- infopolicycoll_test
- spdiagnosticsservice_test
- spdiagnosticslevel_test
- sppolicyfeature_test
- sppolicy_test
- solaris-definitions-schema.xsd (yes)
- isainfo_test
- ndd_test
- package_test
- packagecheck_test
- patch54_test
- patch_test
- smf_test
- unix-definitions-schema.xsd (yes)
- dnscache_test
- file_test
- fileextendedattribute_test
- gconf_test
- inetd_test
- interface_test
- password_test
- process_test
- process58_test
- routingtable_test
- runlevel_test
- sccs_test
- shadow_test
- sysctl_test
- uname_test
- xinetd_test
- windows-definitions-schema.xsd (yes)
- accesstoken_test
- activedirectory_test
- activedirectory57_test
- auditeventpolicy_test
- auditeventpolicysubcategories_test
- cmdlet_test
- dnscache_test
- file_test
- fileauditedpermissions53_test
- fileauditedpermissions_test
- fileeffectiverights53_test
- fileeffectiverights_test
- group_test
- group_sid_test
- interface_test
- lockoutpolicy_test
- metabase_test
- passwordpolicy_test
- port_test
- printereffectiverights_test
- process_test
- process58_test
- registry_test
- regkeyauditedpermissions53_test
- regkeyauditedpermissions_test
- regkeyeffectiverights53_test
- regkeyeffectiverights_test
- service_test
- serviceeffectiverights_test
- sharedresource_test
- sharedresourceauditedpermissions_test
- sharedresourceeffectiverights_test
- sid_test
- sid_sid_test
- uac_test
- user_test
- user_sid55_test
- user_sid_test
- volume_test
- wmi_test
- wmi57_test
- wuaupdatesearcher_test
Core constructs defined in the OVAL Language that are not supported.
- None
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 can open a support ticket using help desk system (https://support.ptsecurity.ru). All issues are investigated by the technical support team. If a defect is confirmed, it’ll be fixed by the development team. Customers will be informed through the support ticket, and the ticket is closed as far as the fix is satisfactory. Directions to report errors to help desk are given to customers at http://oval.ptsecurity.com/about.
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.
The OVAL content from the repository is tested and validated against W3C XML Schema and Schematron rules.
Type-Specific Capability Questions
Unique IDs <AR_6.1> <AR_6.2> <AR_6.3>
Describe the process by which IDs are assigned and managed in the repository and how global uniqueness of IDs is ensured.
All the definitions in the Positive Technologies OVAL Repository are assigned with unique ID. The assigned IDs are not modified. The repository management tool will ensure that ID’s assigned are unique.
Content Versioning <AR_6.4>
Describe the process by which the versions of Definitions, Tests, Objects, States, and Variables are managed in the repository.
For each modification of Definitions, Tests, Objects, States or Variables, the version is incremented, and also the versions for the referencing Tests, Objects, States or Variables are updated.
Standard References <AR_6.6> <AR_6.7> <AR_6.8>
Indicate how and when CVE-IDs, CCE-IDs, and CPE-IDs are used as references on OVAL Definitions in the repository.
Configuration checking definitions include CCE-ID as a reference. Inventory definitions include CPE-ID as a reference. Vulnerability definitions include CVE-ID as a reference.
Content Updates <AR_6.9>
Describe the process by which users can retrieve content updates.
Users can retrieve the content through Positive Technologies OVAL Repository search interface.
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: Andrew Abramov
TITLE: Head of Promising Developments Department
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: Andrew Abramov
TITLE: Head of Promising Developments Department
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: Andrew Abramov
TITLE: Head of Promising Developments Department
Page Last Updated: May 16, 2012
