|
|
Name of Your Organization:
Altex-Soft
Web Site:
Compatible Capability:
Altex-Soft Ovaldb
Capability home page:
Product Accessibility <CR_2.4>
Provide a short description of how and where your capability is made available to your customers and the public (required):
Our repository of Open Vulnerability and Assessment Language (OVAL®) content, Altex-Soft Ovald, can be accessed online with a standard web browser.
Map Currency Indication <CR_5.1>
Describe how and where your capability indicates the most recent CVE version used to create or update its mappings (required):
Information about most recent CVE version available at about page http://ovaldb.altx-soft.ru/About.aspx.
Map Currency Update Approach <CR_5.2>
Indicate how often you plan on updating the mappings to reflect the current CVE content and describe your approach to keeping reasonably current with the CVE content when mapping them to your repository (required):
We update CVE entries weekly.
Map Currency Update Time <CR_5.3>
Describe how and where you explain to your customers the timeframe they should expect an update of your capability’s mappings to reflect newly available CVE content (required):
Information about CVE mapping available at about page http://ovaldb.altx-soft.ru/About.aspx.
Map Content Selection Criteria <CR_5.4>
Describe the criteria used for determining the relevance of a given CVE Identifier to your Capability (required):
There is CVE Identifier that used in reference section in oval definition (vulnerability or patch class) in our repository.
Map Currency Update Mechanism <CR_5.4>
Describe the mechanism used for reviewing CVE for content changes (required):
Before releasing to our repository we manually check differences with previous release to determine changes.
Map Content Source <CR_5.5>
Describe the source of your CVE content (required):
- http://nvd.nist.gov/
- Security bulletins and advisories from vendors.
CVE and Compatibility Documentation<CR_4.1>
Provide a copy, or directions to its location, of where your documentation describes CVE and CVE compatibility for your customers (required):
The information about CVE is provided by direct link to official CVE web site. At the about page, http://ovaldb.altx-soft.ru/About.aspx, users can click on the CVE logo to navigate to the CVE web site.
Documentation of Finding Elements Using CVE Names <CR_4.2>
Provide a copy, or directions to its location, of where your documentation describes the specific details of how your customers can use CVE names to find the individual security elements within your capability’s repository (required):
Customers have two ways for find related definitions by CVE name:
The interface is straightforward, explicit document isn't provided.
- Use reference field in search page http://ovaldb.altx-soft.ru/Search.aspx for entering CVE name.
- Use http://ovaldb.altx-soft.ru/ReferencesCVE.aspx page and apply CVE name filter.
Documentation of Finding CVE Names Using Elements <CR_4.3>
Provide a copy, or directions to its location, of where your documentation describes the process a user would follow to find the CVE names associated with individual security elements within your capability’s repository (required):
Users can find CVE names associated with certain oval definition using next steps:
The interface is straightforward, no explicit document is provided.
- Open detailed definition page for definition with vulnerability or patch class using oval definition id as request parameter in the link http://ovaldb.altx-soft.ru/Definition.aspx?id=<ovalDefinitionID> or using search page for find certain definition. For example, http://ovaldb.altx-soft.ru/Definition.aspx?id=oval:org.mitre.oval:def:4374.
- Find References section.
- Find CVE expanders and expand them – you will see details of each CVE.
Type-Specific Capability Questions
Finding Tasks Using CVE Names <CR_A.2.1>
Give detailed examples and explanations of how a user can locate tasks in the tool by looking for their associated CVE name (required):
There are two ways:
- Use reference field in search page http://ovaldb.altx-soft.ru/Search.aspx for entering CVE name.
- Use http://ovaldb.altx-soft.ru/ReferencesCVE.aspx page and apply CVE name filter.
Finding CVE Names Using Elements in Reports <CR_A.2.2>
Give detailed examples and explanations of how, for reports that identify individual security elements, the tool allows the user to determine the associated CVE names for the individual security elements in the report (required):
- Open detailed definition page for definition with vulnerability or patch class using oval definition id as request parameter in the link http://ovaldb.altx-soft.ru/Definition.aspx?id=<ovalDefinitionID> or using search page for find certain definition. For example, http://ovaldb.altx-soft.ru/Definition.aspx?id=oval:org.mitre.oval:def:4374.
- Find References section.
- Find CVE expanders and expand them – you will see details of each CVE.
Service Coverage Determination Using CVE Names <CR_A.3.1>
Give detailed examples and explanations of the different ways that a user can use CVE names to find out which security elements are tested or detected by the service (i.e. by asking, by providing a list, by examining a coverage map, or by some other mechanism) (required):
See <CR_A.2.1>.
Finding CVE Names in Service Reports Using Elements <CR_A.3.2>
Give detailed examples and explanations of how, for reports that identify individual security elements, the user can determine the associated CVE names for the individual security elements in the report (required):
See <CR_A.2.2>.
Finding Online Capability Tasks Using CVE Names <CR_A.4.1>
Give detailed examples and explanations of how a "find" or "search" function is available to the user to locate tasks in the online capability by looking for their associated CVE name or through an online mapping that links each element of the capability with its associated CVE name(s) (required):
See <CR_A.2.1>.
Online Capability Interface Template Usage <CR_A.4.1.1>
Provide a detailed description of how someone can use your "URL template" to interface to your capability’s search function (recommended):
http://ovaldb.altx-soft.ru/Definitions.aspx?reference= CVE-YYYY-NNNN
Finding CVE Names Using Online Capability Elements <CR_A.4.2>
Give detailed examples and explanations of how, for reports that identify individual security elements, the online capability allows the user to determine the associated CVE names for the individual security elements in the report. (required):
See <CR_A.2.2>.
Online Capability Element to CVE Name Mapping <CR_A.4.3>
If details for individual security elements are not provided, give examples and explanations of how a user can obtain a mapping that links each element with its associated CVE name(s), otherwise enter N/A (required):
N/A
Finding Elements Using CVE Names <CR_A.5.1>
Give detailed examples and explanations of how a user can find associated elements in the capability by looking for their associated CVE name (required):
CVE references are used in definitions with vulnerability or patch class.User can find definitions for certain CVE using steps described in <CR_A.2.1>.
Finding CVE Names Using Elements in Reports <CR_A.5.2>
Give detailed examples and explanations of how, for reports that identify individual security elements, the capability allows the user to determine the associated CVE names for the individual security elements in the report (required):
See <CR_A.2.2>.
Electronic Document Format Info <CR_B.3.1>
Provide details about the different electronic document formats that you provide and describe how they can be searched for specific CVE-related text (required):
Search CVE-related text available in HTML format in ovaldb.altx-soft.ru database.
Electronic Document Listing of CVE Names <CR_B.3.2>
If one of the capability’s standard electronic documents only lists security elements by their short names or titles provide example documents that demonstrate how the associated CVE names are listed for each individual security element (required):
Our electronic documents are provided online via HTML. To discover CVE names and their associated definitions, see <CR_A.2.1>.
Finding Elements Using CVE Names Through the GUI <CR_B.4.1>
Give detailed examples and explanations of how the GUI provides a "find" or "search" function for the user to identify your capability’s elements by looking for their associated CVE name(s) (required):
GUI represented by HTML web page. To discover CVE names and their associated definitions, see <CR_A.2.1>.
GUI Element to CVE Name Mapping <CR_B.4.2>
Briefly describe how the associated CVE names are listed for the individual security elements or discuss how the user can use the mapping between CVE entries and the capability’s elements, also describe the format of the mapping (required):
See <CR_A.2.2>.
Statement of Compatibility <CR_2.7>
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 CVE Compatibility Requirements as well as all of the additional mandatory CVE Compatibility Requirements that are appropriate for our specific type of capability."
Name: Sergey Artykhov
Title: R&D Director
Statement of Accuracy <CR_3.4>
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 mapping between our capability’s Repository and the CVE entries our capability identifies."
Name: Sergey Artykhov
Title: R&D Director
Statement on False-Positives and False-Negatives <CR_A.2.8 and/or CR_A.3.5>
FOR TOOLS ONLY - Have an authorized individual sign and date the following statement about your tools efficiency in identification of security elements (required):
"As an authorized representative of my organization and to the best of my knowledge, normally when our capability reports a specific security element, it is generally correct and normally when an event occurs that is related to a specific security element our capability generally reports it."
Name: Sergey Artykhov
Title: R&D Director