Name of Your Organization:

Qualys, Inc.

Web Site:

www.qualys.com

Compatible Capability:

QualysGuard Consultant

Capability home page:

http://www.qualys.com/webservices/qgcons/

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

The QualysGuard OnDemand Platform for Network Security Audits, Vulnerability Management and Remediation is available via secure Web Browser.

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

The QualysGuard Vulnerability KnowledgeBase is updated on a daily basis with latest vulnerability and CVE mapping information from a variety of sources including cve.mitre.org.

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

The QualysGuard Vulnerability KnowledgeBase is updated on a daily basis with latest vulnerability and CVE mapping information from a variety of sources including cve.mitre.org.

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

The QualysGuard Vulnerability KnowledgeBase is always up to date, which is documented in the QualysGuard 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):

Documentation on CVE and CVE compatibility is located in the QualysGuard Online Help section of the application. The Web based user interface has a Help icon located at the top of all pages that will bring customers to the main Help page. One way to navigate to the CVE information within the Online Help is to do a search on "CVE".

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

The Online Help page described in Question 7 contains information on finding elements in the QualysGuard Vulnerability Knowledgebase using CVE names. Here's an example:

If you are looking for a specific CGI vulnerability and you know that the last 4 digits of the CVE ID are "0937", enter the following search criteria: Find "CVE ID" within "CGI" containing "0937"

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

The Online Help page described in Question 7 contains information on finding CVE names in the QualysGuard Vulnerability Knowledgebase using elements. Additionally, the vulnerability signatures within the QualysGuard Vulnerability Knowledgebase contain links to the associated CVE vulnerability page on the cve.mitre.org website.

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

The CAN prefix is used for all candidates to differentiate them from CVE entries which have the CVE prefix.

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

The Online Help page described in Question 7 contains explanation on Candidates versus Entries.

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

The QualysGuard Vulnerability KnowledgeBase is updated on a daily basis with graduation information from CAN to CVE which is immediately available via the QualsyGuard Web based Userinterface.

14) Candidate and Entry Search Support <CR_6.4>

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

The Online Help page described in Question 7 contains information on searching candidates and entries in the QualysGuard Vulnerability Knowledgebase. Here's an example:

If you are looking for a specific CGI vulnerability and you know that the last 4 digits of the CVE ID are "0937", enter the following search criteria: Find "CVE ID" within "CGI" containing "0937"

Type-Specific Capability Questions

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

• Login to QualysGuard
• Select "Report"
• Select "Vulnerability KnowledgeBase" tab
• Vulnerabilities with associated CVE names are listed.

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

• Login to QualysGuard
• Select "Report"
• Select "Scan Reports tab"
• Select "Technical Report"
• Vulnerabilities with associated CVE names are listed.

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

• Login to QualysGuard
• Select "Report"
• Select "Vulnerability KnowledgeBase" tab
• Sort by CVE ID.

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

• Login to QualysGuard
• Select "Preferences"
• Select "New Options"
• Scroll down
• Check "Perform Selective Vulnerability Scanning"
• Select "Configure"
• Search KnowledgeBase using CVE name.
• Select vulnerabilities to scan by placing checking CheckBox to the left of the vulnerabilities listed
• Name your Option profile
• Select "Save"
• Select "Scan" from main page
• Select appropriate option profile from list
• Select IP or IP range you wish to scan
• Select "Start Scan"

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

All scan errors are displayed within the application as a new webpage. An "OK" button closes the error notification webpage when selected by the user.

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

• Login to QualysGuard
• Select "Report"
• Select "Vulnerability KnowledgeBase tab

At this point the user can search, sort, filter and find for CVE names tested and detected by QualysGuard.

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

• Login to QualysGuard
• Select "Report"
• Select "Scan Reports tab"
• Select "Technical Report"
• Vulnerabilities with associated CVE names are listed.

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

See answers to 17, 19, and 21

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

First, you must first be logged into the service. Then, you can use the following url to access the search function using CVE ID (using search_value parameter at the end of the url):

https://qualysguard.qualys.com/fo/report/index.php?
search_by=cveid&search_category=2&tab_selected=3&search_value=CVEYYYYNNNN

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

• Login to QualysGuard
• Select "Report"
• Select "Scan Reports tab"
• Select "Technical Report"
• Vulnerabilities with associated CVE names are listed.

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

QualysGuard provides the Vulnerability KnowledgeBase as a Web based application (via HTML) with links to CVE information provided by cve.mitre.org. The Vulnerability KnowledgeBase has search capabilities which can be used to search by CVE ID and for specific vulnerability info.

Vulnerability reports can be generated in HTML or XML and contain the CVE ID and associated link for each vulnerability reported, if applicable.

To Search Reports:

• For HTML report, use Browser search function
• For XML report, a CVE tag is used that can be parsed with any XML parser.

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

As the following screenshot demonstrates, vulnerabilities listed in the QualysGuard Vulnerability KnowledgeBase have CVE names listed and a link to the associated page on the cve.mitre.org website.

For Example: http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-YYYY-NNNN

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

The following is an example report screenshot. Notice the CVE ID associated with the detected vulnerability.

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

• Login to QualysGuard
• Select "Report"
• Select "Vulnerability KnowledgeBase tab
• Vulnerabilities with associated CVE names are listed and available for find and search

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

All vulnerabilities listed have the CVE ID listed on the right side of the description. See screenshot in 32.

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: Gerhard Eschelbeck

Title: CTO and VP Engineering

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: Gerhard Eschelbeck

Title: CTO and VP Engineering

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: Gerhard Eschelbeck

Title: CTO and VP Engineering