Name of Your Organization:

SecurityReason

Web Site:

www.securityreason.com

Compatible Capability:

SecurityAlert

Capability home page:

http://securityreason.com/security_alert
General Capability Questions

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 SecurityAlert Database contains CVE references that are updated everyday and are based on the most recent updates made by Mitre. Anyone can access this information through the SecurityAlert Database visiting http://securityreason.com/security_alert.
Mapping Questions

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 reference CVE versions because our data is linked directly to the CVE data in the MITRE database.

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):

Mappings are updated constantly by obtaining the latest mapping file directly from mitre.org and nvd.nist.gov. All our CVE data includes most recent CVE numbers.

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 have time frame for CVE mappings but we provide constant updates.
Documentation Questions

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):

We provide search option, searching by "CVE", visible from from search page.

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 SecurityReason has a visible option - search by - "CVE" on 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):

The CVE name of a vulnerability, if available, is displayed in the "Details" tab of the SecurityAlert Database.
Candidate Support Questions

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):

Vulnerabilities from SecurityAlert Database include hyperlinks to the candidate in the MITRE database which do display the message that the candidate is under review, because there is not direct explanation to the difference between CAN and CVE bulletins.

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):

The SecurityAlert Database does not provide any explanation of this, also see response in Item 11.

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):

When there were made changes by Mitre then in our SecurityAlert Databes we also make changes. In our Database store the candidate and the CVE name.

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):

We do not provide any indication about how up-to-date the candidate information is, though we constantly add them as they are issued.

Type-Specific Capability Questions

Online 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 User go to search page:

http://securityreason.com/search/

Selecting "CVE" in "Where:" section. The user then inputs the CVE name into the text field and clicks the submit option.

Associated vulnerabilities will be presented as the search results.

27) 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):

Example :
http://securityreason.com/securityalert/440

The user will see :

Topic : Critical SQL Injection PHPNuke <= 7.8 - Your_Account module
SecurityAlert Id : 440
CVE : CVE-2006-0679
SecurityRisk : Medium
Remote Exploit : Yes
Local Exploit : No
Exploit Given : Yes
Credit : sp3x
Date : 16.2.2006

...

Media Questions

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):

Vulnerability data is provided in HTML on the SecurityReason website:

http://securityreason.com/security_alert/

By accessing the Search page

http://securityreason.com/search/

and Selecting "CVE" in the "Where:" we can search by CVE name.

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):

The associated CVE name is listed prominently in the "Details" tab of a SecurityAlert Database entry.

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):

http://securityreason.com/securityalert/959

http://securityreason.com/securityalert/440

Graphical User Interface (GUI)

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):

Vulnerability data is provided in HTML on the SecurityReason website:

http://securityreason.com/security_alert/

By accessing the Search page

http://securityreason.com/search/

and Selecting "CVE" in the "Where:" we can search by CVE name.

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):

The associated CVE name is listed prominently in the "Details" tab of a SecurityAlert Database entry.
Questions for Signature

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: Lukas Plonka

Title: Manager, Development SecurityReason

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: Maksymilian Arciemowicz

Title: Senior Manager, Development SecurityReason

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: Lukas Plonka

Title: Manager, Development SecurityReason

Page Last Updated or Reviewed: April 28, 2016