1 | INTRODUCTION | 5 | |||
| 1.1 | ARUBA DELL RELATIONSHIP | 5 | ||
| 1.2 | ACRONYMS AND ABBREVIATIONS | 5 | ||
2 | PRODUCT OVERVIEW | 7 | |||
| 2.1 | ARUBA | 7 | ||
| 2.1.1 | Physical Description | 7 | ||
|
| 2.1.1.1 | Dimensions/Weight | 8 | |
|
| 2.1.1.2 | Interfaces | 8 | |
|
| 2.1.1.3 | Indicator LEDs | 8 | |
3 | MODULE OBJECTIVES | 10 | |||
| 3.1 | SECURITY LEVELS | 10 | ||
| 3.2 | PHYSICAL SECURITY | 10 | ||
| 3.2.1 | Applying TELs | 10 | ||
| 3.2.2 Aruba | 11 | |||
|
| 3.2.2.1 To detect opening of the chassis cover: | 11 | ||
|
| 3.2.2.2 To detect access to restricted ports | 11 | ||
| 3.2.3 Aruba | 13 | |||
|
| 3.2.3.1 To detect opening of the chassis cover: | 13 | ||
|
| 3.2.3.2 To detect access to restricted ports | 13 | ||
| 3.2.4 Inspection/Testing of Physical Security Mechanisms | 16 | |||
| 3.3 | MODES OF OPERATION | 17 | ||
| 3.3.1 Configuring Remote AP FIPS Mode | 17 | |||
| 3.3.2 Configuring Control Plane Security (CPSec) protected AP FIPS mode | 18 | |||
| 3.3.3 Configuring Remote Mesh Portal FIPS Mode | 19 | |||
| 3.3.4 Configuring Remote Mesh Point FIPS Mode | 20 | |||
| 3.3.5 Verify that the module is in FIPS mode | 21 | |||
| 3.4 | OPERATIONAL ENVIRONMENT | 21 | ||
| 3.5 | LOGICAL INTERFACES | 22 | ||
4 ROLES, AUTHENTICATION, AND SERVICES | 23 | ||||
| 4.1 | ROLES | ............................................................................................................................................... | 23 | |
| 4.1.1 | Crypto Officer Authentication | 23 | ||
| 4.1.2 | User Authentication | 24 | ||
| 4.1.3 | Wireless Client Authentication | 24 | ||
| 4.1.4 Strength of Authentication Mechanisms | 24 | |||
| 4.2 | SERVICES | 26 | ||
| 4.2.1 | Crypto Officer Services | 26 |