Name of Your Organization:

Cert-Lexsi

Web Site:

http://www.lexsi.com

Compatible Capability:

CSI

Capability home page:

https://www.lexsi.com/abonnes
General Capability Questions

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

Our vulnerability database is accessible to our customers at the following URL: https://www.lexsi.com/abonnes

Mapping Questions

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

A line is reserved in each of our vulnerabilities bulletins to link to the CVE description from the mitre.org website, when the CVE has been assigned.

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 monitor the CVE changes using the following website: https://cassandra.cerias.purdue.edu/CVE_changes/

A custom automated script sends us a daily mail when there are changes, and we manually review each of our bulletins to add the CVE information if necessary.

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 explain it in the Help/CVE section found at https://www.lexsi.com/abonnes/aide/cvedoc.php

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 have a list of products we watch vulnerabilities for. We read each newly assigned CVE description and compare it to our product database, and update (or create) related bulletins accordingly.

Map Currency Update Mechanism <CR_5.4>

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

Our vulnerability watch service daily reviews for information updates about vulnerabilities discussed in our bulletins and updates them if necessary.

Map Content Source <CR_5.5>

Describe the source of your CVE content (required):

We get the CVE content from the Mitre website (cve.mitre.org) as well as many other sources, such as oss-security mailing list.

Documentation Questions

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

Information describing CVE and CVE compatibility is available at the following location: https://www.lexsi.com/abonnes/aide/cvedoc.php

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

Information describing CVE searchability is available at the following location: https://www.lexsi.com/abonnes/aide/cvedoc.php

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

Several screenshots showing the information related to any vulnerability within our database (including the CVE reference) are present in our documentation, which can be found here: https://www.lexsi.com/abonnes/aide/manuel.php

It also describes the search feature.

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

Our documentation does not provide a list of the items mapped to a CVE.

Service Questions

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 security element displays a list of products affected by the vulnerability under a section named "Vulnerable".

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

By going to a specific vulnerability bulletin, the user can see the CVE related to this bulletin by looking at the right array, inside which there is a line "CVE" listing all CVE names associated to the bulletin.

If there are several security elements and several CVE names, the description section will explain which elements are bound to which CVE names.

Online Capability Questions

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

To find the bulletin associated to a CVE, the user has to perform a search, by clicking on the "Vulnerabilities" tab, and then on "Search". Then, the CVE is entered in the "CVE" field and by clicking "Submit", the security elements associated with the searched CVE will be displayed.

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

If the tool is configured to be in French language, the URL template is: https://www.lexsi.com/abonnes/vulnsearch.php?action=Envoyer&cve=[CVE name]

If the tool is configured in English, the URL template is: https://www.lexsi.com/abonnes/vulnsearch.php?action=Submit&cve=[CVE name]

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

N/A

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

By going to a specific vulnerability bulletin, the user can see the CVE related to this bulletin by looking at the right array, inside which there is a line "CVE" listing all CVE names associated to the bulletin.

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

When there are several CVE names associated with several security elements, the mapping will be found in the "Description" section of our bulletins.

Media Questions

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 web site with security bulletins in html format. The CVE-related text can be found in the "Description" area. There is also a link to the Mitre website.

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 of our documents provide full content of our vulnerability bulletins, which contains CVE names as described in CR_A.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):

Below is a screenshot of the Description section of a vulnerability, and the right array where CVE mapping can be found.
Electronic Document Element to CVE Name Mapping

Graphical User Interface (GUI)

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

See CR_A.4.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):

See CR_A.4.2.

The mapping is an HTML link to the CVE description on Mitre’s website.

Questions for Signature

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: Daniel LUNGHI

Title: Security and Watch Service Engineer

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: Daniel LUNGHI

Title: Security and Watch Service Engineer

Page Last Updated or Reviewed: April 28, 2016