|
|
Name of Your Organization:
Fortinet, Inc.
Web Site:
Compatible Capability:
FortiGuard
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 and vulnerability information is made available through our public web portal, FortiGuard Center (http://www.fortiguard.com). This is available to both our customers and the public.
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):
NVC Reports (New Vulnerability Coverage) are available on a bi-weekly basis on our FortiGuard Center web portal (http://www.fortiguard.com).
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):
Our Virus Encyclopedia is updated whenever we push out new IPS definitions, and is searchable for CVE mappings. On average, this occurs two times per week.
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):
A detailed history of service updates is available to our customers at the following address. Listed vulnerability will map to available CVE content: http://www.fortiguard.com/intrusionprevention/serviceUpdateHistory.html
Map Content Selection Criteria <CR_5.4>
Describe the criteria used for determining the relevance of a given CVE Identifier to your Capability (required):
For FortiGuard intrusion prevention, we select CVE Identifiers for vulnerabilities we cover (develop signature sets / decoders for). These come in through multiple sources, from vulnerabilities we discover, to information sharing programs, to various third parties.
Map Currency Update Mechanism <CR_5.4>
Describe the mechanism used for reviewing CVE for content changes (required):
Our vulnerability encyclopedia includes links for each shown CVE Identifier to the CVE website, so any updated content will reflect here.
Map Content Source <CR_5.5>
Describe the source of your CVE content (required):
CVE content is collected from a variety of resources including the CVE website, information sharing programs (e.g., MAPP), mailing lists (e.g., Bugtraq). At times we will also assign our own CVE Identifier if the vendor has not done so already for vulnerabilities we discover in third-party products.
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):
CVE and CVE Compatibility
Common Vulnerabilities and Exposures (CVE®) is a dictionary of common names (i.e., CVE Identifiers) for publicly known information security vulnerabilities, while its Common Configuration Enumeration (CCE™) provides identifiers for security configuration issues and exposures.
CVE’s common identifiers make it easier to share data across separate network security databases and tools, and provide a baseline for evaluating the coverage of an organization’s security tools. If a report from one of your security tools incorporates CVE Identifiers, you may then quickly and accurately access fix information in one or more separate CVE-compatible databases to remediate the problem.
"CVE-compatible" means that a tool, Web site, database, or service uses CVE names in a way that allows it to cross-link with other repositories that use CVE names. CVE-compatible products and services must meet the four (4) requirements below.
- CVE Searchable: A user can search using a CVE name to find related information.
- CVE Output: Information is presented which includes the related CVE name(s).
- Mapping: The repository owner has provided a mapping relative to a specific version of CVE, and has made a good faith effort to ensure accuracy of that mapping.
- Documentation: The organization’s standard documentation includes a description of CVE, CVE compatibility, and the details of how its customers can use the CVE-related functionality of its product or service.
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):
Searching FortiGuard for CVE
CVE Identifiers protected by FortiGuard IPS services are mapped through the Vulnerability Encyclopedia. They can be found by entering either the numerical ID (YYYY-####) or the fully qualified ID (CVE-YYYY-####) in the ‘Search’ field on the FortiGuard Encyclopedia page:
http://www.fortiguard.com/encyclopedia/index.htmlEach result will bring up specific information on the vulnerability the CVE Identifier is associated with. CVE identifiers for individual vulnerabilities can also be found on the vulnerability entry in the encyclopedia, in the "Common Vulnerabilities and Exposures (CVE)" row.
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):
All CVE names are referenced in our FortiGuard Encyclopedia for individual security elements. The following outlines the simple directions required to find associated CVE names:
- Connect to the FortiGuard Center (http://www.fortiguard.com) with your web browser
- Browse to the Encyclopedia page
- In the "Search" field, enter the individual security element that you wish to find the associated CVE name for. Alternatively, recent security elements that have been listed are available on this page with hot links to their encyclopedia page (where the CVE name will be shown).
- Click on the resulting search link or (as described above), a hot link to a recent security element.
- Observe the "CVE ID" field that is pulled up for the listed security element (see below image). This is where you will find the associated CVE name.
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):
The FortiGuard Vulnerability Encyclopedia supports full-text searches for both vulnerabilities, and their associated side-effects / descriptions. One may search for a CVE name which will pull up the full text description. For further information, refer to <CR_4.2> and <CR_4.3>.
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):
Reports for security elements are provided online through FortiGuard Security Advisories and vulnerability coverage (i.e., Microsoft, Adobe). All reports have references to CVE identifiers in two places. The first will be directly beside a description of the security element. The second place is a reference index which provides links for all described CVE names for all elements outlined in the report. A screenshot is provided below for reference.
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):
Each individual security element has a description page within the FortiGuard Vulnerability Encyclopedia. These pages can be pulled up by either searching for the individual security element <CR_A.2.2> or the direct CVE name mapping <CR_A.4.1.1>. The page will outline both the CVE name and the detection name that the FortiGuard Service detects the vulnerability as. A screen shot of the pulled up security element page is provided below for reference.
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):
See <CR_A.2.2>.
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):
CVE identifiers protected by FortiGuard IPS services are mapped through the Vulnerability Encyclopedia. They can be found by entering either the numerical ID (YYYY-####) or the fully qualified ID (CVE-YYYY-####) in the ‘Search’ field on the FortiGuard Encyclopedia page:
http://www.fortiguard.com/encyclopedia/index.htmlEach result will bring up specific information on the vulnerability the CVE identifier is associated with. CVE identifiers for individual vulnerabilities can also be found on the vulnerability entry in the encyclopedia, in the "Common Vulnerabilities and Exposures (CVE)" row.
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:
Online Capability CGI GET Method Support <CR_A.4.1.2>
If the URL template is for a CGI program, does it support the HTTP "GET" method? (recommended):
Yes
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):
All of our reports are available through security advisories. In each security advisory, there is a ‘References’ section which will provide a direct mapping to the CVE website. See the screenshot below.
Finding Elements Using CVE Names <CR_A.5.1>
Give detailed examples and explanations of how a user can associated elements in the capability by looking for their associated CVE name (required):
See <CR A.4.1.1>.
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):
See <CR A.4.2>.
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):
Security advisories pertaining to risks and their CVE Identifiers, along with our Encyclopedia containing details on individual security elements, are both provided through HTML format.
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):
Our electronic documents are provided online via HTML. To discover CVE names and their associated individual security elements, please refer to <CR_4.2>.
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):
Electronic documents are provided via HTML online. Please refer to <CR_4.3>.
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):
Our online portal GUI (www.fortiguard.com) provides a search function for CVE names through our vulnerability encyclopedia. For further details, please refer to <CR_4.2>.
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):
Our online portal (www.fortiguard.com) provides a search function for elements that will pull up associated CVE names. For further information, please refer to <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: Derek Manky
Title: ||Title||
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: Derek Manky
Title: Sr. Security Strategist
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: Derek Manky
Title: Sr. Security Strategist