|
|
Name of Your Organization:
TecForte Sdn Bhd
Web Site:
www.tecforte.com
Compatible Capability:
Log Radar
Capability home page:
http://www.logradar.com/product/
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):
Log Radar is a commercially available solution for security information management (SIM). For more information, or to request an evaluation copy, visit www.tecforte.com.
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):
We do not provide this information within the Log Radar product itself. The information linked to is updated daily, so we would expect to always be up to date with respect to the latest version.
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):
Log Radar provides links to an online security information knowledge base. This will always contain the latest information from CVE, which is downloaded and updated automatically every day.
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):
We do not explicitly give a timeframe, but our customers would expect Log Radar to include the very latest vulnerability information, and so any changes needed would be considered a high priority task.
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):
Included in the User Manual Appendix:
CVE is a list of information security vulnerabilities and exposures that aims to provide common names for publicly known problems. The goal of CVE is to make it easier to share data across separate vulnerability capabilities (tools, repositories, and services) with this "common enumeration."
CVE-compatible means:
- CVE SEARCHABLE - A user can search using a CVE Identifier to find related information.
- CVE OUTPUT - Information is presented that includes the related CVE Identifier(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.
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 User Manual includes a chapter on how to access the online knowledge base from within Log Radar, and how to perform searches using CVE names.
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):
The User Manual includes a chapter on how to access the online knowledge base from within Log Radar, and how to perform searches using keywords.
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 currently include an index.
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 difference between candidates and entries has effectively disappeared, and a set of candidates has not been promoted since 2004. As such, Log Radar will not make any distinction between the two.
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):
See explanation above.
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):
Log Radar provides several links to an online security information knowledge base, which is provided in HTML format, and contains a dedicated search function. There is also a User Manual provided in PDF format, which can be searched using the built-in search function of any PDF reader.
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):
Vulnerabilities are always referred to by their CVE names.
31) 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):
Vulnerabilities are always referred to by their CVE names.
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):
Log Radar can be used to directly access the online security information knowledge base, which includes a dedicated search function.
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):
Log Radar provides a number of different reports and alerts, based on security information gathered from a wide variety of sources. Where relevant, the reports and alerts will highlight text referring to a particular program, service, OS, etc. By clicking on this the user will be returned a list of matching CVE names.
36) GUI Export Electronic Document Format Info <CR_B.4.3>
We do not provide a means of exporting the CVE-related information.
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: Mark Hrynczak
Title: QA & Support 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: Mark Hrynczak
Title: QA & Support Manager