|
|
Name of Your Organization:
Application Security, Inc.
Web Site:
Compatible Capability:
AppDetectivePro
Capability home page:
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):
Application Security, Inc. (AppSec) provides AppDetectivePro to its customers through a secure download portal. Evaluation versions of AppDetectivePro are also available to the public by registering at www.appsecinc.com. Once operational, AppDetectivePro displays CVE Identifiers as part of each knowledgebase article of each check. CVE Identifiers are then displayed within reports and within the UI when the knowledgebase article is displayed. CVE Identifiers can also be searched in the policy editor.
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 provides ASAP Updates to AppDetectivePro to update any CVE Identifiers, so they 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 through ASAP Updates to AppDetectivePro. These are provided monthly, but also include out-of-band releases when needed to address any critical vulnerabilities.
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):
Customers are notified when an ASAP Update is available via email and via the customer support portal. AppDetectivePro customers also have the ability to schedule ASAP Updates to receive any updates of the vulnerability knowledgebase.
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 products vulnerability knowledgebase and determines any relevance. As AppDetectivePro is specific to scanning databases, Team SHATTER sets criteria for relevance for CVE Identifiers needed.
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 for each ASAP Update release.
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.
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 about CVE and CVE Compatibility is available in the AppDetectivePro User Guide. The user guide is updated with every product update and is available via the customer support portal.
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 about CVE and CVE Compatibility is available in the AppDetectivePro User Guide. The user guide is updated with every product update and is available via the customer support portal.
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 about CVE and CVE Compatibility is available in the AppDetectivePro User Guide. The user guide is updated with every product update and is available via the customer support portal.
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):
Documentation about CVE and CVE Compatibility is available in the AppDetectivePro User Guide. The user guide is updated with every product update and is available via the customer support portal. Information is located in Chapter 6: Viewing SCAP Information.
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):
Users can open AppDetectivePro, open the policy editor, view a built-in policy or create a new one. This will display the full vulnerability knowledgebase. Each knowledgebase article will list a "CVE Reference #". After a scan is completed and issues found, you can also click on the "Vulnerability Description" tab on the main UI to view the CVE Reference #. This will correspond with the issue highlighted in the bottom pane.
Main UI
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):
Users can open AppDetectivePro and generate reports from any session with scan results. Select "Reports" and generate a vulnerability details report. Vulnerability results will include CVE Identifiers in all report types (HTML, XML, Text, Crystal).
Vulnerability Details Report
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):
Users can open the policy editor, input "CVE" into the search and all checks will report with CVE identifiers. Users can also run a policy report for any policy and CVE Identifiers will be included in each knowledgebase article of each check.
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):
Users can also run a policy report for any policy and CVE Identifiers will be included in each knowledgebase article of each check.
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):
Users can open the policy editor, input the specific identifier, i.e., "CVE-2000-0818", into the search to identify the checks that match that specific reference.
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 product as "CVE-NO-MATCH". These checks can be included or excluded from policies by simply checking them on or off in the policy editor.
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):
Users can search CVE Identifiers in the policy editor of AppDetectivePro. Users will see a references section that will link them to the associated link within cve.mitre.org. Example: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2000-0818
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:
- http://www.example.com/cgi-bin/db-search.cgi?cvename=CVE-YYYY-NNNN
- http://www.example.com/cve/CVE-YYYY-NNNN.html
AppDetectivePro does not have an exposed URL template. 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):
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=
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):
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=
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 Detail reports can be generated in XML, HTML, Text, and Crystal Reports and contain the CVE Identifier.
To search reports:
- For HTML reports, use the Browser search function
- For XML reports, a CVE identifier can be parsed with an XML parser or searched using a Browser search function
- Fort Text reports, use the Viewer search function
- For Crystal reports, export it to a desired format (i.e., Word, Excel) and use the appropriate search function
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):
Policy Editor
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_B.3.2>, above.
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>.
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