Common Weakness Enumeration

CWE Glossary Definition

Name of Your Organization:

Hewlett-Packard Development Company, L.P.

Web Site:

www.hpenterprisesecurity.com/

Compatible Capability:

HP Assessment Management Platform (AMP)

Capability home page:

http://www.hpenterprisesecurity.com/products/hp-fortify-software-security-center/hp-assessment-management-platform/

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

HP products are available for download within the customer’s HP Software Updates portal. Additional information about the products is available on either www.hpenterprisesecurity.com or www.fortify.com or download.hpstmartupdate.com/amp.

Map Currency Indication <CR_6.1>

Describe how and where your capability indicates the most recent CWE content used to create or update its mappings (required):

HP Fortify products provide CWE mappings as well as other category/taxonomy information. HP Software Security Center provides out-of-the-box reports for CWE top 25 for years 2009 and 2010.

Map Currency Update Approach <CR_6.2>

Indicate how often you plan on updating the mappings to reflect the current CWE content and describe your approach to keeping reasonably current with the CWE content when mapping them to your repository (recommended):

Security rules are updated by the Web Security Research Group weekly (dynamic rules).

MAP CURRENCY UPDATE TIME <CR_6.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 CWE content (required):

When new dynamic security rules are created, typically released on a weekly basis they include CWE identifiers.  Since CWE Identifiers hyperlink back to the MITRE website, updated content is accessible whenever MITRE publishes updates.

CWE AND COMPATIBILITY DOCUMENTATION <CR_5.1>

Provide a copy, or directions to its location, of where your documentation describes CWE and CWE compatibility for your customers (required):

This information is available in the AMP product using the Policy Manager tool.

DOCUMENTATION OF FINDING ELEMENTS USING CWE IDENTIFIERS <CR_5.2>

Provide a copy, or directions to its location, of where your documentation describes the specific details of how your customers can use CWE identifiers to find the individual security elements within your capability's repository (required):

Results are presented within the HP Assessment Management Platform product and gives customers the ability to search by CWE and/or group issues by the associated CWE mapping.

DOCUMENTATION OF FINDING CWE IDENTIFIERS USING ELEMENTS <CR_5.3>

Provide a copy, or directions to its location, of where your documentation describes the process a user would follow to find the CWE identifiers associated with individual security elements within your capability's repository (required):

Issues reported with a CWE mapping contain the CWE information inside the Recommendations tab, as a supporting reference. Additionally, users can group issues by CWE for faster access.

HP AMP, showing the issue list with CWE mappings (right-most column).

DOCUMENTATION INDEXING OF CWE-RELATED MATERIAL <CR_5.4>

If your documentation includes an index, provide a copy of the items and resources that you have listed under "CWE" in your index. Alternately, provide directions to where these "CWE" items are posted on your web site (recommended):

HP AMP has the ability to search by a CWE-ID and read our vulnerability description with a link to the MITRE documentation.

Type-Specific Capability Questions

FINDING TASKS USING CWE IDENTIFIERS <CR_A.2.1>

Give detailed examples and explanations of how a user can locate tasks in the tool by looking for their associated CWE identifier (required):

All interfaces provide users with the ability to group findings by CWE Identifiers.

Users searching for issues relating to specific CWE Identifiers can locate issues using search criteria, such as: cwe:cwe id

FINDING CWE IDENTIFIERS 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 CWE identifier for the individual security elements in the report (required):

CWE Identifiers are included when each vulnerability is identified. (See in the blue header.)

The CWE Identifier is included in reports along with a link to MITRE. (See under classifications.)

GETTING A LIST OF CLAIMED CWE IDENTIFIER COVERAGE <CR_A.2.3>

Give detailed examples and explanations of how a user can obtain a listing of all of the CWE identifiers that the owner claims the tool is effective at locating in software (required):

You can get a list of the CWE vulnerabilities that we check for through our policy manager tool available in AMP.

GETTING A LIST OF CWE IDENTIFIERS ASSOCIATED WITH TASKS <CR_A.2.6>

Give detailed examples and explanations of how a user can obtain a listing of all of the CWE identifiers that are associated with the tool's tasks (recommended):

You can get a list of the CWE vulnerabilities that we check for through our policy manager tool available in AMP.

SELECTING TASKS WITH A LIST OF CWE IDENTIFIERS <CR_A.2.7>

Describe the steps and format that a user would use to select a set of tasks by providing a file with a list of CWE identifiers (recommended):

If the user wanted to create a “policy” to check for certain CWE Identifiers, they would open the policy manager and “search by CWE” number and select the associated “rules”. They would repeat this for each CWE number. Once they’ve completed this process, they would select the created policy when they go through the scanning process. 

SELECTING TASKS USING INDIVIDUAL CWE IDENTIFIERS <CR_A.2.8>

Describe the steps that a user would follow to browse, select, and deselect a set of tasks for the tool by using individual CWE identifiers (recommended):

Same steps as <CR_A.2.7>, but they would only select a single CWE.

ELECTRONIC DOCUMENT FORMAT INFO <B.3.1>

Provide details about the different electronic document formats that you provide and describe how they can be searched for specific CWE-related text (required):

HP AMP supports exporting documents in XML and CSV. Both these formats include the CWE identifier for each vulnerability.

FINDING ONLINE CAPABILITY TASKS USING CWE IDENTIFIERS <CR_B.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 CWE identifier or through an online mapping that links each element of the capability with its associated CWE identifier(s) (required):

All interfaces provide users with the ability to group findings by CWE Identifiers.

Users searching for issues relating to specific CWE Identifiers can locate issues using search criteria, such as: cwe:XX

In HP AMP, you can group by CWE-ID.

GUI ELEMENT TO CWE IDENTIFIER MAPPING <CR_B.4.2>

Briefly describe how the associated CWE identifiers are listed for the individual security elements or discuss how the user can use the mapping between CWE identifiers and the capability's elements, also describe the format of the mapping (required):

HP AMP enables grouping by CWE.

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 CWE-related data and describe how they can be searched for specific CWE-related text (recommended):

CWE information is contained in the two export formats that HP AMP contains: XML and Comma Separated Values.

STATEMENT OF COMPATIBILITY <CR_2.11>

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 CWE Compatibility Requirements as well as all of the additional mandatory CWE Compatibility Requirements that are appropriate for our specific type of capability."

Name: Brian Miller

Title: Product 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 I agree that we will abide by all of the mandatory CWE Compatibility Requirements as well as all of the additional mandatory CWE Compatibility Requirements that are appropriate for our specific type of capability."

Name: Brian Miller

Title: Product Manager

STATEMENT ON FALSE-POSITIVES AND FALSE-NEGATIVES <CR_B.2.10> and/or <CR_B.3.7>

FOR TOOLS AND SERVICES 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 I agree that we will abide by all of the mandatory CWE Compatibility Requirements as well as all of the additional mandatory CWE Compatibility Requirements that are appropriate for our specific type of capability."

Name: Brian Miller

Title: Product Manager