|
|
Name of Your Organization:
InfoSec Technologies Co., Ltd.
Web Site:
http://www.infosec.co.kr
Compatible Capability:
TESS Threats Management System
Capability home page:
http://www.infosec.co.kr/solution/solution_02.asp
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 product, TESS TMS is a monitoring and response system against cyber threats. TESS TMS integrates global threat information, vulnerability information and real time response system through intrusion detection, traffic and relation analysis. It also provides threat alert/forecast in advance.
For more information, please visit our website: http://www.infosec.co.kr/solution/solution_02.asp, or call: 82-2-6003-0993.
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 provide CVE information in our rule help information.
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 check CVE content links whether accessible or not daily. And monitor that mapping information is correct.
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):
When create detection rules, up-to-date CVE information is inserted. And this information is kept up to date.
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 completely analyze vulnerability and select CVE Identifier. And we use CVE Identifier that specific vendors (MS, apple, etc.) assigned.
Map Currency Update Mechanism <CR_5.4>
Describe the mechanism used for reviewing CVE for content changes (required):
We check that mapping information is correct and there are updates or not daily.
Map Content Source <CR_5.5>
Describe the source of your CVE content (required):
MAPP(MS vulnerability, ADOBE vulnerability), securityfocus, vupen, full-disclosure, US-CERT, KR-CERT, Snort, https://cve.mitre.org/ and etc.
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):
We provide CVE information in rule help information page of TMS web or console. Our TMS manual shows how users can find CVE information.
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):
Our TMS manual shows how users can find CVE information.
Example 1:
Example 2:
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):
Our TMS manual shows how users can find CVE information. Examples are in above.
Type-Specific Capability Questions
Finding Tasks Using CVE Names <CR_A.2.1>
Give detailed examples and explanations of how a user can locate tasks in the tool by looking for their associated CVE name (required):
This task can be done refer to section <CR_A.5.1>
Example:
Finding CVE Names Using Elements in Reports <CR_A.2.2>
Give detailed examples and explanations of how, for reports that identify individual security elements, the tool allows the user to determine the associated CVE names for the individual security elements in the report (required):
Users can click CVE code and it shows related CVE site.
Example:
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):
TMS web:
- Click "탐지분석" (detection analysis)
- Click specific alert’s help page
- Can use CVE code
Example:
TMS console:
- Click "뷰어" (viewer)
- Double click specific alert
- Click "로그설명" (log explanation)
- Can use CVE code
Example:
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):
After <CR_A.3.1>, click CVE ID and show CVE site.
Example 1:
Example 2:
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):
User can access TMS web in online Using ID/PASSWORD. TESS TMS can have a public IP. All of CVE ID have a hyperlink to the CVE web page. Users can find CVE information refer to steps <CR_A.3.1>, <CR_4.2>, <CR_4.3>, <CR_A.5.1>
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.html
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):
User can access TMS web in online Using ID/PASSWORD. TESS TMS can have a public IP. All of CVE ID have a hyperlink to the CVE web page. Users can find CVE information refer to steps <CR_A.3.1>, <CR_4.2>, <CR_4.3>, <CR_A.5.1>
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):
User can access TMS web in online Using ID/PASSWORD. TESS TMS can have a public IP. All of CVE ID have a hyperlink to the CVE web page. Users can find CVE information refer to steps <CR_A.3.1>, <CR_4.2>, <CR_4.3>, <CR_A.5.1>
Finding Elements Using CVE Names <CR_A.5.1>
Give detailed examples and explanations of how a user can associated elements in the capability by looking for their associated CVE name (required):
TMS web:
- Click 탐지정보 (detection information)
- Click 검색어 (search)
- Insert CVE code
- Can search detection information which is mapped specific CVE code
TMS console:
- Click 컨트롤러 (controller)
- Click 보안 정책 (security policy)
- Click specific rule
- Click mouse right button
- Click 도움말보기 (help)
- Click CVE code
An example is in section <CR_A.2.1>
Finding CVE Names Using Elements in Reports <CR_A.5.2>
Give detailed examples and explanations of how, for reports that identify individual security elements, the capability allows the user to determine the associated CVE names for the individual security elements in the report (required):
TMS web:
- Click 탐지정보 (detection information)
- Click 검색어 (search)
- Insert elements
- Can search CVE information which is mapped specific element
TMS console:
- Click 컨트롤러 (controller)
- Click 보안 정책 (security policy)
- Click 상세조건검색 (detail search)
- Can search CVE information which is mapped specific element
An example is in section <CR_A.2.2>
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 CVE-related text in HTML format and console GUI. (Refer to section <CR_A.3.2>)
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):
We provide listing of CVE names text in HTML format.
Example:
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):
TMS console provides GUI which show elements information. See example 2 in section <CR_A.3.2>.
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):
TMS console provides GUI which show mapping information. See example 2 in section <CR_A.3.2>.
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: MuSung Kim
Title: Security 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: MuSung Kim
Title: Security Engineer
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: MuSung Kim
Title: Security Engineer