Dell AP-134 Network Card User Manual
Contents
1. Doelect aceess fO TeSEEICIe d POMS E 14 3 2 4 Inspection Testing of Physical Security Mechanisme 15 9 3 MODES OP OPERATION EE 16 33L Confieurine Remote AP TIPS E 16 3 3 2 Configuring Control Plane Security CPSec protected AP FIPS mode 17 3 3 3 Configuring Remote Mesh Portal FIPS Mode 18 3 3 4 Configuring Remote Mesh Point FIPS Mode 19 3a Verify thatthe moduless Tn RIP EEN 20 Sof OPERATIONAL ENVIRONMENT eer 20 3 5 LOGICAL INTERFACES EE 21 4 ROLES AUTHENTICATION AND SERVICES eege 22 RE e E 22 Zh OPyDIO OCerdAut E 22 qp E sut lebat sedi dat tit unten teat iae Gode ooa ds mates Don Ea isis 23 4 1 3 Wireless Client Authentication cccccccccsccsceccuccuccscoscscuscscencescuscsccscescescescssescescescssessescescusenses 23 4 1 4 Strength of Authentication Mechanisms eeeeesessssssseeeeeeeee essen nnne esnn innen essen nnn nnns 23 A SERN t oct sap anasto ut ean ay es cass ap eto ae cats AO ds sat eanenea estan Senteeau A 25 qud C EYDIOAITICOPSSOEUICONS EE E EE 23 ga SEE C 26 E Wirel S enS EIV O ES er E M 27 424 Unduthenticat ed SCIVICOS ioiii earar tes un OUR eus RTE EEE E DUI UE A 5 CRYPTOGRAPHIC ALGORITHMS eegeeseeee enee aeara aaea aaa 29 6 CRITICAL SECURITY PA RAMETERS eeoscssseeiiccsossscsssossisossresosososssiecsessisoisees bost sssois kesson otsesesse 30 De SELCE TESTS EE 34 1 Introduction This document constitutes the non proprietary Cryptographic Module Security Policy for2. Wireless gt 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 18 10 11 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 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 Via the logging facility of the staging controller ensure that the module the AP is successful
3. encryption dec ryption keys are derived from the PTK Used for integrity validation 1n 4 Way handshake Used for confidentiality in 4 way handshake Used for 802 111 packet encryption and integrity verification this is the CCMP or AES CCM key 802 111 Group Master Key GMK 802 111 Group Transient Key GTK 802 111 Group AES CCM Data Encryption MIC Key RSA private Key CSP TYPE 256 bit secret used to derive GTK 256 bit shared secret used to derive group multicast encryption and integrity keys 128 bit AES CCM key derived from GTK 1024 2048 bit RSA private key GENERATION Generated from approved RNG Internally derived by AP which assumes authenticator role in handshake Derived from 802 11 group key handshake Generated on the AP remains in AP at all times 33 STORAGE And ZEROIZATI ON Stored in plaintext in volatile memory zeroized on reboot Stored in plaintext in volatile memory zeroized on reboot Stored in plaintext in volatile memory zeroized on reboot Stored in and protected by AP s non volatile memory zeroized by the ap wipe out flash command Used to derive Group Transient Key GTK Used to derive multicast cryptographic keys Used to protect multicast message confidentiality and integrity AES CCM Used for IKEv1 IKEv2 authentication when AP is authenticating using certificate base
4. a maximum idealized guessing rate of 60 000 000 000 4 672 12 842 466 guesses per minute This means the odds of guessing a correct key in one minute is less than 12 842 466 6 63x10 15 2 1 94 x 10 9 which 1s much less than 1 in 10 5 22 Authentication Mechanism Strength Mechanism Wireless Client For WPA2 PSK there are at least 9516 4 4 x 10431 possible WPA2 PSK combinations In order to test a guessed key the attacker must complete the Wireless Client 4 way handshake with the AP Prior to completing the 4 way handshake the role attacker must complete the 802 11 association process That process involves the following packet exchange Attacker sends Authentication request at least 34 bytes AP sends Authentication response at least 34 bytes Attacker sends Associate Request at least 36 bytes AP sends Associate Response at least 36 bytes Total bytes sent at least 140 Note that since we do not include the actual 4 way handshake this is less than half the bytes that would actually be sent so the numbers we derive will absolutely bound the answer The theoretical bandwidth limit for IEEE 802 1 1n is 300Mbit which is 37 500 000 bytes sec In the real world actual throughput is significantly less than this but we will use this idealized number to ensure that our estimate is very conservative This means that the maximum number of associations assume no delays no inter frame gaps that could be completed is
5. e 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 111 session The Crypto Officer role is the Mobility Controller that authenticates via IKEvI IKEv2 pre shared key or RSA certificate authentication method and Users are the n Mesh Points that authenticate via 802 111 preshared key e Mesh Point FIPS MODE an AP that establishes all wireless path to the Remote Mesh portal in FIPS mode over 802 11 and an IPSec tunnel via the Remote Mesh Portal to the controller This section explains how to place the module in FIPS mode in either Remote AP FIPS mode Control Plane Security AP FIPS Mode Remote Mesh Portal FIPS mode or Mesh Point FIPS Mode 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 provisi
6. for the module to operate in a FIPS approved mode of operation To protect the device from tampering TELs should be applied by the Crypto Officer as pictured below 1 3 2 2 AP 134 TEL Placement This section displays all the TEL locations of the Aruba AP 134 The AP 134 requires a minimum of 5 TELs to be applied as follows 3 2 2 1 To detect opening of the chassis cover 1 Spanning the bottom and top chassis covers and placed in the front left corner 2 Spanning the bottom and top chassis covers and placed in the back left corner 3 Spanning the chassis screw on the bottom left corner 4 Spanning the chassis screw on the bottom right corner 3 2 2 2 To detect access to restricted ports 5 Spanning the serial port Following is the TEL placement for the AP 134 Figure 1 AP 134 Front view Figure 2 AP 134 Back View Figure 3 AP 134 Left View 12 Figure 5 AP 134 Right View Figure 6 AP 134 Bottom View 3 2 3 AP 135 TEL Placement This section displays all the TEL locations of the Aruba AP 135 The AP 134 requires a minimum of 5 TELs to be applied as follows 3 2 3 1 To detect opening of the chassis cover 1 Spanning the bottom and top chassis covers and placed in the front left corner 13 2 Spanning the bottom and top chassis covers and placed in the back left corner 3 Spanning the chassis screw on the bottom left corner 4 Spanning the chassis screw on the bottom right corner 3 2 3 2 To detect
7. intrusion detection and prevention over the 2 4 2 5GHz and 5GHz RF spectrum The access points work in conjunction with Aruba Mobility Controllers to deliver high speed secure user centric network services in education enterprise finance government healthcare and retail applications 2 1 1 Physical Description The Aruba AP 134 series Access Point is a multi chip standalone cryptographic module consisting of hardware and software all contained in a hard plastic case The module contains 802 11 a b g n transceivers and supports external antennas through 3 x dual band RP SMA antenna interfaces for supporting external antennas The plastic case physically encloses the complete set of hardware and software components and represents the cryptographic boundary of the module The Access Point configuration tested during the cryptographic module testing included Aruba Part Number Dell Corresponding Part Number AP 134 F1 W API34 FI The exact firmware versions tested were e ArubaOS_6xx_6 1 2 3 FIPS e Dell PCW 6xx 6 1 2 3 FIPS 2 1 1 1 Dimensions Weight The AP has the following physical dimensions e 170mm H x 170 mm W x 45 mm e 760 g 1 68 Ib 2 1 1 2 Interfaces The module provides the following network interfaces e 2x 10 100 1000 Base T Ethernet RJ45 Auto sensing link speed and MDI MDX e Antenna o 3x RP SMA antenna interfaces supports up to 3x3 MIMO with spatial diversity e 1x RJ 45 console interface The module pr
8. less than 37 500 000 214 267 857 per second or 16 071 429 associations per minute This means that an attacker could certainly not try more than this many keys per second it would actually be MUCH less due to the added overhead of the 4 way handshake m each case and the probability of a successful attack in any 60 second interval MUST be less than 16 071 429 4 4 x 10431 or roughly 1 in 10425 which is much less than 1 in 1045 Mesh AP WPA2 Same as Wireless Client WPA2 PSK above PSK User role RSA Certificate The module supports RSA 1024 bit keys and 2048 bit RSA keys RSA 1024 based authentication bit keys correspond to 80 bits of security The probability of a successful CO role random attempt is 1 2480 which is less than 1 1 000 000 The probability of a success with multiple consecutive attempts in a one minute period is less than 1 100 000 24 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 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 IKEv1 IKEv2 shared IKEv1 IKEv2 shared secret The secret RSA private key is protected by non volatile memory and cannot WPA2 PSK be m
9. network access services e Mesh AP Mesh Point or Remote Mesh Portal configuration O Crypto Officer Role the Crypto Officer role is the Aruba Mobility Controller that has the ability to configure manage and monitor the module including the configuration loading and zeroization of CSPs User role the second or third or nth AP in a given mesh cluster Wireless Client role in Mesh AP configuration a wireless client can 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 IKEvI IKEv2 pre shared key or RSA certificate which occurs during the IKEvI IKEv2 key exchange 22 4 1 2 User Authentication Authentication for the User role depends on the module configuration When the module is configured as a Remote Mesh Portal FIPS mode and Remote Mesh Point FIPS mode the User role is authenticated via the WPA2 pre shared key 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 IKEvI IKEv2 pre shared key RSA certificate that is used by the Crypto Officer 4 1 3 Wireless Client Authentication The wireless client role
10. 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 2011 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 Dell the DELL logo andPowerConnect are trademarks of Dell Inc 1 INTRODUCTIQON BE 5 Li ARUBA DELE RELATIONSHIP 3 55 30 eeh EE eg 5 L2 JXXCRONYMS AND ABBREVIATIONS EEN 5 se PRODUCE OVER VIEW eegene ege 7 SN AP E 7 Zub A e Re 7 ALLU Pus A erent ege 7 PX NP MENNe Rc sade S a cin cid het haat Sade Sa an dca cid hha hacen sade ue same oh a T 2 155 IndicatoE EDS ever votis et e o D opa aevo ot ed Pd od e nota estas otov Head pA 8 E 9 EE PS TEE 9 23 1 L Dimensions WEIER oe ete o vetere dE 9 22 EXAMEN dele RO A anata sabres ee atereene hoaeuah ace 9 22 15 Tecor LED 62er eorr ede eden eere eno eta deed eed eaa da edo ege 10 3 MODULE OBJECTIVES beet 11 tM NE eU e LEVEES c E 11 J2 PHYSICAL SBC URERY EE II S TEMP EE Heger Eet 11 Soo EE Cactus totu teens ee denti LU LE e 12 32A Todetecr penins of the Chassis EEN 12 J222 Dosdetecbaeocess LO restricted DONS EE 12 020 9 APSS DERI E 15 3 2 3 1 To detect opening of the chassis cover cccccccccccccccceeceseesseseeeeeeeceeceeeeeeeeuaasassssseeeeeeeeeees 13 322 357
11. FIPS 140 2 Non Proprietary Security Policy for Aruba AP 134 AP 135 and Dell W AP134 W AP135 Wireless Access Points Version 1 2 February 2012 ATTESA net works Aruba Networks 1322 Crossman Ave Sunnyvale CA 94089 1113 I Copyright 2012 Aruba Networks Inc Aruba Networks trademarks include C AI WW AVE 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
12. 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 SNMP SPOE TEL TFTP WLAN Secure Hash Algorithm simple Network Management Protocol Serial amp Power Over Ethernet Tamper Evident Label Trivial File Transfer Protocol Wireless Local Area Network 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 134 This section introduces the Aruba AP 134 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 Aruba AP 134 is high performance 802 1 1n 3x3 3 MIMO dual radio concurrent 802 1 1a n b g n indoor wireless access points capable of delivering combined wireless data rates of up to 900Mbps These multi function access points provide wireless LAN access air monitoring and wireless
13. NG WPA2 PSK 802 111 Pairwise Master Key PMK 802 111 Pairwise Transient Key PTK 802 11i EAPOL MIC Key 802 111 EAPOL Encr Key 802 111 data AES CCM encryption MIC key CSP TYPE 16 64 character shared secret used to authenticate mesh connections and in remote AP advanced configuration 512 bit shared secret used to derive 802 111 session keys 512 bit shared secret from which Temporal Keys TKs are derived 128 bit shared secret used to protect 4 way key handshake 128 bit shared secret used to protect 4 way handshakes 128 bit AES CCM key GENERATION CO configured Derived from WPA2 PSK Derived during 802 111 4 way handshake Derived from PTK Derived from PTK Derived from PTK 32 STORAGE And ZEROIZATI ON Encrypted in flash using the KEK zeroized by updating through administrative interface or by the ap wipe out flash command In volatile memory only zeroized on reboot In volatile memory only zeroized on reboot In volatile memory only zeroized on reboot In volatile memory only zeroized on reboot Stored in plaintext in volatile memory zeroized on reboot USE Used to derive the PMK for 802 111 mesh connections between APs and in advanced Remote AP connections programmed into AP by the controller over the IPSec session Used to derive 802 111 Pairwise Transient Key PTK All session
14. OS Cryptographic Module RNG Seed key for FIPS compliant 186 2 General Purpose X change Notice SHA 1 RNG CSP TYPE 1024 bit Diffie Hellman private key Seed 16 Bytes Seed key 16 bytes AES 128 Key algorithm Seed 64 bytes Seed Key 64 bytes 128 bit Octet GENERATION Generated internally during IKEvI IKEv2 negotiation Generated internally during IKEvI IKEv2 negotiation Derived using NON FIPS approved HW RNG dev urandom Derived using NON FIPS approved HW RNG dev urandom Derived using NON FIPS approved HW RNG dev urandom Derived using NON FIPS approved HW RNG dev urandom 31 STORAGE And ZEROIZATI ON Stored in plaintext in volatile memory zeroized when session is closed or system is powered off Stored in plaintext in volatile memory zeroized when session is closed or system is powered off Stored in plaintext in volatile memory only zeroized on reboot Stored in plaintext in volatile memory only zeroized on reboot Stored in plaintext in volatile memory only zeroized on reboot Stored in plaintext in volatile memory only zeroized on reboot USE Used in establishing the session key for IPSec IKEvI IKEv2 payload integrity verification Seed ANSI X9 31 RNG Seed ANSI X9 31 RNG Seed 186 2 General Purpose X change Notice SHA 1 RNG Seed 186 2 General Purpose X change Notice SHA 1 R
15. SSL AP Module implements the following FIPS approved algorithms o AES Cert 1851 o HMAC Cert 1099 o RNG Cert 4970 o RSA Cert 934 o SHS Cert 1628 o Triple DES Cert 1199 e ArubaOS Module implements the following FIPS approved algorithms o AES Cert 1850 o HMAC Cert 1098 o RNG Cert 969 o RSA Cert 933 o SHS Cert 1627 o Triple DES Cert 1198 e ArubaOS Kernel implements the following FIPS approved algorithms o AES Cert 1847 o HMAC Cert 1097 o SHS Cert 1625 o Triple DES Cert 1197 e ArubaOS UBOOT Bootloader implements the following FIPS approved algorithms o RSA Cert 935 o SHS Cert 1629 e Aruba Atheros hardware CCM implements the following FIPS approved algorithms o AES Cert 1849 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 e MI In addition within the FIPS Approved mode of operation the module supports the following allowed key establishment schemes e Diffie Hellman key agreement key establishment methodology provides 80 bits of encryption strength 29 6 Critical Security Parameters The following Critical Security Parameters CSPs are used by the module Key Encryption Key KEK IKEv1 IKEv2 Pre shared secret IPSec session encryption keys IPSec session authentication keys CSP TYPE Triple DES 168 bit
16. access to restricted ports 5 Spanning the serial port Following is the TEL placement for the AP 135 Figure 7 AP 135 Front view Figure 8 AP 135 Back view Figure 9 AP 135 Left view Figure 10 AP 135 Right view 14 Figure 11 AP 135 Top view Figure 12 AP 135 Bottom View 3 2 4 Inspection Testing of Physical Security Mechanisms Physical Security Mechanism Recommended Test Frequency 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 15 3 3 Modes of Operation The module has the following FIPS approved modes of operations e Remote AP RAP 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 e 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
17. ails on the steps Enable FIPS mode on the controller This is accomplished by going to the Configuration Network gt Controller gt System Settings page this is the default page when you click the Configuration tab and clicking the FIPS Mode for Mobility Controller Enable checkbox 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 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 17 10 11 3 3 3 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 Once the module is connected to the controller by the Ethernet cable navigate to the Configuration gt Wireless gt AP Installation page where you should see an entry for the AP Select that AP click the Provision button which will open th
18. al 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 Enable FIPS mode on the controller This is accomplished by going to the Configuration gt Network gt Controller gt System Settings page this is the default page when you click the Configuration tab and clicking the FIPS Mode for Mobility Controller Enable checkbox Enable FIPS mode on the AP This accomplished by going to the Configuration gt Wireless gt AP Configuration gt AP Group page There you click the Edit button for the appropriate AP group and then select AP gt AP System Profile Then check the Fips Enable box check Apply and save the configuration 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 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 Once the module is connected to the controller by the Ethernet cable navigate to the Configuration gt
19. annel connections between mesh points using 802 11i 802 111 PMK 802 111 PTK 802 111 EAPOL MIC Key 802 111 EAPOL Encryption Key 802 111 AES CCM key 802 111 GMK 802 111 GTK 802 111 AES CCM key System Status CO may view system status See creation use of secure information through the secured management session above management channel 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 The following services are provided for the User role defined in Remote Mesh Portal FIPS mode and Remote Mesh Point FIPS mode Service Description CSPs Accessed see section 6 below for complete description of CSPs Generation and use of 802 111 When the module is in mesh 802 111 PMK cryptographic keys configuration the inter module d d E i 802 111 PTK mesh links are secured with 802 111 802 111 EAPOL MIC Key 802 111 EAPOL Encryption Key 26 Service Description CSPs Accessed see section 6 below for complete description of CSPs e 802 111 AES CCM key e 802 111 GMK e 802 111 GTK Use of WPA pre shared key for When the module is in mesh establishment of IEEE 802 111 configuration the inter module keys mesh links are secured with 802 111 This is authenticated with a shared secret e WPA2 PSK 4 2 3 Wireless Client Services The following modul
20. at use the networking functionality of the module e Control input consists of manual control inputs for power and reset through the power interfaces SV DC or PoE It also consists of all of the data that is entered into the access point while using the management interfaces e 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 e A power supply may be used to connect the electric power cable Operating power may also be provided via Power Over Ethernet POE device when connected The power is provided through the connected Ethernet cable e Console port is disabled when operating in each of FIPS modes The module distinguishes between different forms of data control and status traffic over the network ports by analyzing the packet headers and contents 21 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 mon
21. ckbox 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 gt AP System Profile Then check the Fips Enable box check Apply and save the configuration 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 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 19 10 11 3 3 5 represents the only exception That is nothing other than a PoE injector should be present between the module and the staging controller Once the module is connected to the controller by the Ethernet cable navigate to the Configuration gt Wireless gt 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
22. d authentication 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 e Aruba Hardware known Answer tests o AES KAT o HMAC SHAI KAT o Triple DES KAT e ArubaOS OpenSSL AP Module o AES KAT o HMAC HMAC SHA1 HMAC SHA256 and HMAC SHA384 KAT o RNG KAT o RSA KAT o SHA SHA1 SHA256 and SHA384 KAT o Triple DES KAT e ArubaOS Cryptographic Module o AES KAT o HMAC HMAC SHAI HMAC SHA256 HMAC SHA384 and HMAC512 KAT o FIPS 186 2 RNG KAT o RSA sign verify o SHA SHAI SHA256 SHA384 and SHA512 KAT o Triple DES KAT e ArubaOS Uboot Bootloader Module o Firmware Integrity Test RSA 2048 bit Signature Validation e Aruba Atheros hardware CCM o AES CCM KAT The following Conditional Self tests are performed in the module e Continuous Random Number Generator Test This test is run upon generation of random data by the module s random number generators to detect failure to a constant value The module stores the first random number for subsequent comparison and the module compares the value of the new random number with the random number generated in the previous round and enters an error state if the comparison is succ
23. defined in each of FIPS approved modes authenticates to the module via WPA2 Please notice that WEP and or Open System 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 Authentication Mechanism Strength Mechanism IKEvI IKEv2 For IKEvI IKEv2 there are a 95 8 26 63 x 10 15 possible pre shared keys shared secret CO In order to test the guessed key the attacker must complete an IKEv1 IKEv2 role aggressive mode exchange with the module IKEv1 IKEv2 aggressive mode consists of a 3 packet exchange but for simplicity let s ignore the final packet sent from the AP to the attacker An IKEvI IKEv2 aggressive mode initiator packet with a single transform using Diffie Hellman group 2 and having an eight character group name has an IKEvI IKEv2 packet size of 256 bytes Adding the eight byte UDP header and 20 byte IP header gives a total size of 284 bytes 2272 bits The response packet is very similar in size except that it also contains the HASH R payload an additional 16 bytes so the total size of the second packet is 300 bytes 2400 bits Assuming a link speed of I Gbits sec this is the maximum rate supported by the module this gives
24. e 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 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 Via the logging facility of the staging controller ensure that the module the AP is successfully provisioned with firmware and configuration Terminate the administrative session 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 Configuring Remote Mesh Portal FIPS Mode Apply TELs according to the directions in section 3 2 Log into the administrative console of the staging controller 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 Manu
25. e services are provided for the Wireless Client role in each of FIPS approved modes defined in section 3 3 Service Description CSPs Accessed see section 6 below for complete description of CSPs Generation and use of 802 111 In all modes the links between 802 111 PMK cryptographic keys the module and wireless client are secured with 802 111 802 111 PTK 802 111 EAPOL MIC Key 802 111 EAPOL Encryption Key 802 111 AES CCM key 802 111 GMK 802 111 GTK Use of WPA pre shared key for When the module is in advanced establishment of IEEE 802 111 Remote AP configuration the keys links between the module and the wireless client are secured with 802 111 This is authenticated with a shared secret only WPA2 PSK Wireless bridging services The module bridges traffic between the wireless client and the wired network 4 2 4 Unauthenticated Services The module provides the following unauthenticated services which are available regardless of role No CSPs are accessed by these services 27 System status SYSLOG and module LEDs 802 11 a b g n FTP TFTP NTP GRE tunneling of 802 11 wireless user frames when acting as a Local AP Reboot module by removing replacing power Self test and initialization at power on 28 5 Cryptographic Algorithms FIPS approved cryptographic algorithms have been implemented in hardware and firmware The firmware supports the following cryptographic implementations e ArubaOS Open
26. essful The test is performed for the approved as well as non approved RNGs e RSA pairwise Consistency Test e Firmware load test These self tests are run for the Atheros hardware cryptographic implementation as well as for the Aruba OpenSSL and ArubaOS cryptographic module implementations 34 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 AES Atheros hardware POST failure Starting HW SHA1 KAT Completed HW SHA1 AT Starting HW HMACSSHAL RAT 2 Complebceo HW HMAC SHAT KAT Starting HW DES KAT Completed HW DES KAT Starting HW AES KAT Restarting system 35
27. itor 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 e Remote AP 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 User role in the standard configuration the User operator shares the same services and authentication techniques as the Mobility Controller in the Crypto Officer role Wireless Client role in Remote AP configuration a wireless client can create a 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 e CPSec AP 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 User role in the standard configuration the User operator shares the same services and authentication techniques as the Mobility Controller in the Crypto Officer Wireless Client role in CPSec AP configuration a wireless client can create a connection to the module using WPA2 and access wireless
28. iversity e 1x RJ 45 console interface The module provides the following power interfaces e 48V DC 802 3af or 802 3at or PoE interoperable Power over Ethernet PoE with intelli source PSE sourcing intelligence e 5V DC for external AC supplied power adapter sold separately 2 2 1 3 Indicator LEDs There are 5 bicolor power ENET and WLAN LEDs which operate as follows Table 2 AP 135 Indicator LEDs AP power ready status on ins NN Areva ae OT p ff No power to AP Flashing Green Device booting not ready n men Ethernet Network Link Off Ethernet link unavailable Status Activity On Amber 10 100Mbs Ethernet link negotiated On Green 1000Mbps Ethernet link negotiated Flashing Ethernet link activity 2 4GHz radio disabled On Amber 2 4GHz radio enabled in non HT WLAN mode On Green 2 4GHz radio enabled in HT WLAN mode 5GHz radio disabled On Amber 5GHz radio enabled in non HT WLAN mode On Green 5GHz radio enabled in HT WLAN mode Flashing Green 2 4GHz Air monitor Flashing Green 5GHz Air monitor 10 3 Module Objectives This section describes the assurance levels for each of the areas described in the FIPS 140 2 Standard In addition it provides information on placing the module in a FIPS 140 2 approved configuration 3 1 Security Levels Cryptographic Module Specification Cryptographic Module Ports and Interfaces Roles Services and Authenticati
29. ller 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 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 Once the module is connected to the controller by the Ethernet cable navigate to the Configuration gt Wireless gt 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 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 a During the provisioning process as Remote AP 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 e
30. ly provisioned with firmware and configuration Terminate the administrative session 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 l 2 3 Log into the administrative console of the Aruba Mobility Controller Verify that the module is connected to the Mobility Controller Verify that the module has FIPS mode enabled by issuing command show ap ap name lt ap name config Terminate the administrative session Configuring Remote Mesh Point FIPS Mode Apply TELs according to the directions in section 3 2 Log into the administrative console of the staging controller Deploying the AP in Remote Mesh Point mode create the corresponding Mesh Profiles on the controller as described in detail in Section Mesh Points 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 Enable FIPS mode on the controller This is accomplished by going to the Configuration Network gt Controller gt System Settings page this is the default page when you click the Configuration tab and clicking the FIPS Mode for Mobility Controller Enable che
31. ntered 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 Via the logging facility of the staging controller ensure that the module the AP is successfully provisioned with firmware and configuration Terminate the administrative session 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 Configuring Control Plane Security CPSec protected AP FIPS mode Apply TELs according to the directions in section 3 2 Log into the administrative console of the staging controller Deploying the AP in CPSec AP mode configure the staging controller with CPSec under Configuration Controller Control Plane Security tab AP will authenticate to the controller using certificate based authentication to establish IPSec AP is configured with RSA key pair at manufacturing AP s certificate 1s 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 Configuring Control Plane Security Section in ArubaOS User Manual for det
32. odified and the WPA2 PSK KEK 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 KEK is accessed when reboot configuration is read during reboot The firmware verification key and firmware verification CA key are accessed to validate firmware prior to boot Self test triggered by CO User The CO can trigger a KEK is accessed when reboot programmatic reset leading to configuration is read during self test and initialization reboot The firmware verification key and firmware verification CA key are accessed to validate firmware prior to boot Update module firmware The CO can trigger a module The firmware verification key firmware update and firmware verification CA key are accessed to validate firmware prior to writing to flash Configure non security related CO can configure various module parameters operational parameters that do not relate to security 25 Service Description CSPs Accessed see section 6 below for complete description of CSPs Creation use of secure The module supports use of IKEv1 IKEv2 Preshared management session between IPSec for securing the Secret module and CO management channel DH Private Key DH Public Key IPSec session encryption keys IPSec session authentication keys RSA key pair Creation use of secure mesh The module requires secure WPA2 PSK ch
33. on Finite State Model Operational Environment Cryptographic Key Management EMI EMC 7 A MEN Design Assurance Mitigation of Other Attacks 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 tested 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 2 2 2 2 2 N A 2 2 2 2 A 3 2 1 Applying TELs 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 e Before applying a TEL make sure the target surfaces are clean and dry e Do not cut trim punch or otherwise alter the TEL e Apply the wholly intact TEL firmly and completely to the target surfaces e Ensure that TEL placement is not defeated by simultaneous removal of multiple modules e Allow 24 hours for the TEL adhesive seal to completely cure e Record the position and serial number of each applied TEL in a security log For physical security the AP requires Tamper Evident Labels TELs to allow detection of the opening of the device and to block the serial console port on the bottom of the device The tamper evident labels shall be installed
34. on 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 tested to FIPS 140 2 prior to initiating AP provisioning After setting up the Access Point by following the basic installation instructions in the module User Manual the Crypto Officer performs the following steps 3 3 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 gt Network gt Controller gt 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 gt Wireless gt AP Configuration gt AP Group page There you click the Edit button for the appropriate AP group and then select AP gt AP System Profile Then check the Fips Enable box check Apply and save the configuration 16 10 11 3 3 2 If the staging contro
35. ovides the following power interfaces e 48V DC 802 3af or 802 3at or PoE interoperable Power over Ethernet PoE with intelli source PSE sourcing intelligence e 12V DC for external AC supplied power adapter sold separately 2 1 1 3 Indicator LEDs There are 5 bicolor power ENET and WLAN LEDs which operate as follows Table 1 AP 134 Indicator LEDs AP power ready status No power to AP Flashing Green Device booting not ready n Ethernet Network Link Off Ethernet link unavailable Status Activity On Amber 10 100Mbs Ethernet link negotiated On Green 1000Mbps Ethernet link negotiated DENS Flashing Ethernet link activity 2 4GHz radio disabled On Amber 2 4GHz radio enabled in non HT WLAN mode On Green 2 4GHz radio enabled in HT WLAN mode Flashing Green 2 4GHz Air monitor Aree ee OT f 5GHz radio disabled On Amber 5GHz radio enabled in non HT WLAN mode On Green 5GHz radio enabled in HT WLAN mode Flashing Green 5GHz Air monitor 2 2 AP 135 This section introduces the Aruba AP 135 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 Aruba AP 135 is high performance 802 1 1n 3x3 3 MIMO dual radio concurrent 802 1 1a n b g n indoor wireless access points capable of delivering combined wireless data rates of up to 900Mbps These multi function access points provide wirele
36. s key 64 character preshared key 168 bit Triple DES Or 128 192 256 bit AES keys HMAC SHA 1 keys GENERATION Hard coded CO configured Established during Diffie Hellman key agreement Established during Diffie Hellman key agreement 30 STORAGE And ZEROIZATI ON Stored in flash zeroized by the ap wipe out flash command Encrypted in flash using the KEK zeroized by updating through administrative interface or by the ap wipe out flash command Stored in plaintext in volatile memory zeroized when session 1S closed or system powers off Stored in plaintext in volatile memory zeroized when session 1S closed or system powers off USE Encrypts IKEv1 IKEv2 preshared keys and configuration parameters Module and crypto officer authentication during IKEvI IKEv2 entered into the module in plaintext during initialization and encrypted over the IPSec session subsequently Secure IPSec traffic Secure IPSec traffic CSP IKEvI IKEv2 Diffie Hellman Private key IKEvI IKEv2 Diffie Hellman shared secret ArubaOS OpenSSL RNG Seed for FIPS compliant ANSI X9 31 Appendix A2 4 using AES 128 Key algorithm ArubaOS OpenSSL RNG Seed key for FIPS compliant ANSI X9 31 Appendix A2 4 using AES 128 Key algorithm ArubaOS Cryptographic Module RNG Seed for FIPS compliant 186 2 General Purpose X change Notice SHA 1 RNG Aruba
37. ss LAN access air monitoring and wireless intrusion detection and prevention over the 2 4 2 5GHz and 5GHz RF spectrum The access points work in conjunction with Aruba Mobility Controllers to deliver high speed secure user centric network services in education enterprise finance government healthcare and retail applications 2 2 1 Physical Description The Aruba AP 135 series Access Point is a multi chip standalone cryptographic module consisting of hardware and software all contained in a hard plastic case The module contains 802 11 a b g n transceivers and supports 3 integrated omni directional multi band dipole antenna elements supporting up to 3x3 MIMO with spatial diversity The plastic case physically encloses the complete set of hardware and software components and represents the cryptographic boundary of the module The Access Point configuration tested during the cryptographic module testing included Aruba Part Number Dell Corresponding Part Number AP 135 F1 W AP135 F1 The exact firmware versions tested were e ArubaOS_6xx_6 1 2 3 FIPS e Dell PCW 6xx 6 1 2 3 FIPS 2 2 1 1 Dimensions Weight The AP has the following physical dimensions e 170mm H x 170 mm W x 45 mm e 760 g 1 68 Ib 2 2 1 2 Interfaces The module provides the following network interfaces e 2x 10 100 1000 Base T Ethernet RJ45 Auto sensing link speed and MDI MDX e Antenna o 3x RP SMA antenna interfaces supports up to 3x3 MIMO with spatial d
38. te Mesh Portal FIPS mode or Mesh Point 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 lt ap name gt config 4 Terminate the administrative session 3 4 Operational Environment The operational environment is non modifiable The Operating System OS is Linux a real time multi threaded operating system that supports memory protection between processes Access to the underlying Linux implementation is not provided directly Only Aruba provided Crypto Officer interfaces are used There is no user interface provided 20 3 5 Logical Interfaces The physical interfaces are divided into logical interfaces defined by FIPS 140 2 as described in the following table FIPS 140 2 Logical Interface Module Physical Interface Data Input Interface 10 100 1000 Ethernet Ports 802 1 1a b g n Radio Transceiver Data Output Interface 10 100 1000 Ethernet Ports 802 1 1a b g n Radio Transceiver Control Input Interface 10 100 1000 Ethernet Ports PoE Status Output Interface 10 100 1000 Ethernet Ports 802 1 1a b g n Radio Transceiver LEDs Power Interface Power Supply Data input and output control input status output and power interfaces are defined as follows e Data input and output are the packets th
39. the AP 134 AP 135 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 Aruba Dell Relationship Aruba Networks is the OEM for the Dell PowerConnect W line of products Dell products are identical to the Aruba products other than branding and Dell software is identical to Aruba software other than branding Table 1 Corresponding Aruba and Dell Part Numbers Aruba Part Number Dell Corresponding Part Number AP 134 F1 W API34 FI AP 135 F1 W AP135 F1 NOTE References to Aruba ArubaOS Aruba AP 134 and AP 135 wireless access points apply to both the Aruba and Dell versions of these products and documentation 1 2 Acronyms and Abbreviations AES Advanced Encryption Standard AP Access Point CBC Cipher Block Chaining CLI Command
40. to complete the provisioning process a During the provisioning process as Remote Mesh Point 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 Mesh Point the WPA2 PSK is input to the module via the corresponding Mesh cluster profile This key is stored on flash encrypted Via the logging facility of the staging controller ensure that the module the AP is successfully provisioned with firmware and configuration Terminate the administrative session 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 Verify that the module is in FIPS mode For all the approved modes of operations in either Remote AP FIPS mode Control Plane Security AP FIPS Mode Remo
Download Pdf Manuals
Related Search