|
|
Name of Your Organization:
Sangfor Technologies Co., Ltd.
Web Site:
Compatible Capability:
Next Generation Application Firewall (NGAF)
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):
CVE compatibility information is available within the NGAF product management Web page.
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 Rule, our NGAF product has a hyperlink to the respective rule page, and from the page, the CVE name and detail content is supplied. Our vulnerability database updates every two weeks. So customers can find the up-to-date CVE content on the NGAF product management Web page.
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):
We will update the CVE mapping information every two weeks. Our signature research team will track CVE content change, and will select some of them to put into the new signature database version.
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):
We will issue release notice on web site. Our NGAF product provides auto update and manual update methods and customers can update the new vulnerability database version.
Map Content Selection Criteria <CR_5.4>
Describe the criteria used for determining the relevance of a given CVE Identifier to your Capability (required):
We select the CVE Identifiers that are popular in use and vital for system and applications.
Map Currency Update Mechanism <CR_5.4>
Describe the mechanism used for reviewing CVE for content changes (required):
Our signature research team has special personnel to review CVE content changes every day.
Map Content Source <CR_5.5>
Describe the source of your CVE content (required):
The new CVE content mainly comes from CVE website, and from the CVE website we know the new 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):
We provide CVE content in the vulnerability database module within the NGAF product management web page.
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):
CVE names may be used as a search criterion in the NGAF product management web page.
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 associated elements in the NGAF product management web page according to the following steps:
- Select Object define » Vulnerability database.
- Select search method such as vulnerability name keyword.
- Input element in the search box.
- Press the search button to complete the search task.
Input "ACDSee" using vulnerability name keyword.
Select one to view detail vulnerability information include CVE content.
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):
CVE names may be used as a search criterion in the NGAF product management web page according to the following steps:
- Select Object define » vulnerability database
- Select search method using CVE name
- Input CVE name in the search box.
- Press the Search button to complete the search task.
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 web page supplies CVE names. When users browse the report in the web page, they can select one item to view the details of the individual security elements, including the associated CVE names.
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 provide a .xls file, which include all the related CVE names. Users can use "find" and "search" function in it.
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):
Some of the mapping information example between the CVE_ID and SID are listed hereinafter:
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):
Please refer to the answer for <CR_A.2.1>.
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):
Users can select the associated security elements such as "attack ID" or "name" in the NGAF product management web page. The result will display in another web page, and users can obtain the mapping information between CVE entries and the capability’s elements.
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: Zhou Xin
Title: Director of Security Team
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: Zhou Xin
Title: Director of Security Team
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: Zhou Xin
Title: Director of Security Team