FIPS 140-2 Non-Proprietary Security Policy for Aruba RAP-5WN Remote Access Point Version 2.1 August 2014 Aruba Networks™ 1344 Crossman Ave. Sunnyvale, CA 94089 1 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®, RFProtect®, Green Island®. All rights reserved. All other trademarks are the property of their respective owners. Open Source Code Certain Aruba products include Open Source software code developed by third parties, including software code subject to the GNU General Public License (GPL), GNU Lesser General Public License (LGPL), or other Open Source Licenses. The Open Source code used can be found at this site: http://www.arubanetworks.com/open_source Legal Notice The use of Aruba Networks, Inc. switching platforms and software, by all individuals or corporations, to terminate other vendors’ VPN client devices constitutes complete acceptance of liability by that individual or corporation for this action and indemnifies, in full, Aruba Networks, Inc. from any and all legal actions that might be taken against it with respect to infringement of copyright on behalf of those vendors. Warranty This hardware product is protected by the standard Aruba warranty of one year parts/labor. For more information, refer to the ARUBACARE SERVICE AND SUPPORT TERMS AND CONDITIONS. Altering this device (such as painting it) voids the warranty. Copyright © 2014 Aruba Networks, Inc. Aruba Networks trademarks include , Aruba Networks®, Aruba Wireless Networks®,the registered Aruba the Mobile Edge Company logo, and Aruba Mobility Management System®. 2 1  INTRODUCTION .................................................................................................................................4  1.1  ACRONYMS AND ABBREVIATIONS ................................................................................................... 4  2  PRODUCT OVERVIEW ......................................................................................................................5  2.1  RAP-5WN ...................................................................................................................................... 5  2.1.1  Physical Description............................................................................................................... 5  2.1.1.1  Dimensions/Weight ............................................................................................................ 5  2.1.1.2  Interfaces ............................................................................................................................ 5  2.1.1.3  Indicator LEDs ................................................................................................................... 6  3  MODULE OBJECTIVES .....................................................................................................................8  3.1  SECURITY LEVELS ........................................................................................................................... 8  3.2  PHYSICAL SECURITY ....................................................................................................................... 8  3.2.1  Applying TELs ........................................................................................................................ 8  3.2.2  Required TEL Locations ......................................................................................................... 9  3.2.3  Inspection/Testing of Physical Security Mechanisms ........................................................... 11  3.3  OPERATIONAL ENVIRONMENT....................................................................................................... 11  3.4  LOGICAL INTERFACES ................................................................................................................... 11  4  ROLES, AUTHENTICATION AND SERVICES ............................................................................13  4.1  ROLES ........................................................................................................................................... 13  4.1.1  Crypto Officer Authentication .............................................................................................. 13  4.1.2  User Authentication .............................................................................................................. 13  4.1.3  Wireless Client Authentication ............................................................................................. 14  4.1.4  Strength of Authentication Mechanisms ............................................................................... 14  4.2  SERVICES ...................................................................................................................................... 14  4.2.1  Crypto Officer Services......................................................................................................... 14  4.2.2  User Services ........................................................................................................................ 15  4.2.3  Wireless Client Services ....................................................................................................... 16  4.2.4  Unauthenticated Services ..................................................................................................... 16  5  CRYPTOGRAPHIC ALGORITHMS ..............................................................................................17  6  CRITICAL SECURITY PARAMETERS .........................................................................................19  7  SELF TESTS........................................................................................................................................24  8  SECURE OPERATION ......................................................................................................................26  3 1 Introduction This document constitutes the non-proprietary Cryptographic Module Security Policy for the Aruba RAP- 5WN Access Point with FIPS 140-2 Level 2 validation from Aruba Networks. This security policy describes how the AP meets the security requirements of FIPS 140-2 Level 2, and how to place and maintain the AP in a secure FIPS 140-2 mode. This policy was prepared as part of the FIPS 140-2 Level 2 validation of the product. FIPS 140-2 (Federal Information Processing Standards Publication 140-2, Security Requirements for Cryptographic Modules) details the U.S. Government requirements for cryptographic modules. More information about the FIPS 140-2 standard and validation program is available on the National Institute of Standards and Technology (NIST) Web-site at: http://csrc.nist.gov/groups/STM/cmvp/index.html This document can be freely distributed. 1.1 Acronyms and Abbreviations AES Advanced Encryption Standard AP Access Point CBC Cipher Block Chaining CLI Command Line Interface CO Crypto Officer CPSec Control Plane Security protected CSE Communications Security Establishment Canada CSP Critical Security Parameter ECO External Crypto Officer EMC Electromagnetic Compatibility EMI Electromagnetic Interference FE Fast Ethernet GE Gigabit Ethernet GHz Gigahertz HMAC Hashed Message Authentication Code Hz Hertz IKE Internet Key Exchange IPsec Internet Protocol security KAT Known Answer Test KEK Key Encryption Key L2TP Layer-2 Tunneling Protocol LAN Local Area Network LED Light Emitting Diode SHA Secure Hash Algorithm SNMP Simple Network Management Protocol SPOE Serial & Power Over Ethernet TEL Tamper-Evident Label TFTP Trivial File Transfer Protocol WLAN Wireless Local Area Network 4 2 Product Overview This section introduces the various Aruba Wireless Access Points, providing a brief overview and summary of the physical features of each model covered by this FIPS 140-2 security policy. 2.1 RAP-5WN This section introduces the Aruba RAP-5WN Access Point (AP) with FIPS 140-2 Level 2 validation. It describes the purpose of the AP, its physical attributes, and its interfaces. The RAP-5WN is a powerful platform for the multi-user small branch office or for power users who work from a home office. The RAP-5WN is a high-performance indoor Remote Access Point platform with multiple access and uplink technologies available. The RAP-5WN features wired and wireless connectivity and security, the ability forward traffic based on policy, user centric security, and backup connectivity over cellular networks make this platform ideally suited to the always-on office. The RAP-5WN features wireless LAN capabilities on multiple SSIDs, air monitoring, and wireless intrusion detection and prevention over the 2.4GHz and 5GHz bands (802.11a/b/g and 802.11n). The RAP-5WN provides a USB port for connection to a 3G/4G modem for cellular backup of the WAN link. The Remote Access Point works in conjunction with Aruba Mobility Controllers to deliver high-speed, secure network services to remote locations. 2.1.1 Physical Description The Aruba RAP-5WN series Access Point is a multi-chip standalone cryptographic module consisting of hardware and firmware, all contained in a hard plastic case. The module contains 802.11 a/b/g/n transceiver and supports external antennas through dual, detachable antenna interface The plastic case physically encloses the complete set of hardware and firmware components and represents the cryptographic boundary of the module. Access Point configuration validated during the cryptographic module testing included:  RAP-5WN-F1  FIPS Kit 4010061-01 (Part number for Tamper Evident Labels) o The exact firmware version validated was:  ArubaOS 6.3.1.7-FIPS 2.1.1.1 Dimensions/Weight The AP has the following physical dimensions:  6.9" x 9.5" x 1.4" (175 mm x 240 mm x 35 mm)  1.0 pounds (450 grams) 2.1.1.2 Interfaces The module provides the following network interfaces:  1 x 10/100/1000 Base-T Ethernet (RJ45) Port  4 x 10/100 Base-T Ethernet (RJ45) Ports  802.11a/b/g/n Antenna Interfaces (Internal)  1 x USB 2.0 5 The module provides the following power interfaces:  12V DC power supply 2.1.1.3 Indicator LEDs There are 8 bicolor (power, ENET and WLAN) LEDs which operate as follows: Table 1 - RAP-5WN Indicator LEDs Label Function Action Status POWER AP power / ready status Off No power to AP Flashing Device booting, not ready On Device ready ENET 0 Ethernet Network Link Off Ethernet link unavailable Status / Activity On - Amber 10/100 Mbps Ethernet link negotiated On - Green 1000 Mbps Ethernet link negotiated Flashing Ethernet link activity ENET 1 Ethernet Network Link Off Ethernet link unavailable Status / Activity On – Amber 10 Mbps Ethernet link negotiated On - Green 100 Mbps Ethernet link negotiated Flashing Ethernet link activity ENET 2 Ethernet Network Link Off Ethernet link unavailable Status / Activity On - Amber 10 Mbps Ethernet link negotiated On - Green 100Mbps Ethernet link negotiated Flashing Ethernet link activity ENET 3 Ethernet Network Link Off Ethernet link unavailable Status / Activity On - Amber 10Mbps Ethernet link negotiated On - Green 100 Mbps Ethernet link negotiated Flashing Ethernet link activity ENET 4 Ethernet Network Link Off Ethernet link unavailable Status / Activity On - Amber 10 Mbps Ethernet link negotiated On - Green 100 Mbps Ethernet link negotiated 6 Flashing Ethernet link activity WLAN 2.4GHz Radio Status Off 2.4GHz radio disabled 11B/G/N On - Amber 2.4GHz radio enabled in legacy 802.11b/g mode On – Green 2.4GHz radio enabled in 802.11n mode Flashing 2.4GHz Air monitor WLAN 11A/N 5GHz Radio Status Off 5GHz radio disabled On - Amber 5GHz radio enabled in legacy 802.11a mode On – Green 5GHz radio enabled in 802.11n mode Flashing 2.4GHz Air monitor 7 3 Module Objectives This section describes the assurance levels for each of the areas described in the FIPS 140-2 Standard. . 3.1 Security Levels Table 2- Security Levels Section Section Title Level 1 Cryptographic Module Specification 2 2 Cryptographic Module Ports and Interfaces 2 3 Roles, Services, and Authentication 2 4 Finite State Model 2 5 Physical Security 2 6 Operational Environment N/A 7 Cryptographic Key Management 2 8 EMI/EMC 2 9 Self-tests 2 10 Design Assurance 2 11 Mitigation of Other Attacks N/A Overall Overall module validation level 2 3.2 Physical Security The Aruba Wireless AP is a scalable, multi-processor standalone network device and is enclosed in a robust plastic housing. The AP enclosure is resistant to probing (please note that this feature has not been validated as part of the FIPS 140-2 validation) and is opaque within the visible spectrum. The enclosure of the AP has been designed to satisfy FIPS 140-2 Level 2 physical security requirements. 3.2.1 Applying TELs The Crypto Officer must apply Tamper-Evident Labels (TELs) to the AP to allow detection of the opening of the device, and to block the serial console port (on the bottom of the device). The TELs shall be installed for the module to operate in a FIPS Approved mode of operation. Vendor provides FIPS 140 designated TELs which have met the physical security testing requirements for tamper evident labels under the FIPS 140-2 Standard. TELs are not endorsed by the Cryptographic Module Validation Program (CMVP). Aruba provides double the required amount of TELs with shipping and additional replacement TELs can be obtained by calling customer support and requesting part number 4010061-01. The Crypto Officer is responsible for securing and having control at all times of any unused tamper evident labels. 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. 8  Allow 24 hours for the TEL adhesive seal to completely cure.  Record the position and serial number of each applied TEL in a security log. Once applied, the TELs included with the AP cannot be surreptitiously broken, removed or reapplied without an obvious change in appearance: Each TEL has a unique serial number to prevent replacement with similar label. To protect the device from tampering, TELs should be applied by the Crypto Officer as pictured below: 3.2.2 Required TEL Locations This section displays all the TEL locations on the Aruba RAP-5WN. The RAP-5WN requires four (4) TELs to be applied as follows: 1. Spanning the top and bottom chassis covers and left chassis cover placed in the left corner 2. Spanning the top and bottom chassis covers and left chassis cover placed in the right corner 3. Spanning the top and bottom chassis covers and right chassis cover placed in the left corner 4. Spanning the top and bottom chassis covers and right chassis cover placed in the right corner The tamper-evident labels shall be installed for the module to operate in a FIPS approved mode of operation. Figure 1 - Front view of Aruba RAP-5WN Figure 2 - Back view of Aruba RAP-5WN 9 Figure 3 - Left side view of Aruba RAP-5WN Figure 4 - Right side view of Aruba RAP-5WN Figure 5 - Top view of Aruba RAP-5WN 10 3.2.3 Inspection/Testing of Physical Security Mechanisms Table 3 - Inspection/Testing of Physical Security Mechanisms Physical Security Mechanism Recommended Test Frequency Guidance Tamper-evident labels (TELs) Once per month Examine for any sign of removal, replacement, tearing, etc. See images above for locations of TELs Opaque module enclosure Once per month Examine module enclosure for any evidence of new openings or other access to the module internals. 3.3 Operational Environment This section does not apply as the operational environment is non-modifiable. 3.4 Logical Interfaces The physical interfaces are divided into logical interfaces defined by FIPS 140-2 as described in the following table. Table 4 - Logical Interfaces FIPS 140-2 Logical Interface Module Physical Interface  Data Input Interface 10/100/1000 Ethernet Ports  802.11a/b/g/n/ac Antenna Interfaces  USB 2.0 port  Data Output Interface 10/100/1000 Ethernet Ports 11  802.11a/b/g/n/ac Antenna Interfaces  USB 2.0 port  Control Input Interface 10/100/1000 Ethernet Ports  802.11a/b/g/n/ac Antenna Interfaces  Reset button  Status Output Interface 10/100/1000 Ethernet Ports  802.11a/b/g/n/ac Antenna Interfaces  LEDs  Power Interface Power Supply Data input and output, control input, status output, and power interfaces are defined as follows:  Data input and output are the packets that use the networking functionality of the module.  Control input consists of manual control inputs for power and reset through the power interfaces (DC power supply). It also consists of all of the data that is entered into the access point while using the management interfaces. A reset button is present which is used to reset the AP to factory default settings.  Status output consists of the status indicators displayed through the LEDs, the status data that is output from the module while using the management interfaces, and the log file. LEDs indicate the physical state of the module, such as power-up (or rebooting), o utilization level, and activation state. The log file records the results of self-tests, configuration errors, and monitoring data.  A power supply is used to connect the electric power cable  The module distinguishes between different forms of data, control, and status traffic over the network ports by analyzing the packet headers and contents. 12 4 Roles, Authentication and Services 4.1 Roles The module supports the roles of Crypto Officer, User, and Wireless Client; no additional roles (e.g., Maintenance) are supported. Administrative operations carried out by the Aruba Mobility Controller map to the Crypto Officer role. The Crypto Officer has the ability to configure, manage, and monitor the module, including the configuration, loading, and zeroization of CSPs. Defining characteristics of the roles depend on whether the module is configured as a Remote AP mode or as a Remote Mesh Portal mode.  Remote AP FIPS mode: Crypto Officer role: the Crypto Officer is the Aruba Mobility Controller that has the o ability to configure, manage, and monitor the module, including the configuration, loading, and zeroization of CSPs. User role: in the configuration, the User operator shares the same services and o authentication techniques as the Mobility Controller in the Crypto Officer role. Wireless Client role: in Remote AP configuration, a wireless client can create a o connection to the module using WPA2 and access wireless network access/bridging services. In advanced Remote AP configuration, when Remote AP cannot communicate with the controller, the wireless client role authenticates to the module via WPA2-PSK only.  Remote Mesh Portal FIPS mode: Crypto Officer role: the Crypto Officer is the Aruba Mobility Controller that has the o ability to configure, manage, and monitor the module, including the configuration, loading, and zeroization of CSPs. User role: the adjacent Mesh Point APs in a given mesh cluster. Please notice that o Remote Mesh Portal AP must be physically wired to Mobility Controller. Wireless Client role: in Remote Mesh Portal FIPS AP configuration, a wireless client can o create a connection to the module using WPA2 and access wireless network access services. 4.1.1 Crypto Officer Authentication In each of FIPS approved modes, the Aruba Mobility Controller implements the Crypto Officer role. Connections between the module and the mobility controller are protected using IPSec. Crypto Officer authentication is accomplished via either proof of possession of the IKEv1/IKEv2 pre-shared key or RSA/ECDSA certificate, which occurs during the IKEv1/IKEv2 key exchange. 4.1.2 User Authentication Authentication for the User role depends on the module configuration. When the module is configured in Remote Mesh Portal FIPS mode, the User role is authenticated via the WPA2 pre-shared key. When the module is configured in Remote AP FIPS mode, the User role is authenticated via the same IKEv1/IKEv2 pre-shared key or RSA/ECDSA certificate that is used by the Crypto Officer 13 4.1.3 Wireless Client Authentication The wireless client role defined in each of FIPS approved modes authenticates to the module via WPA2. Please notice that WEP and TKIP configurations are not permitted in FIPS mode. In advanced Remote AP configuration, when Remote AP cannot communicate with the controller, the wireless client role authenticates to the module via WPA2-PSK only. 4.1.4 Strength of Authentication Mechanisms The following table describes the relative strength of each supported authentication mechanism. Table 5 - Strength of Authentication Mechanisms Authentication Mechanism Strength Mechanism IKEv1/IKEv2 Passwords are required to be a minimum of eight characters and a maximum shared secret (CO of 32 with a minimum of one letter and one number. If six (6) integers, one role) (1) special character and one (1) alphabet are used without repetition for an eight (8) digit PIN, the probability of randomly guessing the correct sequence is one (1) in 251,596,800 (this calculation is based on the assumption that the typical standard American QWERTY computer keyboard has 10 Integer digits, 52 alphabetic characters, and 32 special characters providing 94 characters to choose from in total. The calculation should be 10 x 9 x 8 x 7 x 6 x 5 x 32 x 52 = 251, 596, 800). Therefore, the associated probability of a successful random attempt is approximately 1 in 251,596,800, which is less than 1 in 1,000,000 required by FIPS 140-2. Wireless Client Same mechanism strength as IKEv1/IKEv2 shared secret above. WPA2-PSK (Wireless Client role) Mesh AP WPA2 Same mechanism strength as IKEv1/IKEv2 shared secret above. PSK (User role) RSA Certificate The module supports 2048-bit RSA keys. RSA 2048 bit keys correspond to based authentication 112 bits of security. Assuming the low end of that range, the associated (CO role) probability of a successful random attempt is 1 in 2^112, which is less than 1 in 1,000,000 required by FIPS 140-2. ECDSA-based ECDSA signing and verification is used to authenticate to the module during authentication IKEv2. Both P-256 and P-384 curves are supported. ECDSA P-256 provides (IKEv2) 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. 4.2 Services The module provides various services depending on role. These are described below. 4.2.1 Crypto Officer Services The CO role in each of FIPS modes defined in section 3.3 has the same services. Table 6 - Crypto Officer Services 14 Service Description CSPs Accessed (see section 6 below for complete description of CSPs) FIPS mode enable/disable The CO selects/de-selects FIPS None. mode as a configuration option. Key Management The CO can configure/modify the 1 (read) IKEv1/IKEv2 shared secret (The 14, 23, 24, 25 (read/write) RSA private key is protected by non-volatile memory and cannot be modified) and the WPA2 PSK (used in advanced Remote AP configuration). Also, the CO/User implicitly uses the KEK to read/write configuration to non- volatile memory. Remotely reboot module The CO can remotely trigger a 1 (read) reboot Self-test triggered by CO/User The CO can trigger a 1, 32 (read) reboot programmatic reset leading to self-test and initialization Update module firmware The CO can trigger a module 32 (read) firmware update Configure non-security related CO can configure various None. module parameters operational parameters that do not relate to security Creation/use of secure The module supports use of 14, 21, 22, 23, 24 (read) management session between IPSec for securing the 8, 9, 10, 11, 12, 13, 15, 16, 17, module and CO management channel. 18, 19, 20 (read/write) Creation/use of secure mesh The module requires secure 25 (read) channel connections between mesh points 26, 27, 28, 29, 30, 31 (read/write) using 802.11i System Status CO may view system status See creation/use of secure information through the secured management session above. management channel Zeroization Zeroizes all flash memory All CSPs will be destroyed. 4.2.2 User Services The User services defined in Remote AP FIPS mode share the same services with the Crypto Officer role, please refer to Section 4.2.1, “Crypto Officer Services”. The following services are provided for the User role defined in Remote Mesh Portal FIPS mode: Table 7 - User Services Service Description CSPs Accessed (see section 6 below for complete description of CSPs) Generation and use of 802.11i When the module is in mesh 26, 27, 28, 29, 30, 31 (read/write) configuration, the inter-module 15 Service Description CSPs Accessed (see section 6 below for complete description of CSPs) cryptographic keys mesh links are secured with 802.11i. Use of WPA pre-shared key for When the module is in mesh 25 (read) establishment of IEEE 802.11i configuration, the inter-module keys mesh links are secured with 802.11i. This is authenticated with a shared secret Zeroization Zeroizes all flash memory All CSPs will be destroyed. 4.2.3 Wireless Client Services The following module services are provided for the Wireless Client role in each of FIPS approved modes defined in section 3.3. Table 8 - Wireless Client Services Service Description CSPs Accessed (see section 6 below for complete description of CSPs) Generation and use of 802.11i In all modes, the links between 26, 27, 28, 29, 30, 31 (read/write) cryptographic keys the module and wireless client are secured with 802.11i. Use of WPA pre-shared key for When the module is in advanced 25 (read) establishment of IEEE 802.11i Remote AP configuration, the keys links between the module and the wireless client are secured with 802.11i. This is authenticated with a shared secret only. Wireless bridging services The module bridges traffic between the wireless client and None the wired network. 4.2.4 Unauthenticated Services The module provides the following unauthenticated services, which are available regardless of role.  System status – module LEDs  Reboot module by removing/replacing power  Self-test and initialization at power-on. 16 5 Cryptographic Algorithms FIPS-approved cryptographic algorithms have been implemented in hardware and firmware. The firmware supports the following cryptographic implementations.  ArubaOS OpenSSL Module implements the following FIPS-approved algorithms: AES (Cert. #2680) o CVL (Cert. #152) o DRBG (Cert. #433) o ECDSA (Cert. #469) o HMAC (Cert. #1666) o KBKDF (Cert. #16) o RSA (Cert. #1379) o SHS (Cert. #2249) o Triple-DES (Cert. #1607) o Note: RSA (Cert. #1379; non-compliant with the functions from the CAVP Historical RSA o 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/SHA-512, 2048, SHS: SHA-1 ECDSA (Cert. #469; non-compliant with the functions from the CAVP Historical o ECDSA List)  FIPS186-2: SIG(gen): CURVES(P-256 P-384), SHS: SHA-1  ArubaOS Crypto Module implements the following FIPS-approved algorithms: AES (Cert. #2677) o CVL (Cert. #150) o ECDSA (Cert. #466) o HMAC (Cert. #1663) o RNG (Cert. #1250) o RSA (Cert. #1376) o SHS (Cert. #2246) o Triple-DES (Cert. #1605) o Note: RSA (Cert. #1376; non-compliant with the functions from the CAVP Historical RSA o List)  FIPS186-2: 17 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/SHA-512, 2048, SHS: SHA-1 ECDSA (Cert. #466; non-compliant with the functions from the CAVP Historical o ECDSA List)  FIPS186-2: SIG(gen): CURVES(P-256 P-384), SHS: SHA-1  ArubaOS UBOOT Bootloader implements the following FIPS-approved algorithms: RSA (Cert. #1380) o SHS (Cert. #2250) o  ArubaOS AP Kernel Crypto implements the following FIPS-approved algorithms: AES (Cert. #2689) o  Aruba AP Hardware (Atheros WLAN) implements the following FIPS-approved algorithms: AES (Cert. #2450) o Hardware encryption acceleration is provided by Cavium Octeon 5010 for bulk cryptographic operations for the following FIPS-approved algorithms:  AES (Cert. #861)  HMAC (Cert. #478)  SHS (Cert. #856)  Triple-DES (Cert. #708) Non-FIPS Approved Algorithms Allowed in FIPS Mode  Diffie-Hellman (key agreement; key establishment methodology provides 112 bits of encryption strength; non-compliant less than 112 bits of encryption strength)  EC Diffie-Hellman (key agreement; key establishment methodology provides 128 or 192 bits of encryption strength)  NDRNGs Non-FIPS Approved Algorithms The cryptographic module implements the following non-approved algorithms that are not permitted for use in the FIPS 140-2 mode of operations:  MD5 18 6 Critical Security Parameters The following Critical Security Parameters (CSPs) are used by the module: Table 9 - Critical Security Parameters # Storage and Name CSPs type Generation Use Zeroization 1 Key Encryption Key Triple-DES 168-bit key Hardcoded during Stored in Flash. Encrypts (KEK) manufacturing Zeroized by using IKEv1/IKEv2 Pre- command ‘ap wipe shared key, ECDSA out flash’ private key and configuration parameters. 2 SP800-90a DRBG (512 Derived using NON- Stored in plaintext in DRBG entropy input DRBG initialization bits) FIPS approved HW volatile memory. RNG Zeroized on reboot. 3 SP800-90a DRBG (384 Generated per SP800- Stored in plaintext in DRBG seed DRBG initialization bits) 90A using a derivation volatile memory. function Zeroized on reboot. 4 Generated per SP800- Stored in plaintext in DRBG key SP800-90a (256 bits) DRBG 90A volatile memory. Zeroized on reboot. 5 Generated per SP800- Stored in plaintext in DRBG V SP800-90a (128 bits) DRBG 90A volatile memory. Zeroized on reboot. 6 FIPS 186-2 RNG Seed Derived using NON- Stored in plaintext in Seed 186-2 General RNG seed (512 bits) FIPS approved HW volatile memory. purpose (x-change RNG Zeroized on reboot. Notice); SHA-1 RNG 19 7 FIPS 186-2 RNG Seed Derived using NON- Stored in plaintext in Seed 186-2 General RNG seed key key (512 bits) FIPS approved HW volatile memory. purpose (x-change RNG Zeroized on reboot. Notice); SHA-1 RNG 8 Diffie-Hellman Diffie-Hellman private Generated internally Stored in the volatile Used in establishing private key key (224 bits) during Diffie-Hellman memory. Zeroized the session key for an Exchange after the session is IPSec session closed. 9 Diffie-Hellman public Diffie-Hellman public Generated internally Stored in the volatile Used in establishing key key (2048 bits) during Diffie-Hellman memory. Zeroized the session key for an Exchange after the session is IPSec session closed. Note: Key size of DH Group 1 (768 bits) and Group 2 (1024 bits) are not allowed in FIPS mode. 10 Diffie-Hellman shared Diffie-Hellman shared Established during Stored in plain text in Used in establishing secret secret (2048 bits) Diffie-Hellman volatile memory, the session key for an Exchange Zeroized when session IPSec session is closed. 11 EC Diffie-Hellman Elliptic Curve Diffie- Generated internally Stored in the volatile Used in establishing private key Hellman (P-256 and P- during EC Diffie- memory. Zeroized the session key for an 384). Hellman Exchange after the session is IPSec session closed. 12 EC Diffie-Hellman Elliptic Curve Diffie- Generated internally Stored in the volatile Used in establishing public key Hellman (P-256 and P- during EC Diffie- memory. Zeroized the session key for an 384). Hellman Exchange after the session is IPSec session closed. 13 EC Diffie-Hellman Elliptic Curve Diffie- Established during EC Stored in plaintext in Key agreement in shared secret Hellman ( P-256 and P- Diffie-Hellman volatile memory. IKEv1/IKEv2 384) Exchange Zeroized when session is closed. 20 14 IKEv1/IKEv2 Pre- 8-64 character pre- Stored encrypted in User and module CO configured shared key shared key Flash with the KEK. authentication during Zeroized by changing IKEv1/IKEv2 (updating) the pre- shared key through the User interface. 15 HMAC-SHA- Established during Stored in plaintext in Key agreement in skeyid 1/256/384 IKEv1 negotiation volatile memory. IKEv1 (160/256/384 bits) Zeroized when session is closed. 16 HMAC-SHA- Established during Stored in plaintext in Key agreement in skeyid_d 1/256/384 IKEv1 negotiation volatile memory. IKEv1 (160/256/384 bits) Zeroized when session is closed. 17 IKEv1/IKEv2 session HMAC-SHA- Established as a result Stored in plaintext in IKEv1/IKEv2 payload authentication key 1/256/384 (160 / 256 / of IKEv1/IKEv2 volatile memory. integrity verification 384 bits) service Zeroized when session implementation. is closed. 18 IKEv1/IKEv2 session Triple-DES (168 Established as a result Stored in plaintext in IKEv1/IKEv2 payload encryption key bits/AES (128/196/256 of IKEv1/IKEv2 volatile memory. encryption bits – three key Triple- service Zeroized when session DES only) implementation. is closed. 19 IPSec session Triple-DES (168 bits / Established during the Stored in plaintext in Secure IPSec traffic encryption keys AES (128/196/256 bits IPSec service volatile memory. – three key Triple-DES implementation Zeroized when the only) session is closed. 20 IPSec session HMAC-SHA-1 (160 Established during the Stored in plaintext in IPSec traffic authentication keys bits) IPSec service volatile memory. authentication implementation Zeroized when the session is closed. 21 21 RSA 2048 bits private Generated at time of Stored in non-volatile Used by RSA Private Key key manufacturing by the memory (Trusted IKEv1/IKEv2 for TPM. Platform Module). device authentication Zeroized by physical destruction of the module. 22 RSA 2048 bits public Generated at time of Stored in non-volatile Used by RSA Public key key manufacturing by the memory. Zeroized by IKEv1/IKEv2 for TPM. physical destruction of device authentication the module. 23 ECDSA suite B P-256 Generated in the Stored in flash Used by ECDSA Private Key and P-384 curves module memory encrypted IKEv1/IKEv2 for with KEK. Zeroized device authentication. by the CO command ap wipe out flash. 24 ECDSA suite B P-256 Generated in the Stored in flash Used by ECDSA Public Key and P-384 curves module memory encrypted IKEv1/IKEv2 for with KEK. Zeroized device authentication. by the CO command ap wipe out flash. 25 802.11i Pre-Shared 8-63 character 802.11i Stored in flash Used to derive the CO configured Key (PSK) pre-shared secret for memory encrypted PMK for 802.11i in use in 802.11i (SP with KEK. Zeroized advanced Remote AP by the CO command connections; 800‐108) key ap wipe out flash. programmed into AP derivation by the controller over the IPSec session. 26 802.11i Pair-Wise 802.11i secret key Derived during the Stored in the volatile Used to derive Master key (PMK) (256-bit) 802.1X handshake memory. Zeroized on 802.11i Pairwise reboot. Transient Key (PTK) 27 802.11i Pairwise 512-bit shared secret Derived during 802.11i In volatile memory Used to derive Transient Key (PTK) from which Temporal 4-way handshake only; zeroized on 802.11i session key Keys (TKs) are derived reboot 28 AES-CCM key (128 Derived from 802.11 Stored in plaintext in Used for 802.11i 802.11i session key bits) PMK volatile memory. encryption Zeroized on reboot. 29 802.11i Group Master 256-bit secret used to Generated from Stored in plaintext in Used to derive Group Key (GMK) derive GTK approved RNG volatile memory; Transient Key (GTK) zeroized on reboot 22 30 802.11i Group 256-bit shared secret Internally derived by Stored in plaintext in Used to derive Transient Key (GTK) used to derive group AP which assumes volatile memory; multicast (multicast) encryption “authenticator” role in zeroized on reboot cryptographic keys and integrity keys handshake 31 802.11i Group AES- 128-bit AES-CCM key Derived from 802.11 Stored in plaintext in Used to protect CCM Data derived from GTK group key handshake volatile memory; multicast message Encryption/MIC Key zeroized on reboot confidentiality and integrity (AES-CCM) 32 Factory CA Public RSA 2048 bits public Generated outside the Stored in non-volatile Firmware verification Key key module. memory. Zeroized by physical destruction of the module. 23 7 Self-Tests The module performs the following Self Tests after being configured into either Remote AP mode or Remote Mesh Portal mode. The module performs both power-up and conditional self-tests. In the event any self-test fails, the module enters an error state, logs the error, and reboots automatically. The module performs the following power-up self-tests:  Aruba AP Hardware (Atheros WLAN) Known Answer Test: AES-CCM KAT o  Aruba AP Hardware (Cavium Octeon 5010) Known Answer Tests: AES (encrypt/decrypt) KATs o Triple-DES (encrypt/decrypt ) KATs o HMAC-SHA1 KAT o  ArubaOS OpenSSL Module Known Answer Tests: AES (encrypt/decrypt) KATs o Triple-DES (encrypt/decrypt) KATs o DRBG KAT o RSA KAT o ECDSA Sign/Verify o SHS (SHA1, SHA256, SHA384 and SHA512) KATs o HMAC (HMAC-SHA1, HMAC-SHA256, HMAC-SHA384 and HMAC-SHA512) KATs o  ArubaOS Crypto Module Known Answer Tests: AES (encrypt/decrypt) KATs o Triple-DES (encrypt/decrypt) KATs o SHS (SHA1, SHA256, SHA384 and SHA512) KATs o HMAC (HMAC-SHA1, HMAC-SHA256, HMAC-SHA384 and HMAC-SHA512) KATs o RSA KAT o ECDSA Sign/Verify o FIPS 186-2 RNG KAT o  ArubaOS Uboot Bootloader Module Known Answer Test Firmware Integrity Test: RSA PKCS#1 v1.5 (2048 bits) signature verification with SHA- o 1 ArubaOS AP Kernel Crypto Known Answer Tests: o AES (encrypt/decrypt) KATs o AES-GCM KAT o 24 The following Conditional Self-tests are performed in the module:  ArubaOS OpenSSL Module CRNG Test to Approved RNG (DRBG) o ECDSA Pairwise Consistency Test o RSA Pairwise Consistency Test o  ArubaOS Crypto Module CRNG Test to Approved RNG (FIPS 186-2 RNG) o ECDSA Pairwise Consistency Test o RSA Pairwise Consistency Test o  ArubaOS Uboot BootLoader Module o Firmware Load Test - RSA PKCS#1 v1.5 (2048 bits) signature verification  CRNG tests to non-approved RNGs These self-tests are run for the Atheros and Cavium hardware cryptographic implementation as well as for the Aruba OpenSSL and ArubaOS cryptographic module implementations. Self-test results are written to the serial console. In the event of a KATs failure, the AP logs different messages, depending on the error. For an ArubaOS OpenSSL AP module and ArubaOS cryptographic module KAT failure: AP rebooted [DATE][TIME] : Restarting System, SW FIPS KAT failed For an Atheros or Cavium hardware POST failure: Starting HW SHA1 KAT ...Completed HW SHA1 AT Starting HW HMAC-SHA1 KAT ...Completed HW HMAC-SHA1 KAT Starting HW DES KAT ...Completed HW DES KAT Starting HW AES KAT ...Restarting system. 25 8 Secure Operation The module can be configured to be in the following FIPS approved modes of operations via corresponding Aruba Mobility Controllers that have been certificated to FIPS level 2: • Remote AP FIPS mode – When the module is configured as a Remote AP, it is intended to be deployed in a remote location (relative to the Mobility Controller). The module provides cryptographic processing in the form of IPSec for all traffic to and from the Mobility Controller. • Remote Mesh Portal FIPS mode – When the module is configured in Mesh Portal mode, it is intended to be connected over a physical wire to the mobility controller. These modules serve as the connection point between the Mesh Point and the Mobility Controller. Mesh Portals communicate with the Mobility Controller through IPSec and with Mesh Points via 802.11i session. The Crypto Officer role is the Mobility Controller that authenticates via IKEv1/IKEv2 pre-shared key or RSA/ECDSA certificate authentication method, and Users are the "n" Mesh Points that authenticate via 802.11i preshared key. In addition, the module also supports a non-FIPS mode – an un-provisioned AP, which by default does not serve any wireless clients. The Crypto Officer must first enable and then provision the AP into a FIPS AP mode of operation. This section explains how to place the module in each FIPS mode and how to verify that it is in FIPS mode. An important point in the Aruba APs is that to change configurations from any one mode to any other mode requires the module to be re-provisioned and rebooted before any new configured mode can be enabled. The access point is managed by an Aruba Mobility Controller in FIPS mode, and access to the Mobility Controller’s administrative interface via a non-networked general purpose computer is required to assist in placing the module in FIPS mode. The controller used to provision the AP is referred to below as the “staging controller”. The staging controller must be provisioned with the appropriate firmware image for the module, which has been validated to FIPS 140-2, prior to initiating AP provisioning. The Crypto Officer shall perform the following steps: 8.1.1 Configuring Remote AP FIPS Mode 1. Apply TELs according to the directions in section 3.2 2. Log into the administrative console of the staging controller 3. Deploying the AP in Remote FIPS mode configure the controller for supporting Remote APs, For detailed instructions and steps, see Section “Configuring the Secure Remote Access Point Service” in Chapter “Remote Access Points” of the Aruba OS User Manual. 4. Enable FIPS mode on the controller. This is accomplished by going to the Configuration > Network > Controller > System Settings page (this is the default page when you click the Configuration tab), and clicking the FIPS Mode for Mobility Controller Enable checkbox. 5. Enable FIPS mode on the AP. This accomplished by going to the Configuration > Wireless > AP Configuration > AP Group page. There, you click the Edit button for the appropriate AP group, and then select AP > AP System Profile. Then, check the “Fips Enable” box, check “Apply”, and save the configuration. 6. If the staging controller does not provide PoE, either ensure the presence of a PoE injector for the LAN connection between the module and the controller, or ensure the presence of a DC power supply appropriate to the particular model of the module. 7. Connect the module via an Ethernet cable to the staging controller; note that this should be a direct connection, with no intervening network or devices; if PoE is being supplied by an injector, this represents the only exception. That is, nothing other than a PoE injector should be present between the module and the staging controller. 26 8. Once the module is connected to the controller by the Ethernet cable, navigate to the Configuration > Wireless > AP Installation page, where you should see an entry for the AP. Select that AP, click the “Provision” button, which will open the provisioning window. Now provision the AP as Remote AP by filling in the form appropriately. Detailed steps are listed in section entitled “Provisioning an Individual AP” in the ArubaOS User Guide. Click “Apply and Reboot” to complete the provisioning process. a. During the provisioning process as Remote AP if Pre-shared key is selected to be the Remote AP Authentication Method, the IKE pre-shared key (which is at least 8 characters in length) is input to the module during provisioning. Generation of this key is outside the scope of this policy. In the initial provisioning of an AP, this key will be entered in plaintext; subsequently, during provisioning, it will be entered encrypted over the secure IPSec session. If certificate based authentication is chosen, the AP’s RSA or ECDSA key pair is used to authenticate AP to controller during IPSec. 9. Via the logging facility of the staging controller, ensure that the module (the AP) is successfully provisioned with firmware and configuration 10. Terminate the administrative session 11. Disconnect the module from the staging controller, and install it on the deployment network; when power is applied, the module will attempt to discover and connect to an Aruba Mobility Controller on the network. 8.1.2 Configuring Remote Mesh Portal FIPS Mode 1. Apply TELs according to the directions in section 3.2 2. Log into the administrative console of the staging controller 3. Deploying the AP in Remote Mesh Portal mode, create the corresponding Mesh Profiles on the controller as described in detail in Section “Mesh Profiles” of Chapter “Secure Enterprise Mesh” of the Aruba OS User Manual. a. For mesh configurations, configure a WPA2 PSK which is 16 ASCII characters or 64 hexadecimal digits in length; generation of such keys is outside the scope of this policy. 4. Enable FIPS mode on the controller. This is accomplished by going to the Configuration > Network > Controller > System Settings page (this is the default page when you click the Configuration tab), and clicking the FIPS Mode for Mobility Controller Enable checkbox. 5. Enable FIPS mode on the AP. This accomplished by going to the Configuration > Wireless > AP Configuration > AP Group page. There, you click the Edit button for the appropriate AP group, and then select AP > AP System Profile. Then, check the “FIPS Enable” box, check “Apply”, and save the configuration. 6. If the staging controller does not provide PoE, either ensure the presence of a PoE injector for the LAN connection between the module and the controller, or ensure the presence of a DC power supply appropriate to the particular model of the module. 7. Connect the module via an Ethernet cable to the staging controller; note that this should be a direct connection, with no intervening network or devices; if PoE is being supplied by an injector, this represents the only exception. That is, nothing other than a PoE injector should be present between the module and the staging controller. 8. Once the module is connected to the controller by the Ethernet cable, navigate to the Configuration > Wireless > AP Installation page, where you should see an entry for the AP. Select that AP, click the “Provision” button, which will open the provisioning window. Now provision the AP as Remote Mesh Portal by filling in the form appropriately. Detailed steps are listed in Section “Provisioning an Individual AP” of Chapter “The Basic User-Centric Networks” of the Aruba OS User Guide. Click “Apply and Reboot” to complete the provisioning process. 27 a. During the provisioning process as Remote Mesh Portal, if Pre-shared key is selected to be the Remote IP Authentication Method, the IKE pre-shared key (which is at least 8 characters in length) is input to the module during provisioning. Generation of this key is outside the scope of this policy. In the initial provisioning of an AP, this key will be entered in plaintext; subsequently, during provisioning, it will be entered encrypted over the secure IPSec session. If certificate based authentication is chosen, AP’s RSA key pair is used to authenticate AP to controller during IPSec. AP’s RSA private key is contained in the AP’s non volatile memory and is generated at manufacturing time in factory. b. During the provisioning process as Remote Mesh Portal, the WPA2 PSK is input to the module via the corresponding Mesh cluster profile. This key is stored on flash encrypted. 9. Via the logging facility of the staging controller, ensure that the module (the AP) is successfully provisioned with firmware and configuration 10. Terminate the administrative session 11. Disconnect the module from the staging controller, and install it on the deployment network; when power is applied, the module will attempt to discover and connect to an Aruba Mobility Controller on the network. To verify that the module is in FIPS mode, do the following: 1. Log into the administrative console of the Aruba Mobility Controller 2. Verify that the module is connected to the Mobility Controller 3. Verify that the module has FIPS mode enabled by issuing command “show ap ap-name config” 4. Terminate the administrative session 8.1.3 Verify that the module is in FIPS mode For all the approved modes of operations in either Remote AP FIPS mode or Remote Mesh Portal FIPS mode do the following to verify the module is in FIPS mode: 1. Log into the administrative console of the Aruba Mobility Controller 2. Verify that the module is connected to the Mobility Controller 3. Verify that the module has FIPS mode enabled by issuing command “show ap ap-name config” 4. Terminate the administrative session 28