|
|
Name of Your Organization:
Cert-IST
Web Site:
http://www.cert-ist.com
Compatible Capability:
Cert-IST knowledge base
Capability home page:
Registered users can access the full knowledge database at the following location:
https://wws.cert-ist.comA brief summary is also publicly available at:
http://www.cert-ist.com
1) 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 through a private web site (restricted access through certificates). It is also possible for the public to view the list of Cert-IST latest advisories on our public web site.
4) 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):
See our public web site: http://www.cert-ist.com (home page).
Note that the same information is available on the private web site and can be demonstrated on request.
5) 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 (recommended):
Each time a new version is released, all new entries are added to our database within 1 month. Old candidates are removed.
6) 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 a newly released CVE version (recommended):
Cert-IST releases a monthly bulletin to its customers where one section is devoted to new "services". These bulletins are online on the private site; "April 2002" issue has a section describing the update timeframe.
7) 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):
See our public web site: http://www.cert-ist.com
8) 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):
Page on our private site: "SEARCH FEATURE HELP"
9) 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):
See the list of latest advisory headers on our public web site: http://www.cert-ist.com
Each Cert-IST advisory has a CVE reference section, which is filled whenever appropriate.
10) 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):
URL on our public web site (http://www.cert-ist.com), describing:
- CVE
- CVE compatibility
11) Candidates Versus Entries Indication <CR_6.1>
If CVE candidates are supported or used, explain how you indicate that candidates are not accepted CVE entries (required):
The CAN- prefix is used for all candidates to differentiate them from CVE entries which have the CVE- prefix, both prefixes are stored in the database and displayed with the reference, and we direct our customers to MITRE web site to understand what is the difference between CAN and CVE.
12) Candidates Versus Entries Explanation <CR_6.2>
If CVE candidates are supported or used, explain where and how the difference between candidates and entries is explained to your customers (recommended):
This is explained in our attached document "CVE_DOCUMENTATION".
13) Candidate to Entry Promotion <CR_6.3>
If CVE candidates are supported or used, explain your policy for changing candidates into entries within your capability and describe where and how this is communicated to your customers (recommended):
When a new CVE version is released, we change candidates into entries. Usually, this is communicated to our customers in our monthly security bulletin.
14) Candidate and Entry Search Support <CR_6.4>
If CVE candidates are supported or used, explain where and how a customer can find the explanation of your search function's ability to look for candidates and entries by using just the YYYY-NNNN portion of the CVE names (recommended):
Page on our private site : "SEARCH FEATURE HELP"
16) Candidate Mapping Currency Indication <CR_6.6>
If CVE candidates are supported or used, explain where and how you tell your users how up-to-date your candidate information is (recommended):
Cert-IST releases a monthly bulletin to its customers where one section is devoted to new "services". These bulletins are online on the private site; "April 2002" issue has a section describing the update timeframe.
Type-Specific Capability Questions
26) 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):
Cert-IST private web site provides a search function that allows to search by CVE name.
There is also an online mapping on our public Web site that links each advisory of the database with its associated CVE name (this is available as well on the private web site in the advisory summary list).
27) 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:
https://wws.cert-ist.com/fast-cgi/Recherche?langue=0&Critere=CAN-2002-1179http://www.example.com/cgi-bin/db-search.cgi?cvename=CVE-YYYY-NNNN
http://www.example.com/cve/CVE-YYYY-NNNN.html
28) 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):
NO
29) 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 CVE name is clearly shown in the "CVE references" field.
See attached summary file ("listeavis_en.htm").
31) 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):
Our advisories are sent by (machine readable) structured email; the same advisories can also be easily searched through a web interface using the "search" display capability.
32) 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):
Private site (https://wws.cert-ist.com) : In our Web page "Advisory list", there is the list of our last advisories associated with their CVE name.
Public site (http://www.cert-ist.com) : In the page "Advisories and alerts" you can browse Cert-IST latest advisory list, which gives our last advisories associated with their CVE name.
33) 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):
34) 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):
Cert-IST private web site provides a search function that allows to search by CVE name.
Example showing the search for CVE-2001-0917:
There is also an online mapping on our public Web site (http://www.cert-ist.com) that links each advisory of the database to its associated CVE name.
35) 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 Question #32
36) GUI Export Electronic Document Format Info <CR_B.4.3>
Provide details about the different electronic document formats that you provide for exporting or accessing CVE-related data and describe how they can be searched for specific CVE-related text (recommended):
See Question #33
37) 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: Philippe Bourgeois
Title: Cert-IST Technical Manager
38) 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: Philippe Bourgeois
Title: Cert-IST Technical Manager