|
|
Name of Your Organization:
Symantec Corporation
Web Site:
http://www.symantec.com
Compatible Capability:
DeepSight Alert Services
Capability home page:
http://enterprisesecurity.symantec.com/products/products.cfm?ProductID=160
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):
DeepSight Alert Services is available through a yearly subscription fee. Customers access the DeepSight Alert Services web portal to search and configure the types of vulnerability alerts they wish to receive. Once configured, alerts can be delivered through the following mechanisms:
- SMS
- FAX
- Voice
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):
- In the masthead, select Help.
- From the Contents in the left pane, select Symantect DeepSight Alert Services overview.
- From the open book in the Contents in the left pane, select CVE compliance.
- In the right pane, click How To to view the procedure.
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):
Mappings are updated in an automated fashion by obtaining the latest mapping file directly from mitre.org.
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):
Help on searching the DeepSight Alert Services database by CVE ID is available in the online help. To access the online help, follow the proceeding menu options:
- In the mast-head, select Help
- Select Alerts Button
- Select Advanced Filtering for My Alerts
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):
Help on searching the DeepSight Alert Services database by CVE ID is available in the online help. To access the online help, follow the proceeding menu options:
- In the mast-head, select Help
- Select Alerts Button
- Select Advanced Filtering for My Alerts
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):
Help on searching the DeepSight Alert Services database by CVE ID is available in the online help. To access the online help, follow the proceeding menu options:
- In the mast-head, select Help
- Select Alerts Button
- Select Advanced Filtering for My Alerts
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):
Candidates are designated as not un-accepted CVE entries through the "CAN-" prefix, rather than the accepted "CVE-" prefix.
Type-Specific Capability Questions
Service Questions
23) 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):
Users can search the entire vulnerability database for vulnerability records matching a particular CVE ID. Users can also search all alerts that they have received for a particular CVE ID. The Symantec vulnerability database currently contains over 4559 records with associated CVE IDs that can be searched.
24) 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):
Individual vulnerability records, when selected, will display the chosen CVE ID. The CVE ID numbers will also be displayed in the resulting search output when a Vulnerability record search is being performed.
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):
By using the Advanced Search capability under the Alerts button, users can specify a CVE ID to search for. To do this, follow these steps:
- Log into Alert Services
- Select Alerts tab
- Select Advanced button
- Select All Alerts radio button
- Select Date Range: 1999 Jan 1 through 2004 Jun 30
- Select Alert Type: Vulnerability
- Select vendor Reference: Mitre CVE ID
- Enter "CVE-1999-0002"
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):
The CVE ID is one of the key fields displayed in the header of a particular vulnerability record. It is displayed in both the online HTML version of alerts, in addition to email alerts delivered to customers.
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):
Vulnerability records are available online in HTML format and are easily searchable through an index allowing the entry of a CVE ID.
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):
Vulnerability alerts are available in HTML format online:
Subject: Multiple Vendor Linux Mountd Vulnerability
BUGTRAQ ID: 121 CVE ID: CVE-1999-0002
Published: 1998-08-28 Updated: 1999-06-01 00:00:00 GMTVulnerability alerts are also available in the following formats:
- PDF documents
- Text documents
- XML documents
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):
By using the Advanced Search capability under the Alerts button,
users can specify a CVE ID to search for. To do this, follow these
steps:
- Log into Alert Services
- Select Alerts tab
- Select Advanced button
- Select All Alerts radio button
- Select Date Range: 1999 Jan 1 through 2004 Jun 30
- Select Alert Type: Vulnerability
- Select vendor Reference: Mitre CVE ID
- Enter "CVE-1999-0002"
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 numbers are part of the resulting output from all standard vulnerability record searches. The resulting output list can be sorted in ascending or descending order based on the CVE IDs.
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: Oliver Friedrichs
Title: Senior Manager, Symantec Security Response
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: Oliver Friedrichs
Title: Senior Manager, Symantec Security Response
39) 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: Oliver Friedrichs
Title: Senior Manager, Symantec Security Response