|
|
Name of Your Organization:
SecurityTracker
Web Site:
http://securitytracker.com/
Compatible Capability:
SecurityTracker
Capability home page:
http://securitytracker.com/
1) 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):
SecurityTracker alerts are available to the general public at our public web site (http://securitytracker.com/) and also to our subscription customers on a secure web site.
4) 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):
The SecurityTracker site does not currently indicate the CVE version used. We update our database based on additions to CVE that occur between official CVE revisions.
5) 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 (recommended):
We monitor changes to CVE on a daily basis. The time frame for updating the alerts with CVE data varies.
6) 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 a newly released CVE version (recommended):
The time frame for updating the alerts with CVE data varies. A description is available at:
http://www.securitytracker.com/help/faq.html
7) 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):
A brief description is available at:
http://www.securitytracker.com/help/faq.html
8) 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):
A brief description is available at:
http://www.securitytracker.com/help/faq.html
9) 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):
A brief description is available at:
http://www.securitytracker.com/help/faq.html
10) Documentation Indexing of CVE-Related Material <CR_4.4>
If your documentation includes an index, provide a copy of the items and resources that you have listed under "CVE" in your index. Alternately, provide directions to where these "CVE" items are posted on your web site (recommended):
An index listing of our alerts that contain CVE numbers is planned for a future release.
11) Candidates Versus Entries Indication <CR_6.1>
If CVE candidates are supported or used, explain how you indicate that candidates are not accepted CVE entries (required):
We mark the entry using either the "CAN-" designation or the "CVE-" designation.
12) Candidates Versus Entries Explanation <CR_6.2>
If CVE candidates are supported or used, explain where and how the difference between candidates and entries is explained to your customers (recommended):
This is explained at:
http://www.securitytracker.com/help/faq.html
13) Candidate to Entry Promotion <CR_6.3>
If CVE candidates are supported or used, explain your policy for changing candidates into entries within your capability and describe where and how this is communicated to your customers (recommended):
When we detect that a candidate has been promoted, we will change the number from a "CAN-" designation to a "CVE-" designation. This is explained at:
http://www.securitytracker.com/help/faq.html
14) Candidate and Entry Search Support <CR_6.4>
If CVE candidates are supported or used, explain where and how a customer can find the explanation of your search function's ability to look for candidates and entries by using just the YYYY-NNNN portion of the CVE names (recommended):
This is available on the Help page for the Search engine:
http://www.securitytracker.com/help/6.html
15) Search Support for Promoted Candidates <CR_6.5>
If CVE candidates are supported or used, explain where and how a customer can find the explanation of your search function's support for retrieving the CVE entry for a candidate that is no longer a candidate (recommended):
We support searching on any of the formats. This is available on the Help page for the Search engine:
http://www.securitytracker.com/help/6.html
16) Candidate Mapping Currency Indication <CR_6.6>
If CVE candidates are supported or used, explain where and how you tell your users how up-to-date your candidate information is (recommended):
A brief description is available at:
http://www.securitytracker.com/help/faq.html
Type-Specific Capability Questions
26) 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):
A user can access our Search engine at the following URL:
http://www.securitytracker.com/search/search.htmlThe user can type a CVE number, CAN candidate number, or short-version number into the search box and then press the "Search" button. If the requested number exists in our database, the search engine will return a list of matching documents. We often have several alerts associated with a single CVE number (especially when the various Linux distribution vendors each issue their own security advisories, as we will issue a separate SecurityTracker Alert ID number for each vendor's advisory). In this case, several matching documents may be returned. The user can click on any of the returned links to access the SecurityTracker Alert (i.e., the task).
We plan to issue a separate interface to allow a user to enter a CVE number and obtain a direct mapping of the applicable alert or alerts. This will provide HTML and XML formatted results. The interface will also allow a user to enter our SecurityTracker Alert ID number and obtain a direct mapping of the applicable CVE numbers.
27) 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):
Examples:
The URL template is:http://www.example.com/cgi-bin/db-search.cgi?cvename=CVE-YYYY-NNNN
http://www.example.com/cve/CVE-YYYY-NNNN.html
http://search.securitytracker.com/cgi-bin/ts.pl?query=CVE-2003-0924
The user can submit queries for the "CAN", "CVE", or short-version numbers.
28) 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, GET is supported.
29) 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):
Each alert clearly identifies the CVE number (listed under "CVE Reference").
30) 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):
Details for individual security elements are provided in each SecurityTracker Alert.
31) 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):
Alerts on the public web site are available in HTML format. The CVE related text is indicated with the "CVE Reference:" string, followed by a hyperlink to the relevant CVE web page(s).
For our subscription-based customers, we offer e-mail alerts in ASCII, HTML, and XML format. The CVE related text in the ASCII-based e-mail messages is indicated with the "CVE Reference:" string, followed by the relevant CVE number(s). The CVE related text in the HTML-based e-mail messages is indicated with the "CVE Reference:" string, followed by a hyperlink to the relevant CVE web page(s). The CVE related text in the XML-based e-mail messages is indicated with the "cvesection" and "cveref" elements.
32) 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):
n/a (the electronic documents contain more than just short names or titles)
33) 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):
See attached example XML file for our SecurityTracker Alert ID 1013239. The XML files are available to subscription-based customers and are not available on our public web site. This particular XML format is one of several XML formats that we offer. In this and other XML formats, there is a 'cveref' tag that includes the relevant CVE number(s), as shown below:
< SecurityTracker:cveref>CAN-2005-0158</SecurityTracker:cveref>
34) 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):
Go to the search page (http://www.securitytracker.com/search/search.html) and type a CVE number into the box and press the "Search" button. CAN candidate numbers and short-version numbers can also be used.
35) 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 CVE name for a particular SecurityTracker Alert is listed under the line marked "CVE Reference."
36) 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):
An index listing of our alerts that contain CVE numbers is planned for a future release. This index listing will be available via a web browser.
In the XML formats that we offer, there is a 'cveref' tag that includes the relevant CVE number(s). A customer can import the XML documents into a database, for example, and then search the database.
37) 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: Stuart Moore
Title: CEO
38) 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: Stuart Moore
Title: CEO