HP StorageWorks Secure Key Manager (Hardware P/N AJ087B, Version 1.1; Firmware Version:1.1) FIPS 140-2 Security Policy Level 2 Validation Document Version 0.7 December 4, 2008 © 2008 Hewlett-Packard Company This document may be freely reproduced in its original entirety.
Security Policy, version 1.0 January 31, 2008 Table of Contents 1 INTRODUCTION ...............................................................................................................................................5 1.1 PURPOSE .........................................................................................................................................................5 1.2 REFERENCES .......................................................................................................
Security Policy, version 1.0 January 31, 2008 Table of Figures FIGURE 1 – DEPLOYMENT ARCHITECTURE OF THE HP STORAGEWORKS SECURE KEY MANAGER ................................6 FIGURE 2 – BLOCK DIAGRAM OF SKM...........................................................................................................................7 FIGURE 3 – FRONT PANEL LEDS ....................................................................................................................................
Security Policy, version 1.0 January 31, 2008 Table of Tables TABLE 1 – SECURITY LEVEL PER FIPS 140-2 SECTION...................................................................................................6 TABLE 2 – LOGICAL INTERFACE AND PHYSICAL PORTS MAPPING ..................................................................................8 TABLE 3 – FRONT PANEL LED DEFINITIONS ..................................................................................................................
Security Policy, version 1.0 January 31, 2008 1 Introduction 1.1 Purpose This document is a non-proprietary Cryptographic Module Security Policy for the HP StorageWorks 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.
Security Policy, version 1.0 January 31, 2008 2 HP StorageWorks Secure Key Manager 2.1 Overview 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.
Security Policy, version 1.0 January 31, 2008 Section Section Title 10 Design Assurance 11 Mitigation of Other Attacks Level 2 N/A The block diagram of the module is given in Figure 2 – Block Diagram of SKM. The cryptographic boundary is clearly shown in the figure.
Security Policy, version 1.0 • • • January 31, 2008 Digital Signature Algorithm (DSA) PQG generation, key generation, signature generation, and signature verification: 1024 bits (certificate # 244) ANSI X9.31 Appendix A.2.
Security Policy, version 1.0 January 31, 2008 Figure 3 – Front Panel LEDs Descriptions of the LEDs are given in Table 3 – Front Panel LED Definitions. Table 3 – Front Panel LED Definitions Item Description Status 1 Power On/Standby button and system power LED Green = System is on. Amber = System is shut down, but power is still applied.
Security Policy, version 1.0 January 31, 2008 Figure 4 – Rear Panel Components Descriptions of components on the rear panel are given in Table 4 – Rear Panel Components Descriptions.
Security Policy, version 1.0 January 31, 2008 Descriptions of LEDs on the rear panel are given in Table 5 – Rear Panel LED Definitions. Table 5 – Rear Panel LED Definitions Item Description Status 1 10/100/1000 NIC 1 activity LED Green = Activity exists. Flashing green = Activity exists. Off = No activity exists. 2 10/100/1000 NIC 1 link LED Green = Link exists. Off = No link exists. 3 10/100/1000 NIC 2 activity LED Green = Activity exists. Flashing green = Activity exists.
Security Policy, version 1.0 January 31, 2008 Service Description Keys/CSPs Perform first-time initialization Configure the module when it is used for the first time Crypto Officer (admin) password – write; Kdsa public/private – write; Krsa private – write; Krsa private – write; Log signing RSA key – write; Log signature verification RSA key – write; KRsaPub – write; KRsaPriv – write.
Security Policy, version 1.0 January 31, 2008 Table 7 – User Services Service Description Keys/CSPs Authenticate to SKM Authenticate to SKM with a username and the associated password User passwords – read Generate key Generate a cryptographic key Client keys – write; PKEK – write. Modify key meta data Change the key owner or update/add/delete the custom attributes None Delete key Delete a cryptographic key Client keys – delete; PKEK – delete.
Security Policy, version 1.0 January 31, 2008 Service Description Zeroize all keys/CSPs 2.4.4 Keys/CSPs Zeroize all keys/CSPs in the module All keys/CSPs – delete Cluster Member Role The Cluster Member role is associated with other SKMs that can connect to this SKM and access cluster services. See Table 9 – Cluster Member Services. The keys and CSPs in the rightmost column correspond to the keys and CSPs introduced in Section 2.7.1.
Security Policy, version 1.0 January 31, 2008 in 60 seconds. Since 10-5 » 6×60-8, the probability of a successful password attempt in 60 seconds is considerably less than 10-5. 2.4.
Security Policy, version 1.0 January 31, 2008 Key Key Type Generation / Input Output Storage DH public param 1024-bit DiffieHellman public parameters Generated by ANSI X9.31 DRNG during session initialization In In volatile plaintext memory Upon session termination Negotiate SSH Ks and SSH Khmac DH private param 1024-bit DiffieHellman private parameters Generated by ANSI X9.
Security Policy, version 1.0 Key January 31, 2008 Generation / Input Key Type Output Storage Zeroization Use KRsaPub Server RSA public key (1024- or 2048bit) Generated by ANSI X9.31 DRNG during first-time initialization In plaintext In nona X509 volatile certificate. memory At operator delete request KRsaPriv Server RSA private key (1024- or 2048bit) Generated by ANSI X9.31 DRNG during first-time initialization Never At operator Server delete or decrypts Prezeroize request MS.
Security Policy, version 1.0 January 31, 2008 Key Type Generation / Input Client AES key 128, 192 or 256-bit AES key Generated by ANSI X9.31 DRNG Via TLS in encrypted form (encrypted with TLS Ks) per client’s request Encrypted in non-volatile memory Per client’s Encrypt request or zeroize plaintexts/decrypt request ciphertexts Client 3DES key 3DES key Generated by ANSI X9.
Security Policy, version 1.0 Key January 31, 2008 Generation / Input Key Type Output Storage Zeroization Use Log signing 1024-bit RSA Generated by Never keys public and ANSI X9.31 private keys DRNG at firsttime initialization In non-volatile memory When new log signing keys are generated on demand by Crypto Officer Sign logs and verify signature on logs ANSI X9.31 DRNG seed DRNG seed Generated by Never non-Approved RNG In non-volatile memory When module is powered off Initialize ANSI X9.
Security Policy, version 1.0 • • • • • • January 31, 2008 Pairwise consistency test for new DSA keys Pairwise consistency test for new RSA keys Continuous random number generator test on ANSI X9.31 DRNG Continuous random number generator test on non-Approved RNG Firmware upgrade integrity test Diffie-Hellman primitive test The module has two error states: a Soft Error state and a Fatal Error state.
Security Policy, version 1.0 January 31, 2008 3 Secure Operation The HP StorageWorks Secure Key Manager meets Level 2 requirements for FIPS 140-2. The sections below describe how to place and keep the module in the FIPS mode of operation. 3.1 Initial Setup The device should be unpacked and inspected according to the User Guide. The User Guide also contains installation and configuration instructions, maintenance information, safety tips, and other information.
Security Policy, version 1.0 January 31, 2008 Figure 6 – FIPS Compliance in CLI In the web administration interface, the Crypto Officer should use the “High Security Configuration” page to enable and disable FIPS compliance. To enable the Approved FIPS mode of operation, click on the “Set FIPS Compliant” button. See Figure 7 – FIPS Compliance in Web Administration Interface. This will alter various server settings as described above.
Security Policy, version 1.0 January 31, 2008 Figure 8 – Tamper-Evidence Labels Figure 9 provides a better view of the positioning of the tamper-evidence labels over the power supplies. Figure 9 – Tamper-Evidence Labels over Power Supplies HP StorageWorks Secure Key Manager © 2008 Hewlett-Packard Company This document may be freely reproduced in its original entirety.
Security Policy, version 1.0 January 31, 2008 3.4 Key and CSP Zeroization To zeroize all keys and CSPs in the module, the Crypto Officer should execute reset factory settings zeroize command in the serial console interface. Notice that, for security reasons, the command cannot be initiated from the SSH interface. When switching between different modes of operations (FIPS and non-FIPS), the Crypto Officer must zeroize all CSPs. 3.
Security Policy, version 1.
Security Policy, version 1.
