Aruba OpenSSL Module

Certificate

Approved Algorithms (36)

Derived Review-Risk Graph (review prompts, not findings)

flowchart LR
  %% Deterministic review-risk graph for Aruba OpenSSL Module
  %% Review prompts and evidence gaps, NOT vulnerability findings.
  subgraph CMVP["CMVP-disclosed clues"]
    C2["[low] Firmware update / recovery<br/>/ rollback (referenced in<br/>text)<br/><i>upgrade</i>"]
    C3["[low] Self-test / status surface<br/>(referenced in text)<br/><i>Status Output<br/>Self-Test</i>"]
    C5["[low] Protocol / secure-channel<br/>references (may be KDF<br/>names, not a live channel)<br/><i>TLS<br/>SSH<br/>IKEV</i>"]
    C6["[low] Operating system / runtime<br/>referenced (boundary<br/>membership not asserted)<br/><i>operating system<br/>linux<br/>application</i>"]
  end
  subgraph Inference["Derived inference"]
    I2["Possible only, trusted<br/>code is reachable through<br/>update and recovery paths."]
    I3["Possible only, some<br/>services may process input<br/>before, or without,<br/>operator authentication."]
    I5["Possible only, a protocol<br/>is referenced, but whether<br/>it is a live channel or<br/>only a KDF/algorithm name<br/>is unconfirmed."]
    I6["Possible only, a<br/>runtime/OS is referenced,<br/>but its membership in the<br/>cryptographic boundary is<br/>not established."]
  end
  subgraph Risk["Reviewer question"]
    R2["Are update images<br/>authenticated before<br/>parsing, and are<br/>downgrade/rollback paths<br/>constrained?"]
    R3["Can unauthenticated<br/>services leak state,<br/>consume resources, or<br/>transition security state?"]
    R5["If a live TLS/SSH/IKE<br/>channel exists, could<br/>library CVEs apply, or is<br/>this only a<br/>KDF/documentation name?"]
    R6["If the OS/runtime is<br/>in-boundary, could its<br/>CVEs be hidden by<br/>firmware-only versioning?"]
  end
  subgraph Evidence["Evidence needed to close"]
    E2["confirm the disclosure<br/>itself (keyword hit,<br/>context unverified) ·<br/>update image format ·<br/>signature-before-parse<br/>proof · anti-rollback /<br/>downgrade policy"]
    E3["confirm the disclosure<br/>itself (keyword hit,<br/>context unverified) ·<br/>pre-auth reachability<br/>matrix · rate limits and<br/>output redaction ·<br/>abuse-case tests"]
    E5["confirm the disclosure<br/>itself (keyword hit,<br/>context unverified) ·<br/>library identity and<br/>version ·<br/>certificate-validation<br/>behaviour · protocol-CVE<br/>disposition"]
    E6["confirm the disclosure<br/>itself (keyword hit,<br/>context unverified) ·<br/>runtime identity and<br/>config · kernel/runtime<br/>hardening profile ·<br/>patch/backport manifest"]
  end
  C2 --> I2 --> R2 --> E2
  C3 --> I3 --> R3 --> E3
  C5 --> I5 --> R5 --> E5
  C6 --> I6 --> R6 --> E6
  classDef clue fill:#eef3f9,stroke:#6f7f91,color:#1f3a5f;
  classDef infer fill:#fff7e6,stroke:#b98500,color:#6b4e00;
  classDef risk fill:#fbe9e9,stroke:#b02a2a,color:#7a1f1f;
  classDef evidence fill:#e6f4ea,stroke:#1e7d34,color:#14532d;
  class C2,C3,C5,C6 clue;
  class I2,I3,I5,I6 infer;
  class R2,R3,R5,R6 risk;
  class E2,E3,E5,E6 evidence;

flowchart LR
  %% Deterministic clue tier for Aruba OpenSSL Module
  %% confidence: high = structured record field; medium = structured but soft; low (dashed) = bare keyword hit, context unverified
  subgraph CMVP["CMVP-disclosed clues (deterministic)"]
    C2["[low] Firmware update / recovery / rollback (referenced in text)<br/><i>upgrade</i><br/>src: text:keyword"]
    C3["[low] Self-test / status surface (referenced in text)<br/><i>Status Output<br/>Self-Test</i><br/>src: text:keyword"]
    C5["[low] Protocol / secure-channel references (may be KDF names, not a live channel)<br/><i>TLS<br/>SSH<br/>IKEV</i><br/>src: text:keyword"]
    C6["[low] Operating system / runtime referenced (boundary membership not asserted)<br/><i>operating system<br/>linux<br/>application</i><br/>src: text:keyword"]
  end
  classDef clueHigh fill:#eef3f9,stroke:#2f6fb0,stroke-width:2px,color:#1f3a5f;
  classDef clueMedium fill:#eef3f9,stroke:#6f7f91,color:#1f3a5f;
  classDef clueLow fill:#f7f7f7,stroke:#999,stroke-dasharray:4 4,color:#444;
  class C2,C3,C5,C6 clueLow;

Security Policy, page by page

Non-Proprietary Aruba OpenSSL Module Firmware Version 1.0 FIPS 140-3 Level 1 Document Version 1.0 November 2024 1| Hewlett Packard Enterprise Aruba OpenSSL Module Firmware Version 1.0 FIPS 140-3 Level 1 Security Policy

Non-Proprietary © 2024 Hewlett Packard Enterprise Company. Hewlett Packard Enterprise Company trademarks include , HPE Networks®, HPE Wireless Networks®, HPE Networking, the registered HPE Networking the Mobile Edge Company logo, HPE Networking Mobility Management System®, Mobile Edge Architecture®, property of their respective owners. HPE Networking is a Hewlett Packard Enterprise company. The resource assets in this firmware may include abbreviated and/or legacy terminology for HPE Networking products. See https://www.hpe.com/us/en/networking/ for current and complete HPE Networking product lines and names. 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: https://myenterpriselicense.hpe.com/cwp-ui/software Legal Notice The use of Hewlett Packard Enterprise Company switching platforms and software or firmware, 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, Hewlett Packard Enterprise Company, from vendors. https://www.hpe.com/us/en/networking/

Spring, TX, USA 77389 Phone: 1-888-342-2156 2| Hewlett Packard Enterprise Aruba OpenSSL Module Firmware Version 1.0 FIPS 140-3 Level 1 Security Policy

11.1.1 Setting Up the Hewlett Packard Enterprise Controller, Gateway, Conductor, or Controller-managed

Figures 3| Hewlett Packard Enterprise Aruba OpenSSL Module Firmware Version 1.0 FIPS 140-3 Level 1 Security Policy

Non-Proprietary Tables Preface notice. Products identified herein contain confidential commercial firmware. Valid license required. Document Revision History The following table lists the history of the revisions of this document by version number and date of revision. Table 1 – Document Revision History

This section describes:

• The purpose of this document.
• Hewlett Packard Enterprise documents related to this document contents.
• Where to go for additional Hewlett Packard Enterprise product information.
• Acronyms and abbreviations.
• The assurance security levels for each of the areas described in the FIPS 140-3 Standard.

This release supplement provides information regarding the Hewlett Packard Enterprise Aruba OpenSSL Module firmware version 1.0 FIPS 140-3 Level 1 validation from Hewlett Packard Enterprise (HPE). Throughout this document, references to HPE Networking are to the Hewlett Packard Enterprise division. The material in this supplement modifies the general Hewlett Packard Enterprise firmware documentation included with this product and should be kept with your Hewlett Packard Enterprise product documentation. This supplement primarily covers the non-proprietary Cryptographic Module Security Policy for the Hewlett Packard Enterprise Aruba OpenSSL Module firmware version 1.0. This security policy describes how the module meets the security requirements of FIPS 140-3 Level 1 and how to place and maintain the module in the secure Approved mode. This policy was prepared as part of the FIPS 140-3 Level 1 validation of the product. FIPS 140-3 (Federal Information Processing Standards Publication 140-3, Security Requirements for Cryptographic Modules) details the U.S. Government requirements for cryptographic modules. FIPS 140-3 aligns with ISO/IEC 19790:2012(E) and includes modifications of the Annexes that are allowed to the Cryptographic Module Validation Program (CMVP), as a validation authority. The testing for these requirements will be in accordance with ISO/IEC 24759:2017(E), with the modifications, additions or deletions of vendor evidence and testing allowed as a validation authority under paragraph 5.2. More information about the FIPS 140-3 standard and validation program is available on the National Institute of Standards and Technology (NIST) website at: https://csrc.nist.gov/projects/cryptographic-module-validation-program In addition, in this document, the Hewlett Packard Enterprise Aruba OpenSSL Module is referred to as the module, the cryptographic module, and Aruba OpenSSL module.

More information is available from the following sources:

• See the Hewlett Packard Enterprise web site for the full line of products from HPE Networking: https://www.hpe.com/us/en/networking/
• The NIST Validated Modules web site contains contact information for answers to technical or sales-related questions for the product: https://csrc.nist.gov/projects/cryptographic-module-validation-program/validated-modules/search Enter Hewlett Packard Enterprise in the Vendor field then select Search to see a list of FIPS validated Hewlett Packard Enterprise cryptographic modules. Select the Certificate Number for the Module Name ‘Aruba OpenSSL Module’. 5| Hewlett Packard Enterprise Aruba OpenSSL Module Firmware Version 1.0 FIPS 140-3 Level 1 Security Policy

AES            Advanced Encryption Standard AP             Access Point CAVP           Cryptographic Algorithm Validation Program CBC            Cipher Block Chaining CCCS           Canadian Centre for Cyber Security, a branch of CSE CLI            Command Line Interface CMVP           Cryptographic Module Validation Program CO             Crypto Officer CPSec          Control Plane Security protected CSE            Communications Security Establishment CSP            Critical Security Parameter DF             Derivation Function EAP            Extensible Authentication Protocol ECO            External Crypto Officer EMC            Electromagnetic Compatibility EMI            Electromagnetic Interference ESV            Entropy Source Validation FE             Fast Ethernet GE             Gigabit Ethernet GHz            Gigahertz HMAC           Hashed Message Authentication Code Hz             Hertz IKE            Internet Key Exchange IPsec          Internet Protocol security KAT            Known Answer Test KEK            Key Encryption Key L2TP           Layer-2 Tunnelling Protocol LAN            Local Area Network LED            Light Emitting Diode NTP            Network Time Protocol OCSP           Online Certificate Status Protocol PCT            Pairwise Consistency Test PSP            Public Security Parameter SFTP           Secure File Transfer Protocol SHA            Secure Hash Algorithm SNMP           Simple Network Management Protocol SSP            Sensitive Security Parameter SPOE           Serial & Power Over Ethernet TEL            Tamper-Evident Label TFTP           Trivial File Transfer Protocol TPM            Trusted Platform Module WLAN           Wireless Local Area Network 6|    Hewlett Packard Enterprise Aruba OpenSSL Module Firmware Version 1.0 FIPS 140-3 Level 1 Security Policy

The Hewlett Packard Enterprise Aruba OpenSSL Module is intended to meet overall FIPS 140-3 Level 1 requirements as shown in the following table. Table 2 – Security Levels 7| Hewlett Packard Enterprise Aruba OpenSSL Module Firmware Version 1.0 FIPS 140-3 Level 1 Security Policy

Purpose and Use: The Hewlett Packard Enterprise Aruba OpenSSL Module version 1.0 (also referred to as ‘the module’) is a firmware type cryptographic module that was validated under FIPS 140-3 Level 1 requirements and meets the claims made in this document. ArubaOS is the operating system for Hewlett Packard Enterprise Mobility Conductors, Mobility Controllers/Gateways, and controller-managed Hewlett Packard Enterprise Access Points (APs). The Hewlett Packard Enterprise Aruba OpenSSL Module (firmware) is an Hewlett Packard Enterprise cryptographic module that provides cryptographic services for the ArubaOS operating system running on the Hewlett Packard Enterprise hardware-based equipment or Hewlett Packard Enterprise virtual appliances. Module Type: Firmware Module Embodiment: Multiple-chip Standalone

The Hewlett Packard Enterprise Aruba OpenSSL Module (firmware) is an Hewlett Packard Enterprise cryptographic module that provides cryptographic services for the ArubaOS operating system. The cryptographic boundary for the Hewlett Packard Enterprise Aruba OpenSSL Module is defined as the module component within the Linux-based User Space. The physical perimeter is the productiongrade enclosure of the hardware chassis of the Hewlett Packard Enterprise hardware device or Hewlett Packard Enterprise virtual appliance host. The module is one of the components within the ArubaOS firmware package in electronic form and is installed automatically when a trusted and verified ArubaOS is booted on an Hewlett Packard Enterprise device. The Hewlett Packard Enterprise Aruba OpenSSL Module component includes the module shared libraries and the associated integrity check files (used for integrity tests):

• libcrypto.so.1.0.2s
• libcrypto.so.1.0.2s.hmac
• libssl.so.1.0.2s
• libssl.so.1.0.2s.hmac Figure 1
• Functional Block Diagram of Cryptographic Boundary for Aruba OpenSSL Module 8| Hewlett Packard Enterprise Aruba OpenSSL Module Firmware Version 1.0 FIPS 140-3 Level 1 Security Policy

The Hewlett Packard Enterprise Aruba OpenSSL Module (firmware) version 1.0 was validated against FIPS 140-3 Level 1 requirements. The CMVP makes no claim as to the correct operation of the module or the security strengths of the generated keys when operating under a version that is not listed on the validation certificate. Table 3 – Version Information

The module operates in a limited operational environment. The module runs on the ArubaOS operating system and related hardware or virtual platform and provides cryptographic services for the ArubaOS operating system. See the following tables of Tested Operational Environments and Vendor Affirmed Operational Environments for details. Table 4 – Tested Operational Environments 9| Hewlett Packard Enterprise Aruba OpenSSL Module Firmware Version 1.0 FIPS 140-3 Level 1 Security Policy

Non-Proprietary Table 5 – Vender Affirmed Operational Environments

There are no excluded components for the module.

The Hewlett Packard Enterprise Aruba OpenSSL Module (firmware) is one of the Hewlett Packard Enterprise cryptographic modules that provide cryptographic services for the host ArubaOS operating system, and is installed automatically when a trusted and verified ArubaOS is booted on an Hewlett Packard Enterprise host device.

When the module starts up successfully, after passing all the Cryptographic Algorithm Self-Tests (CASTs) and Pre-Operational Self-Tests (POSTs), and following the guidance in section 11.1, Start-up Procedures, the module is operating in the Approved mode of operation, provided that the guidelines on services, algorithms, and key management found in this Security Policy are followed.

When the module starts up but FIPS Settings are not enabled as per the guidance in section 11.1, Start-up Procedures, then the module is operating in non-Approved mode of operation. 10| Hewlett Packard Enterprise Aruba OpenSSL Module Firmware Version 1.0 FIPS 140-3 Level 1 Security Policy

The firmware in the Hewlett Packard Enterprise Aruba OpenSSL Module contains the following cryptographic algorithm implementations that will be used for the corresponding security services supported by the module in the Approved mode. Table 6 – Approved Algorithms Vendor Affirmed algorithms are approved by the CMVP but CAVP testing is not yet available. Resulting symmetric keys and seeds used for asymmetric key generation are unmodified output from SP 800-90A This KDF is used in the Approved IKEv1, HTTP over TLS, EAP-TLS, SSH and SNMP services. No parts of the IKEv1, TLS, SSH and SNMP protocols, other than the KDF, have been reviewed or tested by the CAVP and CMVP. This KDF is used in the Approved HTTP over TLS and EAP-TLS services. No parts of the TLS protocols, other than the KDF, have been reviewed or tested by the CAVP and CMVP. Refer to section 9.1, Non-Deterministic Random Number Generation Specification for entropy source details. DSA was CAVP tested but is only used as a pre-requisite for DH. 11| Hewlett Packard Enterprise Aruba OpenSSL Module Firmware Version 1.0 FIPS 140-3 Level 1 Security Policy

Non-Proprietary AES-GCM is an authenticated encryption algorithm that is approved for use in key transport per FIPS 140-3 IG D.G. This key establishment methodology provides 128 or 256 bits of encryption strength. AES-CBC combined with HMAC is approved for use in key transport per FIPS 140-3 IG D.G. This key establishment methodology provides between 128 and 256 bits of encryption strength. 12| Hewlett Packard Enterprise Aruba OpenSSL Module Firmware Version 1.0 FIPS 140-3 Level 1 Security Policy

2.7 Non-Approved Cryptographic Algorithms Allowed in the Approved Mode of Operation

The cryptographic module implements no non-Approved algorithms allowed for use in the Approved The cryptographic module implements the following non-Approved algorithms allowed in the Approved

2.9 Non-Approved Algorithms Not Allowed in the Approved Mode of Operation

The cryptographic module implements the following non-Approved algorithms that are not permitted Table 8 – Non-Approved Algorithms Not Allowed in the Approved Mode of Operation 13| Hewlett Packard Enterprise Aruba OpenSSL Module Firmware Version 1.0 FIPS 140-3 Level 1 Security Policy

As a firmware module, the module interfaces are defined as Software or Firmware Module Interfaces (SFMI), and there are no physical ports. The logical interfaces are defined as the API of the cryptographic module. The interfaces are listed in the table below. All data output via data output interface is inhibited when the module is performing pre-operational tests or zeroization or when the module enters error state. Table 9

• Ports and Interfaces Notes:
• Module API return codes to calling application: 1 = success, 0 = failure.

The following section lists the roles supported by the module, authentication mechanisms used by the module, and services (both security and non-security, Approved and non-Approved) available from the module. The Hewlett Packard Enterprise Aruba OpenSSL Module does not provide any identification or authentication methods of its own. The CO and the User roles are implicitly identified by the service requested.

The module supports two distinct operator roles: the Crypto Officer role and the User role. These roles are implicitly assumed by the operator of the module when performing a service. The module does not support multiple concurrent operators, a maintenance role, nor bypass capability. Table 10 – Roles and Authentication 14| Hewlett Packard Enterprise Aruba OpenSSL Module Firmware Version 1.0 FIPS 140-3 Level 1 Security Policy

Non-Proprietary The table below lists descriptions of the services available to the roles, with input and output. Table 11 – Roles, Service Commands, Input, Output Note: The Crypto Officer must ensure that the module is kept in the Approved mode of operation, following the guidance in section 11.1, Start-up Procedures, and provided that the guidelines on services, algorithms, and key management found in this Security Policy are followed. 15| Hewlett Packard Enterprise Aruba OpenSSL Module Firmware Version 1.0 FIPS 140-3 Level 1 Security Policy

The module provides various services depending on role. These are described in the sections below. The meaning of the letters used to describe the ‘Access Rights to Keys and/or SSPs’ are: •    G – Generate         The module generates or derives the Key/SSP. •    R – Read             The Key/SSP is read from the module (e.g. the Key/SSP is output). •    W – Write            The Key/SSP is updated, imported, or written to the module. •    E – Execute          The module uses the Key/SSP in performing a cryptographic operation. •    Z – Zeroize          The module zeroizes the Key/SSP.

See the tables below for descriptions of the services, Approved security functions, keys and/or SSPs available to the module’s roles. The Hewlett Packard Enterprise Aruba OpenSSL Module is one of the components within the ArubaOS firmware package which runs on the host device. ArubaOS includes CLI commands, some of which interact with the module via APIs. Successful completion of a security service (via API return code for success) when the module is in Approved mode (see section 11.1, Start-up Procedures) denotes use of approved security W/E 16| Hewlett Packard Enterprise Aruba OpenSSL Module Firmware Version 1.0 FIPS 140-3 Level 1 Security Policy

Non-Proprietary 17| Hewlett Packard Enterprise Aruba OpenSSL Module Firmware Version 1.0 FIPS 140-3 Level 1 Security Policy

Non-Proprietary Table 13 – Approved Services Not Using Any Approved Security Functions 18| Hewlett Packard Enterprise Aruba OpenSSL Module Firmware Version 1.0 FIPS 140-3 Level 1 Security Policy

Zeroization

The cryptographic keys stored in SDRAM memory can be zeroized by rebooting the module. The cryptographic keys (IKE Pre-shared key and RSA/ECDSA Private/Public keys) stored in the host flash can be zeroized by using the ArubaOS command ‘wipe out flash’ on the host or by overwriting with a new secret. Please see ArubaOS CLI guide for details.

None

All SSPs will be destroyed.

Crypto Officer

Z

API return code for success

Non-Proprietary Note: • Log message displayed each time RSA-based key transport using RSA PKCS#1-1.5 is executed: Please ensure a FIPS 140-3 compliant transport scheme is configured 19| Hewlett Packard Enterprise Aruba OpenSSL Module Firmware Version 1.0 FIPS 140-3 Level 1 Security Policy

The Hewlett Packard Enterprise Aruba OpenSSL Module (firmware version 1.0) is an Hewlett Packard Enterprise cryptographic module that provides cryptographic services for the ArubaOS operating system. The module is one of the components within the ArubaOS firmware package and is installed automatically when a trusted and verified ArubaOS firmware package signed by Hewlett Packard Enterprise is booted on an Hewlett Packard Enterprise host device. The module performs a firmware integrity test when powered on (refer to Self-Tests for details). All cryptographic algorithm self-tests are run at power-up, prior to the first operational use of the cryptographic algorithm. The firmware integrity test verifies the integrity of the module by comparing a calculated HMAC-SHA-1 value against the stored HMAC value. The operator can initiate the firmware integrity test on demand by rebooting the host device. Rebooting also zeroizes all SSPs stored in SDRAM memory. All data output via the data output interface is inhibited until the firmware integrity test has completed successfully. If the firmware integrity test fails, the module enters the error state (while in this state, the module provides no functionality). The temporary values generated during the firmware integrity test are zeroized upon completion of the integrity test. After the ArubaOS firmware boot, the operator can determine the version of the loaded module through reviewing the log and by using the show version ArubaOS CLI command on the host (use the link in the section Full Documentation to refer to ArubaOS 8.10 Command-Line Interface Reference Guide and ArubaOS 8.10 User Guide).

The operational environment is limited. The control plane Operating System (OS) is Linux, a multi-threaded operating system that supports memory protection between processes. Access to the underlying Linux implementation is not provided directly. Only Hewlett Packard Enterprise provided interfaces are used. The Hewlett Packard Enterprise Aruba OpenSSL Module is one of the components within the ArubaOS firmware package which runs on the host device. ArubaOS includes Command Line Interface (CLI) commands, some of which interact with the module via APIs. The ArubaOS CLI and the module APIs are restricted command sets. These operating control mechanisms protect against unauthorized execution, unauthorized modification, and unauthorized reading of SSPs, control and status data. The module was tested on the platforms listed above in section 2.3, Table 4, Tested Operational Environments.

The Hewlett Packard Enterprise Aruba OpenSSL Module is a firmware type module and obtains its physical security from the host platform. As per FIPS 140-3 for multiple-chip standalone cryptographic modules at Security Level 1, the host platform consists of production-grade components within a production-grade enclosure. The platforms listed above in section 2.3 meet these requirements.

Since the module has not been purposely designed, built and publicly documented to include non-invasive mitigation techniques, the Non-Invasive Security requirements are not applicable. 20| Hewlett Packard Enterprise Aruba OpenSSL Module Firmware Version 1.0 FIPS 140-3 Level 1 Security Policy

The following are the Sensitive Security Parameters (SSPs) used in the module. As specified in the Zeroization column of the following table, the majority service. The Hewlett Packard Enterprise Aruba OpenSSL Module is one of the components within the ArubaOS firmware package which runs on the host device, thus the module is rebooted when the host device is rebooted. ArubaOS includes CLI commands. As specified in the Zeroization column of the following table, there are a minority of SSPs/Keys used in the module that are stored in the host flash. The host flash can be zeroized explicitly by using the ArubaOS CLI command ‘wipe out flash’ on the host device. 21| Hewlett Packard Enterprise Aruba OpenSSL Module Firmware Version 1.0 FIPS 140-3 Level 1 Security Policy

Non-Proprietary 22| Hewlett Packard Enterprise Aruba OpenSSL Module Firmware Version 1.0 FIPS 140-3 Level 1 Security Policy

Non-Proprietary 23| Hewlett Packard Enterprise Aruba OpenSSL Module Firmware Version 1.0 FIPS 140-3 Level 1 Security Policy

Non-Proprietary 24| Hewlett Packard Enterprise Aruba OpenSSL Module Firmware Version 1.0 FIPS 140-3 Level 1 Security Policy

Non-Proprietary 25| Hewlett Packard Enterprise Aruba OpenSSL Module Firmware Version 1.0 FIPS 140-3 Level 1 Security Policy

Non-Proprietary 26| Hewlett Packard Enterprise Aruba OpenSSL Module Firmware Version 1.0 FIPS 140-3 Level 1 Security Policy

Non-Proprietary 27| Hewlett Packard Enterprise Aruba OpenSSL Module Firmware Version 1.0 FIPS 140-3 Level 1 Security Policy

Non-Proprietary 28| Hewlett Packard Enterprise Aruba OpenSSL Module Firmware Version 1.0 FIPS 140-3 Level 1 Security Policy

Non-Proprietary Notes:

• AES GCM IV generation is performed in compliance with the Implementation Guidance C.H scenario 1 for TLS.
• For TLS, the module is compliant with RFC 5288. Specifically, the module uses RFC 5288 compliant TLS 1.2 GCM Cipher Suites (TLS_ECDHE_RSA and TLS_ECDHE_ECDSA with AES_128_GCM_SHA256 and AES_256_GCM_SHA384) for TLS as per NIST SP 800-52 Rev2 section 3.3.1.
• When the nonce_explicit part of the IV for TLS exhausts the maximum number of possible values for session key for TLS, either party to the client/server for TLS that encounters this condition triggers a handshake with TLS to establish a new encryption key.
• AES GCM IV generation is performed in compliance with the Implementation Guidance C.H scenario 4 for WPA3. The session is reauthenticated by the module after 24 hours which resets the AES GCM IV counter. The 24 hours (86400 seconds) interval is the default setting and shall not be changed.
• AES GCM IV is generated internally in compliance with the Implementation Guidance C.H scenario 3 and SP800-38D section 8.2.2.
• In case the module’s power is lost and then restored, a new key for use with the AES-GCM encryption/decryption shall be established.
• CKG (vendor affirmed to SP 800-133 Rev2): For keys identified as being “Generated internally", the generated seed used in the asymmetric key generation is an unmodified output from the Approved DRBG (Cert. #A2690).
• Sensitive Security Parameters (SSPs) can be Critical Security Parameters (CSPs) or Public Security Parameters (PSPs).
• Keys established while operating in the non-Approved mode cannot be used in the Approved mode, and vice versa. 29| Hewlett Packard Enterprise Aruba OpenSSL Module Firmware Version 1.0 FIPS 140-3 Level 1 Security Policy

Non-Proprietary 30| Hewlett Packard Enterprise Aruba OpenSSL Module Firmware Version 1.0 FIPS 140-3 Level 1 Security Policy

is executing the cryptographic algorithm and pre-operational self-tests, services are not available, and input and output are inhibited. In addition, the use of the cryptographic algorithm. After the cryptographic algorithm, pre-operational, and conditional self-tests are passed successfully, the module When a cryptographic algorithm self-test or pre-operational self-test fails, or when a conditional self-test fails, the module enters the Critical Error state (while in this state, the module provides no functionality and inhibits data output), logs the error, and reboots automatically. The Hewlett Packard Enterprise Aruba OpenSSL Module performs the following Pre-Operational Self-Tests (POSTs): Table 17

• Pre-Operational Self-Tests The Hewlett Packard Enterprise Aruba OpenSSL Module performs the following Conditional Tests: Table 18
• Conditional Cryptographic Algorithm Tests 31| Hewlett Packard Enterprise Aruba OpenSSL Module Firmware Version 1.0 FIPS 140-3 Level 1 Security Policy

Non-Proprietary Table 19 – Conditional Pairwise Consistency Tests Self-Test Types: KAT = Known Answer Test, PCT = Pairwise Consistency Test 32| Hewlett Packard Enterprise Aruba OpenSSL Module Firmware Version 1.0 FIPS 140-3 Level 1 Security Policy

Non-Proprietary To see the results of the self-tests run by the module, use the ArubaOS CLI command on the host device: show log crypto all Upon successful completion of the power-up self-tests, the module displays results on the host device console: Completed OpenSSL FIPS KAT test successfully. In the event any self-test fails, the module will enter a Critical Error state (while in this state, the module provides no functionality and inhibits data output), logs the error, and reboots automatically. After a self-test failure, the module displays on the host device console: FIPS POST: FAIL Rebooting… When the firmware integrity test fails at power-up, the module enters the Critical Error state, where the invalid host ArubaOS firmware file is deleted to clear the error. The host device will automatically reboot from the backup ArubaOS image on the secondary partition. The module displays on the host device console: FATAL FIPS SELFTEST FAILURE Rebooting… 33| Hewlett Packard Enterprise Aruba OpenSSL Module Firmware Version 1.0 FIPS 140-3 Level 1 Security Policy

The Hewlett Packard Enterprise Aruba OpenSSL Module is a firmware type module, and must run on an Hewlett Packard Enterprise hardware unit (e.g., Controller, Gateway, Conductor, or Access Point) or virtual appliance (e.g., VMWare ESXi or open source KVM hypervisor running on a hardware server unit (e.g., HPE ProLiant ML110 Gen10 or HPE EdgeLine 20)). ArubaOS is the operating system for Hewlett Packard Enterprise Mobility Conductors, Mobility Controllers/Gateways, and controller-managed Hewlett Packard Enterprise Access Points (APs). The Hewlett Packard Enterprise Aruba OpenSSL Module (firmware) is one of the Hewlett Packard Enterprise cryptographic modules that provide cryptographic services for the host ArubaOS operating system running on the Hewlett Packard Enterprise hardware-based equipment or Hewlett Packard Enterprise virtual appliances.

The Hewlett Packard Enterprise Aruba OpenSSL Module is one of the components within the ArubaOS firmware package in electronic form and is installed automatically when a trusted and verified ArubaOS is booted on an Hewlett Packard Enterprise host device. ArubaOS firmware in electronic form is installed by Hewlett Packard Enterprise technical support personnel or downloaded from the HPE Networking Support Portal (NSP) by authenticated licensed customer personnel.

11.1.1 Setting Up the Hewlett Packard Enterprise Controller, Gateway, Conductor, or

Controller-managed Access Point (AP) and Running Hewlett Packard Enterprise Aruba OpenSSL Module Automatically The Crypto Officer shall perform the following steps to set-up the Hewlett Packard Enterprise Controller, Gateway, Conductor, or controller-managed Access Point (AP) either as a host hardware unit or a virtual appliance:

1. Since the Hewlett Packard Enterprise Aruba OpenSSL Module firmware is a component of ArubaOS and is installed automatically when a trusted and verified ArubaOS firmware image is booted successfully on the Hewlett Packard Enterprise host device, the Crypto Officer (CO) shall review the ArubaOS 8.10 Getting Started Guide, ArubaOS 8.10.0.x AP Software Quick Start Guide, and ArubaOS 8.10 Virtual Appliance Installation Guide. Select the Hewlett Packard Enterprise host device running ArubaOS deployment scenario that best fits your installation and follow the scenario’s deployment procedures.
2. Connect your PC or workstation to a line port (or virtual port mapped to the module interface) on the Hewlett Packard Enterprise Controller, Gateway, Conductor, or controller-managed Access Point (AP).
3. Enable power to the Hewlett Packard Enterprise Controller, Gateway, Conductor, or controllermanaged Access Point (AP).
4. Monitor the Hewlett Packard Enterprise host device boot progress messages on the console.
5. Once ArubaOS is loaded successfully and operating normally on the Hewlett Packard Enterprise host device, check the console messages to make sure that all the power-up self-tests passed. a. Check that the following console message is displayed: Completed OpenSSL FIPS KAT test successfully. b. As specified in the Self-Tests section, if any of the checks fail, error messages will be displayed on the console. If the errors persist after the Hewlett Packard Enterprise device is rebooted, contact Hewlett Packard Enterprise.
6. Enable the Approved mode with the ArubaOS CLI on the host. a. Login to the Hewlett Packard Enterprise Controller, Gateway, or Conductor following the guidance from step 1. above (a controller-managed Access Point (AP) is placed in the Approved mode using a Staging Controller in the Approved mode as per the Aruba AP Software Quick Start Guide). 34| Hewlett Packard Enterprise Aruba OpenSSL Module Firmware Version 1.0 FIPS 140-3 Level 1 Security Policy

Non-Proprietary b. Enable the Approved mode using the following ArubaOS CLI commands on the host: #configure terminal Enter Configuration commands, one per line. End with CNTL/Z (config) #fips enable (config) #exit #write memory Saving Configuration... Configuration Saved. c. To verify the Approved mode has been enabled, issue the ArubaOS CLI command on the host: show fips to see: FIPS Settings: Mode Enabled

Documentation for any Hewlett Packard Enterprise product can be found on the HPE Networking Support Portal (NSP). Filters can be used to limit the displayed results by Product(s), Product Series, Version(s), and File Category. For example, • Full ArubaOS version 8.10 documentation for Hewlett Packard Enterprise Mobility Controllers, Virtual Mobility Controllers, Gateways, Mobility Conductors, and Access Points can be found at the link provided below after authentication. https://networkingsupport.hpe.com/downloads;pageSize=100;fileTypes=DOCUMENT;products=Aruba%20A ccess%20Points,Aruba%20Mobility%20Gateways;softwareGroups=ArubaOS;softwareMajorVersions=8.10

The following Hewlett Packard Enterprise documents can be referenced to ensure that ArubaOS and the Hewlett Packard Enterprise hardware-based equipment or Hewlett Packard Enterprise virtual appliances that run ArubaOS are installed and operated correctly in the Approved mode:

• Aruba Access Points Installation Guides
• ArubaOS 8.10.0.x AP Software Quick Start Guide
• ArubaOS 8.10.0.0 Virtual Appliance Installation Guide
• ArubaOS 8.10.0.0 User Guide
• ArubaOS 8.10.0.x CLI Reference Guide
• ArubaOS 8.10.0.0 API Guide
• ArubaOS 8.10.0.0 Getting Started Guide
• ArubaOS 8.10.0.0 Syslog Reference Guide

The Crypto Officer must ensure that the module is kept in the Approved mode of operation. To keep the module in the Approved mode, abide by section 11.1, Start-up Procedures, section 2.9, Non-Approved Algorithms Not Allowed in the Approved Mode of Operation, and section 4.3.2, Non-Approved Services.

Not Applicable (N/A) 35| Hewlett Packard Enterprise Aruba OpenSSL Module Firmware Version 1.0 FIPS 140-3 Level 1 Security Policy

To determine if an Hewlett Packard Enterprise product is considered end of life, refer to the Hewlett Packard Enterprise end-of life information at https://networkingsupport.hpe.com/end-of-life. If an Hewlett Packard Enterprise product is deemed end-of-life, the CO should work with their Hewlett Packard Enterprise representative to determine the appropriate Hewlett Packard Enterprise product upgrade path to use a newer Approved version. For secure sanitization and zeroization of SSP values, the CO should follow the guidance in the Zeroization service entry above in Table 13, Approved Services to wipe out host flash and reboot the module. Since the module is a component of ArubaOS, if the module is deprecated, the module will be upgraded to a newer Approved validated version by loading and booting a newer validated version of ArubaOS with the help of an Hewlett Packard Enterprise-Certified Mobility Professional (ACMP).

The module has not been purposely designed, built and publicly documented to mitigate one or more specific attacks. The Mitigation of Other Attacks requirements are not applicable, per FIPS 140-3 IG 12.A. 36| Hewlett Packard Enterprise Aruba OpenSSL Module Firmware Version 1.0 FIPS 140-3 Level 1 Security Policy