|
|
Name of Your Organization:
Rapid7 LLC
Web Site:
www.rapid7.com
Compatible Capability:
Metasploit Express
Capability home page:
http://www.rapid7.com/products/penetration-testing.jsp
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):
Metasploit Express is easy-to-use software for security professionals with a broad range of responsibilities who need an accessible and affordable penetration testing solution to verify the findings of their vulnerability scanners without extensive training.
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):
The Modules tab of the product UI indicates will display the exploits most recently disclosed first. Exploit modules include CVE Identifiers, when available and are updated to include CVE Identifiers when they become available for a specific vulnerability. Our modules only include the identifier itself, not the descriptive text for a given CVE.
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 validate our CVE mappings with each weekly updates and correct any mappings that may have changed. Since CVE Identifiers that have been accepted are normally static, we rarely need to change these references.
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 our modules on a weekly basis, including the CVE Identifiers. We describe our update cycle as weekly and mention this in sales discussions, email, web site content, and documentation.
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 develop exploits. These exploits usually correlate to a known vulnerability, which often has an assigned CVE Identifier. If a CVE Identifier is available, we include this CVE ID within the module file.
Map Currency Update Mechanism <CR_5.4>
Describe the mechanism used for reviewing CVE for content changes (required):
During each weekly update build, we review all new modules and verify that the existing modules point to valid references.
Map Content Source <CR_5.5>
Describe the source of your CVE content (required):
We access the CVE web site, along with the web sites of OSVDB and SecurityFocus to determine which vulnerability applies to our exploit. In some cases, we determine the CVE from the advisory published by the vendor or the identifying organization.
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):
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):
http://www.metasploit.com/documents/express/UserGuide.pdf
Page 22 ff.The Module Browser within Metasploit Express provides specific support for CVE references. To search for an exploit or auxiliary module by its CVE reference, simple enter "CVE:IDENTIFIER" into the search form. One example of this would be: "CVE:2008-4250" to locate the Microsoft Server Service Relative Path Stack Corruption exploit.
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):
http://www.metasploit.com/documents/express/UserGuide.pdf
Page 50 ff.Searching for Modules
To search for modules:
- Click on the Modules tab.
- Enter a keyword expression in the Search Modules field to search for a specific module. Use the Search Keywords table located directly below the search field to create the desired keyword expression (e.g., name:Microsoft, cve:2008).
- Hit Enter to perform the search.
When the results are returned, you can click on any Module name to view more detailed information about that module and view all the configurable options for a manual attack.
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):
Indexing is provided through the Modules tab.
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):
The process for using the Modules tab for searching for a vulnerability based on an identifier: cve:2010-XXXX
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):
Reports generated by the tool list the CVE reference and link to the CVE web site.
Getting a List of CVE Names Associated with Tasks <CR_A.2.4>
Give detailed examples and explanations of how a user can obtain a listing of all of the CVE names that are associated with the tool’s tasks (recommended):
CVEs are not associated with tasks within the tool.
Selecting Tasks with a List of CVE Names <CR_A.2.5>
Describe the steps and format that a user would use to select a set of tasks by providing a file with a list of CVE names (recommended):
The capability does not exist to select a set of tasks based on CVE names.
Selecting Tasks Using Individual CVE Names <CR_A.2.6>
Describe the steps that a user would follow to browse, select, and deselect a set of tasks for the tool by using individual CVE names (recommended):
The user can search for a specific identifier within the modules tab.
Non-Support Notification for a Requested CVE Name <CR_A.2.7>
Provide a description of how the tool notifies the user that task associated to a selected CVE name cannot be performed (recommended):
If the CVE is found within the Modules tab, then the task can be performed.
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):
The Module Browser within Metasploit Express provides specific support for CVE references. To search for an exploit or auxiliary module by its CVE reference, simple enter "CVE:IDENTIFIER" into the search form. One example of this would be: "CVE:2008-4250" to locate the Microsoft Server Service Relative Path Stack Corruption exploit.
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):
We reference the CVE name and the link within the report for any identified vulnerability.
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):
The Module Browser within Metasploit Express provides specific support for CVE references. To search for an exploit or auxiliary module by its CVE reference, simple enter "CVE:IDENTIFIER" into the search form. One example of this would be: "CVE:2008-4250" to locate the Microsoft Server Service Relative Path Stack Corruption exploit.
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):
A search for the CVE- prefix within the generated report will indicate references.
Getting a List of CVE Names Associated with Tasks <CR_A.5.4>
Give detailed examples and explanations of how a user can obtain a listing of all of the CVE names that are associated with the capability’s tasks (recommended):
CVEs are not associated with tasks within the tool.
Selecting Tasks with a List of CVE Names <CR_A.5.5>
Describe the steps and format that a user would use to select a set of tasks by providing a file with a list of CVE names (recommended):
CVEs are not associated with tasks within the tool.
Selecting Tasks Using Individual CVE Names <CR_A.5.6>
Describe the steps that a user would follow to browse, select, and deselect a set of tasks for the capability by using individual CVE names (recommended):
CVEs cannot be used to select sets of tasks (only single task, via Modules).
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):
Report formats: PDF, Word, HTML, bultin in search functionality and the report index for exploited vulnerabilities.
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 identifiers link to the CVE web site.
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):
Searching for Modules
To search for modules:
- Click on the Modules tab.
- Enter a keyword expression in the Search Modules field to search for a specific module. Use the Search Keywords table located directly below the search field to create the desired keyword expression (e.g., name:Microsoft, cve:2008).
- Hit Enter to perform the search.
When the results are returned, you can click on any Module name to view more detailed information about that module and view all the configurable options for a manual attack.
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):
Searching for Modules
To search for modules:
- Click on the Modules tab.
- Enter a keyword expression in the Search Modules field to search for a specific module. Use the Search Keywords table located directly below the search field to create the desired keyword expression (e.g., name:Microsoft, cve:2008).
- Hit Enter to perform the search.
When the results are returned, you can click on any Module name to view more detailed information about that module and view all the configurable options for a manual attack.
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):
Users can carry out a Modules tab search. Reports also list vulnerabilities by CVE Identifier.
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):
Report formats: PDF, Word, HTML, bultin in search functionality and the report index for exploited vulnerabilities.
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: Christian Kirsch
Title: Product Marketing Manager
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: Christian Kirsch
Title: Product Marketing Manager
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: Christian Kirsch
Title: Product Marketing Manager