Dell W-3000 and W-6000/M3 Mobility Controllers with Dell AOS FIPS Firmware Non-Proprietary Security Policy FIPS 140-2 Level 2 January 26, 2015 This is to advise that the document entitled “Aruba 3000 and 6000/M3 Mobility Controllers with ArubaOS FIPS Firmware Non-Proprietary Security Policy FIPS 140-2 Level 2” Version 3.2, dated August 2014, applies to Dell W-3000 and W-6000/M3 Mobility Controllers with Dell AOS FIPS Firmware.
Dell Networking W-3000 Controller Series Product Images: Aruba 3000 Controller Series Product Images: Dell W-3000, W-6000/M3 Series Controllers FIPS 140-2 Security Policy 2
Dell Networking W-6000 Controller chassis with W-6000M3 module (1) and PSU (2): Aruba 6000-400 controller chassis with M3 Mark I modules (4) and PSU (3): If you have questions or concerns, please contact Dell Technical Support at www.dell.com/support, additional product documentation is also available by device under user manuals.
Aruba 3000 and 6000/M3 Mobility Controllers with ArubaOS FIPS Firmware Non-Proprietary Security Policy FIPS 140-2 Level 2 Version 3.
Copyright ® © 2014 Aruba Networks, Inc. Aruba Networks trademarks include , Aruba Networks , Aruba Wireless Networks®, the registered Aruba the Mobile Edge Company logo, Aruba Mobility Management System®, Mobile Edge Architecture®, ® ® ® People Move. Networks Must Follow , RFprotectrotect , Green Island . All rights reserved. All other trademarks are the property of their respective owners.
Contents Contents............................................................................................................................................................................. 3 Preface ............................................................................................................................................................................... 5 Purpose of this Document.............................................................................................................
Tamper-Evident Labels ................................................................................................................................................. 30 Reading TELs ..............................................................................................................................................30 Required TEL Locations ..............................................................................................................................
Preface This security policy document can be copied and distributed freely. Purpose of this Document This release supplement provides information regarding the Aruba 3000 and 6000/M3 Mobility Controllers with FIPS 1402 Level 2 validation from Aruba Networks. The material in this supplement modifies the general Aruba hardware and firmware documentation included with this product and should be kept with your Aruba product documentation.
Overview The Aruba 6000 and 3000 series Mobility Controllers are network infrastructure devices providing secure, scalable solutions for enterprise Wi-Fi, network security policy enforcement, VPN services, and wireless intrusion detection and prevention. Mobility controllers serve as central points of authentication, encryption, access control, and network coordination for all mobile network services.
Physical Description Cryptographic Module Boundaries For FIPS 140-2 Level 2 validation, the Controller has been validated as a multi-chip standalone cryptographic module. The steel chassis physically encloses the complete set of hardware and firmware components and represents the cryptographic boundary of the controller. The cryptographic boundary is defined as encompassing the top, front, left, right, rear, and bottom surfaces of the chassis.
M3mk1-S-F1 LC-2G-1 LC-2G-1 LC-2G-1 M3mk1-S-F1 LC-2G-1 LC-2G24F-1 x M3mk1-S-F1 LC-2G-1 LC-2G24F-1 LC-2G24F-1 M3mk1-S-F1 LC-2G-1 LC-2G24F-1 LC-2G24FP-1 M3mk1-S-F1 LC-2G-1 LC-2G24FP-1 x M3mk1-S-F1 LC-2G-1 LC-2G24FP-1 LC-2G24FP-1 M3mk1-S-F1 LC-2G24F-1 x x M3mk1-S-F1 LC-2G24F-1 LC-2G24F-1 x M3mk1-S-F1 LC-2G24F-1 LC-2G24F-1 LC-2G24F-1 M3mk1-S-F1 LC-2G24F-1 LC-2G24F-1 LC-2G24FP-1 M3mk1-S-F1 LC-2G24F-1 LC-2G24FP-1 LC-2G24FP-1 M3mk1-S-F1 LC-2G24FP-1 x x M3mk1-S-F1 LC-
M3mk1-S-F1 M3mk1-S-F1 M3mk1-S-F1 LC-2G24FP-1 M3mk1-S-F1 M3mk1-S-F1 M3mk1-S-F1 M3mk1-S-F1 An”x” represents an empty slot. Status indicator LEDs indicate power state, status of the device, and link activity. PS1, PS2, and PS3 are for Power Supply modules. The number of power supplies required for the system depends on the number of Line Cards installed, and whether to include redundancy for fault tolerance (please refer to the Aruba 6000 Mobility Controller Installation Guide).
Intended Level of Security The Aruba 3000 and 6000/M3 Controllers and associated modules are intended to meet overall FIPS 140-2 Level 2 requirements as shown in Table 2.
Physical Security The Aruba Controller is a scalable, multi-processor standalone network device and is enclosed in a robust steel housing. The switch enclosure is resistant to probing and is opaque within the visible spectrum. The enclosure of the switch has been designed to satisfy FIPS 140-2 Level 2 physical security requirements. For the Aruba 6000-400 the left, top, right, and bottom surfaces are irremovable. The rear panel can be removed by unscrewing fifteen screws.
Table 3 ‐ FIPS 140‐2 Logical Interfaces Control Input Interface Power switch (Aruba 6000 only) Reset button (Aruba 6000 only) 10/100 Mbps Ethernet port 10/100/1000 Mbps Ethernet ports Serial console port (disabled) Status Output Interface 10/100 Mbps Ethernet port 10/100/1000 Mbps Ethernet ports LEDs Serial console port (disabled) Power Interface Power Supply POE (Aruba 6000 only) Data input and output, control input, status output, and power interfaces are defined as follows
management session over the Ethernet ports or locally over the serial port. In FIPS mode, the serial port is disabled. Web Interface The Crypto Officer can use the Web Interface as an alternative to the CLI. The Web Interface provides a highly intuitive, graphical interface for a comprehensive set of controller management tools. The Web Interface can be accessed from a TLS-enabled Web browser using HTTPS (HTTP with Secure Socket Layer) on logical port 4343.
Table 4 ‐ Crypto‐Officer Services Configuring Module Platform Define the platform subsystem firmware of the module by entering Bootrom Monitor Mode, File System, fault report, message logging, and other platform related commands Commands and configuration data Status of commands and configuration data None Configuring Hardware Controllers Define synchronization features for module Commands and configuration data Status of commands and configuration data None Configuring Internet Protocol Set IP
Table 4 ‐ Crypto‐Officer Services Status Function Cryptographic officer may use CLI "show" commands or view WebUI via TLS to view the controller configuration, routing tables, and active sessions; view health, temperature, memory status, voltage, and packet statistics; review accounting logs, and view physical interface status Commands and configuration data Status of commands and configurations IPSec tunnel establishment for RADIUS protection Provided authenticated/encrypted channel to RADIUS server
Table 4 ‐ Crypto‐Officer Services Zeroization Zeroizes all flash memory Command Progress information All CSPs will be destroyed. User Role The User role can access the controller’s IPSec and IKEv1/IKEv2 services.
802.11i with EAPTLS Access the module’s 802.11i services in order to secure network traffic 802.11i inputs, commands and data 802.11i outputs, status, and data 29, 30, 31, 32 (read) 34, 35 (read/write) Self-Tests Run Power-On Self-Tests and Conditional Tests None Error messages logged if a failure occurs None Authentication Mechanisms The Aruba Controller supports role-based authentication.
ECDSA-based authentication (IKEv1/IKEv2) User ECDSA signing and verification is used to authenticate to the module during IKEv1/IKEv2. Both P-256 and P-384 curves are supported. ECDSA P-256 provides 128 bits of equivalent security, and P-384 provides 192 bits of equivalent security. Assuming the low end of that range, the associated probability of a successful random attempt is 1 in 2^128, which is less than 1 in 1,000,000 required by FIPS 140-2.
Cryptographic Key Management Implemented Algorithms FIPS-approved cryptographic algorithms have been implemented in firmware and hardware. Hardware encryption acceleration is provided for bulk cryptographic operations for the following FIPS approved algorithms: o o o o AES (Cert. #762) Triple-DES (Cert. #667) SHS (Cert. #769) HMAC (Cert. #417) The firmware supports the following cryptographic implementations.
Note: o RSA (Cert. #1376; non-compliant with the functions from the CAVP Historical RSA List) FIPS186-2: ALG[ANSIX9.31]: Key(gen)(MOD: 1024 PubKey Values: 65537) ALG[RSASSA-PKCS1_V1_5]: SIG(gen): 1024, SHS: SHA-1/SHA-256/SHA-384/SHA512, 2048, SHS: SHA-1 o ECDSA (Cert. #466; non-compliant with the functions from the CAVP Historical ECDSA List) FIPS186-2: SIG(gen): CURVES(P-256 P-384), SHS: SHA-1 ArubaOS UBOOT Bootloader implements the following FIPS-approved algorithms: o o RSA (Cert.
Critical Security Parameters The following are the Critical Security Parameters (CSPs) used in the controller. Table 7 ‐ CSPs/Keys Used in Aruba Controllers # Name CSPs type Generation Storage and Zeroization Use 1 Key Encryption Key (KEK) Triple-DES 168-bit key Hardcoded during manufacturing Stored in Flash. Zeroized by using command ‘wipe out flash’ Encrypts IKEv1/IKEv2 Pre-shared key, RADIUS server shared secret, RSA private key, ECDSA private key, 802.11i pre-shared key and Passwords.
7 RNG seed key FIPS 186-2 RNG Seed key (512 bits) Derived using NONFIPS approved HW RNG Stored in plaintext in volatile memory. Zeroized on reboot. Seed 186-2 General purpose (x-change Notice); SHA-1 RNG 8 Diffie-Hellman private key Diffie-Hellman private key (224 bits) Generated internally during Diffie-Hellman Exchange Stored in the volatile memory. Zeroized after the session is closed.
15 Enable secret 8-64 character password CO configured Store in ciphertext in flash. Zeroized by changing (updating) through the user interface. Administrator authentication 16 User Passwords 8-64 character password CO configured Stored encrypted in Flash with KEK. Zeroized by either deleting the password configuration file or by overwriting the password with a new one.
23 IPSec session authentication keys HMAC-SHA-1 (160 bits) Established during the IPSec service implementation Stored in plaintext in volatile memory. Zeroized when the session is closed. User authentication 24 SSHv2 session keys AES (128/196/256 bits) Established during the SSHv2 key exchange Stored in plaintext in volatile memory. Zeroized when the session is closed.
31 ECDSA Private Key ECDSA suite B P-256 and P-384 curves Generated in the module Stored in flash memory encrypted with KEK. Zeroized by the CO command write erase all. Used by TLS and EAP-TLS/PEAP protocols during the handshake. 32 ECDSA Public Key ECDSA suite B P-256 and P-384 curves Generated in the module Stored in flash memory encrypted with KEK. Zeroized by the CO command write erase all. Used by TLS and EAP-TLS/PEAP protocols during the handshake. 33 802.
Self-Tests The Aruba Controller performs both power-up and conditional self-tests. In the event any self-test fails, the controller will enter an error state, log the error, and reboot automatically.
ArubaOS UBoot BootLoader Module Firmware Load Test - RSA PKCS#1 v1.5 (2048 bits) signature verification Conditional Tests on Hardware: CRNG Test to non-Approved RNGs Self-test results are logged in a log file. Upon successful completion of the power-up self tests, the module logs a KATS: passed message into a log file. Confirm the file update by checking the associated time of the file.
Installing the Controller This chapter covers the physical installation of the Aruba 3000 and 6000/M3 Controllers with FIPS 140-2 Level 2 validation. The Crypto Officer is responsible for ensuring that the following procedures are used to place the controller in a FIPS-approved mode of operation.
Package Contents The product carton should include the following: Aruba 3000 or 6000/M3 Controller Rack mounting kit Aruba User Documentation CD Tamper-Evident Labels Minimum Configuration for the Aruba 6000-400 The Aruba 6000-400 controller chassis must include the following basic components: One modular switch chassis One fan tray One Aruba M3mk1-S-F1 card in slot 0 Power Supply The number and type of power supplies required depends on the number of line cards installed in the chassis
Tamper-Evident Labels After testing, the Crypto Officer must apply Tamper-Evident Labels (TELs) to the controller. When applied properly, the TELs allow the Crypto Officer to detect the opening of the chassis cover, the removal or replacement of modules or cover plates, or physical access to restricted ports. Vendor provides FIPS 140 designated TELs which have met the physical security testing requirements for tamper evident labels under the FIPS 140-2 Standard.
Required TEL Locations The Aruba 6000-400 controller chassis requires a minimum of 11 TELs to be applied as follows: Figure 4 ‐ Required TELs for the Aruba 6000 Controller Chassis To Detect Opening the Chassis Cover 1. Spanning the left side and rear of the chassis 2. Spanning the right side and rear of the chassis To Detect the Removal of Any Module or Cover Plate 3. 4. 5. 6. 7. 8. 9. 10.
To Detect Opening the Chassis Cover 2. Spanning the top of the faceplate and top of the chassis 3. Spanning the back and top of the chassis Applying TELs The Crypto Officer should employ TELs as follows: Before applying a TEL, make sure the target surfaces are clean and dry. Do not cut, trim, punch, or otherwise alter the TEL. Apply the wholly intact TEL firmly and completely to the target surfaces.
When installing expansion modules for the Aruba 6000, use only FIPS-approved modules, replace TELs affected by the change, and record the reason for the change, along with the new TEL locations and serial numbers, in the security log. The Crypto Officer shall not configure the Diffie-Hellman algorithm with 768-bits (Group 1) or 1024-bits (Group 2) in FIPS mode for IKEv1/IKEv2-IPSec and SSHv2. User Guidance The User accesses the controller VPN functionality as an IPsec client.
Setup and Configuration The Aruba 3000 and 6000/M3 Controllers meet FIPS 140-2 Level 2 requirements. The sections below describe how to place and keep the controller in FIPS-approved mode of operation. The Crypto Officer (CO) must ensure that the controller is kept in a FIPS-approved mode of operation. The controller can operate in two modes: the FIPS-approved mode, and the standard non-FIPS mode. By default, the controller operates in non-FIPS mode. Setting Up Your Controller To set up your controller: 1.
To verify that FIPS mode has been enabled, issue the command “show fips”.
