|
|
Name of Your Organization:
CXSecurity
Web Site:
Compatible Capability:
World Laboratory of Bugtraq 2
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 vulnerability database is accessible to the general public at our web site:(http://cxsecurity.com). The WLB2 Database contains CVE and CWE references that are updated every day.
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):
We provide CVE information in our rule help information: http://cxsecurity.com/wlb/about/#cve.
Map Currency Update Approach <CR_5.2>
Indicate how often you plan on updating the mappings to reflect new CVE versions and describe your approach to keeping reasonably current with CVE versions when mapping them to your repository (required):
Mappings are updated constantly by obtaining the latest mapping file and we monitor changes to CVE on a daily basis.
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):
We supply RSS feeds to inform our customers.
Our time frame for CVE mappings:
- 2.00 AM CET
- 2.00 PM CET
Map Content Selection Criteria <CR_5.4>
Describe the criteria used for determining the relevance of a given CVE Identifier to your Capability (required):
- references
- vendors
- products
Map Currency Update Mechanism <CR_5.4>
Describe the mechanism used for reviewing CVE for content changes (required):
Manually checking differences with previous release to determine changes before releasing to our database. The CVE MAP is generating automatically.
Map Content Source <CR_5.5>
Describe the source of your CVE content (required):
CXSecurity Team maintains the vulnerability database and determines any relevance. From last list of CVE changes (NVD/CVE XML 1.2).
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):
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):
http://cxsecurity.com/wlb/about#cve
Use the search form: http://cxsecurity.com/cve/
Or using syntax:
http://cxsecurity.com/cveshow/CVEYYYYNNNN
http://cxsecurity.com/issue/CVEYYYYNNNNExample: http://cxsecurity.com/cveshow/CVE20090689/
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):
http://cxsecurity.com/wlb/about#cve
Use the search form: http://cxsecurity.com/cve/
The CVE name of a vulnerability, if available, is displayed in the "Details" tab of the WLB2 Database.
Example: http://cxsecurity.com/issue/WLB2011050133
CVERELATED
List: http://cxsecurity.com/cvelist/
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):
The User can use the search form: http://cxsecurity.com/cve/
Associated vulnerabilities will be presented as the search results.
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):
In each WLB2 record.
Example: http://cxsecurity.com/issue/WLB2011050133
The user will see:
- Topic: Multiple Vendors libc/fnmatch(3) DoS (incl apache poc)
- Credit: Maksymilian Arciemowicz
- Date: 2011.05.13
- CWE: CWE399
- (Show similar)
- CVE: CVE20110419
- Risk: Medium
- Local: Yes
- Remote: Yes
- History: [20110513]
- Started
In each CVEMAP record
Example: http://cxsecurity.com/cveshow/CVE20090689/
Vulnerability CVE20090689
Getting a List of CVE Names Associated with Tasks <CR_A.2.4>
Give detailed examples and explanations of how a user can obtain a listing of all of the CVE names that are associated with the tool’s tasks (recommended):
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):
http://cxsecurity.com/cve/
CVERELATED
list: http://cxsecurity.com/cvelist/
CVEMAP: http://cxsecurity.com/cvemap/
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):
The CVE Identifiers of a vulnerability, if available, is displayed in the "Details" tab of the WLB2 Database.
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):
The User can use the search form: http://cxsecurity.com/cve/
Associated vulnerabilities will be presented as the search results.
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):
CVEMAP: http://cxsecurity.com/cveshow/[CVEYYYYNNNN]
WLB2: http://cxsecurity.com/issue/[CVEYYYYNNNN]
Online Capability CGI GET Method Support <CR_A.4.1.2>
If the URL template is for a CGI program, does it support the HTTP "GET" method? (recommended):
Yes
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):
In each security advisory, there is a ‘Details’ section which will provide a direct mapping to the CVE website.
Example: http://cxsecurity.com/issue/WLB2011050133
The user will see:
- Date: 2011.05.13
- CWE: CWE399
- (Show similar)
- CVE: CVE20110419
Finding Elements Using CVE Names <CR_A.5.1>
Give detailed examples and explanations of how a user can associated elements in the capability by looking for their associated CVE name (required):
GET: http://cxsecurity.com/cveshow/[CVEYYYYNNNN]
POST: http://cxsecurity.com/cve/
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):
Using: http://cxsecurity.com/searchwlb/
Example: CVE20110762
Each advisories related with CVE Identifiers, should be returned.
Getting a List of CVE Names Associated with Tasks <CR_A.5.4>
Give detailed examples and explanations of how a user can obtain a listing of all of the CVE names that are associated with the capability’s tasks (recommended):
Selecting Tasks with a List of CVE Names <CR_A.5.5>
Describe the steps and format that a user would use to select a set of tasks by providing a file with a list of CVE names (recommended):
The WLB2 ID assigned with CVERELATED: http://cxsecurity.com/cvelist/
CVEMAP: http://cxsecurity.com/cvemap/
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):
WLB2 Database is provided in HTML on the CXSecurity website: http://cxsecurity.com/wlb/
CVEMAP Database is provided in HTML on the CXSecurity website: http://cxsecurity.com/cvemap/
By accessing the search page: http://cxsecurity.com/searchwlb/
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):
The associated CVE name is listed prominently in the "Details" tab of a WLB2 Database entry.
In CVEMAP: http://cxsecurity.com/cvemap/
In CVEMAP product list (example for PHP): http://cxsecurity.com/cveproduct/81/php/
Electronic Document Element to CVE Name Mapping <CR_B.3.3>
Provide example documents that demonstrate the mapping from the capability’s individual elements to the respective CVE name(s) (recommended):
- http://cxsecurity.com/issue/WLB2011050133
- http://cxsecurity.com/issue/WLB2011030139
- http://cxsecurity.com/issue/WLB2011070105
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):
By accessing the search page: http://cxsecurity.com/searchwlb/
By accessing the search page for CVE: http://cxsecurity.com/cve/
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):
The associated CVE name is listed prominently in the "Details" tab of a WLB2 Database entry.
GUI Export Electronic Document Format Info <CR_B.4.3>
Provide details about the different electronic document formats that you provide for exporting or accessing CVE-related data and describe how they can be searched for specific CVE-related text (recommended):
HTML and RSS formats are available.
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: Maksymilian Arciemowicz
Title: Security Officer
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: Ewa Michalak
Title: Project manager
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: Maksymilian Arciemowicz
Title: Security Officer