|
|
Name of Your Organization:
Stabsstelle DV-Sicherheit (RUS-CERT)
University of Stuttgart
Web Site:
cert.uni-stuttgart.de
Compatible Capability:
RUS-CERT's Security Announcement Service
Capability home page:
http://cert.uni-stuttgart.de/ticker/
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):
The documents published via RUS-CERT's announcement service are publicly accessible via the service's web server, and RSS-feed as well as via a mailing list.
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):
Since CVE-names are used along with a link and URL in the documents, they point to the database provided by https://cve.mitre.org/. Hence, as long as the URLs are mapped correctly at the central data base, the service inherently always uses the latest CVE version.
If there will be a major update including a change or discontinuation of old mappings (e.g. URLs to CAN numbers matching the current corresponding CVE names) the service's data base must be altered manually or semi-automatically.
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):
See above. Updates of mappings are necessary only, if there is a major update at MITRE's data base that includes a discontinuation of old mapping schemes.
A special case is the maintenance of single announcements: if there is no CVE name available at publication time, a first version without a reference is published and the CVE name creation process is iniciated (usually the author or O. Goebel sends an email message to Steven M. Christey) and the name is included in the document as soon as it is available. Then this announcement is published a second time with an appropriate version tag.
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):
In case of a major update, that requires changes in the archived documents, a special announcement describing the changes (to be) made is issued.
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):
The page that provides CVE searchability and a description how to use ist can be found at:
http://cert.uni-stuttgart.de/ticker/search.php and http://cert.uni-stuttgart.de/ticker/cve.php
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):
The page that provides CVE searchability and a description how to use ist can be found at:
http://cert.uni-stuttgart.de/ticker/search.php and http://cert.uni-stuttgart.de/ticker/cve.php
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):
Since CVE names are part of the announcements, users will implicitly find them when reading the document.
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):
The documentation does not contain an index.
A sitemap, providing a link to http://cert.uni-stuttgart.de/ticker/cve.php can be found at: http://cert.uni-stuttgart.de/sitemap.php
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):
This is also done implicitly, since the documents contain links or URLs to the appropriate page at https://cve.mitre.org/ that contain the description as well as the status of the respective CVE name.
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 done here: http://cert.uni-stuttgart.de/ticker/cve.php
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):
This is also done implicitly, since the documents contain links or URLs to the appropriate page at https://cve.mitre.org/ that contain the description as well as the status of the respective CVE name. Hence, users get this information as soon as they follow the link to the CVE database.
14) Candidate Mapping Currency Indication <CR_6.6>
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):
See above.
Type-Specific Capability Questions
24) 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 search function not only allows for the search for CVE names but also for keywords or strings. Thus, there are two ways to find a CVE name:
- When selecting an announcement by another identification characteristic than a CVE name the reader gets the CVE name within the document itself if there is a matching name (the database does contain documents that do not refer to a CVE name, because they describe somethind that is not identified by CVE).
- When searching for a specific CVE name, the system returns all documents that refer to this CVE name.
25) 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):
An URI can be produced according the following template:
http://cert.uni-stuttgart.de/ticker/search.php?query=CVE-YYYY-NNNN
Example:
http://cert.uni-stuttgart.de/ticker/search.php?query=CVE-2006-6235The System then produces an answer page that contains a search form containing the CVE name that has been searched for, some information on how to use the search function especially when seraching for CVE names and a list of links to the documents found as well as their abstacts.
26) Online Capability CGI GET Method Support <CR_A.4.1.1>
If the URL template is for a CGI program, does it support the HTTP "GET" method? (recommended):
YES (in the way described above)
29) 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):
In the current version the service provides plain text and HTML renderings of the documents. CVE names in these documents are provided within special structures to allow for an structured search. In the next version of the service will provide the XML documents in CAIF 1.2 (see http://www.caif.info/) which provides very sophisticated structures to reference single paragraphs to external IDs like CVE names.
30) 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 Documents provide a description.
See: http://cert.uni-stuttgart.de/ticker/article.php?mid=1342
31) Electronic Document Element to CVE Name Mapping <CR_B.3.2>
Provide example documents that demonstrate the mapping from the capability's individual elements to the respective CVE name(s) (recommended):
See as an example:
32) 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):
The capability is a webservice and hence has a web based GUI.
The page http://cert.uni-stuttgart.de/ticker/cve.php provides some documentation as well as a text input widget in which the user can type the required CVE name or keywords that he wants to be contained in document(s) to be found.
33) 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):
Documents provided in HTML rendering contain a hyperlink that is pointing to the appropriate CVE name's web page at cve.mitre.com. Hence, users may follow this link to get to the appropriate information on the referenced CVE name.
Documents in plain text rendering (not available via a GUI) provide the appropriate URL to the respective page.
34) GUI Export Electronic Document Format Info <CR_B.4.3>
The standard rendering formats are HTML and plain Text. When viewed on the service's web site, the search finction can be used. When viewed offline, any search function can be used that matches text. This also applies to plain text renderings.
35) 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: Oliver Goebel
Title: Chief Information Security Officer
36) 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: Oliver Goebel
Title: Chief Information Security Officer
37) 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: Oliver Goebel
Title: Chief Information Security Officer