2.4.2 User Role.............................................................................................................................................12
2.4.3 HP User Role.......................................................................................................................................13
2.4.4 Cluster Member Role...........................................................................................................................14
2.7.1 Keys and CSPs.....................................................................................................................................15
FIGURE 1–DEPLOYMENT ARCHITECTURE OF THE HPSTORAGEWORKS SECURE KEY MANAGER ................................6
FIGURE 2–BLOCK DIAGRAM OF SKM...........................................................................................................................7
FIGURE 6–FIPSCOMPLIANCE IN CLI .........................................................................................................................22
FIGURE 7–FIPSCOMPLIANCE IN WEB ADMINISTRATION INTERFACE.........................................................................22
TABLE 9–CLUSTER MEMBER SERVICES......................................................................................................................14
TABLE 10–ROLES AND AUTHENTICATIONS ................................................................................................................14
TABLE 11–LIST OF CRYPTOGRAPHIC KEYS,CRYPTOGRAPHIC KEY COMPONENTS, AND CSPS FOR SSH....................15
TABLE 12–LIST OF CRYPTOGRAPHIC KEYS,CRYPTOGRAPHIC KEY COMPONENTS, AND CSPS FOR TLS....................16
TABLE 13–CIPHER SUITES SUPPORTED BY THE MODULE’S TLSIMPLEMENTATION IN FIPSMODE ...........................17
TABLE 14–OTHER CRYPTOGRAPHIC KEYS,CRYPTOGRAPHIC KEY COMPONENTS, AND CSPS ...................................17
This document is a non-proprietary Cryptographic Module Security Policy for the HP StorageW orks Secure Key
Manager (SKM) from Hewlett-Packard Company. Federal Information Processing Standards (FIPS) 140-2, Security Requirements for Cryptographic Modules, specifies the U.S. and Canadian Governments’ requirements for
cryptographic modules. The following pages describe how HP’s SKM meets these requirements and how to use the
SKM in a mode of operation compliant with FIPS 140-2. This policy was prepared as part of the Level 2 FIPS 140-2
validation of the HP StorageWorks Secure Key Manager.
More information about FIPS 140-2 and the Cryptographic Module Validation Program (CMVP) is available at the
website of the National Institute of Standards and Technology (NIST):
http://csrc.nist.gov/groups/STM/cmvp/index.html
In this document, the HP StorageWorks Secure Key Manager is referred to as the SKM, the module, or the device.
1.2 References
This document deals only with the operations and capabilities of the module in the techn ical terms of a FIPS 140-2
cryptographic module security policy. More information is available on the module from the following sources:
.
• The HP website (http://www.hp.com
) contains information on the full line of products from HP.
• The CMVP website (http://csrc.nist.gov/groups/STM/cmvp/index.html
answers to technical or sales-related questions for the module.
) contains contact information for
HP StorageWorks Secure Key Manager
This document may be freely reproduced in its original entirety.
HP provides a range of security products for banking, the Internet, and enterprise security applications. These
products use encryption technology—often embedded in hardware—to safeguard sensitive data, such as financial
transactions over private and public networks and to offload security processing from the server.
The HP StorageWorks Secure Key Manager is a hardened serv er that provides secur ity policy and key management
services to encrypting client devices and applications. After enrollment, clients, such as storage systems, application
servers and databases, make requests to the SKM for creation and management of cryptographic keys and related
metadata.
Client applications can access the SKM via its Key Management Service (KMS) server. Configuration and
management can be performed via web administration, Secure Shell (SSH), or serial console. Status-monitoring
interfaces include a dedicated FIPS status interface, a health check interface, and Simple Network Management
Protocol (SNMP).
The deployment architecture of the HP StorageWorks Secure Key Manager is shown in Figure 1 below.
Web ServerApplication ServerDatabaseStorage System
HP StorageWorks Secure Key Manager
Figure 1 – Deployment Architecture of the HP StorageWorks Secure Key Manager
2.2 Cryptographic Module Specification
The HP StorageWorks Secure Key Manager is validated at FIPS 140-2 section levels shown in Table 1 – Security
Level per FIPS 140-2 Section.
In the FIPS mode of operation, the module implements the following non-approved algorithms:
• A non-approved Random Number Generator (RNG) to seed the ANSI X9.31 DRNG
• The following commercially-available protocols for key establishment:
o Transport Layer Security (TLS) 1.0/ Secure Socket Layer (SSL) 3.1 protocol using RSA 1024 and
2048 bits for key transport. Caveat: The RSA 1024- and 2048-bit key wrapping and key
establishment provide 80 and 112 bits of encryption strength, respectively.
In the non-FIPS mode of operation, the module also implements DES, MD5, RC4, and 512- and 768-bit RSA for
signature generation and verification, and key establishment.
2.3 Module Interfaces
FIPS 140-2 defines four logical interfaces:
• Data Input
• Data Output
• Control Input
• Status Output
The module features the following physical ports and LEDs: