National Information Assurance Partnership
Common Criteria Evaluation and Validation Scheme
Validation Report
HPE Aruba Networking Gateways and Mobility
Controllers running software version 8.13.0
Report Number: CCEVS-VR-VID11646-2026
Dated: February 13, 2026
Version: 1.0
National Institute of Standards and Technology Department of Defense
Information Technology Laboratory ATTN: NIAP, Suite 6982
100 Bureau Drive 9800 Savage Road
Gaithersburg, MD 20899 Fort Meade, MD 20755-6982
HPE Aruba Networking Gateways Validation Report Version 1.0, February 13, 2026
and Mobility Controllers running
software version 8.13.0
ii
ACKNOWLEDGEMENTS
Validation Team
Swapna Katikaneni
Patrick Mallett, Ph.D.
The Aerospace Corporation
Common Criteria Testing Laboratory
Douglas Kalmus
Gossamer Security Solutions, Inc.
Columbia, MD
HPE Aruba Networking Gateways Validation Report Version 1.0, February 13, 2026
and Mobility Controllers running
software version 8.13.0
iii
Table of Contents
1 Executive Summary............................................................................................................1
2 Identification.......................................................................................................................2
3 Architectural Information...................................................................................................3
3.1 TOE Description.........................................................................................................3
3.2 TOE Evaluated Platforms...........................................................................................4
3.3 TOE Architecture .......................................................................................................4
3.4 Physical Boundaries ...................................................................................................5
4 Security Policy....................................................................................................................6
4.1 Security audit..............................................................................................................6
4.2 Cryptographic support................................................................................................6
4.3 User data protection....................................................................................................6
4.4 Firewall.......................................................................................................................7
4.5 Identification and authentication ................................................................................7
4.6 Security management .................................................................................................7
4.7 Protection of the TSF..................................................................................................7
4.8 TOE access .................................................................................................................7
4.9 Trusted path/channels.................................................................................................8
5 Assumptions & Clarification of Scope...............................................................................8
6 Documentation ...................................................................................................................9
7 IT Product Testing..............................................................................................................9
7.1 Developer Testing ....................................................................................................10
7.2 Evaluation Team Independent Testing.....................................................................10
8 Evaluated Configuration...................................................................................................10
9 Results of the Evaluation..................................................................................................10
9.1 Evaluation of the Security Target (ASE)..................................................................11
9.2 Evaluation of the Development (ADV)....................................................................11
9.3 Evaluation of the Guidance Documents (AGD).......................................................11
9.4 Evaluation of the Life Cycle Support Activities (ALC)...........................................11
9.5 Evaluation of the Test Documentation and the Test Activity (ATE).......................12
9.6 Vulnerability Assessment Activity (VAN) ..............................................................12
9.7 Summary of Evaluation Results ...............................................................................12
10 Validator Comments/Recommendations......................................................................13
11 Annexes ........................................................................................................................13
12 Security Target .............................................................................................................13
13 Glossary........................................................................................................................13
14 Bibliography.................................................................................................................14
HPE Aruba Networking Gateways Validation Report Version 1.0, February 13, 2026
and Mobility Controllers running
software version 8.13.0
1
1 Executive Summary
This report documents the assessment of the National Information Assurance Partnership (NIAP)
validation team of the evaluation of HPE Aruba Networking Gateways and Mobility Controllers
running software version 8.13.0 solution provided by HPE Aruba Networking. It presents the
evaluation results, their justifications, and the conformance results. This Validation Report is not
an endorsement of the Target of Evaluation by any agency of the U.S. government, and no
warranty is either expressed or implied.
The evaluation was performed by the Gossamer Security Solutions (Gossamer) Common Criteria
Testing Laboratory (CCTL) in Columbia, MD, United States of America, and was completed in
February 2026. The information in this report is largely derived from the Evaluation Technical
Report (ETR) and associated test reports, all written by Gossamer Security Solutions. The
evaluation determined that the product is both Common Criteria Part 2 Extended and Part 3
Conformant, and meets the assurance requirements of the PP-Configuration for Network Devices,
Stateful Traffic Filter Firewalls, and Wireless Local Area Network (WLAN) Access System which
includes the Base PP: collaborative Protection Profile for Network Devices, Version 3.0e, 06
December 2023 (NDcPP30e) with the PP-Module for Stateful Traffic Filter Firewalls, Version 1.4
+ Errata 20200625, 25 June 2020 (STFFW14e) and the PP-Module for Wireless Local Area
Network (WLAN) Access System, Version 1.0, 19 April 2022 (WLANAS10) plus the Functional
Package for SSH, Version 1.0, 13 May 2021 (SSH10).
The Target of Evaluation (TOE) is the HPE Aruba Networking Gateways and Mobility Controllers
running software version 8.13.0.
The TOE identified in this Validation Report has been evaluated at a NIAP approved Common
Criteria Testing Laboratory using the Common Methodology for IT Security Evaluation (Version
3.1, Rev 5) for conformance to the Common Criteria for IT Security Evaluation (Version 3.1, Rev
5). This Validation Report applies only to the specific version of the TOE as evaluated. The
evaluation has been conducted in accordance with the provisions of the NIAP Common Criteria
Evaluation and Validation Scheme and the conclusions of the testing laboratory in the evaluation
technical report are consistent with the evidence provided.
The validation team monitored the activities of the evaluation team, provided guidance on
technical issues and evaluation processes, and reviewed the individual work units and successive
versions of the ETR. The validation team found that the evaluation showed that the product
satisfies all of the functional requirements and assurance requirements stated in the Security Target
(ST). Therefore the validation team concludes that the testing laboratory’s findings are accurate,
the conclusions justified, and the conformance results are correct. The conclusions of the testing
laboratory in the evaluation technical report are consistent with the evidence produced.
The technical information included in this report was obtained from the HPE Aruba Networking
Gateways and Mobility Controllers running software version 8.13.0 Security Target, version 0.6,
February 13, 2026 and analysis performed by the Validation Team.
HPE Aruba Networking Gateways Validation Report Version 1.0, February 13, 2026
and Mobility Controllers running
software version 8.13.0
2
2 Identification
The CCEVS is a joint National Security Agency (NSA) and National Institute of Standards and
Technology (NIST) effort to establish commercial facilities to perform trusted product evaluations.
Under this program, security evaluations are conducted by commercial testing laboratories called
Common Criteria Testing Laboratories (CCTLs) using the Common Evaluation Methodology
(CEM) in accordance with National Voluntary Laboratory Assessment Program (NVLAP)
accreditation.
The NIAP Validation Body assigns Validators to monitor the CCTLs to ensure quality and
consistency across evaluations. Developers of information technology products desiring a security
evaluation contract with a CCTL and pay a fee for their product’s evaluation. Upon successful
completion of the evaluation, the product is added to NIAP’s Validated Products List.
Table 1 provides information needed to completely identify the product, including:
• The Target of Evaluation (TOE): the fully qualified identifier of the product as evaluated.
• The Security Target (ST), describing the security features, claims, and assurances of the
product.
• The conformance result of the evaluation.
• The Protection Profile to which the product is conformant.
• The organizations and individuals participating in the evaluation.
Table 1: Evaluation Identifiers
Item Identifier
Evaluation Scheme United States NIAP Common Criteria Evaluation and Validation Scheme
TOE HPE Aruba Networking Gateways and Mobility Controllers running software
version 8.13.0 (Specific models identified in Section 8)
Protection Profile PP-Configuration for Network Devices, Stateful Traffic Filter Firewalls, and
Wireless Local Area Network (WLAN) Access System which includes the Base
PP: collaborative Protection Profile for Network Devices, Version 3.0e, 06
December 2023 (NDcPP30e) with the PP-Module for Stateful Traffic Filter
Firewalls, Version 1.4 + Errata 20200625, 25 June 2020 (STFFW14e) and the PP-
Module for Wireless Local Area Network (WLAN) Access System, Version 1.0,
19 April 2022 plus the Functional Package for SSH, Version 1.0, 13 May 2021
(SSH10)
ST HPE Aruba Networking Gateways and Mobility Controllers running software
version 8.13.0 Security Target, version 0.6, February 13, 2026
Evaluation Technical
Report
Evaluation Technical Report for HPE Aruba Networking Gateways and Mobility
Controllers running software version 8.13.0, version 0.2, February 13, 2026
CC Version Common Criteria for Information Technology Security Evaluation, Version 3.1,
rev 5
Conformance Result CC Part 2 extended, CC Part 3 conformant
Sponsor HPE Aruba Networking
HPE Aruba Networking Gateways Validation Report Version 1.0, February 13, 2026
and Mobility Controllers running
software version 8.13.0
3
Item Identifier
Developer HPE Aruba Networking
Common Criteria
Testing Lab (CCTL)
Gossamer Security Solutions, Inc.
Columbia, MD
CCEVS Validators Swapna Katikaneni, Patrick Mallett
3 Architectural Information
Note: The following architectural description is based on the description presented in the Security
Target.
The Target of Evaluation (TOE) is HPE Aruba Networking Gateways and Mobility Controllers
running software version 8.13.0. The TOE is a multi-purpose network device that includes WLAN
access system, and stateful traffic filter firewall capabilities. Note that the terms gateway and
mobility controller are used interchangeably.
3.1 TOE Description
The HPE Aruba Networking Mobility Controller platform serves as a gateway between wired and
wireless networks and provides command and control over Aruba Access Points (APs) within an
Aruba dependent wireless network.
The HPE Aruba Networking Mobility Controllers (MCs) are wireless switch hardware appliances
that provide a wide range of security services and features including wireless and wired network
mobility, security, centralized management, auditing, authentication, secure remote access, self-
verification of integrity and operation, and stateful traffic filtering functionality.
The ArubaOS is a suite of mobility applications that runs on all Aruba controllers and allows
administrators to configure and manage the wireless and mobile user environment. The TOE is
generally deployed in a configuration consisting of one or more Aruba mobility controllers (MC)
and multiple HPE Aruba Networking wireless APs.
The TOE performs stateful packet filtering on network packets processed by the TOE. Filtering
rules may be applied to appliance Ethernet interfaces and to user roles (for wireless clients as
described above) to allow fine grained control over network traffic.
In an encrypted WLAN, a wireless client first associates to the Mobility Controller through an AP
and then authenticates (IEEE 802.11i1
) using credentials to obtain access to the network. The
authenticated wireless client is then assigned a role based on the configuration in the Mobility
Controller or the authentication server. The role, in turn, maps a set of firewall policies to the
client’s session such that all wireless client traffic passes through a logical firewall component
before traffic is forwarded outside of the Mobility Controller. The client’s role can also be used
to determine VLAN membership.
1
Implements 802.1X for wireless access points to address the security vulnerabilities found in WEP.
HPE Aruba Networking Gateways Validation Report Version 1.0, February 13, 2026
and Mobility Controllers running
software version 8.13.0
4
3.2 TOE Evaluated Platforms
Detail regarding the evaluated configuration is provided in Section 8 below.
3.3 TOE Architecture
HPE Aruba Networking Mobility Controllers (MCs) are hardware appliances consisting of a
multicore network processor, Ethernet interfaces, and required supporting circuitry and power
supplies enclosed in a metal chassis.
The ArubaOS software running on the MCs consists of two main components:
• Control Plane (CP) – implements functions which can be handled at lower speeds such as
Mobility Controller system management (CLI and Web GUI), user authentication (e.g.
802.1X, RADIUS), Internet Key Exchange (IKE), auditing/logging (syslog), Wireless IDS
(WIDS), and termination of protocols operating at the system level (e.g. SSH, TLS, NTP,
etc.). The Control Plane runs the Linux operating system along with various user-space
applications (described below).
• Data Plane (DP) - implements functions that must be handled at high speeds such as high-
speed switching functions (forwarding, VLAN tagging/enforcement, bridging),
termination of 802.11 associations/sessions, tunnel termination (IPsec), stateful firewall
and deep packet inspection functions, and cryptographic acceleration. The Data Plane runs
a lightweight, proprietary real-time OS which is known as “SOS” (an acronym which used
to mean “SiByte Operating System” for an earlier generation of Mobility Controller that
used the SiByte CPU). On the Mobility Controller hardware appliances, SOS runs on
separate CPU cores.
The Control Plane and Data Plane are inseparable. Administrators install the MC software by
loading a single file, identified as “ArubaOS”. Internally, the controllers unpack the ArubaOS
software image into its various components. A given ArubaOS software image has a single version
number and includes all software components necessary to operate the MC appliances as well as
the APs which are in the operating environment of the TOE.
The CP runs the Linux OS, along with various custom user-space applications which provide the
following CP functions:
• Monitors and manages critical system resources, including processes, memory, and flash
• Manages system configuration and licensing
• Manages an internal database used to store licenses, user authentication information, etc
• Provides network anomaly detection, hardware monitoring, mobility management,
wireless management, and radio frequency management services
• Provides a Command Line Interface (CLI)
• Provides a web-based (HTTPS/TLS) management UI for the MCs
• Provides various WLAN station management functions
• Provides authentication services for the system management interfaces (CLI, web GUI) as
well as for WLAN users
HPE Aruba Networking Gateways Validation Report Version 1.0, February 13, 2026
and Mobility Controllers running
software version 8.13.0
5
• Provides IPsec key management services
• Provides network time protocol service, point to point tunneling protocol services for
users, layer 2 tunneling protocol services for users, SSH services for incoming
management connections, SNMP client/agent services, and protocol independent
multicast (routing) services for the controller
• Provides syslog services by sending logs to the operating environment
The Linux OS running on the CP is a version 2.6.32 kernel for the 7xxx models and a version
4.14.181 kernel for the 9xxx models. Linux is a soft real-time, multi-threaded operating system
that supports memory protection between processes. Only Aruba provided interfaces are used,
and the CLI is a restricted command set. Administrators do not have access to the Linux
command shell or operating system.
All Aruba Mobility Controller models run the same ArubaOS 8.13.0 software and include the
same ArubaOS Crypto Module. Regardless of the different hardware platforms, the security
functionality remains the same. The differences in the platforms are in the processing speed,
throughput, memory capacity, storage, physical interfaces, number of ports, etc., and are based
on performance and scalability requirements. The USB interfaces on the devices are intended for
storage only. All models run the same code with the only differences being the hardware specific
code for the differently scaled hardware.
Although the TOE models have different specifications (in terms of performance and scalability),
they all provide the same security functions described in the ST; therefore, they have been
considered to be the same for the purposes of the ST description.
3.4 Physical Boundaries
The TOE consists of the following components:
• HPE Aruba Networking Mobility Controllers: 9004, 9012, 9240, 7005, 7008, 7010,
7024, 7030, 7205, 7210, 7220, 7240, 7240XM, 7280
• ArubaOS version 8.13.0
These components are identified and described in section 1.2 of this ST. The TOE is being
evaluated as a physical device (this is Use Case 2 of the NDcPP30e).
The ArubaOS consists of a base software package with add-on software modules that can be
activated by installing the appropriate licenses. The following SFR-enforcing software modules
are required to be licensed and installed in the CC evaluated configuration.
Required Software
Module
Description
Policy Enforcement
Firewall Next
Generation
Provides identity-based security for wired and wireless clients.
Stateful firewall enables classification based on client identity,
device type, location, and time of day, and provides differentiated
access for different classes of users.
HPE Aruba Networking Gateways Validation Report Version 1.0, February 13, 2026
and Mobility Controllers running
software version 8.13.0
6
Required Software
Module
Description
RFprotect Detects, classifies and limits designated wireless security threats
such as rogue APs, DoS attacks, malicious wireless attacks,
impersonations, and unauthorized intrusions. Eliminates need for
separate system of RF sensors and security appliances. Also
provides spectrum intelligence and spectrum visibility when used
with compatible AP platforms.
Advanced
Cryptography
Required for SuiteB, AES-GCM and ECDSA functionality.
4 Security Policy
This section summarizes the security functionality of the TOE:
1. Security audit
2. Cryptographic support
3. User data protection
4. Firewall
5. Identification and authentication
6. Security management
7. Protection of the TSF
8. TOE access
9. Trusted path/channels
4.1 Security audit
The TOE is designed to be able to generate logs for a wide range of security relevant events
including start-up and shutdown of the TOE, all administrator actions, and all events identified in
Table 8 Auditable Events. The TOE can be configured to store the logs locally so they can be
accessed by an administrator or alternately to send the logs to a designated syslog server in the
operational environment.
4.2 Cryptographic support
The TOE includes cryptographic modules that provide key management, random bit generation,
encryption/decryption, digital signature and secure hashing and key-hashing features in support of
higher-level cryptographic protocols including IPsec, SSH, and TLS/HTTPS.
4.3 User data protection
The TOE ensures that any data packets passing through do not inadvertently contain any residual
information that might be disclosed inappropriately.
HPE Aruba Networking Gateways Validation Report Version 1.0, February 13, 2026
and Mobility Controllers running
software version 8.13.0
7
4.4 Firewall
The TOE performs stateful packet filtering. Filtering rules may be applied to appliance Ethernet
interfaces or to user-roles (wireless clients connecting through APs are placed into user-roles).
Stateful packet filter policies are applied to user-roles to allow fine grained control over wireless
traffic.
4.5 Identification and authentication
The TOE requires administrators to be identified and authenticated before they can access any
TOE security functions. The TOE supports role-based authentication, so user accounts are
assigned predefined roles which restrict them based on their assigned role. The TOE maintains
these administrator and user attributes which can be defined locally with usernames and passwords
or can be defined in the context of local RADIUS or TACACS+ services. Authentication can be
either locally or remotely through an external authentication server, or internally. Wireless clients
are identified and authenticated by different authentication mechanisms such as 802.1X, etc. After
an administrator-specified number of failed attempts, the user account is locked out. The TOE’s
password mechanism provides configuration for a minimum password length. The TOE also
protects, stores and allows authorized administrators to load X.509.v3 certificates for use to
support authentication for IPsec connections.
4.6 Security management
The TOE provides the administrator role the capability to configure and manage all TOE security
functions including cryptographic operations, user accounts, passwords, advisory banner, session
inactivity and TOE updates. The management functions are restricted to the administrator role.
The role must have the appropriate access privileges or access will be denied. The TOE’s
cryptographic functions ensure that only secure values are accepted for security attributes.
4.7 Protection of the TSF
The TOE has its own internal hardware clock that provides reliable time stamps used for auditing.
The internal clock may be synchronized with a time signal obtained from an external trusted NTP
server. The TOE stores passwords on flash using a SHA1 hash and does not provide any interfaces
that allow passwords or keys to be read.
The TOE runs self-tests during power up and periodically during operation to ensure the correct
operation of the cryptographic functions and TSF hardware. There is an option for the
administrator to verify the integrity of stored TSF executable code.
The TOE includes mechanisms so that the administrator can determine the TOE version and update
the TOE securely using digital signatures.
4.8 TOE access
The TOE allows administrators to configure a period of inactivity for administrator sessions. Once
that time period has been reached while the session has no activity, the session is terminated. All
HPE Aruba Networking Gateways Validation Report Version 1.0, February 13, 2026
and Mobility Controllers running
software version 8.13.0
8
users may also terminate their own sessions at any time. A warning banner is displayed at the
management interfaces (Web GUI and CLI) to advise users on appropriate use and penalty for
misuse of system.
In order to limit access to the administrative functions, the TOE can be configured to deny WLAN
clients based on the time/date, IP address (location), as well as information retained in a blacklist.
4.9 Trusted path/channels
The TOE uses IPsec to provide an encrypted channel between itself and third-party trusted IT
entities in the operating environment including external syslog server, external authentication
server, and NTP server.
The TOE also provides a protected communication path between itself and wireless users. The
TOE protects communication with wireless clients using WPA3 and WPA2 with 802.1x EAP-
TLS.
The TOE secures remote communication with administrators by implementing TLS/HTTPS for
remote Web UI access and SSHv2 for CLI access. In each case, both integrity and disclosure
protection is ensured via the secure protocol. If the negotiation of a secure session fails or if the
user cannot be authenticated for remote administration, the attempted session will not be
established.
5 Assumptions & Clarification of Scope
Assumptions
The Security Problem Definition, including the assumptions, may be found in the following
documents:
• collaborative Protection Profile for Network Devices, Version 3.0e, 06 December 2023
(NDcPP30e)
• PP-Module for Stateful Traffic Filter Firewalls, Version 1.4 + Errata 20200625,
25 June 2020 (STFFW14e)
• PP-Module for Wireless Local Area Network (WLAN) Access System, Version 1.0,
19 April 2022 (WLANAS10)
• Functional Package for SSH, Version 1.0, 13 May 2021 (SSH10)
That information has not been reproduced here and the
NDcPP30e/STFFW14e/WLANAS10/SSH10 should be consulted if there is interest in that
material.
The scope of this evaluation was limited to the functionality and assurances covered in the
NDcPP30e/STFFW14e/WLANAS10/SSH10 as described for this TOE in the Security Target.
Other functionality included in the product was not assessed as part of this evaluation. All other
functionality provided by the devices needs to be assessed separately, and no further conclusions
can be drawn about their effectiveness.
HPE Aruba Networking Gateways Validation Report Version 1.0, February 13, 2026
and Mobility Controllers running
software version 8.13.0
9
Clarification of scope
All evaluations (and all products) have limitations, as well as potential misconceptions that need
clarification. This text covers some of the more important limitations and clarifications of this
evaluation. Note that:
• As with any evaluation, this evaluation only shows that the evaluated configuration meets
the security claims made with a certain level of assurance (the assurance activities specified
in the collaborative Protection Profile for Network Devices and the Firewalls and WLAN
Access System Modules and SSH Package and performed by the evaluation team).
• This evaluation covers only the specific device models and software as identified in this
document, and not any earlier or later versions released or in process.
• Apart from the Admin Guide, additional customer documentation for the specific network
device with WLAN Access System and Firewall capabilities models was not included in
the scope of the evaluation and therefore should not be relied upon when configuring or
operating the device as evaluated.
• This evaluation did not specifically search for, nor attempt to exploit, vulnerabilities that
were not “obvious” or vulnerabilities to objectives not claimed in the ST. The CEM defines
an “obvious” vulnerability as one that is easily exploited with a minimum of understanding
of the TOE, technical sophistication and resources.
• The functionality evaluated is scoped exclusively to the security functional requirements
specified in the NDcPP30e/STFFW14e/WLANAS10/SSH10 and applicable Technical
Decisions. Any additional security related functional capabilities of the TOE were not
covered by this evaluation.
6 Documentation
The following documents were available with the TOE for evaluation:
• Common Criteria Configuration Guidance ArubaOS 8.13.0 Supplemental Guidance,
Version 3.0, October 2025
Any additional customer documentation provided with the product, or that is available online
was not included in the scope of the evaluation and therefore should not be relied upon when
configuring or operating the device as evaluated.
To use the product in the evaluated configuration, the product must be configured as specified in
the Guidance Documentation listed above. Consumers are encouraged to download the
configuration guides from the NIAP website to ensure the device is configured as evaluated.
7 IT Product Testing
This section describes the testing efforts of the developer and the Evaluation Team. It is derived
from information contained in the proprietary Detailed Test Report for HPE Aruba Networking
Gateways and Mobility Controllers running software version 8.13.0, Version 0.2, February 13,
2026 (DTR), as summarized in section 3.4.1 of the evaluation Assurance Activity Report (AAR).
HPE Aruba Networking Gateways Validation Report Version 1.0, February 13, 2026
and Mobility Controllers running
software version 8.13.0
10
7.1 Developer Testing
No evidence of developer testing is required in the assurance activities for this product.
7.2 Evaluation Team Independent Testing
The evaluation team verified the product according to a Common Criteria Certification document
and ran the tests specified in the NDcPP30e/STFFW14e/WLANAS10/SSH10 including the tests
associated with optional requirements. The AAR, in sections 1.1 lists the tested devices, provides
a list of test tools, and has diagrams of the test environment.
8 Evaluated Configuration
The TOE consists of the following components:
• HPE Aruba Networking Mobility Controllers: 9004, 9012, 9240, 7005, 7008, 7010,
7024, 7030, 7205, 7210, 7220, 7240, 7240XM, 7280
• ArubaOS version 8.13.0
• One or more of the following HPE Aruba Networking Access Points running
ArubaOS 8.13.0:
HPE Aruba Networking Access Points
300 Series 500 Series 600 Series
AP-303H Access Point AP-503H Access Point AP-635 Access Point
AP-304/5 Access Point AP-504/5 Access Point AP-655 Access Point
AP-314/5 Access Point AP-514/5 Access Point
AP-318 Access Point AP-518 Access Point
AP-324/5 Access Point AP-534/5 Access Point
AP-334/5 Access Point AP-555 Access Point
AP-344/5 Access Point AP-565/7 Access Point
AP-364/5 Access Point AP-574/5/7 Access Point
AP-374/5/7 Access Point AP-584/5/7 Access Point
AP-387 Access Point
9 Results of the Evaluation
The results of the assurance requirements are generally described in this section and are presented
in detail in the proprietary ETR. The reader of this document can assume that all assurance
activities and work units received a passing verdict.
A verdict for an assurance component is determined by the resulting verdicts assigned to the
corresponding evaluator action elements. The evaluation was conducted based upon CC version
3.1 rev 5 and CEM version 3.1 rev 5. The evaluation determined the HPE Aruba Networking
Gateways and Mobility Controllers running software version 8.13.0 TOE to be Part 2 extended,
and to meet the SARs contained in the NDcPP30e/STFFW14e/WLANAS10/SSH10.
HPE Aruba Networking Gateways Validation Report Version 1.0, February 13, 2026
and Mobility Controllers running
software version 8.13.0
11
9.1 Evaluation of the Security Target (ASE)
The evaluation team applied each ASE CEM work unit. The ST evaluation ensured the ST contains
a description of the environment in terms of policies and assumptions, a statement of security
requirements claimed to be met by the HPE Aruba Networking Gateways and Mobility Controllers
running software version 8.13.0 products that are consistent with the Common Criteria, and
product security function descriptions that support the requirements.
The validator reviewed the work of the evaluation team and found that sufficient evidence and
justification was provided by the evaluation team to confirm that the evaluation was conducted in
accordance with the requirements of the CEM, and that the conclusion reached by the evaluation
team was justified.
9.2 Evaluation of the Development (ADV)
The evaluation team applied each ADV CEM work unit. The evaluation team assessed the design
documentation and found it adequate to aid in understanding how the TSF provides the security
functions. The design documentation consists of a functional specification contained in the
Security Target and Guidance documents. Additionally, the evaluator performed the assurance
activities specified in the NDcPP30e/STFFW14e/WLANAS10/SSH10 related to the examination
of the information contained in the TSS.
The validator reviewed the work of the evaluation team and found that sufficient evidence and
justification was provided by the evaluation team to confirm that the evaluation was conducted in
accordance with the requirements of the CEM, and that the conclusion reached by the evaluation
team was justified.
9.3 Evaluation of the Guidance Documents (AGD)
The evaluation team applied each AGD CEM work unit. The evaluation team ensured the
adequacy of the user guidance in describing how to use the operational TOE. Additionally, the
evaluation team ensured the adequacy of the administrator guidance in describing how to securely
administer the TOE. All of the guides were assessed during the design and testing phases of the
evaluation to ensure they were complete.
The validator reviewed the work of the evaluation team and found that sufficient evidence and
justification was provided by the evaluation team to confirm that the evaluation was conducted in
accordance with the requirements of the CEM, and that the conclusion reached by the evaluation
team was justified.
9.4 Evaluation of the Life Cycle Support Activities (ALC)
The evaluation team applied each ALC CEM work unit. The evaluation team found that the TOE
was identified.
The validator reviewed the work of the evaluation team and found that sufficient evidence and
justification was provided by the evaluation team to confirm that the evaluation was conducted in
HPE Aruba Networking Gateways Validation Report Version 1.0, February 13, 2026
and Mobility Controllers running
software version 8.13.0
12
accordance with the requirements of the CEM, and that the conclusion reached by the evaluation
team was justified.
9.5 Evaluation of the Test Documentation and the Test Activity (ATE)
The evaluation team applied each ATE CEM work unit. The evaluation team ran the set of tests
specified by the assurance activities in the NDcPP30e/STFFW14e/WLANAS10/SSH10 and
recorded the results in a Test Report, summarized in the AAR.
The validator reviewed the work of the evaluation team and found that sufficient evidence and
justification was provided by the evaluation team to confirm that the evaluation was conducted in
accordance with the requirements of the CEM, and that the conclusion reached by the evaluation
team was justified.
9.6 Vulnerability Assessment Activity (VAN)
The evaluation team applied each AVA CEM work unit. The vulnerability analysis is in the
Detailed Test Report (DTR) prepared by the evaluator. The vulnerability analysis includes a
public search for vulnerabilities. The public search for vulnerabilities did not uncover any
residual vulnerability.
The evaluator searched the MITRE CVE Database, National Vulnerability Database, and CVE
details (https://www.cve.org/, https://web.nvd.nist.gov/vuln/search, and
https://www.cvedetails.com/vulnerability-search.php, ref CVE), Known Vulnerability Exploit
Catalog (https://www.cisa.gov/known-exploited-vulnerabilities-catalog, ref KEV), Vulnerability
Notes Database (http://www.kb.cert.org/vuls/, ref VND), Rapid7 Vulnerability Database
(https://www.rapid7.com/db/vulnerabilities, ref Rapid7), Tipping Point Zero Day Initiative
(http://www.zerodayinitiative.com/advisories, ref ZDI), Tenable Network Security
(http://nessus.org/plugins/index.php?view=search, ref TEN), and Offensive Security Exploit
Database (https://www.exploit-db.com/, ref EDB) on 1/26/2026 (from 5/1/2023) with the
following search terms: "aruba 802.1X", "aruba tcp", "aruba mobility controller", "arubaos",
"AOS", "ArubaOS Crypto Module", "aruba ipsec", "aruba ssh", "aruba tls", "arubaos openssl",
"arubaos uboot", "aruba vpn", "sos", "sibyte", "Linux OS v2.6.32 kernel", "Linux OS v4.14.181
kernel", "Intel Atom C3508", and "Broadcom XLP".
The validator reviewed the work of the evaluation team and found that sufficient evidence and
justification was provided by the evaluation team to confirm that the evaluation was conducted in
accordance with the requirements of the CEM, and that the conclusion reached by the evaluation
team was justified.
9.7 Summary of Evaluation Results
The evaluation team’s assessment of the evaluation evidence demonstrates that the claims in the
ST are met. Additionally, the evaluation team’s testing also demonstrated the accuracy of the
claims in the ST.
HPE Aruba Networking Gateways Validation Report Version 1.0, February 13, 2026
and Mobility Controllers running
software version 8.13.0
13
The validation team’s assessment of the evidence provided by the evaluation team is that it
demonstrates that the evaluation team followed the procedures defined in the CEM, and correctly
verified that the product meets the claims in the ST.
10 Validator Comments/Recommendations
None.
11 Annexes
Not applicable
12 Security Target
The Security Target is identified as: HPE Aruba Networking Gateways and Mobility Controllers
running software version 8.13.0 Security Target, Version 0.6, February 13, 2026.
13 Glossary
The following definitions are used throughout this document:
• Common Criteria Testing Laboratory (CCTL). An IT security evaluation facility
accredited by the National Voluntary Laboratory Accreditation Program (NVLAP) and
approved by the CCEVS Validation Body to conduct Common Criteria-based evaluations.
• Conformance. The ability to demonstrate in an unambiguous way that a given implementation
is correct with respect to the formal model.
• Evaluation. The assessment of an IT product against the Common Criteria using the Common
Criteria Evaluation Methodology to determine whether or not the claims made are justified; or
the assessment of a protection profile against the Common Criteria using the Common
Evaluation Methodology to determine if the Profile is complete, consistent, technically sound
and hence suitable for use as a statement of requirements for one or more TOEs that may be
evaluated.
• Evaluation Evidence. Any tangible resource (information) required from the sponsor or
developer by the evaluator to perform one or more evaluation activities.
• Feature. Part of a product that is either included with the product or can be ordered separately.
• Target of Evaluation (TOE). A group of IT products configured as an IT system, or an IT
product, and associated documentation that is the subject of a security evaluation under the
CC.
• Validation. The process carried out by the CCEVS Validation Body leading to the issue of a
Common Criteria certificate.
HPE Aruba Networking Gateways Validation Report Version 1.0, February 13, 2026
and Mobility Controllers running
software version 8.13.0
14
• Validation Body. A governmental organization responsible for carrying out validation and for
overseeing the day-to-day operation of the NIAP Common Criteria Evaluation and Validation
Scheme.
14 Bibliography
The Validation Team used the following documents to produce this Validation Report:
[1] Common Criteria for Information Technology Security Evaluation: Part 1: Introduction
and General Model, Version 3.1, Revision 5, April 2017.
[2] Common Criteria for Information Technology Security Evaluation Part 2: Security
functional components, Version 3.1, Revision 5, April 2017.
[3] Common Criteria for Information Technology Security Evaluation Part 3: Security
assurance components, Version 3.1 Revision 5, April 2017.
[4] collaborative Protection Profile for Network Devices, Version 3.0e, 06 December 2023
(NDcPP30e).
[5] PP-Module for Stateful Traffic Filter Firewalls, Version 1.4 + Errata 20200625, 25 June
2020 (STFFW14e).
[6] PP-Module for Wireless Local Area Network (WLAN) Access System, Version 1.0, 19
April 2022 (WLANAS10).
[7] Functional Package for SSH, Version 1.0, 13 May 2021 (SSH10).
[8] HPE Aruba Networking Gateways and Mobility Controllers running software version
8.13.0 Security Target, Version 0.6, February 13, 2026 (ST).
[9] Assurance Activity Report for HPE Aruba Networking Gateways and Mobility Controllers
running software version 8.13.0, Version 0.2, February 13, 2026 (AAR).
[10] Detailed Test Report for HPE Aruba Networking Gateways and Mobility Controllers
running software version 8.13.0, Version 0.2, February 13, 2026 (DTR).
[11] Evaluation Technical Report for HPE Aruba Networking Gateways and Mobility
Controllers running software version 8.13.0, Version 0.2, February 13, 2026 (ETR).