Aruba 7XXX Series Controllers
with ArubaOS FIPS Firmware
Non-Proprietary Security Policy
FIPS 140-2 Level 2
Version 1.17
June 2016
Aruba 7200 Series Controllers FIPS 140-2 Level 2 Security Policy
Copyright
© 2016 Hewlett Packard Enterprise Company. Hewlett Packard Enterprise Company trademarks include ,
Aruba Networks
®
, Aruba Wireless Networks
®
, the registered Aruba the Mobile Edge Company logo, Aruba Mobility Management
System
®
, Mobile Edge Architecture
®
, People Move. Networks Must Follow
®
, RFprotectrotect
®
, Green Island
®
. All rights reserved. All
other trademarks are the property of their respective owners. Open Source Code
Certain Hewlett Packard Enterprise Company 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. 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. 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
© 2016 Hewlett Packard Enterprise Company. Hewlett Packard Enterprise Company trademarks include, Aruba Networks®, Aruba
Wireless Networks®,the registered Aruba the Mobile Edge Company logo, and Aruba Mobility Management System®.
www.arubanetworks.com
1344 Crossman Avenue
Sunnyvale, California 94089
Phone: 408.227.4500
Fax 408.227.4550
2| Aruba 7XXX Series Controllers FIPS 140-2 Level 2 Security Policy
Contents
Contents............................................................................................................................................................................. 3
Preface............................................................................................................................................................................... 5
Purpose of this Document............................................................................................................................................... 5
Related Documents ......................................................................................................................................................... 5
Additional Product Information ......................................................................................................................5
Overview............................................................................................................................................................................ 6
Cryptographic Module Boundaries ................................................................................................................7
Intended Level of Security ............................................................................................................................................ 10
Physical Security ............................................................................................................................................................ 11
Operational Environment .............................................................................................................................................. 11
Logical Interfaces ........................................................................................................................................................... 12
Roles and Services ........................................................................................................................................................ 13
Crypto Officer Role......................................................................................................................................13
Authentication Mechanisms.........................................................................................................................18
Unauthenticated Services............................................................................................................................19
Non-Approved Services...............................................................................................................................19
Cryptographic Key Management ................................................................................................................................. 19
Implemented Algorithms..............................................................................................................................19
Critical Security Parameters........................................................................................................................22
Alternating Bypass State............................................................................................................................................... 30
Installing the Controller ........................................................................................................................................................ 31
Pre-Installation Checklist............................................................................................................................................... 31
Precautions ..................................................................................................................................................................... 31
Product Examination ...................................................................................................................................31
Package Contents .......................................................................................................................................32
Tamper-Evident Labels ................................................................................................................................................. 33
Reading TELs..............................................................................................................................................33
Required TEL Locations..............................................................................................................................34
Applying TELs .............................................................................................................................................42
Ongoing Management .......................................................................................................................................................... 42
Crypto Officer Management.......................................................................................................................................... 42
Aruba 7XXX Series Controllers FIPS 140-2 Level 2 Security Policy|3
User Guidance................................................................................................................................................................ 43
Setup and Configuration................................................................................................................................................ 43
Setting Up Your Controller............................................................................................................................................ 43
Enabling FIPS Mode...................................................................................................................................................... 43
Enabling FIPS Mode with the WebUI ..........................................................................................................43
Enabling FIPS Mode with the CLI................................................................................................................43
Disabling the LCD........................................................................................................................................44
Disallowed FIPS Mode Configurations ....................................................................................................................... 44
4| Aruba 7XXX Series Controllers FIPS 140-2 Level 2 Security Policy
Preface
This security policy document can be copied and distributed freely.
Purpose of this Document
This release supplement provides information regarding the Aruba 7XXX Controllers with FIPS 140-2 Level 2 validation
from Aruba Networks. The material in this supplement modifies the general Aruba hardware and firmware documentation
included with this product and should be kept with your Aruba product documentation.
This supplement primarily covers the non-proprietary Cryptographic Module Security Policy for the Aruba Controller. This
security policy describes how the controller meets the security requirements of FIPS 140-2 Level 2 and how to place and
maintain the controller 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) website at:
http://csrc.nist.gov/groups/STM/cmvp/index.html
Related Documents
The following items are part of the complete installation and operations documentation included with this product:
• Aruba 7XXX Mobility Controller Installation Guide
• Aruba 7XXX- series Mobility Controller Installation Guide
• ArubaOS 6.5 User Guide
• ArubaOS 6.5 CLI Reference Guide
• ArubaOS 6.5 Quick Start Guide
• ArubaOS 6.5 Upgrade Guide
• Aruba AP Installation Guides
Additional Product Information
More information is available from the following sources:
• The Aruba Networks Web-site contains information on the full line of products from Aruba Networks:
http://www.arubanetworks.com
• The NIST Validated Modules Web-site contains contact information for answers to technical or sales-related
questions for the product:
http://csrc.nist.gov/groups/STM/cmvp/index.html
Aruba 7XXX Series Controllers FIPS 140-2 Level 2 Security Policy|5
Overview
Aruba 7XXX series Mobility Controllers are optimized for 802.11ac and mobile app delivery. Fully
application-aware, the 7XXX series prioritizes mobile apps based on user identity and offers exceptional
scale for BYOD transactions and device densities.
With a new central processor employing eight CPU cores and four virtual cores, the 7XXX series supports
over 32,000 wireless devices and performs stateful firewall policy enforcement at speeds up to 40 Gbps –
plenty of capacity for BYOD and 802.11ac devices.
New levels of visibility, delivered by Aruba AppRF on the controller, allow IT to see applications by user,
including top web-based applications like Facebook and Box.
The 7XXX series also manages authentication, encryption, VPN connections, IPv4 and IPv6 services, the
Aruba Policy Enforcement Firewall™ with AppRF Technology, Aruba Adaptive Radio Management™,
and Aruba RFprotect™ spectrum analysis and wireless intrusion protection.
The Aruba controller configurations validated during the cryptographic module testing included:
• Aruba 7005-F1
• Aruba 7005-USF1
• Aruba 7010-F1
• Aruba 7010-USF1
• Aruba 7024-F1
• Aruba 7024-USF1
• Aruba 7030-F1
 Aruba 7030-USF1
 Aruba 7205-F1
 Aruba 7205-USF1
 FIPS Kit: 4011570-01 (Part number for Tamper Evident Labels)
 The firmware versions validated are ArubaOS 6.4.4-FIPS and ArubaOS 6.5.0-FIPS
Note: For radio regulatory reasons, part numbers ending with -USF1 are to be sold in the US only. Part
numbers ending with -F1 are considered ‘rest of the world’ and must not be used for deployment in the
United States. From a FIPS perspective, both -USF1 and -F1 models are identical and fully FIPS
compliant.
6| Aruba 7XXX Series Controllers FIPS 140-2 Level 2 Security Policy
Physical Description
Cryptographic Module Boundaries
For FIPS 140-2 Level 2 validation, the Controller has been validated as a multi-chip standalone
cryptographic module. The opaque hard plastic (Aruba 7005 Controller only) or metal chassis physically
encloses the complete set of hardware and firmware components and represents the cryptographic
boundary of the module. The cryptographic boundary is defined as encompassing the top, front, left, right,
rear, and bottom surfaces of the chassis.
Figure 1 - The Aruba 7005 controller
Figure 1 shows the front of the Aruba 7005 Controller, and illustrates the following:
• Four Gigabit Ethernet ports
• One Type A USB port
• LINK/ACT and Status LEDs
• Management/Status LED
• Console Connections - RJ-45 and Mini-USB (Disabled in FIPS mode by TELs)
Figure 2 - The Aruba 7010 controller
Aruba 7XXX Series Controllers FIPS 140-2 Level 2 Security Policy|7
Figure 2 shows the front of the Aruba 7010 Controller, and illustrates the following:
• Sixteen 10/100/1000 Ethernet ports
• Two Small Form-Factor Pluggable (SFP) Uplink ports
• Two Type A USB ports
• LINK/ACT and Status LEDs
• Management/Status LED
• LCD Panel
• Navigation Buttons (Functionally disabled in FIPS mode)
• Console Connections - RJ-45 and Mini-USB (Disabled in FIPS mode by TELs)
Figure 3 - The Aruba 7024 controller
8| Aruba 7XXX Series Controllers FIPS 140-2 Level 2 Security Policy
Figure 3 shows the front of the Aruba 7024 Controller, and illustrates the following:
• Twenty-four 10/100/1000 Ethernet ports
• Two Enhanced Small Form-Factor Pluggable (SFP+) Uplink ports
• One Type A USB ports
• LINK/ACT and Status LEDs
• Management/Status LED
• LCD Panel
• Navigation Buttons (Functionally disabled in FIPS mode)
• Console Connections - RJ-45 and Mini-USB (Disabled in FIPS mode by TELs)
Figure 4 - The Aruba 7030 controller chassis
Figure 4 shows the front of the Aruba 7030 Controller, and illustrates the following:
• Eight 10/100/1000 Ethernet ports
• Eight Small Form-Factor Pluggable (SFP) Uplink ports
• One Type A USB port
• LINK/ACT and Status LEDs
• Management/Status LED
• LCD Panel
• Navigation Buttons (Functionally disabled in FIPS mode)
• Console Connections - RJ-45 and Mini-USB (Disabled in FIPS mode by TELs)
Aruba 7XXX Series Controllers FIPS 140-2 Level 2 Security Policy|9
Figure 5 - The Aruba 7205 controller chassis
Figure 5 shows the front of the Aruba 7205 Controller, and illustrates the following:
• Four 10/100/1000 Ethernet ports
• Four Small Form-Factor Pluggable (SFP) Uplink ports
• Two Dual-Purpose Gigabit Uplink Ports
• Two Type A USB ports (one is on the front and one is on the back)
• LINK/ACT and Status LEDs
• Management/Status LED
• LCD Panel
• Navigation Buttons (Functionally disabled in FIPS mode)
• Console Connections - RJ-45 and Mini-USB (Disabled in FIPS mode by TELs)
Intended Level of Security
The 7XXX Controller and associated modules are intended to meet overall FIPS 140-2 Level 2
requirements as shown in Table 1.
Table 1 Intended Level of Security
Section Section Title Level
1 Cryptographic Module Specification 2
2 Cryptographic Module Ports and Interfaces 2
3 Roles, Services, and Authentication 2
10| Aruba 7XXX Series Controllers FIPS 140-2 Level 2 Security Policy
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
Physical Security
The Aruba Controller is a scalable, multi-processor standalone network device and is enclosed in a robust
steel housing. The controller enclosure is resistant to probing and is opaque within the visible spectrum.
The enclosure of the module has been designed to satisfy FIPS 140-2 Level 2 physical security
requirements.
The Aruba 7XXX Controller requires Tamper-Evident Labels (TELs) to allow the detection of the opening
of the chassis cover and to block the Serial console port.
To protect the Aruba 7XXX Controller from any tampering with the product, TELs should be applied by
the Crypto Officer as covered under “Tamper-Evident Labels” on page 33.
Operational Environment
The operational environment is non-modifiable. The control plane 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 Networks provided interfaces are
used, and the CLI is a restricted command set. The module only allows the loading of trusted and verified
firmware that is signed by Aruba.
Aruba 7XXX Series Controllers FIPS 140-2 Level 2 Security Policy|11
Logical Interfaces
All of these physical interfaces are separated into logical interfaces defined by FIPS 140-2, as described
in the following table.
Table 2 FIPS 140-2 Logical Interfaces
FIPS 140-2 Logical Interface Module Physical Interface
Data Input Interface • 10/100/1000 Ethernet Ports
• SFP/SFP+ Uplink Ports
• USB Port
Data Output Interface • 10/100/1000 Ethernet Ports
• SFP/SFP+ Uplink Ports
• USB Port
Control Input Interface • 10/100/1000 Ethernet Ports
• SFP/SFP+ Uplink Ports
Status Output Interface • 10/100/1000 Ethernet Ports
• SFP/SFP+ Uplink Ports
• USB Port
• LEDs
Power Interface • Power Supply
Data input and output, control input, status output, and power interfaces are defined as follows:
Data input and output are the packets that use the firewall, VPN, and routing functionality of the modules.
• Control input consists of manual control inputs for power and reset through the power and reset
switch. It also consists of all of the data that is entered into the controller while using the management
interfaces.
• Status output consists of the status indicators displayed through the LEDs, the status data that is
output from the controller while using the management interfaces, and the log file.
• LEDs indicate the physical state of the module, such as power-up (or rebooting), utilization level,
activation state (including fan, ports, and power). The log file records the results of self-tests,
configuration errors, and monitoring data.
• A power supply is used to connect the electric power cable.
The controller distinguishes between different forms of data, control, and status traffic over the network
ports by analyzing the packets header information and contents.
12| Aruba 7XXX Series Controllers FIPS 140-2 Level 2 Security Policy
Roles and Services
The Aruba Controller supports role-based authentication. There are two roles in the module (as required
by FIPS 140-2 Level 2) that operators may assume: a Crypto Officer role and a User role. The
Administrator maps to the Crypto-Officer role and the client Users map to the User role.
Crypto Officer Role
The Crypto Officer role has the ability to configure, manage, and monitor the controller. Three
management interfaces can be used for this purpose:
• SSHv2 CLI
The Crypto Officer can use the CLI to perform non-security-sensitive and security-sensitive
monitoring and configuration. The CLI can be accessed remotely by using the SSHv2 secured
management session over the Ethernet ports or locally over the serial port. In FIPS mode, the serial
port is disabled.
• Web Interface
The Crypto Officer can use the Web Interface as an alternative to the CLI. The Web Interface
provides a highly intuitive, graphical interface for a comprehensive set of controller management
tools. The Web Interface can be accessed from a TLS-enabled Web browser using HTTPS (HTTP
with Secure Socket Layer) on logical port 4343.
• SNMPv3
The Crypto Officer can also use SNMPv3 to remotely perform monitoring and use ‘get’ and ‘getnext’
commands.
See the table below for descriptions of the services available to the Crypto Officer role.
Table 3 Crypto-Officer Services
Service Description Input Output
CSP Access
(please see table
6 below for CSP
details)
SSHv2 Provide authenticated and
encrypted remote management
sessions while using the CLI
SSHv2 key agreement
parameters, SSH
inputs, and data
SSHv2 outputs and
data
27, 28 (delete)
Aruba 7XXX Series Controllers FIPS 140-2 Level 2 Security Policy|13
Table 3 Crypto-Officer Services
SNMPv3 Provides ability to query
management information
SNMPv3 requests SNMPv3
responses
32, 33 (read)
34 (delete)
IKEv1/IKEv2-
IPSec
Provide authenticated and
encrypted remote management
sessions to access the CLI
functionality
IKEv1/IKEv2 inputs and
data; IPSec inputs,
commands, and data
IKEv1/IKEv2
outputs, status, and
data; IPSec
outputs, status, and
data
19 (read)
20, 21, 22, 23, 24,
25 and 26 (delete)
Configuring
Network
Management
Create management Users and
set their password and privilege
level; configure the SNMP agent
Commands and
configuration data
Status of
commands and
configuration data
32, 33 (read)
34 (delete)
Configuring
Module Platform
Define the platform subsystem
firmware of the module by
entering Bootrom Monitor Mode,
File System, fault report,
message logging, and other
platform related commands
Commands and
configuration data
Status of
commands and
configuration data
None
Configuring
Hardware
Controllers
Define synchronization features
for module
Commands and
configuration data
Status of
commands and
configuration data
None
Configuring
Internet Protocol
Set IP functionality Commands and
configuration data
Status of
commands and
configuration data
None
Configuring
Quality of Service
(QoS)
Configure QOS values for module Commands and
configuration data
Status of
commands and
configuration data
None
14| Aruba 7XXX Series Controllers FIPS 140-2 Level 2 Security Policy
Table 3 Crypto-Officer Services
Configuring VPN Configure Public Key
Infrastructure (PKI); configure the
Internet Key Exchange
(IKEv1/IKEv2) Security Protocol;
configure the IPSec protocol
Commands and
configuration data
Status of
commands and
configuration data
19 (read)
16, 17, 18, 19, 20,
21, 22, 23, 24,25 and
26 (delete)
Configuring DHCP Configure DHCP on module Commands and
configuration data
Status of
commands and
configuration data
None
Configuring
Security
Define security features for
module, including Access List,
Authentication, Authorization and
Accounting (AAA), and firewall
functionality
Commands and
configuration data
Status of
commands and
configuration data
12, 13, 14
(read/write/delete)
Manage
Certificates
Install, rename, and delete X.509
certificates
Commands and
configuration data;
Certificates and keys
Status of
certificates,
commands, and
configuration
15, 16, 17,18
(write/delete)
HTTPS over TLS Secure browser connection over
Transport Layer Security acting
as a Crypto Officer service (web
management interface)
TLS inputs, commands,
and data
TLS outputs,
status, and data
29, 30 and 31
(delete)
Status Function Cryptographic officer may use
CLI "show" commands or view
WebUI via TLS to view the
controller configuration, routing
tables, and active sessions; view
health, temperature, memory
status, voltage, and packet
statistics; review accounting logs,
and view physical interface status
Commands and
configuration data
Status of
commands and
configurations
None
IPSec tunnel
establishment for
RADIUS
protection
Provided authenticated/encrypted
channel to RADIUS server
IKEv1/IKEv2 inputs and
data; IPSec inputs,
commands, and data
IKEv1/IKEv2
outputs, status, and
data; IPSec
outputs, status, and
data
12 and 19
(read/write/delete)
20, 21, 22, 23, 24, 25
and 26 (write/delete)
Aruba 7XXX Series Controllers FIPS 140-2 Level 2 Security Policy|15
Table 3 Crypto-Officer Services
Self-Test Perform FIPS start-up tests on
demand
None Error messages
logged if a failure
occurs
None
Configuring
Bypass Operation
Configure bypass operation on
the module
Commands and
configuration data
Status of
commands and
configuration data
None
Updating
Firmware
Updating firmware on the module Commands and
configuration data
Status of
commands and
configuration data
None
Configuring Online
Certificate Status
Protocol (OCSP)
Responder
Configuring OCSP responder
functionality
OCSP inputs,
commands, and data
OCSP outputs,
status, and data
27, 28, 29, 30 (read)
Configuring
Control Plane
Security (CPSec)
Configuring Control Plane
Security mode to protect
communication with APs using
IPSec and issue self signed
certificates to APs
Commands and
configuration data,
IKEv1/IKEv2 inputs and
data; IPSec inputs,
commands, and data
Status of
commands, IKEv1/
IKEv2 outputs,
status, and data;
IPSec outputs,
status, and data
and configuration
data, self signed
certificates
12 and 19
(read/write/delete)
20, 21, 23, 22, 24, 25
and 26 (write/delete)
Zeroization The cryptographic keys stored in
SDRAM memory can be zeroized
by rebooting the module. The
cryptographic keys (IKEv1 Pre-
shared key and 802.11i Pre-
Shared Key) 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 ‘write erase all.
Command Progress
information
All CSPs will be
destroyed.
16| Aruba 7XXX Series Controllers FIPS 140-2 Level 2 Security Policy
User Role
Table 4 below lists the services available to User role:
Table 4 User Service
Service Description Input Output
CSP Access (please
see table 6 below for
CSP details)
IKEv1/IKEv2-
IPSec
Access the module's IPSec
services in order to secure
network traffic
IPSec inputs,
commands, and data
IPSec outputs,
status, and data 20, 21, 22, 23, 24, 25 and
26 (delete)
HTTPS over TLS Access the module’s TLS
services in order to secure
network traffic
TLS inputs,
commands, and data
TLS outputs,
status, and data
29, 30, 31 (delete)
EAP-TLS
termination
Provide EAP-TLS termination EAP-TLS inputs,
commands and data
EAP-TLS outputs,
status and data
29, 30, 31 (read/delete)
802.11i Shared
Key Mode
Access the module’s 802.11i
services in order to secure
network traffic
802.11i inputs,
commands and data
802.11i outputs,
status and data
36, 37 and 38 (delete)
802.11i with EAP-
TLS
Access the module’s 802.11i
services in order to secure
network traffic
802.11i inputs,
commands and data
802.11i outputs,
status, and data
36, 37 and 38 (delete)
Self-Tests Run Power-On Self-Tests and
Conditional Tests
None Error messages
logged if a failure
occurs
None
Aruba 7XXX Series Controllers FIPS 140-2 Level 2 Security Policy|17
Authentication Mechanisms
The Aruba Controller supports role-based authentication. Role-based authentication is performed before
the Crypto Officer enters privileged mode using admin password via Web Interface or SSHv2 or by
entering enable command and password in console. Role-based authentication is also performed for
User authentication.
This includes password and RSA/ECDSA-based authentication mechanisms. The strength of each
authentication mechanism is described below.
Table 5 Estimated Strength of Authentication Mechanisms
Authentication Type Role Strength
Password-based authentication Crypto Officer Passwords are required to be a minimum of eight characters and a
maximum of 32 with a minimum of one letter and one number. If six
(6) integers, one (1) special character and one (1) alphabet are used
without repetition for an eight (8) digit PIN, the probability of
randomly guessing the correct sequence is one (1) in 251,596,800
(this calculation is based on the assumption that the typical standard
American QWERTY computer keyboard has 10 Integer digits, 52
alphabetic characters, and 32 special characters providing 94
characters to choose from in total. The calculation should be 10 x 9 x
8 x 7 x 6 x 5 x 32 x 52 = 251, 595, 800). Therefore, the associated
probability of a successful random attempt during a one-minute
period is approximate 1 in 251,596,800, which is less than 1 in
100,000 required by FIPS 140-2.
Password-based authentication
(WPA2-PSK)
User Same authentication mechanism strength as CO role above.
Password-based authentication
(IKEv1)
User A 64 ASCII (128 HEX) character pre-shared string is randomly
chosen by the administrator. It may consist of upper and lower case
alphabetic characters, numeric characters and 32 special characters.
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 is
approximately 1 in 94^64, which is less than 1 in 1,000,000 required
by FIPS 140-2.
RSA-based authentication
(IKEv1, IKEv2 and TLS)
User The module supports 2048-bit RSA keys authentication during
IKEv1, IKEv2 and TLS. RSA 2048 bit keys correspond to 112 bits of
security. Assuming the low end 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.
18| Aruba 7XXX Series Controllers FIPS 140-2 Level 2 Security Policy
ECDSA-based authentication
IKEv1, IKEv2 and TLS
User ECDSA signing and verification is used to authenticate to the module
during IKEv1/IKEv2. Both P-256 and P-384 curves are supported.
ECDSA P-256 provides 128 bits of equivalent security, and P-384
provides 192 bits of equivalent security. Assuming the low end of
that range, the associated probability of a successful random attempt
during a one-minute period is 1 in 2^128, which is less than 1 in
100,000 required by FIPS 140-2.
Unauthenticated Services
The Aruba Controller can perform VLAN, bridging, firewall, routing, and forwarding functionality without
authentication. These services do not involve any cryptographic processing.
Additional unauthenticated services include performance of the power-on self-test and system status
indication via LEDs.
Non-Approved Services
The following non-approved services are available in non-FIPS mode.
• IPSec/IKE with Diffie-Hellman 768-bit/1024-bit moduli, DES, HMAC-MD5 and MD5
• SSHv1 using RC4
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.
Cryptographic Key Management
Implemented Algorithms
The firmware 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 library algorithm implementation
• ArubaOS Crypto library algorithm implementation
• ArubaOS UBootloader library algorithm implementation
• Aruba Hardware Crypto Accelerator algorithm implementation
Below are the detailed lists for the FIPS approved algorithms and the associated certificate implemented
by each algorithm implementation.
• Aruba Hardware Crypto Accelerator algorithm implementation:
o AES (Certs. #2477 and #3014)
o Triple-DES (Certs. #1516 and #1770)
o SHS (Certs. #2096 and #2522)
o HMAC (Certs. #1520 and #1906)
o RSA (Certs. #1266 and #1573)
Aruba 7XXX Series Controllers FIPS 140-2 Level 2 Security Policy|19
The above hardware algorithm certificates were tested on Broadcom XLP series processors by Broadcom
Corporation. Aruba Networks purchased the processors and put them in the Aruba modules to support
bulk cryptographic operations. Please be aware that there is no partnership between Aruba Networks and
Broadcom Corporation.
The firmware supports the following cryptographic implementations.
• ArubaOS OpenSSL library implements the following FIPS-approved algorithms:
o AES (Cert. #2900)
o SP800-135rev1 KDF CVL (Cert. #326)
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 library implements the following FIPS Approved Algorithms:
o AES (Cert. #2884)
o SP800-135rev1 KDF CVL (Cert. #314)1
o ECDSA (Cert. #519)
o HMAC (Cert. #1818)
o RSA (Cert. #1518)
o SHS (Cert. #2425)
o Triple-DES (Cert. #1720)
• ArubaOS UBOOT Bootloader library implements the following FIPS-approved algorithms:
o RSA (Cert. #1517)
o SHS (Cert. #2424)
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)
• RSA (key wrapping; key establishment methodology provides 112 bits of encryption strength)
• NDRNG
Note: RSA key wrapping is used in TLS protocol implementation.
Non-FIPS Approved Cryptographic Algorithms
1
Only the IKEv2 KDF is active on this algorithm implementation
20| Aruba 7XXX Series Controllers FIPS 140-2 Level 2 Security Policy
• DES
• Diffie-Hellman (less than 112 bits of encryption strength)
• HMAC-MD5
• MD5
• RC4
NOTE: IKEv1, IKEv2, TLS, SSH and SNMP protocols have not been reviewed or tested by the CAVP and
CMVP.
Aruba 7XXX Series Controllers FIPS 140-2 Level 2 Security Policy|21
Critical Security Parameters
The following are the Critical Security Parameters (CSPs) used in the module.
Table 6 CSPs/Keys Used in the module
#
Name Algorithm/Key Size Generation/Use Storage Zeroization
General Keys/CSPs
1 Key Encryption Key
(KEK)
Triple-DES
(192 bits)
Hardcoded during
manufacturing. Used to
protect keys stored in
the flash.
Stored in Flash
memory (plaintext).
Zeroized by using
command ‘write erase
all’.
2 DRBG entropy input SP 800-90a
CTR_DRBG
(512 bits)
Entropy inputs to DRBG
function used to
construct the DRBG
seed.
Stored in SDRAM
memory (plaintext)
Zeroized by rebooting
the module
3 DRBG seed SP 800-90a
CTR_DRBG
(384-bits)
Input to the DRBG that
determines the internal
state of the DRBG.
Generated using DRBG
derivation function that
includes the entropy
input from the entropy
source.
Stored in SDRAM
memory (plaintext)
Zeroized by rebooting
the module
4 DRBG Key SP 800-90a
CTR_DRBG
(256 bits)
This is the DRBG key
used for SP 800-90a
CTR_DRBG
Stored in SDRAM
memory (plaintext)
Zeroized by rebooting
the module
5 DRBG V SP 800-90a
CTR_DRBG V
(128 bits)
Internal V value used as
part of SP 800-90a
CTR_DRBG
Stored in SDRAM
memory (plaintext)
Zeroized by rebooting
the module
22| Aruba 7XXX Series Controllers FIPS 140-2 Level 2 Security Policy
Table 6 CSPs/Keys Used in the module
6 Diffie-Hellman
private key
Diffie-Hellman Group
14 (224 bits)
Generated internally by
calling FIPS approved
DRBG (cert #528)
during Diffie-Hellman
Exchange. Used for
establishing DH shared
secret.
Stored in SDRAM
memory (plaintext).
Zeroized by rebooting
the module
7 Diffie-Hellman public
key
Diffie-Hellman Group
14 (2048 bits)
Generated internally by
calling FIPS approved
DRBG (cert #528)
during Diffie-Hellman
Exchange. Used for
establishing DH shared
secret.
Stored in SDRAM
memory (plaintext).
Zeroized by rebooting
the module
8 Diffie-Hellman shared
secret
Diffie-Hellman Group
14 (2048 bits)
Established during
Diffie-Hellman
Exchange. Used for
deriving IPSec/IKE
cryptographic keys
Stored in SDRAM
memory (plaintext).
Zeroized by rebooting
the module
9 EC Diffie-Hellman
private key
EC Diffie-Hellman
(Curves: P-256 or P-
384).
Generated internally by
calling FIPS approved
DRBG (cert #528)
during EC Diffie-
Hellman Exchange.
Used for establishing
ECDH shared secret
Stored in SDRAM
memory (plaintext).
Zeroized by rebooting
the module
10 EC Diffie-Hellman
public key
EC Diffie-Hellman
(Curves: P-256 or P-
384).
Generated internally by
calling FIPS approved
DRBG (cert #528)
during EC Diffie-
Hellman Exchange.
Used for establishing
ECDH shared secret
Stored in SDRAM
memory (plaintext).
Zeroized by rebooting
the module
11 EC Diffie-Hellman
shared secret
EC Diffie-Hellman
(Curves: P-256 or P-
384)
Established during EC
Diffie-Hellman
Exchange. Used for
deriving IPSec/IKE
cryptographic keys
Stored in SDRAM
memory (plaintext).
Zeroized by rebooting
the module
Aruba 7XXX Series Controllers FIPS 140-2 Level 2 Security Policy|23
Table 6 CSPs/Keys Used in the module
12 RADIUS server
shared secret
8-128 characters
shared secret
Entered by CO role.
Used for RADIUS
server authentication
Stored in SDRAM
memory (plaintext).
Zeroized by using
command ‘write erase
all’ or by overwriting
with a new secret
13 Enable secret 8-64 characters
password
Entered by CO role.
Used for CO role
authentication
Stored in SDRAM
memory (plaintext).
Zeroized by using
command ‘write erase
all’ or by overwriting
with a new secret
14 User Passwords 8-64 characters
password
Entered by CO role.
Used for User role
authentication.
Stored in SDRAM
memory (plaintext).
Zeroized by using
command ‘write erase
all’ or by overwriting
with a new secret
15 RSA Private Key RSA 2048 bit private
key
This key is generated by
calling FIPS approved
DRBG (cert #528) in the
module. Used for
IKEv1, IKEv2, TLS,
OCSP (signing OCSP
messages) and EAP-
TLS peers
authentication.
Stored in Flash
memory (plaintext)
encrypted with KEK.
Zeroized by using
command ‘write erase
all’
16 RSA public key RSA 2048 bits public
key
This key is generated by
calling FIPS approved
DRBG (cert #528) in the
module. Used for
IKEv1, IKEv2, TLS,
OCSP (verifying OCSP
messages) and EAP-
TLS peers
authentication.
Stored in Flash
memory (plaintext)
encrypted with KEK.
Zeroized by using
command ‘write erase
all’
17 ECDSA Private Key ECDSA suite B P-256
and P-384 curves
This key is generated by
calling FIPS approved
DRBG (cert #528) in the
module. Used for
IKEv1, IKEv2, TLS and
EAP-TLS peers
authentication.
Stored in Flash
memory (plaintext)
encrypted with KEK.
Zeroized by using
command ‘write erase
all’
24| Aruba 7XXX Series Controllers FIPS 140-2 Level 2 Security Policy
Table 6 CSPs/Keys Used in the module
18 ECDSA Public Key ECDSA suite B P-256
and P-384 curves
This key is generated by
calling FIPS approved
DRBG (cert #528) in the
module. Used for
IKEv1, IKEv2, TLS and
EAP-TLS peers
authentication.
Stored in Flash
memory (plaintext)
encrypted with KEK.
Zeroized by using
command ‘write erase
all’.
IPSec/IKE
19 IKEv1 Pre-shared key Shared secret
(64 ASCII or 128 HEX
characters)
Entered by CO role.
Used for IKEv1 peers
authentication.
Stored in Flash
memory encrypted
with KEK.
Zeroized by using
command ‘write erase
all’ or by overwriting
with a new secret
20 skeyid Shared Secret
(160/256/384 bits)
A shared secret known
only to IKE peers. It
was established via key
derivation function
defined in SP800-135
KDF (IKEv1). Used
for deriving other keys
in IKE protocol
implementation.
Stored in SDRAM
memory (plaintext).
Zeroized by rebooting
the module.
21 skeyid_d Shared Secret
(160/256/384 bits)
A shared secret known
only to IKE peers. It
was derived via key
derivation function
defined in SP800-135
KDF (IKEv1). Used
for deriving IKE
session authentication
key
Stored in SDRAM
memory (plaintext).
Zeroized by rebooting
the module
22 SKEYSEED Shared Secret
(160/256/384 bits)
A shared secret known
only to IKE peers. It
was derived via key
derivation function
defined in SP800-135
KDF (IKEv2) and it
will be used for
deriving IKE session
authentication key.
Stored in SDRAM
memory (plaintext).
Zeroized by rebooting
the module
Aruba 7XXX Series Controllers FIPS 140-2 Level 2 Security Policy|25
Table 6 CSPs/Keys Used in the module
23 IKE session
authentication key
HMAC-SHA-
1/256/384
(160/256/384 bits)
The IKE session (IKE
Phase I) authentication
key. This key is
derived via key
derivation function
defined in SP800-135
KDF (IKEv1/IKEv2).
Used for IKEv1/IKEv2
payload integrity
verification.
Stored in SDRAM
memory (plaintext).
Zeroized by rebooting
the module
24 IKE session
encryption key
Triple-DES
(192 bits) /AES
(128/192/256 bits)
The IKE session (IKE
Phase I) encrypt key.
This key is derived via
key derivation function
defined in SP800-135
KDF
(IKEv1/IKEv2).Used
for IKE payload
protection.
Stored in SDRAM
memory (plaintext).
Zeroized by rebooting
the module
25 IPSec session
encryption keys
Triple-DES (192 bits) /
AES and AES-GCM
(128/192/256 bits)
The IPsec (IKE phase
II) encryption key. This
key is derived via a key
derivation function
defined in SP800-135
KDF (IKEv1/IKEv2).
Used for IPSec traffics
protection
Stored in SDRAM
memory (plaintext).
Zeroized by rebooting
the module
26 IPSec session
authentication keys
HMAC-SHA-1 (160
bits)
The IPsec (IKE Phase
II) authentication key.
This key is derived via
using the KDF defined
in SP800-135 KDF
(IKEv1/IKEv2). Used
for IPSec traffics
integrity verification.
Stored in SDRAM
memory (plaintext).
Zeroized by rebooting
the module
SSHv2
27 SSHv2 session keys AES (128/192/256
bits)
This key is derived via
a key derivation
function defined in
SP800-135 KDF
(SSHv2). Used for
SSHv2 traffics
protection.
Stored in SDRAM
memory (plaintext).
Zeroized by rebooting
the module
26| Aruba 7XXX Series Controllers FIPS 140-2 Level 2 Security Policy
Table 6 CSPs/Keys Used in the module
28 SSHv2 session
authentication key
HMAC-SHA-1 (160-
bit)
This key is derived via
a key derivation
function defined in
SP800-135 KDF
(SSHv2). Used for
SSHv2 traffics
integrity verification.
Stored in SDRAM
memory (plaintext).
Zeroized by rebooting
the module
TLS
29 TLS pre-master secret 48 bytes secret This key is transferred
into the module,
protected by TLS RSA
public key.
Stored in SDRAM
memory (plaintext).
Zeroized by rebooting
the module
30 TLS session
encryption key
AES 128/192/256 bits This key is derived via
a key derivation
function defined in
SP800-135 KDF
(TLS). Used for TLS
traffics protection
Stored in SDRAM
memory (plaintext).
Zeroized by rebooting
the module
31 TLS session
authentication key
HMAC-SHA-
1/256/384
(160/256/384 bits)
This key is derived via
a key derivation
function defined in
SP800-135 KDF
(TLS). Used for TLS
traffics integrity
verification.
Stored in SDRAM
memory (plaintext).
Zeroized by rebooting
the module
SNMPv3
32 SNMPv3
authentication
password
8-64 characters
password
Entered by CO role.
User for SNMPv3
authentication
Stored in Flash
memory (plaintext)
encrypted with KEK.
Zeroized by using
command ‘write erase
all’ or by overwriting
with a new secret
33 SNMPv3 engine ID 8-64 characters
password
Entered by CO role. A
unique string used to
identify the SNMP
engine.
Stored in Flash
memory (plaintext)
encrypted with KEK.
Zeroized by using
command ‘write erase
all’ or by overwriting
with a new secret
Aruba 7XXX Series Controllers FIPS 140-2 Level 2 Security Policy|27
Table 6 CSPs/Keys Used in the module
34 SNMPv3 session key AES-CFB key (128
bits)
This key is derived via
a key derivation
function defined in
SP800-135 KDF
(SNMPv3). Used for
SNMPv3 traffics
protection.
Stored in SDRAM
memory (plaintext).
Zeroized by rebooting
the module
802.11i
35 802.11i Pre-Shared
Key (PSK)
Shared secret
(8-63 characters)
Entered by CO role.
Used for 802.11i
client/server
authentication
Stored in Flash
memory encrypted
with KEK.
Zeroized by using
command ‘write erase
all’ or by overwriting
with a new secret
36 802.11i Pair-Wise
Master key (PMK)
Shared secret
(256 bits)
The PMK is transferred
to the module,
protected by IPSec
secure tunnel. Used to
derive the Pairwise
Transient Key (PTK)
for 802.11i
communications.
Stored in SDRAM
(plaintext).
Zeroized by rebooting
the module
37 802.11i Pairwise
Transient Key (PTK)
Shared secret
(512 bits)
This key is used to
derive 802.11i session
key by using the KDF
defined in SP800-108.
Stored in SDRAM
memory (plaintext)
Zeroized by rebooting
the module
38 802.11i session key AES-CCM
(128 bits)
Derived during 802.11i
4-way handshake by
using the KDF defined
in SP800-108.
Stored in SDRAM
memory (plaintext).
Zeroized by rebooting
the module
Note: Key size of DH Group 1 (768 bits) and Group 2 (1024 bits) are not allowed in FIPS mode.
Self-Tests
The module performs Power On Self-Tests regardless the modes (non-FIPS mode and FIPS mode). In
addition, the module also performs Conditional tests after being configured into the FIPS mode. In the
event any self-test fails, the module will enter an error state, log the error, and reboot automatically.
28| Aruba 7XXX Series Controllers FIPS 140-2 Level 2 Security Policy
The module performs the following POSTs (Power On Self-Tests):
• ArubaOS OpenSSL library (Firmware)
o AES encrypt KAT
o AES decrypt KAT
o Triple-DES encrypt KAT
o Triple-DES decrypt KAT
o DRBG KAT
o RSA sign KAT
o RSA verify KAT
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 library (Firmware)
o AES encrypt KAT
o AES decrypt KAT
o AES-GCM KAT
o Triple-DES encrypt KAT
o Triple-DES decrypt KAT
o SHA (SHA1, SHA256, SHA384 and SHA512) KAT
o HMAC (HMAC-SHA1, HMAC-SHA256, HMAC-SHA384 and HMAC-SHA512) KAT
o RSA sign KAT
o RSA verify KAT
o ECDSA Pairwise Consistency Test
• ArubaOS Uboot BootLoader library (Firmware)
o Firmware Integrity Test: RSA PKCS#1 v1.5 (2048 bits) signature verification with SHA-1
• Aruba Hardware Crypto Accelerator (Hardware):
o AES encrypt KAT
o AES decrypt KAT
o AES-CCM encrypt KAT
o AES-CCM decrypt KAT
o Triple-DES encrypt KAT
o Triple-DES decrypt KAT
o HMAC (HMAC-SHA1) KAT
o RSA sign KAT
o RSA verify KAT
The module performs the following Conditional Tests:
• ArubaOS OpenSSL library (Firmware)
o Bypass Tests (Wired Bypass Test and Wireless Bypass Test)
o CRNG Test on Approved DRBG
o ECDSA Pairwise Consistency Test
o RSA Pairwise Consistency Test
• ArubaOS Crypto library (Firmware)
Aruba 7XXX Series Controllers FIPS 140-2 Level 2 Security Policy|29
o ECDSA Pairwise Consistency Test
o RSA Pairwise Consistency Test
• ArubaOS Uboot BootLoader library (Firmware)
o Firmware Load Test - RSA PKCS#1 v1.5 (2048 bits) signature verification
• CRNG Test to NDRNG (Firmware)
Self-test results are logged in a log file. Upon successful completion of the power-up self tests, the
module logs a KATS: passed message into a log file. Confirm the file update by checking the associated
time of the file.
In the event of a hardware KATs failure, the log file records one of the following messages depending on
the algorithm being validated:
• AES256 HMAC-SHA1 hash failed
• AES256 Encrypt failed
• AES256 Decrypt Failed
• 3DES HMAC-SHA1 hash failed
• 3DES Encrypt failed
• 3DES Decrypt Failed
• DES HMAC-SHA1 hash failed
• DES Encrypt failed
• DES Decrypt Failed
• HW KAT test failed for AESCCM CTR. Rebooting
• AESCCM Encrypt Failed
This text is followed by this message:
The POST Test failed!!!!
Rebooting…
Alternating Bypass State
The controller implements an alternating bypass state when:
• a port is configured in trusted mode to provide unauthenticated services
• a configuration provides wireless access without encryption
The alternating bypass status can be identified by retrieving the port configuration or the wireless network
configuration.
30| Aruba 7XXX Series Controllers FIPS 140-2 Level 2 Security Policy
Installing the Controller
This chapter covers the physical installation of the 7XXX Controllers with FIPS 140-2 Level 2 validation. The Crypto
Officer is responsible for ensuring that the following procedures are used to place the controller in a FIPS-approved mode
of operation.
This chapter covers the following installation topics:
• Precautions to be observed during installation
• Requirements for the controller components and rack mounting gear
• Selecting a proper environment for the controller
• Mounting the controller in a rack
• Connecting power to the controller
Pre-Installation Checklist
You will need the following during installation:
• Aruba 7XXXController components.
• Phillips or cross-head screwdriver.
• Equipment rack.
• Aruba power cord for each power supply, rated to at least 10 A with IEC320 connector.
• Adequate power supplies and electrical power.
• Cool, non-condensing air 0 to 40 ºC (32 to 104 ºF). May require air conditioning.
• Management Station (PC) with 10/100 Mbps Ethernet port and SSHv2 software.
• A 4- or 8-conductor Category 5 UTP Ethernet cable.
Precautions
• Installation should be performed only by a trained technician.
• Dangerous voltage in excess of 240 VAC is always present while the Aruba power supply is plugged into an electrical
outlet. Remove all rings, jewelry, and other potentially conductive material before working with this product.
• Never insert foreign objects into the chassis, the power supply, or any other component, even when the power
supplies have been turned off, unplugged, or removed.
• Main power is fully disconnected from the controller only by unplugging all power cords from their power outlets. For
safety reasons, make sure the power outlets and plugs are within easy reach of the operator.
• Do not handle electrical cables that are not insulated. This includes any network cables.
• Keep water and other fluids away from the product.
• Comply with electrical grounding standards during all phases of installation and operation of the product. Do not allow
the controller chassis, network ports, power supplies, or mounting brackets to contact any device, cable, object, or
person attached to a different electrical ground. Also, never connect the device to external storm grounding sources.
• Installation or removal of the chassis or any module must be performed in a static-free environment. The proper use
of anti-static body straps and mats is strongly recommended.
• Keep modules in anti-static packaging when not installed in the chassis.
• Do not ship or store this product near strong electromagnetic, electrostatic, magnetic or radioactive fields.
• Do not disassemble chassis or modules. They have no internal user-serviceable parts. When service or repair is
needed, contact Aruba Networks.
Product Examination
The units are shipped to the Crypto Officer in factory-sealed boxes using trusted commercial carrier shipping companies.
The Crypto Officer should examine the carton for evidence of tampering. Tamper-evidence includes tears, scratches, and
other irregularities in the packaging.
Aruba 7XXX Series Controllers FIPS 140-2 Level 2 Security Policy|31
Package Contents
The product carton should include the following:
• 7XXX Controller
• Rack mounting kit (optional)
• Aruba User Documentation CD
• Tamper-Evident Labels
32| Aruba 7XXX Series Controllers FIPS 140-2 Level 2 Security Policy
Tamper-Evident Labels
After testing, the Crypto Officer must apply Tamper-Evident Labels (TELs) to the controller. When applied properly, the
TELs allow the Crypto Officer to detect the opening of the chassis cover, the removal or replacement of modules or cover
plates, or physical access to restricted ports. Vendor provides FIPS 140 designated TELs which have met the physical
security testing requirements for tamper evident labels under the FIPS 140-2 Standard. TELs are not endorsed by the
Cryptographic Module Validation Program (CMVP).
The tamper-evident labels shall be installed for the module to operate in a FIPS
Approved mode of operation.
Aruba Provides double the required amount of TELs. If a customer requires
replacement TELs, please call customer support and Aruba will provide the TELs
(Part # 4011570-01).
The Crypto officer shall be responsible for keeping the extra TELs at a safe location
and managing the use of the TELs.
Reading TELs
Once applied, the TELs included with the controller cannot be surreptitiously broken, removed, or reapplied without an
obvious change in appearance:
Figure 6 Tamper-Evident Labels
Each TEL also has a unique serial number to prevent replacement with similar labels.
Aruba 7XXX Series Controllers FIPS 140-2 Level 2 Security Policy|33
Required TEL Locations
The Aruba 7005 Mobility Controller requires a minimum of 4 TELs to be applied as follows:
To Detect Opening the Chassis Lid
• Spanning the front left side and right rear corners of the chassis lid where it meets the chassis bottom, as shown
in Figures 7 and 8 (Labels 1 & 2).
To Detect Access to Restricted Ports
• Two labels spanning the RJ-45 and mini-USB serial ports, as shown in figure 8. Press down on this label to
ensure that it adheres to a sufficient area of the front bezel. The RJ-45 port is raised relative to the bezel so there
will be some air gap under the label in this area. However, the air gap should not be larger than 2-3mm.
Figure 7 Required TELs for the Aruba 7005 Mobility Controller – Bottom
Figure 8 Required TELs for the Aruba 7005 Mobility Controller – Front
34| Aruba 7XXX Series Controllers FIPS 140-2 Level 2 Security Policy
The Aruba 7010 Mobility Controller requires a minimum of 6 TELs to be applied as follows:
To Detect Opening the Chassis Lid Top
• Spanning the front bezel and the chassis lid, as shown in Figure 9 (Label 1).
To Detect Opening the Chassis Lid Bottom
• Spanning the bottom and the chassis lid, as shown in Figures 10 and 11 (Labels 3, 4, 5 and 6).
To Detect Access to Restricted Ports
• One label (label 2) spanning the RJ-45 and mini-USB serial ports, as shown in Figure 10. Press down on this
label to ensure that it adheres to a sufficient area of the front bezel. The RJ-45 port is raised relative to the bezel
so there will be some air gap under the label in this area. However, the air gap should not be larger than 2-3mm.
Figure 9 Required TELs for the Aruba 7010 Mobility Controller – Top
Aruba 7XXX Series Controllers FIPS 140-2 Level 2 Security Policy|35
Figure 10 Required TELs for the Aruba 7010 Mobility Controller – Front
Figure 11 Required TELs for the Aruba 7010 Mobility Controller – Bottom
36| Aruba 7XXX Series Controllers FIPS 140-2 Level 2 Security Policy
The Aruba 7024 Mobility Controller requires a minimum of 7 TELs to be applied as follows:
To Detect Opening the Chassis Lid Top
• Spanning the front bezel and the chassis lid, as shown in Figures 12 and 13 (Label 1).
To Detect Opening the Chassis Lid Bottom
• Spanning the bottom and the chassis lid, as shown in Figure 13 (Labels 4, 5, 6 and 7).
To Detect Access to Restricted Ports
• One label (label 3) spanning the RJ-45 serial port and one spanning the mini-USB port (label 2) as shown in
Figure 14 and 15 (labels 2 & 3). Press down on this label to ensure that it adheres to a sufficient area of the front
bezel. The RJ-45 port is raised relative to the bezel so there will be some air gap under the label in this area.
However, the air gap should not be larger than 2-3mm.
Figure 12 Required TELs for the Aruba 7024 Mobility Controller - Front
Figure 13 Required TELs for the Aruba 7024 Mobility Controller – Top
Figure 14 Required TELs for the Aruba 7024 Mobility Controller – Rear
Aruba 7XXX Series Controllers FIPS 140-2 Level 2 Security Policy|37
Figure 15 Required TELs for the Aruba 7024 Mobility Controller – Bottom
The Aruba 7030 Mobility Controller requires a minimum of 6 TELs to be applied as follows:
To Detect Opening the Chassis Lid Top
• Spanning the front bezel and the chassis lid, as shown in Figures 16 & 17 (Label 1).
To Detect Opening the Chassis Lid Bottom
• Spanning the bottom and the chassis lid, as shown in Figures 16 and 18 (Labels 3, 4, 5 and 6).
To Detect Access to Restricted Ports
• One label (label 2) spanning the RJ-45 and mini-USB serial ports, as shown in figure 16 (Label 2). Press down
on this label to ensure that it adheres to a sufficient area of the front bezel. The RJ-45 port is raised relative to the
bezel so there will be some air gap under the label in this area. However, the air gap should not be larger than 2-
3mm.
38| Aruba 7XXX Series Controllers FIPS 140-2 Level 2 Security Policy
Figure 16 Required TELs for the Aruba 7030 Mobility Controller – Top
Figure 17 Required TELs for the Aruba 7030 Mobility Controller – Front
Aruba 7XXX Series Controllers FIPS 140-2 Level 2 Security Policy|39
Figure 18 Required TELs for the Aruba 7030 Mobility Controller – Bottom
The Aruba 7205 Mobility Controller requires a minimum of 6 TELs to be applied as follows:
To Detect Opening the Chassis Lid Top
• Spanning the front bezel and the chassis lid, as shown in Figure 19 (Label 1).
To Detect Opening the Chassis Lid Bottom
• Spanning the bottom and the chassis lid, as shown in Figures 19 and 21 (Labels 3, 4, 5 and 6).
To Detect Access to Restricted Ports
• One label (label 2) spanning the RJ-45 and mini-USB serial ports, as shown in Figure 20 (label 2). Press down
on this label to ensure that it adheres to a sufficient area of the front bezel. The RJ-45 port is raised relative to the
bezel so there will be some air gap under the label in this area. However, the air gap should not be larger than 2-
3mm.
40| Aruba 7XXX Series Controllers FIPS 140-2 Level 2 Security Policy
Figure 19 Required TELs for the Aruba 7205 Mobility Controller – Top
Figure 20 Required TELs for the Aruba 7205 Mobility Controller – Front
Figure 21 Required TELs for the Aruba 7205 Mobility Controller – Bottom
Aruba 7XXX Series Controllers FIPS 140-2 Level 2 Security Policy|41
Applying TELs
The Crypto Officer should employ TELs as follows:
• Before applying a TEL, make sure the target surfaces are clean and dry.
• Do not cut, trim, punch, or otherwise alter the TEL.
• Apply the wholly intact TEL firmly and completely to the target surfaces.
• Press down firmly across the entire label surface, making several back-and-forth passes to ensure that the label
securely adheres to the chassis.
• 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.
Once the TELs are applied, the Crypto Officer (CO) should perform initial setup and configuration as described in the next
chapter.
Ongoing Management
The Aruba 7XXX Controllers meet FIPS 140-2 Level 2 requirements. The information below describes how to keep the
controller in FIPS-approved mode of operation. The Crypto Officer must ensure that the controller is kept in a FIPS-
approved mode of operation.
Crypto Officer Management
The Crypto Officer must ensure that the controller is always operating in a FIPS-approved mode of operation. This can be
achieved by ensuring the following:
• FIPS mode must be enabled on the controller before Users are permitted to use the controller (see “Enabling FIPS
Mode” on page 37)
• The admin role must be root.
• Passwords must be at least eight characters long.
• VPN services can only be provided by IPsec or L2TP over IPsec.
• Access to the controller Web Interface is permitted only using HTTPS over a TLS tunnel. Basic HTTP and HTTPS
over SSL are not permitted.
• Only SNMP read-only may be enabled.
• Only FIPS-approved algorithms can be used for cryptographic services (such as HTTPS, L2, AES-CBC, SSH, and
IKEv1/IKEv2-IPSec), which include AES, Triple-DES, SHA-1, HMAC SHA-1, and RSA signature and verification.
• TFTP can only be used to load backup and restore files. These files are: Configuration files (system setup
configuration), the WMS database (radio network configuration), and log files. (FTP and TFTP over IPsec can be used
to transfer configuration files.)
• The controller logs must be monitored. If a strange activity is found, the Crypto Officer should take the controller off
line and investigate.
• The Tamper-Evident Labels (TELs) must be regularly examined for signs of tampering.
• When installing expansion or replacement modules for the Aruba 7200, use only FIPS-approved modules, replace
TELs affected by the change, and record the reason for the change, along with the new TEL locations and serial
numbers, in the security log.
• The Crypto Officer shall not configure the Diffie-Hellman algorithm with 768-bits (Group 1) in FIPS mode for
IKEv1/IKEv2-IPSec and SSHv2.
42| Aruba 7XXX Series Controllers FIPS 140-2 Level 2 Security Policy
User Guidance
The User accesses the controller VPN functionality as an IPsec client. The user can also access the controller 802.11i
functionality as an 802.11 client. Although outside the boundary of the controller, the User should be directed to be careful
not to provide authentication information and session keys to others parties.
Setup and Configuration
The Aruba 7XXX Controllers meet FIPS 140-2 Level 2 requirements. The sections below describe how to place and keep
the controller in FIPS-approved mode of operation. The Crypto Officer (CO) must ensure that the controller is kept in a
FIPS-approved mode of operation.
The controller can operate in two modes: the FIPS-approved mode, and the standard non-FIPS mode. By default, the
controller operates in non-FIPS mode.
Setting Up Your Controller
To set up your controller:
1. Make sure that the controller is not connected to any device on your network.
2. Boot up the controller.
3. Connect your PC or workstation to a line port on the controller.
For further details, see the ArubaOS 6.5 Quick Start Guide.
Enabling FIPS Mode
For FIPS compliance, users cannot be allowed to access the controller until the CO changes the mode of operation to
FIPS mode. There are two ways to enable FIPS mode:
• Use the WebUI
• Use the CLI
Enabling FIPS Mode with the WebUI
The IP address of the controller will be set during initial setup of the controller, as described in the ArubaOS 6.5 Quick
Start Guide. When you connect a PC or workstation to a line port on the controller, you can connect to this IP address
through a Web browser.
To log in with the WebUI:
1. Open a Web browser and connect to https://ip_address.
2. Log in using the username/password set during the initial setup procedure.
3. Go to the Configuration > Network > Controller > System Settings page (the default page when you click the
Configuration tab).
4. Click the FIPS Mode for Controller Enable checkbox.
Enabling FIPS Mode with the CLI
Login to the controller using an SSHv2 client. After entering the “enable” command and supplying the enable secret
(established during the initial setup procedure), enable FIPS mode using the following commands:
#configure terminal
Enter Configuration commands, one per line. End with CNTL/Z
(config) #fips enable
Aruba 7XXX Series Controllers FIPS 140-2 Level 2 Security Policy|43
(config) #exit
#write memory
Saving Configuration...
Configuration Saved.
To verify that FIPS mode has been enabled, issue the command “show fips”.
Disabling the LCD
Configuration through the front-panel LCD should be disabled. To disable the LCD screen, enter the Enable mode and
use the following CLI commands:
(host) #configure terminal
(host) (config) #lcd-menu
(host) (lcd-menu) #disable menu
Disallowed FIPS Mode Configurations
When you enable FIPS mode, the following configuration options are disallowed:
• All WEP features
• WPA
• TKIP mixed mode
• Any combination of DES, MD5, and PPTP
44| Aruba 7XXX Series Controllers FIPS 140-2 Level 2 Security Policy