|
|
Name of Your Organization:
TippingPoint Technologies, Inc.
Web Site:
www.tippingpoint.com
Compatible Capability:
TippingPoint Intrusion Prevention System
Capability home page:
http://www.tippingpoint.com/products_ips.html
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):
CVE compatibility information is available through our Security Management System, which allows specific CVE ID# searches
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):
With each of our filters that contain CVE mappings – TippingPoint provides a hyperlink to the relevant CVE ID# webpage.
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):
Our security filter sets are updated twice a week, which include any updates or additions to CVE mappings. As our mappings include hyperlinks directly to the CVE ID webpages, our customers are provided the latest information on each vulnerability and exploit.
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):
When new Digital Vaccine security filter packages are released (twice a week) an email is sent to all customers who have subscribed to our email notification list. This email contains all the detailed information surrounding the filter updates and the corresponding CVE ID information. In addition to the email, we also post the detail information and the package updates on our Threat Management Center website.
Map Content Selection Criteria <CR_5.4>
Describe the criteria used for determining the relevance of a given CVE Identifier to your Capability (required):
CVE descriptions are used to align CVE ID#s with relevant vendor advisories and known public exploits. This information is used during the development of new security filters and updates to existing security filters.
Map Currency Update Mechanism <CR_5.4>
Describe the mechanism used for reviewing CVE for content changes (required):
When developing new security filters or updating existing security filters, our security development team reviews the CVE website and relevant CVE ID#s relating to the specific vulnerably or exploit they are working on to ensure the most recent updates are incorporated.
Map Content Source <CR_5.5>
Describe the source of your CVE content (required):
We collect CVE content from the CVE website, as well as RSS feeds and mailing lists. We also subscribe to 3rd party services that provide CVE content within their products.
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):
CVE information is provided in the filter details page; within our Security Management System; for each of our Digital Vaccine security filters. We also provide CVE ID# information for each updated or new filter that is released with our semiweekly Digital Vaccine release notification. Two screen shots have been attached as examples (figures 1 & 2).
Figure 1
Figure 2
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):
Within the Security Management System, the user has the ability to search for a given filter based on several different search criteria – one of them being the CEV-ID# (screen shot below – figure 3)
Figure 3
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):
The following steps outline the procedure a user would follow to find CVE names using elements:
- Upon successful login to the Security Management System, a user must select the "Profiles" icon (see Red arrow on screen shoot below – figure 4).
- Next the user must expand the "IPS Profiles" navigation tree (see Blue arrow on screen shoot below – figure 4) and then expand the "Default" branch (see Black arrow on screen shoot below – figure 4).
- Then the user must select the "Search" page (see Green arrow on screen shoot below – figure 4).
- Now the user can enter the CVE search criteria as "YYYY-NNNN" or "NNNN" and select the "Search" button (see Gray and Purple arrows respectively on screen shoot below – figure 4).
- Next the user will double click the displayed filter(s) under "Search Results" (see Orange arrow on screen shoot below – figure 4) and a new window will pop-up.
Figure 4
- In the new window the user will select "Filter Details" and then click the CVE ID hyperlink – this will take the user to the CVE website corresponding to the specific CVE ID (see attached screen shot below – figure 5)
Figure 5
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):
We do not have an indexing of CVE-related material.
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):
Much like what is described in response to question CR_4.3, when the filter(s) is displayed in the "search results" the task for that filter is listed under the column heading "Action Set" (see figure 4 above).
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):
The following steps outline the procedure a user would follow to find CVE names using elements within reports:
- Upon successful login to the Security Management System, a user must select the "Reports" icon (see Red arrow on screen shoot below – figure 6).
- Next the user must expand the "Templates" navigation tree (see Black arrow on screen shoot below – figure 6) and then expand the "Attacks" branch (see Blue arrow on screen shoot below – figure 6).
- Next the user will select "All Attacks" and must run the report by clicking the "Run" button on the bottom right of the page (see Green and Gray arrows respectively on screen shoot below – figure 6).
- This will display the filters that have been triggered. The user will double click on a specific filter (see Orange arrow on screen shoot below – figure 6).
Figure 6
- This will take them to the events page for that filter. When the user double clicks that filter again a new window pops-up, which displays detailed information on that filter – including the CVE ID# and hyperlinks to the CVE web pages for the specific CVE ID#s.(see Red arrow on screen shoot below – figure 7). See figure 8 below for the CVE webpage corresponding to the CVE ID#.
Figure 7
Figure 8
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):
Follow the steps in the answer for question CR_4.3. When the "Filter Details" page is displayed, if there are multiple CVE IDs for a single filter, they will be displayed and each CVE ID# is a hyperlink to the specific CVE webpage for the ID# (See Black arrow in figure 9 below).
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):
Follow the steps in the answer for question CR_4.3. When multiple filters are associated with a single CVE ID, they will be displayed in the "Search Results" section. (See figure 10 below)
Figure 10
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 steps outlined in question 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):
All of our CVE ID references are hyperlinks to the CVE webpage that corresponds to the CVE ID. Follow and of the above steps that get a user to a "Filer Detail" page and the user will be able to find the online CVE information for that specific ID (CR_A.2.4 or CR_A.2.2 or CR_4.3)
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):
All of our CVE ID references are hyperlinks to the CVE webpage that corresponds to the CVE ID. Follow and of the above steps that get a user to a "Filer Detail" page and the user will be able to find the online CVE information for that specific ID (CR_A.2.4 or CR_A.2.2 or CR_4.3)
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):
All of our CVE ID references are hyperlinks to the CVE webpage that corresponds to the CVE ID. Follow and of the above steps that get a user to a "Filer Detail" page and the user will be able to find the online CVE information for that specific ID (CR_A.2.4 or CR_A.2.2 or CR_4.3)
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):
The following steps outline the procedure a user would follow to find capabilities that are associated to CVE IDs:
- Upon successful login to the Security Management System, a user must select the "Profiles" icon (see Red arrow on screen shoot below – figure 11).
- Next the user must expand the "IPS Profiles" navigation tree (see Blue arrow on screen shoot below – figure 11) and then expand the "Default" branch (see Black arrow on screen shoot below – figure 11).
- Then the user must select the "Search" page (see Green arrow on screen shoot below – figure 11).
- Now the user can enter the CVE search criteria as "YYYY-NNNN" or "NNNN" and select the "Search" button (see Gray and Purple arrows respectively on screen shoot below – figure 11).
- This will display, under the "Search Results" section, the capability(ies) that are associated to a specific CVE ID(see Orange arrow on screen shoot below – figure 11).
Figure 11
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 steps outlined in section CR_A.2.2
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):
See steps outlined in section CR_A.2.4
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):
Our CVE-related text is provided in HTML format and accessed via hyperlinks for each CVE ID associated with each of our security elements and the information is provided in email from when our semiweekly Digital Vaccines packages are released (see figure 2 above for the email screen shot).
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):
Associated CVE IDs are listed for each security element under the "Events/Event Details" page (see figure 7 above) and they are listed in the email from when our semiweekly Digital Vaccines packages are released (see figure 2 above for the email screen shot)
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):
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):
See answer to section CR_4.2 above.
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 steps outlined in section CR_4.3 above.
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):
Our CVE-related text is provided in HTML format and accessed via hyperlinks for each CVE ID associated with each of our security elements and the information is provided in email from when our semiweekly Digital Vaccines packages are released (see figure 2 above for the email screen shot).
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: Freddie Jimenez
Title: Director of Quality Assurance
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: Freddie Jimenez
Title: Director of Quality Assurance
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: Freddie Jimenez
Title: Director of Quality Assurance