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 CVE content will be included in the "Event Set" module of the WAF
management, the user can get the according CVE info when viewing the full event
info through the pop-up window "Event Description". Our DB update application
updates WAF Knowledge Base per week. If we find new important vulnerability, we
will update WAF Knowledge Base as soon as possible.

Map Currency Update Approach <CR_5.2>

Indicate how often you plan on updating the
mappings to reflect the current CVE content and describe your approach
to keeping reasonably current with the CVE content when mapping them to
your repository (required):

When a new CVE version is released, all new entries will be added to the
website within two weeks. Old candidates will be removed.

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

WAF's CVE content can keep the update at the different intervals: one
day, one week or one month. It's required for the customer to update the
CVE content one time per week, otherwise, the management system will
pop-up the warning message to notify the user on it.

Map Content Selection Criteria <CR_5.4>

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

The experts of ADLab (Attack & Defend Lab) owned by Leadsec will keep
watch the CVE identifier's update and the identifier(s) will be added
into signature DB of Leadsec WAF if the system and/or application
referred to come from China or our customer(s). The new added CVE
details can be got from the "Event Set" module.

Map Currency Update Mechanism <CR_5.4>

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

Leadsec will give the CVE history content at Leadsec’s official website
and the user/customer can get the content he/she want to view by the
search function provided by the site.

Map Content Source <CR_5.5>

Describe the source of your CVE content
(required):

One security researcher of Leadsec will keep get the latest update from
CVE’s official website and make sure to catch the speed of the newest
CVE content.

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

WAF will provide the detailed CVE info in "Event Description" as the below:

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

In WAF's module "Event Set", the full CVE description can be got through the
function "Event description" when to create or update the policy set based on
the event name. The detailed CVE info includes the context content related to
this CVE name.

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

In module named “Event Help” of WAF, there give the user the full CVE list.
The left panel of this page will show event list which includes all the event
items and the right panel will refresh the according CVE full info after the
user choose one item from the list in the left panel.

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

It will be same as that mentioned in <CR_4.2> and <CR_4.3> that the user
can find the event info from the modules "Event Set" and "Event Help".

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

WAF gives the way by which the user can find the related CVE content when
he/she browser the security event log. The module "Application Monitoring" has
the sub-module named "Security Event Monitoring" which will give all the
security logs to the user. The detailed event log info can be got by double
click the event name and the according CVE info can be displayed by click the
event alias name.

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

First, in event set dialog, enter "CVE-2014-3704", in the following picture.

Second, click the "search" button, to browse the individual CVE.

The user can see the result as follows, and can also select/deselect the
individual event or enable or disable the individual.

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

In the module "Event Help" of WAF, there will be one link between the
event/service name at the left panel and CVE details with the CVE's name at the
right panel as the below.

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

The event log module of WAF can allow the user to find the related root CVE details to one event by the event name as the entry point. The module named “Security Event Monitoring” will give all the security logs and the user can get the result through two steps.

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

The "Event Help" of WAF has got the online help ready for the user and
he/she can find CVE details through browsers the event names listed in
this online help and pick out the item which matches the CVE name he/she
is looking for. Please also refer to the answer to <CR_4.3>.

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

The detailed info will keep the same as that described in the answer to
<CR_4.3>.

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

The detailed info will keep the same as that described in the answer to
<CR_4.3>.

Finding Elements Using CVE Names <CR_A.5.1>

Give detailed examples and explanations of how a
user can find associated elements in the capability by looking for their
associated CVE name (required):

The user can get the detailed CVE info from two channels through WAF. One is
in the module "Event Set" and the user can get the detailed CVE description by
click the command link "Event Description" at the last column after the event
name, the other is in the module "Event Help" by which the user can see the full
info including the CVE details.

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

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

The document related to CVE content will be got from the WAF management
in HTML format. The way by which to find the CVE-related content will be
same as that in the parts <CR_4.2> and <CR_4.3>.

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

WAF's modules "Event Set" and "Event Help" described in the parts
<CR_4.2> and <CR_4.3> can help the user to find the target content
through short names or titles. The more details can refer to these two
parts.

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

WAF's modules "Event Set" and "Event Help" described in the parts
<CR_4.2> and <CR_4.3> can help the user to find the target content
through short names or titles. More details can refer to these two
parts.

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 user can view this mapping the modules which are “Event Set”, “Event
Help”, and “Security Event Monitoring” and make use of the mapping
through the policy set, log report and online help to achieve the
target. More details can refer to <CR_4.2> and <CR_4.3>.

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: Yibo, Guo

Title: PM

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