Name of Your Organization:

Trustwave

Web Site:

www.trustwave.com

Compatible Capability:

TrustKeeper

Capability home page:

http://www.trustkeeper.net

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):

TrustKeeper is an Internet-accessible information security compliance service, with a strong emphasis on PCI compliance assessment. Part of this service includes vulnerability scanning of client networks.

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 TrustKeeper web interface includes an indicator on the "View Reports" page that includes the current version of the CVE that is being used in our system.

Figure 1

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):

Trustwave has developed a custom vulnerability and signature management tool which synchronizes with the CVE content on a daily basis. This tool analyzes the data from the CVE feed, identifies new and changed entries, and assigns a priority score to each entry so that it can be queued for manual review. The Signature Management System is reviewed every business day by Trustwave's security operations team, and relevant entries are then assigned to analysts for additional development (e.g., scanner test development, etc.).

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 (required):

Trustwave's use of CVE is included in the Scoring section of the client-facing scan reports.

Map Content Selection Criteria <CR_5.4>

Describe the criteria used for determining the relevance of a given CVE Identifier to your Capability (required):

Trustwave's Signature Management System scores each new CVE Identifier based on Common Product Enumeration (CPE) metadata and keyword rules which are applied to the basic CVE description. This automated scoring allows the Signature Management Team to prioritize the new vulnerabilities and their relevance to the TrustKeeper scanner.

Map Currency Update Mechanism <CR_5.4>

Describe the mechanism used for reviewing CVE for content changes (required):

Trustwave's Signature Management System includes a queue which lists all new and updated CVE identifiers. This queue is reviewed daily by Trustwave's security team. Changes to vulnerability are identified by changes in CVE metadata, including additional references (which may provide additional insight into a vulnerability) and changing CVSS scores.

Map Content Source <CR_5.5>

Describe the source of your CVE content, (i.e., we gather info from mailing lists, product change logs, software vendors' security bulletins...) (required):

The CVE content is primarily gathered from the National Vulnerability Database (NVD), via an automated daily feed. The rich XML in this feed contains extensive reference information, as well as CVSS scoring information, and Common Product Enumeration (CPE) information. Any other source can be added via manual entry into the Signature Management System.

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 descriptions are included in the exportable scan reports, which are PDF documents provided to the user. Furthermore, Trustwave's use of CVE is included in numerous Help and Frequently Asked Question documents and resources.

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):

CVE descriptions are included in the exportable scan reports (shown in Figure 2), which are PDF documents provided to the user.

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):

CVE descriptions are included in the exportable scan reports (shown in Figure 2), which are PDF documents provided to the user.

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):

All documentation is included in the scan reports (shown in Figure 2).

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):

This is not applicable to TrustKeeper.

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 TrustKeeper scan reports include CVE names and links to both the CVE and NVD web sites for all vulnerability findings.

Figure 3

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):

Tasks are associated with identified vulnerability findings, which have the associated CVE identifiers attached within the report (shown in Figure 3).

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):

TrustKeeper scan reports are distributed in a PDF and Excel format that include CVE names whenever they are available (shown in Figure 3). These can be searched using the native search capabilities of the document viewers.

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):

TrustKeeper scan reports are distributed in a PDF and Excel format that include CVE names whenever they are available (shown in Figure 3). These can be searched using the native search capabilities of the document viewers.

Service's Product Utilization Details <CR_A.3.4>

Please provide the name and version number of any product that the service allows users to have direct access to if that product identifies security elements (recommended):

TrustKeeper (all versions)

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):

TrustKeeper scan reports are distributed in a PDF and Excel format that include CVE names whenever they are available (shown in Figure 3). These can be searched using the native search capabilities of the document viewers.

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):

TrustKeeper provides all CVE content in it's exportable PDF or Excel reports (shown in Figure 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):

TrustKeeper scan reports are distributed in a PDF and Excel format that include CVE names whenever they are available (shown in Figure 3). These can be searched using the native search capabilities of the document viewers.

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):

TrustKeeper scan reports are distributed in a PDF and Excel format that include CVE names whenever they are available (shown in Figure 3). These can be searched using the native search capabilities of the document viewers.

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):

PDF Reports - may be searched using the normal PDF reader (e.g., Acrobat) "search" functions.

Excel Reports - may be searched using native Excel functionality

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):

All client-accessible findings are delivered via PDF and Excel documents (shown in Figure 3), which are searchable via standard PDF viewers (e.g., Acrobat).

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):

All findings include CVE names, with links to both the CVE and NVD web sites (shown in Figure 3).

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: Ken Green

Title: SVP, Product Management

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: Ken Green

Title: SVP, Product Management

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: Ken Green

Title: SVP, Product Management