Name of Your Organization:

FuJian RongJi Software Company, Ltd

Web Site:

www.rongji.com.cn

Compatible Capability:

RJ-iTop Network Vulnerability Scanner System

Capability home page:

http://www.rj-itop.com

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

CVE compatibility information available in the module of vulnerabilities analysis and report forms within Our scanner.

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

For each CVE name, our scanner has a hyperlink to the respective CVE page which provides a version number on the top of the vulnerabilities analysis.

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 time a new version is released, all new entries are added to our database. Old candidates are removed.

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

Our Security Team updates the vulnerability database from various sources, with reference to the CVE mechanism. We update at least once per week upon notification of a new CVE version.

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

We provide CVE description information in About CVE on page 43-46 of our User Guide.

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

Finding Elements using CVE Names in the vulnerabilities analysis according to the following steps:

Steps:

1. Select the "vulnerabilities analysis";
2. Input CVE name in the Searching Contents edit box under the find event tab;
3. Press the Search button to complete the task.

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

Finding CVE Names using Elements in the vulnerabilities analysis. Each CVE name is a hyperlink, Click the CVE name item, the CVE page with the respective CVE name will be opened.

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

CVE information is available in the report forms, and indexed by the following terms:

• Common Vulnerabilities and Exposures
• Vulnerabilities by IP
• Vulnerabilities by port

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

A user can also locate a corresponding CVE (CAN) name via related keyword. When a user is not sure if vulnerability is accepted as a formal CVE entry, he can search its number in "YYYY-NNNN" format in the database or product alert, then conveniently determine if it's a formal or candidate CVE entry.

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

RONGJI are subscribed to the CVE mailing list and update CAN/CVE listings regularly. Customers aren't specifically told as they will automatically see the new reference and be linked to the correct definition.

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

RONGJI will try to update modified CVE names at the earliest opportunity, but will not inform customers of these changes individually.

15) Search Support for Promoted Candidates <CR_6.5>

If CVE candidates are supported or used, explain where and how a customer can find the explanation of your search function's support for retrieving the CVE entry for a candidate that is no longer a candidate (recommended):

The user can attain this goal according to the following steps:

1. Select the "vulnerabilities analysis";
   
2. Input CVE name in the Searching Contents edit box under the find event tab;
   
3. Press the Search button to complete the task.
   

16) Candidate Mapping Currency Indication <CR_6.6>

If CVE candidates are supported or used, explain where and how you tell your users how up-to-date your candidate information is (recommended):

The CVE (if available) name is listed in the report for any vulnerability found on a machine. An excerpt from a remediation report is below.

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

Within the product the customer selects the "vulnerabilities analysis"->"search". And then user can enter 'CVE' and 'search'. The customer will see this screen with all available CVE names and vulnerabilities name :

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

As in 15 above, the customer can select the desired tasks from the list of CVE names or search for each required CVE name and select the associated task from there (17).

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

Follow the steps in 15 and select the desired CVE tasks.

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

As a scanner, the task is an audit, which is always performed. If access to perform an audit is not available, the user is notified in the product scan log. Otherwise the scan is performed and the user is notified of any problems.

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

The report details the tests that were performed and wherever vulnerabilities are discovered CVE numbers are referenced for each.

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

CVE/CAN names, if available, are included with every vulnerability report. A user would just need to click on the exact vulnerabilities to view the CAN/CVE number. The executive report groups vulnerability types which can also be viewed.

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

We support HTML, DOC, PDF and TXT outputs - all four formats are searchable and thus the user can simply search for a specific CVE or CAN in the report.

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

All document types contain security descriptions and CVE numbers.

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

Whenever the vulnerability's name and summary appears, the applicable CVE number appears below the description (if one exists for this 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):

The vulnerabilities analysis supports full-text searches and CVE name searches for vulnerability information. The user may search for an element using the CVE name.

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

The vulnerability name appears together with the CVE number. And click CVE name, then a new browser page that links to corresponding CVE name in MITRE website will appear.

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

Export document provides output in HTML, DOC and PDF format. Each is searchable via the browser chosen according to CVE information.

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: Dianmin Li

Title: Director of RongJi Security Dept

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: Dianmin Li

Title: Director of RongJi Security Dept

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: Dianmin Li

Title: Director of RongJi Security Dept