FIPS 140-2 Non-Proprietary Security Policy for Aruba AP-214, AP-215, AP-274, AP-275 and AP-277 Wireless Access Points Version 1.15 October 2015 Aruba NetworksTM 1344 Crossman Ave. Sunnyvale, CA 94089-1113 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 .................................................................................................................................5 1.1 ACRONYMS AND ABBREVIATIONS ................................................................................................... 5 2 PRODUCT OVERVIEW ......................................................................................................................6 2.1 AP-214............................................................................................................................................ 6 2.1.1 Physical Description............................................................................................................... 6 2.1.1.1 Dimensions/Weight ............................................................................................................ 7 2.1.1.2 Interfaces ............................................................................................................................ 7 2.2 AP-215............................................................................................................................................ 8 2.2.1 Physical Description............................................................................................................... 8 2.2.1.1 Dimensions/Weight ............................................................................................................ 8 2.2.1.2 Interfaces ............................................................................................................................ 9 2.3 AP-274............................................................................................................................................ 9 2.3.1 Physical Description............................................................................................................. 10 2.3.1.1 Dimensions/Weight .......................................................................................................... 10 2.3.1.2 Interfaces .......................................................................................................................... 10 2.4 AP-275.......................................................................................................................................... 10 2.4.1 Physical Description............................................................................................................. 11 2.4.1.1 Dimensions/Weight .......................................................................................................... 11 2.4.1.2 Interfaces .......................................................................................................................... 11 2.5 AP-277.......................................................................................................................................... 11 2.5.1 Physical Description............................................................................................................. 12 2.5.1.1 Dimensions/Weight .......................................................................................................... 12 2.5.1.2 Interfaces .......................................................................................................................... 13 3 MODULE OBJECTIVES ...................................................................................................................14 3.1 SECURITY LEVELS ......................................................................................................................... 14 3.2 PHYSICAL SECURITY ..................................................................................................................... 14 3.2.1 Applying TELs ...................................................................................................................... 14 3.2.2 TELs Placement .................................................................................................................... 15 3.2.2.1 TELs Placement on the AP-214........................................................................................ 15 3.2.2.2 TEL Placement on the AP-215 ......................................................................................... 16 3.2.2.3 TEL Placement on the AP-274 ......................................................................................... 17 3.2.2.4 TEL Placement on the AP-275 ......................................................................................... 19 3.2.2.5 TEL Placement on the AP-277 ......................................................................................... 20 3.2.3 Inspection/Testing of Physical Security Mechanisms ........................................................... 21 3.3 OPERATIONAL ENVIRONMENT....................................................................................................... 22 3.4 LOGICAL INTERFACES ................................................................................................................... 22 4 ROLES, AUTHENTICATION AND SERVICES ............................................................................24 3 4.1 ROLES ........................................................................................................................................... 24 4.1.1 Crypto Officer Authentication .............................................................................................. 24 4.1.2 User Authentication .............................................................................................................. 24 4.1.3 Wireless Client Authentication ............................................................................................. 25 4.1.4 Strength of Authentication Mechanisms ............................................................................... 25 4.2 SERVICES ...................................................................................................................................... 26 4.2.1 Crypto Officer Services......................................................................................................... 26 4.2.2 User Services ........................................................................................................................ 27 4.2.3 Wireless Client Services ....................................................................................................... 27 4.2.4 Unauthenticated Services ..................................................................................................... 28 4.2.5 Service Available in Non-FIPS Mode ................................................................................... 28 5 CRYPTOGRAPHIC ALGORITHMS ..............................................................................................29 6 CRITICAL SECURITY PARAMETERS .........................................................................................31 7 SELF TESTS........................................................................................................................................37 8 SECURE OPERATION ......................................................................................................................39 4 1 Introduction This document constitutes the non-proprietary Cryptographic Module Security Policy for the Aruba AP- 214, AP-215, AP-274, AP-275 and AP-277 Wireless Access Points 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 CSEC 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 5 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 AP-214 Figure 1 - Aruba AP-214 This section introduces the Aruba AP-214 Wireless Access Point (AP) with FIPS 140-2 Level 2 validation. It describes the purpose of the AP, its physical attributes, and its interfaces. These compact and cost-effective dual-radio APs deliver wireless data rates of up to 1.3 Gbps to 5-GHz devices with 802.11ac technology. They also support 3×3 MIMO with three spatial streams as well as 2.4- GHz 802.11n clients at data rates up to 450 Mbps. 2.4-GHz (450 Mbps max rate) and 5-GHz (1.3 Gbps max rate) radios, each with 3×3 MIMO and three combined, duplexed (dual-band) external RP-SMA antenna connectors. When managed by Aruba Mobility Controllers, AP-214 offers centralized configuration, data encryption, policy enforcement and network services, as well as distributed and centralized traffic forwarding. 2.1.1 Physical Description The Aruba AP-214 Access Point is a multi-chip standalone cryptographic module consisting of hardware and software, all contained in a hard, opaque plastic case. The module contains 802.11 a/b/g/n/ac transceivers and supports external antennas through three N-type female connectors for external antennas. The case physically encloses the complete set of hardware and software components and represents the cryptographic boundary of the module. The Access Point configuration validated during the cryptographic module testing included: HW: AP-214-F1 The exact firmware version: ArubaOS 6.4.3-FIPS 6 2.1.1.1 Dimensions/Weight The AP has the following physical dimensions: 18 cm (W) x 18c cm (D) x 4.5 cm (H) 0.61 kg (1.34 lbs) 2.1.1.2 Interfaces The module provides the following network interfaces: One 10/100/1000BASE-T Ethernet network interface (RJ-45) Auto-sensing link speed and MDI/MDX 802.3az Energy Efficient Ethernet (EEE) USB 2.0 host interface (Type A connector) Serial console interface (disabled in FIPS mode by TEL) 802.11a/b/g/n/ac Antenna interfaces (External) Visual indicators (LEDs): o Power/system status o Ethernet link status (ENET) o Radio status (two; RAD0, RAD1) Reset button The module provides the following power interfaces: Power-over-Ethernet (POE) 12V DC power interface 7 2.2 AP-215 Figure 2 - Aruba AP-215 This section introduces the Aruba AP-215 Wireless Access Point (AP) with FIPS 140-2 Level 2 validation. It describes the purpose of the AP, its physical attributes, and its interfaces. These compact and cost-effective dual-radio APs deliver wireless data rates of up to 1.3 Gbps to 5-GHz devices with 802.11ac technology. They also support 3×3 MIMO with three spatial streams as well as 2.4- GHz 802.11n clients at data rates up to 450 Mbps. AP-215: Six integrated downtilt omni-directional antennas for 3×3 MIMO with maximum antenna gain of 4.0 dBi in 2.4 GHz and 4.5 dBi in 5 GHz. Built-in antennas are optimized for horizontal ceiling mounted orientation of the AP. Downtilt angle for maximum gain is roughly 30 degrees. When managed by Aruba Mobility Controllers, AP-215 offers centralized configuration, data encryption, policy enforcement and network services, as well as distributed and centralized traffic forwarding. 2.2.1 Physical Description The Aruba AP-215 Access Point is a multi-chip standalone cryptographic module consisting of hardware and software, all contained in a hard, opaque plastic case. The module contains 802.11 a/b/g/n/ac transceivers and six internal antennas. The case physically encloses the complete set of hardware and software components and represents the cryptographic boundary of the module. The Access Point configuration validated during the cryptographic module testing included: HW: AP-215-F1 The exact firmware version: ArubaOS 6.4.3-FIPS 2.2.1.1 Dimensions/Weight The AP has the following physical dimensions: 18 cm (W) x 18 cm (D) x 4.5 cm (H) 8 0.61 kg (1.34 lbs) 2.2.1.2 Interfaces The module provides the following network interfaces: One 10/100/1000BASE-T Ethernet network interface (RJ-45) Auto-sensing link speed and MDI/MDX 802.3az Energy Efficient Ethernet (EEE) USB 2.0 host interface (Type A connector) Serial console interface (disabled in FIPS mode by TEL) 802.11a/b/g/n/ac Antenna interfaces (Internal)connections Visual indicators (LEDs): o Power/system status o Ethernet link status (ENET) o Radio status (two; RAD0, RAD1) Reset button The module provides the following power interfaces: Power-over-Ethernet (POE) 12 DC power interface 2.3 AP-274 Figure 3 - Aruba AP-274 This section introduces the Aruba AP-274 Wireless Access Point (AP) with FIPS 140-2 Level 2 validation. It describes the purpose of the AP, its physical attributes, and its interfaces. The innovative and aesthetically-designed AP-274 outdoor wireless access point delivers gigabit Wi-Fi performance to 802.11ac mobile devices under any weather conditions. Purpose-built to survive in the harshest outdoor environments, AP-274 AP withstands exposure to extreme high and low temperatures, persistent moisture and precipitation, and are fully sealed to keep out airborne contaminants. All electrical interfaces include industrial-strength surge protection. With a maximum data rate of 1.3 Gbps in the 5-GHz band and 600 Mbps in the 2.4-GHz band, AP-274 outdoor AP supports concurrent dual-radio operation at speeds that greatly exceed Fast Ethernet. When managed by Aruba Mobility Controllers, the AP-274 offers centralized configuration, data encryption, policy enforcement and network services, as well as distributed and centralized traffic forwarding. 9 2.3.1 Physical Description The Aruba AP-274 Access Point is a multi-chip standalone cryptographic module consisting of hardware and software, all contained in a metal case. The module contains 802.11 a/b/g/n/ac transceivers and supports external antennas through six N-type female connectors for external antennas. The metal case physically encloses the complete set of hardware and software components and represents the cryptographic boundary of the module. The Access Point configuration validated during the cryptographic module testing included: HW: AP-274-F1 The exact firmware version: ArubaOS 6.4.3-FIPS 2.3.1.1 Dimensions/Weight The AP has the following physical dimensions: 23 cm (W) x 24 cm (D) x 19 cm (H) 2.7 kg (6 lbs) 2.3.1.2 Interfaces The module provides the following network interfaces: 2 x 10/100/1000 Base-T Ethernet (RJ45) Ports 802.11a/b/g/n/ac Antenna (External) 1 x micro-USB console interface (disabled in FIPS mode by TEL) The module provides the following power interfaces: Power-over-Ethernet (POE) 110/240V AC power connector 2.4 AP-275 Figure 4 - Aruba AP-275 This section introduces the Aruba AP-275 Wireless Access Point (AP) with FIPS 140-2 Level 2 validation. It describes the purpose of the AP, its physical attributes, and its interfaces. The innovative and aesthetically-designed AP-275 outdoor wireless access point delivers gigabit Wi-Fi performance to 802.11ac mobile devices under any weather conditions. Purpose-built to survive in the harshest outdoor environments, AP-275 AP withstands exposure to extreme high and low temperatures, 10 persistent moisture and precipitation, and are fully sealed to keep out airborne contaminants. All electrical interfaces include industrial-strength surge protection. With a maximum data rate of 1.3 Gbps in the 5-GHz band and 600 Mbps in the 2.4-GHz band, AP-275 outdoor AP supports concurrent dual-radio operation at speeds that greatly exceed Fast Ethernet. When managed by Aruba Mobility Controllers, the AP-275 offers centralized configuration, data encryption, policy enforcement and network services, as well as distributed and centralized traffic forwarding. 2.4.1 Physical Description The Aruba AP-275 Access Point is a multi-chip standalone cryptographic module consisting of hardware and software, all contained in a metal and plastic case. The module contains 802.11 a/b/g/n/ac transceivers and internal antennas The metal case physically encloses the complete set of hardware and software components and represents the cryptographic boundary of the module. The Access Point configuration validated during the cryptographic module testing included: HW: AP-275-F1 The exact firmware version: ArubaOS 6.4.3-FIPS 2.4.1.1 Dimensions/Weight The AP has the following physical dimensions: 23 cm (W) x 24 cm (D) x 27 cm (H) 2.4 kg (5.3 lbs) 2.4.1.2 Interfaces The module provides the following network interfaces: 2 x 10/100/1000 Base-T Ethernet (RJ45) Ports 802.11a/b/g/n/ac Antenna Interfaces (Internal) 1 x micro-USB console interface (disabled in FIPS mode by TEL) The module provides the following power interfaces: Power-over-Ethernet (POE) 110/240V AC power connector 2.5 AP-277 11 Figure 5 - Aruba AP-277 This section introduces the Aruba AP-277 Wireless Access Point (AP) with FIPS 140-2 Level 2 validation. It describes the purpose of the AP, its physical attributes, and its interfaces. The innovative and aesthetically-designed AP-277outdoor wireless access points delivers gigabit Wi-Fi performance to 802.11ac mobile devices under any weather conditions. Purpose-built to survive in the harshest outdoor environments, AP-277 AP withstands exposure to extreme high and low temperatures, persistent moisture and precipitation, and are fully sealed to keep out airborne contaminants. All electrical interfaces include industrial-strength surge protection. With a maximum data rate of 1.3 Gbps in the 5-GHz band and 600 Mbps in the 2.4-GHz band, AP-277outdoor AP supports concurrent dual-radio operation at speeds that greatly exceed Fast Ethernet. When managed by Aruba Mobility Controllers, AP-277 offers centralized configuration, data encryption, policy enforcement and network services, as well as distributed and centralized traffic forwarding. 2.5.1 Physical Description The Aruba AP-277 Access Point is a multi-chip standalone cryptographic module consisting of hardware and software, all contained in a metal and plastic case. The module contains 802.11 a/b/g/n/ac transceivers and connectors for external antennas The metal case physically encloses the complete set of hardware and software components and represents the cryptographic boundary of the module. The Access Point configuration validated during the cryptographic module testing included: HW: AP-277-F1 The exact firmware version: ArubaOS 6.4.3-FIPS 2.5.1.1 Dimensions/Weight The AP has the following physical dimensions: 23 cm (W) x 24 cm (D) x 27 cm (H) 2.0 kg (4.4 lbs) 12 2.5.1.2 Interfaces The module provides the following network interfaces: 2 x 10/100/1000 Base-T Ethernet (RJ45) Ports 802.11a/b/g/n/ac Antenna Interfaces (Internal) 1 x micro-USB console interface (disabled in FIPS mode by TEL) The module provides the following power interfaces: Power-over-Ethernet (POE) 110/240V AC power connector 13 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 1 - 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 metal 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 4011570-01. The Crypto Officer is responsible for securing and having control at all times of any unused tamper evident labels. If evidence of tampering is found with the TELs, the module must immediately be powered down and the administrator must be made aware of a physical security breach. 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. 14 Apply the wholly intact TEL firmly and completely to the target surfaces. Ensure that TEL placement is not defeated by simultaneous removal of multiple modules. 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. To obtain additional or replacement TELS, please order Aruba Networks part number: 4011570- 01. 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 TELs Placement This section displays all the TELs locations on each of module. 3.2.2.1 TELs Placement on the AP-214 The AP-214 requires 3 TELs. One on each edge (labels 1 and 2) and one covering the console port (label 3). See figures 6, and 7 for placement. Figure 6 - Top View of AP-214 with TELs 15 Figure 7 ­ Bottom View of AP-214 with TELs 3.2.2.2 TEL Placement on the AP-215 The AP-215 requires 3 TELS. One on each edge (labels 1 and 2) and one covering the console port (label 3). See figures 8 and 9 for placement. Figure 8 ­ Top View of AP-215 with TELs 16 Figure 9 ­ Bottom View of AP-215 with TELs 3.2.2.3 TEL Placement on the AP-274 The AP-274 requires a minimum of 6 TELS. Two sealing the top plate (labels 1 and 2), see Figure 10. One covering the console port (label 3) and one securing the body to the bottom (label 4), see Figure 11. Finally apply one label to each side sealing it to the bottom (labels 5 & 6), see figures 12 and 13 for placement. Figure 10 ­ Top View of AP­274 with TELs 17 Figure 11 ­ Rear View of AP-274 with TELs Figure 12 ­ Right Side View of AP-274 with TELs Figure 13 ­ Left Side View of AP-274 with TELs 18 3.2.2.4 TEL Placement on the AP-275 The AP-275 requires a minimum of 6 TELS. Two sealing the top plate (labels 1 and 2), see Figure 14. One covering the console port (label 3) and one securing the body to the bottom (label 4), see Figure 15. Finally apply one label to each side sealing it to the bottom (labels 5 & 6), see figures 16 and 17 for placement. Figure 14 ­ Top View of AP­275 with TELs Figure 15 ­ Rear View of AP-275 with TELs 19 Figure 16 ­ Right Side View of AP-275 with TELs Figure 17 ­ Left Side View of AP-275 with TELs 3.2.2.5 TEL Placement on the AP-277 The AP-277 requires a minimum of 3 TELS. One covering the console port (label 1) see Figure 17. Apply one label to each side sealing it to the bottom (labels 2 & 3), see figures 18 and 19 for placement. 20 Figure 18 ­ Top View of AP­277 with TELs Figure 19 ­ Right Side View of AP-277 with TELs Figure 20 ­ Left Side View of AP-277 with TELs 3.2.3 Inspection/Testing of Physical Security Mechanisms Table 2 - 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. 21 3.3 Operational Environment The FIPS 1402 Operational Environment requirements are not applicable because the module is designated as a non-modifiable operational environment. The module only allows the loading of trusted and verified firmware that is signed by Aruba. 3.4 Logical Interfaces The physical interfaces are divided into logical interfaces defined by FIPS 140-2 as described in the following table. Table 3 - 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 Interface (AP-214/215) Data Output Interface 10/100/1000 Ethernet Ports 802.11a/b/g/n/ac Antenna Interfaces USB 2.0 Interface (AP-214/215) Control Input Interface 10/100/1000 Ethernet Ports 802.11a/b/g/n/ac Antenna Interfaces Reset button (AP-214/215) Status Output Interface 10/100/1000 Ethernet Ports 802.11a/b/g/n/ac Antenna Interfaces USB 2.0 Interface (AP-214/215) Power Interface Power Input Power-over-Ethernet (POE) 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 (power supply or POE). 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. o LEDs indicate the physical state of the module, such as power-up (or rebooting), utilization level, and activation state. The log file records the results of self-tests, configuration errors, and monitoring data. The module may be powered by an external power supply. Operating power may also be provided via Power Over Ethernet (POE) device, when connected, the power is provided through the connected Ethernet cable. Console port is disabled when operating in FIPS mode by TEL. 22 The module distinguishes between different forms of data, control, and status traffic over the network ports by analyzing the packet headers and contents. 23 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 in either Remote AP FIPS mode or in Control Plane Security (CPSec) Protected AP FIPS mode. There are two FIPS approved modes of operations, which are Remote AP FIPS mode and Control Plane Security (CPSec) Protected AP FIPS mode. Please refer to section 8 in this documentation for more information. Remote AP FIPS mode: o Crypto Officer role: the Crypto Officer is the Aruba Mobility Controller that has the ability to configure, manage, and monitor the module, including the configuration, loading, and zeroization of CSPs. o User role: in the configuration, the User operator shares the same services and authentication techniques as the Mobility Controller in the Crypto Officer role. o Wireless Client role: in Remote AP FIPS mode configuration, a wireless client can create a connection to the module using 802.11i and access wireless network access/bridging services. When Remote AP cannot communicate with the controller, the wireless client role authenticates to the module via 802.11i Pre-shared secret only. CPSec Protected AP FIPS mode: o Crypto Officer role: the Crypto Officer is the Aruba Mobility Controller that has the ability to configure, manage, and monitor the module, including the configuration, loading, and zeroization of CSPs. o User role: in the configuration, the User operator shares the same services and authentication techniques as the Mobility Controller in the Crypto Officer o Wireless Client role: in CPSec Protected AP FIPS mode configuration, a wireless client can create a connection to the module using 802.11i Pre-shared secret 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's authentication is accomplished via either Pre-shared secret (IKEv1), RSA digital certificate (IKEv1/IKEv2) or ECDSA digital certificate (IKEv2). 4.1.2 User Authentication When the module is configured as a Remote AP FIPS mode and CPSec protected AP FIPS mode, the User role is authenticated via the same Pre-shared secret (IKEv1), RSA digital certificate (IKEv1/IKEv2) or ECDSA digital certificate (IKEv2) that is used by the Crypto Officer. 24 4.1.3 Wireless Client Authentication The wireless client role defined in each of FIPS approved modes authenticates to the module via 802.11i. Please notice that WEP and TKIP configurations are not permitted in FIPS mode. When Remote AP cannot communicate with the controller, the wireless client role authenticates to the module via 802.11i Pre-shared secret only. 4.1.4 Strength of Authentication Mechanisms The following table describes the relative strength of each supported authentication mechanism. Table 4 - Strength of Authentication Mechanisms Authentication Mechanism Strength Mechanism IKEv1 Pre-shared A 64 ASCII (128 HEX) characters pre-shared secret is randomly chosen by secret based the administrator. It may consist of upper and lower case alphabetic authentication characters, numeric characters and 32 special characters. (CO/User role) The probability of randomly guessing the correct sequence is one (1) in 94^64. 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. Therefore, the associated probability of a successful random attempt, with no restrictions on character usage, is approximately 1 in 94^64, which is less than 1 in 1,000,000 required by FIPS 140-2. 802.11i Pre-shared The secret is required to be a minimum of eight characters and a maximum of secret based 32 with a minimum of one letter and one number. If eight characters are authentication chosen with a minimum of one letter and one number, the probability of (Wireless Client randomly guessing the correct sequence is one (1) in 358,732,286,149,120 role) (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 94 x 94 x 94 x 94 x 94 x 94 x 52 x 10 = 358,732,286,149,120). Therefore, the associated probability of a successful random attempt is approximately 1 in 358,732,286,149,120, which is less than 1 in 1,000,000 required by FIPS 140-2. RSA Certificate The module supports 2048-bit RSA keys authentication during IKEv1/IKEv2. based authentication RSA 2048 bit keys correspond to 112 bits of security. Assuming the low end (CO/User role) of that range, the associated 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 Certificate ECDSA signing and verification is used to authenticate to the module during based authentication IKEv2. Either P-256 or P-384 curves are supported. ECDSA P-256 provides (CO/User role) 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. 25 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 5 - Crypto Officer Services Services Description CSPs Accessed (see section 6 below for a complete description to each CSP and the associated cryptographic algorithms) FIPS mode enable/disable The CO selects/de-selects FIPS None. mode as a configuration option. Key Management The CO can configure/modify the 15 and 27(write) IKEv1shared secret (The RSA private key is protected by non- volatile memory and cannot be modified) and the 802.11i Pre- shared secret (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 None reboot Self-test triggered by CO/User The CO can trigger a None. reboot programmatic reset leading to self-test and initialization Update module firmware The CO can trigger a module 14 (write) 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 15 and 27(write) management session between IPSec for securing the module and CO management channel. System Status CO may view system status See creation/use of secure information through the secured management session above. management channel 26 Services Description CSPs Accessed (see section 6 below for a complete description to each CSP and the associated cryptographic algorithms) Zeroization The cryptographic keys stored in All CSPs will be destroyed. SDRAM memory can be zeroized by rebooting the module. The cryptographic keys (IKEv1 Pre- shared secret and 802.11i Pre- shared secret) stored in the flash can be zeroized by using command `ap wipe out flash' or by overwriting with a new secret. The other keys/CSPs (KEK, RSA/ECDSA public key/private key and certificate) stored in Flash memory can be zeroized by using command `ap wipe out flash'. 4.2.2 User Services The User services defined in Remote AP FIPS mode and CPSec protected AP FIPS mode shares the same services with the Crypto Officer role, please refer to Section 4.2.1, "Crypto Officer Services". 4.2.3 Wireless Client Services The following module services are provided for the Wireless Client role in Remote AP FIPS mode and CPSec protected AP FIPS mode. Table 6- Wireless Client Services Service Description CSPs Accessed (see section 6 below for a complete description to each CSP and the associated cryptographic algorithms) Generation and use of 802.11i In all modes, the links between None cryptographic keys the module and wireless client are secured with 802.11i. Use of 802.11i Pre-shared secret When the module is in advanced None for establishment of IEEE Remote AP configuration, the 802.11i 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. 27 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. 4.2.5 Service Available in Non-FIPS Mode IPSec/IKE with Diffie-Hellman 768/1024-bit modulus and MD5. Please note that all CSPs will be zeroized automatically when switching from FIPS mode to non-FIPS mode, or from non-FIPS mode to FIPS mode. 28 5 Cryptographic Algorithms The firmware (ArubaOS 6.4.3-FIPS) in each module contains the following cryptographic algorithm implementations/crypto libraries to implement the different FIPS approved cryptographic algorithms that will be used for the corresponding security services supported by the module in FIPS mode: ArubaOS OpenSSL Module algorithm implementation ArubaOS Crypto Module algorithm implementation ArubaOS UBootloader algorithm implementation Aruba AP Hardware algorithm implementation Below are the detailed lists for the FIPS approved algorithms and the associated certificate implemented by each crypto library ArubaOS OpenSSL Module algorithm implementation supports the following functions: o AES (Cert. #2900) 1 o CVL (Cert. #326) 2 o DRBG (Cert. #528) o ECDSA (Cert. #524) o HMAC (Cert. #1835) o KBKDF (Cert. #32) o RSA (Cert. #1528) o SHS (Cert. #2440) o Triple-DES (Cert. #1726) ArubaOS Crypto Module algorithm implementation: o AES (Cert. #2884) 3 o CVL (Cert #314) 4 o ECDSA (Cert. #519) o HMAC (Cert. #1818) o RSA (Cert. #1518) o RNG (Cert. #1286) o SHS (Cert. #2425) o Triple-DES (Cert. #1720) ArubaOS UBOOT Bootloader algorithm implementation: o RSA (Cert. #1517) 5 1 Note that only AES-CBC and AES-CTR are active on the module 2 Only the IKE v1 KDF is active on the module 3 Note that only AES-CBC, AES-CTR and AES-GCM are active on the module 4 Only the IKEv2 KDF is active on the module 5 RSA cert. #1517 was only used for RSA Signature verification on the module 29 o SHS (Cert. #2424) Aruba AP Hardware algorithm implementation: o AES (Certs. #1648 and #1649) 6 o HMAC (Certs. #538 and #967) o SHS (Certs. #934 and #1446) o Triple-DES (Certs. #758 and #1075) Non-FIPS Approved but Allowed Cryptographic Algorithms Diffie-Hellman (key agreement; key establishment methodology provides 112 bits of encryption strength) EC Diffie-Hellman (key agreement; key establishment methodology provides 128 or 192 bits of encryption strength) NDRNG Non-FIPS Approved Cryptographic Algorithms Diffie-Hellman (less than 112 bits of encryption strength) MD5 NOTE: IKEv1 and IKEv2 protocols have not been reviewed or tested by the CAVP and CMVP. 6 Note that only AES-CBC, AES-CTR, AES-CCM are active on the module 30 6 Critical Security Parameters The following Critical Security Parameters (CSPs) are used by the module: Table 7 - Critical Security Parameters # Name Algorithm/Key Size Generation/Use Storage Zeroization General Keys/CSPs 1 Key Encryption Key Triple-DES Hardcoded during Stored in Flash Zeroized by using (KEK) (192 bits) manufacturing. Used only memory (plaintext) command `ap wipe to protect keys stored in out flash'. the flash, not for key transport. 2 DRBG entropy input SP 800-90a Entropy inputs to DRBG Stored in SDRAM Zeroized by CTR_DRBG function used to construct memory (plaintext) rebooting the (512 bits) the DRBG seed. module 3 DRBG seed SP 800-90a Input to the DRBG that Stored in SDRAM Zeroized by CTR_DRBG determines the internal memory (plaintext) rebooting the (384-bits) state of the DRBG. module Generated using DRBG derivation function that includes the entropy input from the entropy source. 4 DRBG Key SP 800-90a This is the DRBG key Stored in SDRAM Zeroized by CTR_DRBG used for SP 800-90a memory (plaintext) rebooting the (256 bits) CTR_DRBG. module 5 DRBG V SP 800-90a Internal V value used as Stored in SDRAM Zeroized by CTR_DRBG V part of SP 800-90a memory (plaintext) rebooting the (128 bits) CTR_DRBG. module 6 RNG seed FIPS 186-2 General Used to seed FIPS Stored in SDRAM Zeroized by Purpose RNG seed approved 186-2 general memory (plaintext) rebooting the (512 bits) purpose RNG. Generated module from non-approved RNG 31 7 RNG seed key FIPS 186-2 General This is the RNG seed key Stored in SDRAM Zeroized by Purpose RNG seed used for FIPS approved memory (plaintext) rebooting the key 186-2 general purpose module (512 bits) RNG. 8 Diffie-Hellman Diffie-Hellman Generated internally by Stored in SDRAM Zeroized by private key Group 14 (224 bits) calling FIPS approved memory (plaintext) rebooting the RNG (Cert. #1286) to module derive Diffie-Hellman shared secret used in IKEv2 or calling DRBG (Cert. #528) to derive Diffie-Hellman shared secret used in IKEv1. 9 Diffie-Hellman public Diffie-Hellman Derived internally in Stored in SDRAM Zeroized by key Group 14 (2048 compliance with Diffie- memory (plaintext) rebooting the bits) Hellman key agreement module Note: Key size of scheme. Used for DH Group 1 (768 establishing DH shared secret. bits) and Group 2 (1024 bits) is not allowed in FIPS mode. 10 Diffie-Hellman shared Diffie-Hellman Established during Diffie- Stored in SDRAM Zeroized by secret Group 14 (2048 Hellman Exchange. Used memory (plaintext) rebooting the bits) for deriving IPSec/IKE module cryptographic keys. 11 EC Diffie-Hellman EC Diffie-Hellman Generated internally by Stored in SDRAM Zeroized by private key (Curves: P-256 or calling FIPS approved memory (plaintext) rebooting the P-384). RNG (Cert. #1286) during module EC Diffie-Hellman Exchange. Used for establishing ECDH shared secret. 12 EC Diffie-Hellman EC Diffie-Hellman Derived internally in Stored in SDRAM Zeroized by public key (Curves: P-256 or compliance with EC memory (plaintext) rebooting the P-384). Diffie-Hellman key module agreement scheme. Used for establishing ECDH shared secret. 32 13 EC Diffie-Hellman EC Diffie-Hellman Established during EC Stored in SDRAM Zeroized by shared secret (Curves: P-256 or Diffie-Hellman Exchange. memory (plaintext) rebooting the P-384) Used for deriving module IPSec/IKE cryptographic keys. 14 Factory CA Public RSA This is RSA public key. Stored in Flash Zeroized by using Key (2048 bits) Loaded into the module encrypted with command `ap wipe during manufacturing. KEK out flash' Used for Firmware verification. IPSec/IKE 15 IKEv1 Pre-shared Shared secret Entered by CO role. Stored in Flash Zeroized by using secret (64 ASCII or 128 HEX Used for IKEv1 peers memory encrypted command `ap wipe characters) authentication. with KEK out flash' or by overwriting with a new secret 16 skeyid Shared Secret A shared secret known Stored in SDRAM Zeroized by (160/256/384 bits) only to IKEv1 peers. It memory (plaintext) rebooting the was established via key module. derivation function defined in SP800-135 KDF (IKEv1). Used for deriving other keys in IKEv1 protocol implementation. 17 skeyid_d Shared Secret A shared secret known Stored in SDRAM Zeroized by (160/256/384 bits) only to IKEv1 peers. It memory (plaintext) rebooting the was derived via key module derivation function defined in SP800-135 KDF (IKEv1). Used for deriving IKEv1 session authentication key. 18 SKEYSEED Shared Secret A shared secret known Stored in SDRAM Zeroized by (160/256/384 bits) only to IKEv2 peers. It memory (plaintext) rebooting the was derived via key module derivation function defined in SP800-135 KDF (IKEv2) and it will be used for deriving other keys in IKEv2 protocol. 33 19 IKE session HMAC-SHA- The IKE session (IKE Stored in SDRAM Zeroized by authentication key 1/256/384 Phase I) authentication memory (plaintext) rebooting the (160/256/384 bits) key. This key is derived module via key derivation function defined in SP800-135 KDF (IKEv1/IKEv2). Used for IKEv1/IKEv2 payload integrity verification. 20 IKE session Triple-DES The IKE session (IKE Stored in SDRAM Zeroized by encryption key (192 bits) /AES Phase I) encrypt key. memory (plaintext) rebooting the (128/192/256 bits) This key is derived via module key derivation function defined in SP800-135 KDF (IKEv1/IKEv2). Used for IKE payload protection. 21 IPSec session Triple-DES (192 bits) / The IPsec (IKE phase II) Stored in SDRAM Zeroized by encryption keys AES and AES-GCM encryption key. This key memory (plaintext) rebooting the (128/192/256 bits) is derived via a key module derivation function defined in SP800-135 KDF (IKEv1/IKEv2). Used for IPSec traffics protection. 22 IPSec session HMAC-SHA-1 (160 The IPsec (IKE Phase Stored in SDRAM Zeroized by authentication keys bits) II) authentication key. memory (plaintext) rebooting the This key is derived via module using the KDF defined in SP800-135 KDF (IKEv1/IKEv2). Used for IPSec traffics integrity verification. 23 IKE RSA Private RSA private key This is the RSA private Stored in Flash Zeroized by using Key (2048 bits) key. This key is memory encrypted command `ap wipe generated by the module with KEK out flash' in compliance with FIPS 186-4 RSA key pair generation method. In IKEv1, DRBG (Cert. #528) is called for key generation; in IKEv2, RNG (Cert. #1286) is called for key generation. It is used for RSA signature signing in either IKEv1 or 34 IKEv2. 24 IKE RSA public RSA public key This is the RSA public Stored in Flash Zeroized by using key (2048 bits) key. This key is derived memory encrypted command `ap wipe in compliance with FIPS with KEK out flash' 186-4 RSA key pair generation method in the module. It is used for RSA signature verification in either IKEv1 or IKEv2. . 25 IKE ECDSA ECDSA suite B This is the ECDSA Stored in Flash Zeroized by using Private Key (Curves: P-256 or P- private key. This key is memory encrypted command `ap wipe 384) generated by the module with KEK out flash'. in compliance with FIPS 186-4 ECDSA key pair generation method. In IKEv2, RNG (Cert. #1286) is called for key generation. It is used for ECDSA signature signing in IKEv2. 26 IKE ECDSA Public ECDSA suite B This is the ECDSA Stored in Flash Zeroized by using Key (Curves: P-256 or P- public key. This key is memory encrypted command `ap wipe 384) derived in compliance with KEK out flash' with FIPS 186-4 ECDSA key pair generation method in the module. It is used for ECDSA signature verification in IKEv2. 802.11i 27 802.11i Pre-shared Shared secret Entered by CO role. Stored in Flash Zeroized by using secret (8-63 characters) Used for 802.11i memory encrypted command `ap wipe client/server with KEK out flash' or by authentication. overwriting with a new secret. 35 28 802.11i Pair-Wise Shared secret The PMK is Stored in SDRAM Zeroized by Master key (PMK) (256 bits) transported to the (plaintext) rebooting the module, protected by module IPSec secure tunnel. Used to derive the Pairwise Transient Key (PTK) for 802.11i communications. 29 802.11i Pairwise Shared secret This key is used to Stored in SDRAM Zeroized by Transient Key (512 bits) derive 802.11i session memory (plaintext) rebooting the (PTK) key by using the KDF module defined in SP800-108. 30 802.11i session key AES-CCM Derived during 802.11i Stored in SDRAM Zeroized by (128 bits) 4-way handshake by memory (plaintext) rebooting the using the KDF defined module in SP800-108. 31 802.11i Group Shared secret Generated by calling Stored in SDRAM Zeroized by Master Key (GMK) (256 bits) DRBG (Cert. #528). memory (plaintext) rebooting the Used to derive 802.11i module Group Transient Key GTK. 32 802.11i Group AES-CCM Derived from 802.11 Stored in SDRAM Used to protect Transient Key (256 bits) GMK by using the memory (plaintext) multicast message (GTK) KDF defined in SP800- 108. The GTK is the 802.11i session key used for broadcast communications protection. Please note that: AES GCM IV generation is performed in compliance with the Implementation Guidance A.5 scenario 2. FIPS approved RNG (Cert. #1286) is used for IV generation and 96 bits of IV is supported. 36 7 Self Tests The module performs Power On Self-Tests regardless the modes (non-FIPS mode, Remote AP FIPS mode or Control Plane Security (CPSec) Protected AP FIPS mode). In addition, the module also performs Conditional tests after being configured into either Remote AP FIPS mode or Control Plane Security (CPSec) Protected AP FIPS mode. 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 on self-tests: ArubaOS OpenSSL Module algorithm implementation power on self-tests: o AES (encrypt/decrypt) KATs o Triple-DES (encrypt/decrypt) KATs o DRBG KAT o RSA (sign/verify) KATs o ECDSA Pairwise Consistency Test o SHS (SHA1, SHA256, SHA384 and SHA512) KATs o HMAC (HMAC-SHA1, HMAC-SHA256, HMAC-SHA384 and HMAC-SHA512) KATs ArubaOS Crypto Module algorithm implementation power on self-tests: o AES (encrypt/decrypt) KATs o AES-GCM KAT 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 FIPS 186-2 RNG KAT o RSA (sign/verify) KATs o ECDSA Pairwise Consistency Test ArubaOS Uboot Bootloader Module algorithm implementation power on self-tests: o Firmware Integrity Test: RSA PKCS#1 v1.5 (2048 bits) signature verification with SHA- 1 Aruba AP Hardware algorithm implementation power on self-tests: o AES (encrypt/decrypt) KATs o AES-CCM (encrypt/decrypt) KATs o Triple-DES (encrypt/decrypt) KATs o HMAC-SHA1 KAT The following Conditional Tests are performed in the module: o ArubaOS OpenSSL Module algorithm implementation o CRNG Test to Approved RNG (DRBG) o ECDSA Pairwise Consistency Test o RSA Pairwise Consistency Test 37 o ArubaOS Crypto Module algorithm implementation o CRNG Test to Approved RNG (FIPS 186-2 RNG) o ECDSA Pairwise Consistency Test o RSA Pairwise Consistency Test o ArubaOS Uboot BootLoader Module algorithm implementation o Firmware Load Test - RSA PKCS#1 v1.5 (2048 bits) signature verification o CRNG test to non-approved RNG (NDRNG) These self-tests are run for the Freescale hardware cryptographic implementation as well as for the Aruba OpenSSL and ArubaOS cryptographic module implementations. 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 AES Atheros 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. 38 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 certified 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. · Control Plane Security (CPSec) Protected AP FIPS mode ­ When the module is configured as a Control Plane Security protected AP it is intended to be deployed in a local/private location (LAN, WAN, MPLS) relative to the Mobility Controller. The module provides cryptographic processing in the form of IPSec for all Control traffic to and from the Mobility Controller. 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. 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. 39 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 secret is selected to be the Remote AP Authentication Method, the IKE Pre-shared secret (64 ASCII or 128 HEX characters) is input to the module during provisioning. 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 Control Plane Security (CPSec) Protected 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. Configure the staging controller with CPSec under Configuration > Controller > Control Plane Security tab. AP will authenticate to the controller using certificate based authentication (IKEv2) to establish IPSec. The AP is configured with an RSA key pair at manufacturing. The AP's certificate is signed by Aruba Certification Authority (trusted by all Aruba controllers) and the AP's RSA private key is stored in non-volatile memory. Refer to the "Configuring Control Plane Security" section in the ArubaOS User Manual for details on the steps. 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 CPSec Mode 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. 40 a. For CPSec AP mode, the AP always uses certificate based authentication to establish IPSec connection with controller. AP uses the RSA key pair assigned to it at manufacturing to authenticate itself to controller during IPSec. Refer to "Configuring Control Plane Security" Section in Aruba OS User Manual for details on the steps to provision an AP with CPSec enabled on controller. 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.3 Verifying the FIPS mode For all the approved modes of operations in either Remote AP FIPS mode or Control Plane Security (CPSec) Protected AP FIPS mode, follow the steps below to verify the 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 41