|
|
Name of Your Organization:
TecForte Sdn Bhd
Web Site:
www.tecforte.com
Compatible Capability:
LR Assist
Capability home page:
https://support.tecforte.com/lr_assist/
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):
LR Assist is accessible from within TecForte SIM products, and can also be accessed directly at https://support.tecforte.com/lr_assist. A username and password is required.
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):
LR Assist does not explicitly state the CVE version. The most recent version of the CVE database is automatically downloaded and updated to LR Assist on a daily basis.
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):
A new CVE version will be investigated by our technical team to decide whether a change is needed in the automated update process for LR Assist.
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 LR Assist 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:
The LR Assist vulnerabilities information is provided by CVE.
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):
Included in the User Manual:
To find a particular vulnerability using the CVE ID number:
- Click on the Vulnerabilities Tab.
- Use the checkboxes to indicate whether you wish to restrict the search to Entry or Candidate status only.
- Enter the ID into the "Search by ID" text box, and then press Enter or click on Search button.
- From the result page, click 'Back to Search' link to go back to the search page.
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):
Included in the User Manual:
To search for information using keywords:
- Click on the Vulnerabilities Tab, check on the criteria box.
- Use the checkboxes to indicate whether you wish to restrict the search to Entry or Candidate status only.
- Enter keyword(s) into the "Search by Keyword" text box, and then press Enter or click on Search button.
- From the result page, click 'Back to Search' link to go back to the search page.
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, LR Assist does not make any distinction between the two, other than displaying the CVE Status as one of the fields. It is possible to restrict the search results based on the CVE Status field, but this feature may be removed depending on how the CVE Board updates the information in future versions.
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.
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):
LR Assist will automatically download and update the information from CVE on a daily basis. If there were any changes in status for an existing CVE entry or candidate, then the changes would be updated to LR Assist.
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):
LR Assist will automatically download and update the information from CVE on a daily basis. If there were any changes in status for an existing CVE entry or candidate, then the changes would be updated to LR Assist.
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):
LR Assist allows a user to find information for a number of different information security topics. To find a particular vulnerability using a CVE name, after logging in to LR Assist the user can click on the 'Vulnerabilities' heading, select the 'Search by ID' option and enter the CVE ID in the text box. Clicking on 'Search' will then take the user directly to the required information. LR Assist will also recognize an ID entered in non-standard ways, such as using the digits only, using both CAN and CVE prefixes, and using all, some, or none of the separators.
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:
http://www.example.com/cgi-bin/db-search.cgi?cvename=CVE-YYYY-NNNN
http://www.example.com/cve/CVE-YYYY-NNNN.htmlThe URL template can be used to access a particular CVE in the following way: https://support.tecforte.com/lr_assist/Servlet?cmd=searchCVE&searchType=searchID&from=result&txtID=CVE-YYYY-NNNN
Note that the user must log in to LR Assist for this to work.
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):
LR Assist does not provide reports which identify individual security elements.
30) 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):
LR Assist is intended for customers who wish to research security information on a variety of topics, and a keyword search is provided for this purpose. To find CVE names associated with particular security elements, after logging in to LR Assist the user can click on the 'Vulnerabilities' heading, select the 'Search by Keyword' option and enter the chosen keywords into the text box. Clicking on 'Search' will then return a list of CVE names matching the entered information. Standard operators such as AND, OR, NOT can be used to help narrow down the results.
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):
LR Assist is available in HTML format, and includes a dedicated search function which can be used to search for CVE-related text (see above for details).
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):
LR Assist uses the CVE name exclusively to identify vulnerabilities.
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):
LR Assist uses the CVE name exclusively to identify vulnerabilities.
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):
LR Assist uses the CVE name exclusively to identify vulnerabilities.
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):
LR Assist uses the CVE name exclusively to identify vulnerabilities.
36) GUI Export Electronic Document Format Info <CR_B.4.3>
CVE-related data can be accessed in HTML format either directly using the CVE ID, or by performing a search on particular keywords. We do not provide a method for exporting the data, but the user would be able to print it, or copy and paste in the normal fashion.
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