|
|
Name of Your Organization:
Information-technology Promotion Agency, Japan (IPA)
Web Site:
www.ipa.go.jp/index-e.html
Compatible Capability:
Vulnerability Countermeasure Information Database (JVN iPedia)
Capability home page:
English Version: http://jvndb.jvn.jp/en/
Japanese Version: http://jvndb.jvn.jp/
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):
Vulnerability Countermeasure Information Database (JVN iPedia) is publicly available via the Internet at http://jvndb.jvn.jp/en/ (English Version) and http://jvndb.jvn.jp/ (Japanese Version). Below depicts the relationship between the English and Japanese versions of JVN, JVN iPedia and MyJVN.
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):
JVN iPedia does not indicate CVE versions, since it is updated using the most current CVE 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):
Mappings will be updated as soon as the update information is made available from the CVE/NVD website.
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):
We update the website and JVNDBRSS on a daily basis on business days (according to the Japanese calendar).
JVNDBRSS is a data feed to provide the vulnerability information newly added/updated and a yearly collection of those in the JVNRSS format ( http://jvndb.jvn.jp/schema/jvnrss_2.0.xsd ).
Using an RSS reader, people can expect and get the latest contents of the database easily, including the mapping updates that will be made, as soon as possible.
Map Content Selection Criteria <CR_5.4>
Describe the criteria used for determining the relevance of a given CVE Identifier to your Capability (required):
It covers Japanese products and the oversea software popularly used in Japan.
Map Currency Update Mechanism <CR_5.4>
Describe the mechanism used for reviewing CVE for content changes (required):
If the CVE content changes, it will reflect on the NVD webpage. We will update our repository based on the NVD update information (e.g., CVSS, CWE, CPE, ...).
Map Content Source <CR_5.5>
Describe the source of your CVE content (required):
We collect the CVE content from the CVE and NVD website. We also collect it from the software developers and other security information websites.
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):
CVE is described at the following URL. CVE Compatibility is described in section 3.
English Version: http://www.ipa.go.jp/security/english/vuln/CVE_en.html
Japanese Version: http://www.ipa.go.jp/security/vuln/CVE.html
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):
By using the search function in JVN iPedia, the vulnerability countermeasure information database, users are able to conduct a search using CVE identifiers as the keyword.
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):
CVE identifiers are displayed in the "References" section within each vulnerability countermeasure information pages.
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):
Entering the CVE name as the keyword in the search field found on JVN iPedia, will return any associated security elements that match the search parameter.
The following is an example of search results after inputting 'CVE-2009-2' to the "Keyword search" box and clicking the "Search" button to search for 'CVE-2009-2nnn.'
When JVNDB-2009-000046 is clicked, detailed information for the vulnerability is displayed.
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):
English Version:
http://jvndb.jvn.jp/search/index.php?mode=_vulnerability_search_IA_VulnSearch&lang=en&useSynonym=1&keyword=CVE-YYYY-NNNNJapanese Version:
http://jvndb.jvn.jp/search/index.php?mode=_vulnerability_search_IA_VulnSearch&lang=ja&useSynonym=1&keyword=CVE-YYYY-NNNNThe following are the search results using "URL template".
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):
YES
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 displayed in the "References" section within each vulnerability countermeasure information page. The following shows all information contained in the "References" section of a report.
Ex: http://jvndb.jvn.jp/jvndb/JVNDB-2009-000001 .
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):
The primary method for accessing JVN iPedia is through its web interface found at http://jvndb.jvn.jp/en/ . Entering the CVE name as the keyword in the search field found on JVN iPedia, will return any associated security elements that match the search parameter.
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):
The associated CVE name is listed prominently in the "References" section of a vulnerability database entry.
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):
http://jvndb.jvn.jp/jvndb/JVNDB-2009-000001
http://jvndb.jvn.jp/jvndb/JVNDB-2009-000002
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 JVN iPedia GUI provides a keyword search located on the main page. Entering the CVE name as the Keyword in the search field found on JVN iPedia, will return any associated security elements that match the search parameter.
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):
The CVE name is displayed in the "References" section within each vulnerability countermeasure information page.
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):
JVN iPedia can export electronic document formats. The following is the "JVNDBRSS" section in JVN iPedia http://jvndb.jvn.jp/en/.
By setting a JVN iPedia ID in the sec:identifier field of JVNDBRSS, which is used to specify the identifier of the security information, and storing the JVN ID and CVE identifier in the sec:reference field, which are used to specify the URL of the related security information, it is possible to demonstrate the correspondence of the JVN or JVN iPedia ID with the CVE identifier.
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: Tadashi Yamagishi
Title: Senior Researcher, Security Engineering Laboratory, IT Security Center, Information-technology Promotion Agency, Japan (IPA)
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: Tadashi Yamagishi
Title: Senior Researcher, Security Engineering Laboratory, IT Security Center, Information-technology Promotion Agency, Japan (IPA)
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: Tadashi Yamagishi
Title: Senior Researcher, Security Engineering Laboratory, IT Security Center, Information-technology Promotion Agency, Japan (IPA)