Aruba Networks 3000 Series User manual

Dell W-3000, W-6000/M3 Series Controllers FIPS 140-2 Security Policy 1
Dell W-3000 and W-6000/M3 Mobility Controllers with Dell AOS
FIPS Firmware
Non-Proprietary Security Policy FIPS 140-2 Level 2
January 26, 2015
This is to advise that the document entitled “Aruba 3000 and 6000/M3 Mobility Controllers with
ArubaOS FIPS Firmware Non-Proprietary Security Policy FIPS 140-2 Level 2”Version 3.2, dated August
2014,applies to Dell W-3000 and W-6000/M3 Mobility Controllers with Dell AOS FIPS Firmware. Aruba
Networks is the Original Equipment Manufacturer (OEM) for the Dell Networking W-Series of products.
This document, provided below, is applicable for use by Dell W-Series customers for security policy
information and instruction on how to place and maintain the W-3000 and W-6000/M3 Mobility
Controllers in a secure FIPS 140-2 mode.
Dell Networking W-Series products are equivalent in features and functionality to the corresponding
Aruba Networks product models. Accordingly, the Dell AOS FIPS firmware is the validated ArubaOS FIPS
firmware version, with the exception of branding. When using the FIPS Security Policy document, the
screenshots, configurations, TEL placement locations, and images can be applied to Dell Networking W-
Series products without any need for changes.
Product Name Mapping:
Aruba Networks Model name
Dell Networking Model name
Description
Aruba 3200-F1
W-3200-F1
Non-US –32 AP Controller
Aruba 3200-USF1
W-3200-USF1
US –32 AP Controller
Aruba 3400-F1
W-3400-F1
Non-US –64 AP Controller
Aruba 3400-USF1
W-3400-USF1
US –64 AP Controller
Aruba 3600-F1
W-3600-F1
Non-US –128 AP Controller
Aruba 3600-USF1
W-3600-USF1
US –128 AP Controller
Aruba 6000-400-F1
W-6000-F1
Non-US –Controller Chassis
Aruba 6000-400-USF1
W-6000-USF1
US –Controller Chassis
M3mk1-S-F1
W-6000M3
M3 Controller Module for
Chassis
HW-PSU-200
HW-PSU-200
Power Supply (not re-branded)
HW-PSU-400
HW-PSU-400
Power Supply (not re-branded)
LC-2G-1
No Dell model
Ethernet Line card
LC-2G24F-1
No Dell model
Ethernet Line card
LC-2G24FP-1
No Dell model
Ethernet Line card
These models include Aruba FIPS kit 4010061-01 (contains tamper evident labels)
The exact firmware version validated was ArubaOS 6.3.1.7-FIPS
The Dell Networking W-Series products are rebranded for Dell customers, as shown in the product
images below.

Dell W-3000, W-6000/M3 Series Controllers FIPS 140-2 Security Policy 2
Dell Networking W-3000 Controller Series Product Images:
Aruba 3000 Controller Series Product Images:

Dell W-3000, W-6000/M3 Series Controllers FIPS 140-2 Security Policy 3
Dell Networking W-6000 Controller chassis with W-6000M3 module (1) and PSU (2):
Aruba 6000-400 controller chassis with M3 Mark I modules (4) and PSU (3):
If you have questions or concerns, please contact Dell Technical Support at www.dell.com/support,
additional product documentation is also available by device under user manuals.
Attachment: Aruba 3000 and 6000/M3 Mobility Controllers with ArubaOS FIPS Firmware Non-Proprietary
Security Policy FIPS 140-2 Level 2



Aruba 3000, 6000/M3 Mobility Controller FIPS 140-2 Level 2 Security Policy 

Aruba 3000 and 6000/M3 Mobility
Controllers
with ArubaOS FIPS Firmware
Non-Proprietary Security Policy
FIPS 140-2 Level 2
Version 3.2
August 2014

2|Aruba 3000, 6000/M3 Mobility Controller FIPS 140-2 Level 2 Security Policy
Copyright
© 2014 Aruba Networks, Inc. Aruba Networks trademarks include , Aruba Networks®, Aruba Wireless
Networks®, the registered Aruba the Mobile Edge Company logo, Aruba Mobility Management System®, Mobile Edge Architecture®,
People Move. Networks Must Follow®, RFprotectrotect®, Green Island®. All rights reserved. All other trademarks are the property of
their respective owners. Open Source Code
Certain Aruba products include Open Source software code developed by third parties, including software code subject to the GNU
General Public License (GPL), GNU Lesser General Public License (LGPL), or other Open Source Licenses. The Open Source code
used can be found at this site:
http://www.arubanetworks.com/open_source
Legal Notice
The use of Aruba Networks, Inc. switching platforms and software, by all individuals or corporations, to terminate other vendors’ VPN
client devices constitutes complete acceptance of liability by that individual or corporation for this action and indemnifies, in full, Aruba
Networks, Inc. from any and all legal actions that might be taken against it with respect to infringement of copyright on behalf of those
vendors.
Warranty
This hardware product is protected by the standard Aruba warranty of one year parts/labor. For more information, refer to the
ARUBACARE SERVICE AND SUPPORT TERMS AND CONDITIONS.
Altering this device (such as painting it) voids the warranty.
Copyright
© 2014 Aruba Networks, Inc. Aruba Networks trademarks include, Aruba Networks®, Aruba Wireless Networks®, the registered Aruba
the Mobile Edge Company logo, and Aruba Mobility Management System®.
www.arubanetworks.com
1344 Crossman Avenue
Sunnyvale, California 94089
Phone: [phone]
Fax [phone]

Aruba 3000, 6000/M3 Mobility Controller FIPS 140-2 Level 2 Security Policy|3
Contents

Contents.............................................................................................................................................................................3
Preface...............................................................................................................................................................................5
Purpose of this Document...............................................................................................................................................5
Related Documents.........................................................................................................................................................5
Additional Product Information ......................................................................................................................5
Overview............................................................................................................................................................................6
Cryptographic Module Boundaries................................................................................................................7
Aruba 6000....................................................................................................................................................7
Aruba 3000 Series.........................................................................................................................................9
Intended Level of Security............................................................................................................................................10
Physical Security............................................................................................................................................................11
Operational Environment..............................................................................................................................................11
Logical Interfaces...........................................................................................................................................................11
Roles and Services........................................................................................................................................................12
Crypto Officer Role......................................................................................................................................12
Authentication Mechanisms.........................................................................................................................17
Unauthenticated Services............................................................................................................................18
Non-Approved Services...............................................................................................................................18
Cryptographic Key Management.................................................................................................................................19
Implemented Algorithms..............................................................................................................................19
Non-FIPS Approved Algorithms Allowed in FIPS Mode..............................................................................20
Non-FIPS Approved Algorithms ..................................................................................................................20
Critical Security Parameters........................................................................................................................21
Self-Tests.........................................................................................................................................................................26
Alternating Bypass State...............................................................................................................................................27
InstallingtheController........................................................................................................................................................28
Pre-Installation Checklist...............................................................................................................................................28
Precautions.....................................................................................................................................................................28
Product Examination ...................................................................................................................................28
Package Contents.......................................................................................................................................29
Minimum Configuration for the Aruba 6000-400..........................................................................................29

4|Aruba 3000, 6000/M3 Mobility Controller FIPS 140-2 Level 2 Security Policy
Tamper-Evident Labels.................................................................................................................................................30
Reading TELs..............................................................................................................................................30
Required TEL Locations..............................................................................................................................31
To Detect Opening the Chassis Cover...............................................................................................................31
To Detect the Removal of Any Module or Cover Plate.....................................................................................31
To Detect Access to Restricted Ports.................................................................................................................31
To Detect Access to Restricted Port...................................................................................................................31
To Detect Opening the Chassis Cover...............................................................................................................32
Applying TELs .............................................................................................................................................32
OngoingManagement..........................................................................................................................................................32
Crypto Officer Management..........................................................................................................................................32
User Guidance................................................................................................................................................................33
Setup and Configuration................................................................................................................................................34
Setting Up Your Controller............................................................................................................................................34
Enabling FIPS Mode......................................................................................................................................................34
Enabling FIPS Mode with the WebUI..........................................................................................................34
Enabling FIPS Mode with the CLI................................................................................................................34
Disallowed FIPS Mode Configurations.......................................................................................................................35

Aruba 3000, 6000/M3 Mobility Controller FIPS 140-2 Level 2 Security Policy|5
Preface
Thissecuritypolicydocumentcanbecopiedanddistributedfreely.
Purpose of this Document
This release supplement provides information regarding the Aruba 3000 and 6000/M3 Mobility Controllers with FIPS 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 6000 Mobility Controller Installation Guide
Aruba 3000-series Mobility Controller Installation Guide
ArubaOS 6.3 User Guide
ArubaOS 6.3 CLI Reference Guide
ArubaOS 6.3 Quick Start Guide
ArubaOS 6.3 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

6|Aruba 3000, 6000/M3 Mobility Controller FIPS 140-2 Level 2 Security Policy
Overview
The Aruba 6000 and 3000 series Mobility Controllers are network infrastructure devices providing secure,
scalable solutions for enterprise Wi-Fi, network security policy enforcement, VPN services, and wireless
intrusion detection and prevention. Mobility controllers serve as central points of authentication,
encryption, access control, and network coordination for all mobile network services.
The controller configurations tested during the cryptographic module testing included:
Aruba 3200-F1
Aruba 3200-USF1
Aruba 3400-F1
Aruba 3400-USF1
Aruba 3600-F1
Aruba 3600-USF1
M3mk1-S-F1 (used in both Aruba 6000-400-F1 and Aruba-6000-400-USF1 chassis)
Aruba 6000-400-F1 and Aruba 6000-400-USF1 chassis (no more than four Aruba line cards,
including the combinations among M3mk1-S-F1, LC-2G-1, LC-2G24F-1, or LC-2G24FP-1, in a
single hardware configuration). Please note that the use of LC-2G-1, LC-2G24F-1 and LC-
2G24FP-1 is optional, but at least one M3mk1-S-F1 is required in a single hardware
configuration).
FIPS Kit
o4010061-01 (Part number for Tamper Evident Labels)
The exact firmware version validated was ArubaOS 6.3.1.7-FIPS
Note: For radio regulatory reasons, Aruba 3200-USF1, Aruba 3400-USF1, Aruba 3600-USF1 and Aruba
6000-400-USF1 are to be sold in the US only. Aruba 3200-F1, Aruba 3400-F1, Aruba 3600-F1 and
Aruba 6000-400-F1 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.

Aruba 3000, 6000/M3 Mobility Controller FIPS 140-2 Level 2 Security Policy|7
Physical Description
Cryptographic Module Boundaries
For FIPS 140-2 Level 2 validation, the Controller has been validated as a multi-chip standalone
cryptographic module. The steel chassis physically encloses the complete set of hardware and firmware
components and represents the cryptographic boundary of the controller. The cryptographic boundary is
defined as encompassing the top, front, left, right, rear, and bottom surfaces of the chassis.
Aruba 6000
Figure1‐TheAruba6000‐400controllerchassiswithM3MarkI
Figure 1shows the front of the Aruba 6000 controller chassis, and illustrates the following:
In each Aruba 6000-400-F1 or Aruba 6000-400-USF1 controller chassis:
One M3mk1-S-F1 card is required to be installed in slot 0.
Up to three Aruba line cards (the combination of LC-2G-1, LC-2G24F-1, LC-2G24FP-1, or
M3mk1-S-F1) can be installed in slots 1, 2 and 3 respectively
Table 1 below lists a detailed line cards configuration in a single Aruba 6000-400-F1 or Aruba 6000-400-
USF1 controller chassis.
Table1‐6000‐400‐F1or6000‐400‐USF1ControllerChassisConfigurations 
Slot 0 Slot 1 Slot 2 Slot 3
M3mk1-S-F1 x x x
M3mk1-S-F1 LC-2G-1 x x
M3mk1-S-F1 LC-2G-1 LC-2G-1 x

8|Aruba 3000, 6000/M3 Mobility Controller FIPS 140-2 Level 2 Security Policy
M3mk1-S-F1 LC-2G-1 LC-2G-1 LC-2G-1
M3mk1-S-F1 LC-2G-1 LC-2G24F-1 x
M3mk1-S-F1 LC-2G-1 LC-2G24F-1 LC-2G24F-1
M3mk1-S-F1 LC-2G-1 LC-2G24F-1 LC-2G24FP-1
M3mk1-S-F1 LC-2G-1 LC-2G24FP-1 x
M3mk1-S-F1 LC-2G-1 LC-2G24FP-1 LC-2G24FP-1
M3mk1-S-F1 LC-2G24F-1 x x
M3mk1-S-F1 LC-2G24F-1 LC-2G24F-1 x
M3mk1-S-F1 LC-2G24F-1 LC-2G24F-1 LC-2G24F-1
M3mk1-S-F1 LC-2G24F-1 LC-2G24F-1 LC-2G24FP-1
M3mk1-S-F1 LC-2G24F-1 LC-2G24FP-1 LC-2G24FP-1
M3mk1-S-F1 LC-2G24FP-1 x x
M3mk1-S-F1 LC-2G24FP-1 LC-2G24FP-1 x
M3mk1-S-F1 LC-2G24FP-1 LC-2G24FP-1 LC-2G24FP-1
M3mk1-S-F1 M3mk1-S-F1 x x
M3mk1-S-F1 M3mk1-S-F1 LC-2G-1 x
M3mk1-S-F1 M3mk1-S-F1 LC-2G-1 LC-2G-1
M3mk1-S-F1 M3mk1-S-F1 LC-2G-1 LC-2G24F-1
M3mk1-S-F1 M3mk1-S-F1 LC-2G-1 LC-2G24FP-1
M3mk1-S-F1 M3mk1-S-F1 LC-2G24F-1 x
M3mk1-S-F1 M3mk1-S-F1 LC-2G24F-1 LC-2G24F-1
M3mk1-S-F1 M3mk1-S-F1 LC-2G24F-1 LC-2G24FP-1
M3mk1-S-F1 M3mk1-S-F1 LC-2G24FP-1 x
M3mk1-S-F1 M3mk1-S-F1 LC-2G24FP-1 LC-2G24FP-1
M3mk1-S-F1 M3mk1-S-F1 M3mk1-S-F1 x
M3mk1-S-F1 M3mk1-S-F1 M3mk1-S-F1 LC-2G-1
M3mk1-S-F1 M3mk1-S-F1 M3mk1-S-F1 LC-2G24F-1

Aruba 3000, 6000/M3 Mobility Controller FIPS 140-2 Level 2 Security Policy|9
M3mk1-S-F1 M3mk1-S-F1 M3mk1-S-F1 LC-2G24FP-1
M3mk1-S-F1 M3mk1-S-F1 M3mk1-S-F1 M3mk1-S-F1
An”x” represents an empty slot.
Status indicator LEDs indicate power state, status of the device, and link activity.
PS1, PS2, and PS3 are for Power Supply modules. The number of power supplies required for the
system depends on the number of Line Cards installed, and whether to include redundancy for fault
tolerance (please refer to the Aruba 6000 Mobility Controller Installation Guide). It is Crypto Officer’s
responsibility to install the power supplies. The two available power supplies are:
200 W Power Supply (HW-PSU-200)
400 W Power Supply (HW-PSU-400)
When using more than one power supply, verify that they are all of the same type. Do not mix 200 W
and 400 W power supplies in the same chassis.

Aruba 3000 Series
The Aruba 3000-series Controller chassis is a 1U non-modular chassis.
Figure2‐Aruba3000‐seriesControllerChassis
Figure 2 shows the front of the Aruba 3000-series Controller, and illustrates the following:
System indicator LEDs indicate power state and status of the device.
Four Gigabit Ethernet ports provide network connectivity.
Optional 1000Base-X fiber optic ports provide network connectivity.
Serial Console port is for connecting to a local management console.

10|Aruba 3000, 6000/M3 Mobility Controller FIPS 140-2 Level 2 Security Policy
Intended Level of Security
The Aruba 3000 and 6000/M3 Controllers and associated modules are intended to meet overall FIPS
140-2 Level 2 requirements as shown in Table2.
Table2‐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
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

Aruba 3000, 6000/M3 Mobility Controller FIPS 140-2 Level 2 Security Policy|11
Physical Security
The Aruba Controller is a scalable, multi-processor standalone network device and is enclosed in a robust
steel housing. The switch enclosure is resistant to probing and is opaque within the visible spectrum. The
enclosure of the switch has been designed to satisfy FIPS 140-2 Level 2 physical security requirements.
For the Aruba 6000-400 the left, top, right, and bottom surfaces are irremovable. The rear panel can be
removed by unscrewing fifteen screws. The switch has a number of components at front side, including
four slots for supervisor and line cards, one fan tray, and three power supplies. Each of the components
is attached with two screws.
For the Aruba 3000-series the left, right, front, rear, and bottom surfaces are irremovable. The top panel
can be removed by unscrewing two screws. A metallic opaque shield is installed at the factory during
manufacturing and cannot be removed by the User.
For physical security, the Aruba 6000-400 chassis requires Tamper-Evident Labels (TELs) to allow the
detection of the opening of the chassis covers; the removal or replacement of any module or cover plate,
and to block the Serial console port.
The Aruba 3000-series Controllers require 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 3000 and 6000/M3 Controllers from any tampering with the product, TELs should be
applied by the Crypto Officer as covered under “Tamper-Evident Labels” in this document.

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.

Logical Interfaces
All of these physical interfaces are separated into logical interfaces defined by FIPS 140-2, as described
in the following table.
Table3‐FIPS140‐2LogicalInterfaces
FIPS 140-2 Logical Interface Module Physical Interface
Data Input Interface 10/100 Mbps Ethernet port
10/100/1000 Mbps Ethernet ports
Data Output Interface 10/100 Mbps Ethernet port
10/100/1000 Mbps Ethernet ports

12|Aruba 3000, 6000/M3 Mobility Controller FIPS 140-2 Level 2 Security Policy
Table3‐FIPS140‐2LogicalInterfaces
Control Input Interface Power switch (Aruba 6000 only)
Reset button (Aruba 6000 only)
10/100 Mbps Ethernet port
10/100/1000 Mbps Ethernet ports
Serial console port (disabled)
Status Output Interface 10/100 Mbps Ethernet port
10/100/1000 Mbps Ethernet ports
LEDs
Serial console port (disabled)
Power Interface Power Supply
POE (Aruba 6000 only)
Data input and output, control input, status output, and power interfaces are defined as follows:
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. Operating power is also provided (Aruba
6000 only) to a compatible Power Over Ethernet (POE) device when connected. The power is
provided through the connected Ethernet 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.

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

Aruba 3000, 6000/M3 Mobility Controller FIPS 140-2 Level 2 Security Policy|13
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.
SNMP v3
The Crypto Officer can also use SNMPv3 to remotely perform non-security-sensitive monitoring using
the ‘get’ and ‘getnext’ commands.
See the table below for descriptions of the services available to the Crypto Officer role.
Table4‐Crypto‐OfficerServices
Service Description Input Output CSP Access
SSH v2.0 Provide authenticated and
encrypted remote management
sessions while using the CLI
SSHv2 key agreement
parameters, SSH
inputs, and data
SSHv2 outputs and
data 6, 16 (read)
8, 9, 24, 25
(read/write)
SNMPv3 Provides ability to query
management information SNMPv3 requests SNMPv3
responses 34, 35 (read)
36 (read/write)
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
29, 30, 31, 32 (read)
8, 9, 10, 11, 12, 13
(read/write)
17 (read)
18, 19, 20, 21, 22, 23
(read/write)
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
36, 37 (read/write)

14|Aruba 3000, 6000/M3 Mobility Controller FIPS 140-2 Level 2 Security Policy
Table4‐Crypto‐OfficerServices
Configuring
Module Platform Define the platform subsystem firmware of the module by
entering Bootrom Monitor Mode,
File System, fault report,
message logging, and other
platform related commands
Commands and
configuration data Status of commands and
configuration data
None
Configuring
Hardware
Controllers
Define synchronization features
for module Commands and configuration data Status of commands and
configuration data
None
Configuring
Internet Protocol Set IP 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
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/write)
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
14, 15, 16
(read/write)
Manage
Certificates Install, rename, and delete X.509 certificates Commands and configuration data;
Certificates and keys
Status of
certificates,
commands, and
configuration
29, 30, 31, 32
(read/write)
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, 31, 32 (read)
26, 27, 28
(read/write)

Aruba 3000, 6000/M3 Mobility Controller FIPS 140-2 Level 2 Security Policy|15
Table4‐Crypto‐OfficerServices
Status Function Cryptographic officer may use
CLI "show" commands or view
WebUI via TLS to view the
controller configuration, routing
tables, and active sessions; view
health, temperature, memory
status, voltage, and packet
statistics; review accounting logs,
and view physical interface status
Commands and
configuration data Status of commands and
configurations
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
29, 30, 31, 32 (read)
8, 9, 10, 11, 12, 13
(read/write)
17 (read)
18, 19, 20, 21, 22, 23
(read/write)
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 29, 30, 31, 32 (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
29, 30, 31, 32 (read)
8, 9, 10, 11, 12, 13
(read/write)
17 (read)
18, 19, 20, 21, 22, 23
(read/write)

16|Aruba 3000, 6000/M3 Mobility Controller FIPS 140-2 Level 2 Security Policy
Table4‐Crypto‐OfficerServices
Zeroization Zeroizes all flash memory Command Progress
information All CSPs will be destroyed.
User Role
The User role can access the controller’s IPSec and IKEv1/IKEv2 services. Service descriptions and
inputs/outputs are listed in the following table:
Table5‐UserService
Service Description Input Output CSP Access
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 29, 30, 31, 32 (read)
8, 9, 10, 11, 12, 13
(read/write)
17 (read)
18, 19, 20, 21, 22, 23
(read/write)
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, 32 (read)
26, 27, 28 (read/write)
EAP-TLS
termination Provide EAP-TLS termination EAP-TLS inputs,
commands and data EAP-TLS outputs, status and data 29, 30, 31, 32 (read)
26, 27, 28 (read/write)
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 33 (read)
35 (read/write)

Aruba 3000, 6000/M3 Mobility Controller FIPS 140-2 Level 2 Security Policy|17
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 29, 30, 31, 32 (read)
34, 35 (read/write)
Self-Tests Run Power-On Self-Tests and
Conditional Tests None Error messages logged if a failure
occurs
None
Authentication Mechanisms
The Aruba Controller supports role-based authentication. 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6‐EstimatedStrengthofAuthenticationMechanisms
Authentication Type Role Strength
Password-based authentication
(CLI and Web Interface) 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 (6) 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 X6 X5 x 32 x 52 = 251,596,800). Therefore, the associated
probability of a successful random attempt is approximately 1 in 8,
386, 560, which is less than 1 in 1,000,000 required by FIPS 140-2.
RSA-based authentication
(IKEv1/IKEv2) User When using RSA based authentication, RSA key pair has modulus
size of 2048 bits, thus providing 112 bits of strength. 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.