|
|
Name of Your Organization:
Watchfire (USA) Limited
Web Site:
www.watchfire.com
Compatible Capability:
AppScan
Capability home page:
http://www.watchfire.com/products/appscan/default.aspx
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):
Users can download the AppScan solution from Watchfire's web site. In addition, an evaluation version is available for download from the website https://www.watchfire.com/securearea/appscan.aspx
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):
When the AppScan/CVE cross-reference table is updated, users will be able to view the CVE database version in AppScan's "Update Log" window. Since this log is persistent, users can always review what is the latest CVE database version that is being used in AppScan.
5) 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 (recommended):
Each vulnerability that is added to AppScan's database will reference the most recently updated CVE version. In addition, with every major release of the product, mappings will be checked for updates and changes.
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):
This information will be available in the product's user guide and online help.
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):
AppScan User Guide, Sections 6-6 and 6-7 (CVE Support)
AppScan Online Help ("CVE Support")
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):
AppScan User Guide, Sections 6-6 and 6-7 (CVE Support)
AppScan Online Help ("CVE Support")
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):
AppScan User Guide, Sections 6-6 and 6-7 (CVE Support)
AppScan Online Help ("CVE Support")
10) 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):
AppScan User Guide, Sections 6-6 and 6-7 (CVE Support)
AppScan Online Help ("CVE Support")
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):
Candidate CVE is written with the prefix CAN- in our security advisories. In addition, the documentation (user guide and online help) includes an explanation of the difference between CAN and CVE.
12) Candidates Versus Entries Explanation <CR_6.2>
If CVE candidates are supported or used, explain where and how the difference between candidates and entries is explained to your customers (recommended):
Candidate CVE is written with the prefix CAN- in our security advisories. In addition, the documentation (user guide and online help) includes an explanation of the difference between CAN and CVE.
13) Candidate to Entry Promotion <CR_6.3>
If CVE candidates are supported or used, explain your policy for changing candidates into entries within your capability and describe where and how this is communicated to your customers (recommended):
Every major release, we will refresh our texts to reflect the most recent status of CVE entries.
14) Candidate Mapping Currency Indication <CR_6.6>
If CVE candidates are supported or used, explain where and how a customer can find the explanation of your search function's ability to look for candidates and entries by using just the YYYY-NNNN portion of the CVE names (recommended):
AppScan's "Update Log" includes the CVE database version. Users can open the "Update log" window, and view the version information.
Type-Specific Capability Questions
15) 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):
In order to locate tasks (vulnerabilities) that include a CVE name, a user has to open the Test Policy Manager, and in the search box, type the name of the CVE he/she is looking for. In addition, he/she should choose the search filter called "CVE ID". When the search is performed, it will search the given CVE name in each vulnerability's CVE field.
16) 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 report includes a special CVE ID field, which represents the CVE name that is relevant for that vulnerability.
17) 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):
In order to locate all the tasks that have a CVE name assigned to them, a user has to open the Test Policy Manager, and in the search box, type one of the following strings: "CVE" or "CAN". In addition the user should choose the search filter called "CVE ID". When the search is performed, it will search the given CVE name (everything that starts with CVE or CAN) in all of the vulnerabilities.
18) 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):
This capability is currently unavailable in the product.
19) 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):
In order to locate tasks (vulnerabilities) that include a CVE name, a user has to open the Test Policy Manager, and in the search box, type the name of the CVE he/she is looking for. In addition, he/she should choose the search filter called "CVE ID". When the search is performed, it will search the given CVE name in each vulnerability's CVE field.
Once a specific vulnerability has been located, the user can check/un-check the checkbox next to it, in order to enable/disable that specific vulnerability.
20) 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):
If a user searches for a CVE name that cannot be performed, the search results will be empty.
29) 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):
AppScan scan results and reports support HTML, PDF, XLS, XML and CSV electronic document formats. These formats allow for text search of the content.
31) Electronic Document Element to CVE Name Mapping <CR_B.3.2>
Provide example documents that demonstrate the mapping from the capability's individual elements to the respective CVE name(s) (recommended):
AppScan's report (and report editor), includes a CVE reference number field, which when applicable, includes the CVE reference number.
32) 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):
The Test Policy Manager allows users to search for specific tests, according to their CVE reference number. All tests include an advisory, with a dedicated CVE Reference(s) field where applicable. This allows users to define specific Test Policies, according to specific CVEs. In addition, by clicking on the CVE reference number, a browser will open and will take the user to the specific CVE entry in the CVE web site.
33) 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):
During/After the scan, users can view the CVE reference number in the "Advisory" tab of each issue that was discovered. In addition, by clicking on the CVE reference number, a browser will open and will take the user to the specific CVE entry in the CVE web site.
34) GUI Export Electronic Document Format Info <CR_B.4.3>
AppScan's report (and report editor), includes a CVE reference number field, which when applicable, includes the CVE reference number. Reports can be exported to PDF, HTML, CSV, XML, and thus can be easily searched by users for CVE references.
35) 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: Arik Zuckerman
Title: Senior Director of Security Development
36) 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: Arik Zuckerman
Title: Senior Director of Security Development
37) 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: Arik Zuckerman
Title: Senior Director of Security Development