Web Site:

Compatible Capability:

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

Information about security vulnerabilities is publicly available on our Jump NVAS website. Customers can find the security vulnerabilities, and search the rules, on the site. Customers can also download and install product updates from our website.

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

We find the new CVE rule and update the rule to our database regularly; users can update from the website.

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

Once every 10 days we check our database against the CVE List, and if there are new CVEs, we complete a new rule for them in our database. Users can then download and update the rules.

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

Jump NVAS is updated every 10 days. If there is a new CVE on the CVE List, we add the new CVE information to our update file in a timely manner.

Map Content Selection Criteria <CR_5.4>

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

Every rule has a field. Its value is the CVE ID. The CVE ID determines the relation between our rule and CVE rule.

Map Currency Update Mechanism <CR_5.4>

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

We will go to CVE website, search for changes, and put them into our database in our website.

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

Security information can be searched from the search page at http://www.jump.net.cn/kf/cve.aspx via general key words. If the information is related to specific CVE information, then the CVE name and link to the CVE website will appear in Description section.

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

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 search by CVE ID (i.e., CVE name) on our website’s search page, and from that page link to the page for the CVE name on the CVE website.

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

On the Alert page, users can find cve relation id, and then can link to the base cve relation id on the CVE website.

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

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

On the Alert page, users can find cve relation id, and then can link to the base cve relation id on the CVE website.

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

From the http://www.jump.net.cn/kf/cve.aspx search page, users can input the CVE ID, the page will list the rule, and the user can then link to the base cve relation id on the CVE website.

Finding CVE Names Using Elements in Reports <CR_A.5.2>

Give detailed examples and explanations of how, for reports that
identify individual security elements, the capability allows the
user to determine the associated CVE names for the individual
security elements in the report (required):

We do not map security elements to CVE names in our reports, but we can search in web manage or website.

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

Jump NVAS provides output in PDF format. Each is searchable via the browser.

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

We do not map security elements to CVE names in our reports, but we can search in web manage or website.

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

In our website or web manager, we can get the mapping from individual elements to the respective CVE names.

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

In our web gui, users can find rule by inputting the CVE ID or rule name.

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

In our rule helper for individual security elements, users can click on the CVE ID, then we can link to the page for the CVE name on the CVE website.

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: HongWei Chen

Title: Manager for Jump NVAS Development

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."

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."