Name of Your Organization:

Application Security, Inc.

Web Site:

http://www.appsecinc.com/

Compatible Capability:

TeamSHATTER.com

Capability home page:

http://www.teamshatter.com/

General Capability Questions

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

TeamSHATTER.com is Application Security Inc.’s (AppSec) dedicated public website for information about database security, risk and compliance news, research and analysis. It provides a threat finder database of vulnerabilities that is CVE Identifier searchable.

Mapping Questions

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

AppSec monitors new and changed CVE Identifiers via the cve.mitre.org and also monitors for new vulnerability announcements via the NVD (nvd.nist.gov) and other sources (i.e., Oracle Critical Patch Update announcements). AppSec continuously updates TeamSHATTER.com so CVE Identifiers are always up-to-date.

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 of CVE Identifiers are managed frequently at TeamSHATTER.com. Every month the vulnerability database is refreshed and made current with any new content. Changes are also made on an as needed 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):

As public resource center for database threats and vulnerabilities, TeamSHATTER.com appropriately updates content on an as needed basis. CVE Identifiers can be found in the Threat Finder section of the website and also within any security advisories posted.

Map Content Selection Criteria <CR_5.4>

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

AppSec’s security research group, Team SHATTER, maintains the vulnerability knowledgebase and determines any relevance.

Map Currency Update Mechanism <CR_5.4>

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

AppSec’s security group, Team SHATTER reviews CVE for any content changes.

Map Content Source <CR_5.5>

Describe the source of your CVE content (required):

AppSec’s security group, Team SHATTER uses cve.mitre.org, nvd.nist.gov, specific sources that common direct from vendors, such as Oracle Critical Patch Update announcements, as well as other industry sources.

Documentation Questions

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 is available at http://www.teamshatter.com/resources/#Terms%20and%20Definitions.

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

Documentation is available at http://www.teamshatter.com/resources/#Terms%20and%20Definitions.

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

Documentation is available at http://www.teamshatter.com/resources/#Terms%20and%20Definitions.

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

CVE references are available within Security Advisories and within each Threat Finder ID.

Example of a Security Advisory: http://www.teamshatter.com/topics/general/team-shatter-exclusive/oracle-enterprise-manager-vulnerable-to-cross-site-scripting-metricdetailtype-page/.

Example of a Threat Finder ID: http://www.teamshatter.com/threat-finder/1944-oracle-multiple-sql-injection-in-oracle-enterprise-manager-service-level-component/.

Type-Specific Capability Questions

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

Visitors to TeamSHATTER.com can use the Threat Finder section (http://www.teamshatter.com/threat-finder/) and use the CVE reference field in the Advanced Search option.
Finding Tasks Using CVE Names

Users can also search for CVE Identifiers within posted content by using the Site Search feature at TeamSHATTER.com
Finding Tasks Using CVE Names

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

See <CR_A.2.1>.

Selecting Tasks with a List of CVE Names <CR_A.2.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):

See <CR_A.2.1>.

Selecting Tasks Using Individual CVE Names <CR_A.2.6>

Describe the steps that a user would follow to browse, select, and deselect a set of tasks for the tool by using individual CVE names (recommended):

See <CR_A.2.1>.

Non-Support Notification for a Requested CVE Name <CR_A.2.7>

Provide a description of how the tool notifies the user that task associated to a selected CVE name cannot be performed (recommended):

Any non-CVE identifier is reference in the vulnerability database as "CVE-NO-MATCH".

Online Capability Questions

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

See <CR_A.2.1>.

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

Users can refer to TeamSHATTER.com, AppSec’s security group’s knowledge center. Users can use the Treat Finder to search by CVE reference. Example: http://www.teamshatter.com/threat-finder/?risk=Any&category=Any&database=Any&cve=CVE-2000-0818&keywords=

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

See <CR_A.4.1.1>.

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

See <CR_A.4.1.1>.

Media Questions

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

Electronic Document Format Info
Threat Finder section of TeamSHATTER.com

Electronic Document Format Info
Team SHATTER Advisory Post

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

See <CR_A.2.1>.

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 <CR_A.2.1>.

Graphical User Interface (GUI)

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 <CR_A.2.1>.

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 <CR_A.2.1>.

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

See <CR_B.3.1>.

Questions for Signature

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: Mark Trinidad

Title: Product Manager

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: Mark Trinidad

Title: Product 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: Mark Trinidad

Title: Product Manager

Page Last Updated or Reviewed: April 28, 2016