The Target of Evaluation (TOE) is Hewlett Packard Enterprise’s CX-4100i, CX-5420, CX-6100, CX-6200, CX-6300, CX-6400, CX-8100, CX-8320, CX-8325, CX-8325H, CX-8360, CX-8400, CX-9300, CX-9300s, and CX-10000 Switch Series running AOS-CX version 10.16. The TOE is a family of switches designed to support scalability, security and high performance for campus networks.
\r\nFor the purpose of evaluation, the TOE will be treated as a network device offering CAVP tested cryptographic functions, security auditing, secure administration, trusted updates, self-tests, and secure connections to other servers (e.g., to transmit audit records). The scope of the evaluation is limited to the NDcPP30e and SSH10 requirements.
\r\n\r\n
\r\n
","evaluation_configuration":"
The TOE consists of the following models all running AOS-CX version 10.16
\r\n\r\n
The evaluation was carried out in accordance to the Common Criteria Evaluation and Validation Scheme (CCEVS) requirements and guidance. The evaluation demonstrated that the TOE meets the security requirements contained in the Security Target. The criteria against which the TOE was judged are described in the Common Criteria for Information Technology Security Evaluation, Version 3.1, Revision 5, April 2017. The evaluation methodology used by the evaluation team to conduct the evaluation is the Common Methodology for Information Technology Security Evaluation, Evaluation Methodology, Version 3.1, Revision 5, April 2017. The product, when delivered and configured as identified in the Common Criteria Administrator Guidance, Target of Evaluation: 4100, 5000, 6000, 8000, 9000, and 10000 Switch Series, version 2.4, July 14, 2026 document, satisfies all of the security functional requirements stated in the Hewlett Packard Enterprise’s CX-4100i, CX-5420, CX-6100, CX-6200, CX-6300, CX-6400, CX-8100, CX-8320, CX-8325, CX-8325H, CX-8360, CX-8400, CX-9300, CX-9300S, and CX-10000 Switch Series running AOS-CX version 10.16 Security Target, Version 1.0, July 22, 2026. The project underwent CCEVS Validator review. The evaluation was completed in July 2026. Results of the evaluation can be found in the Common Criteria Evaluation and Validation Scheme Validation Report (report number CCEVS-VR-VID11653-2026) prepared by CCEVS.
\r\n\r\n
","environmental_strengths":"
The logical boundaries of the Hewlett Packard Enterprise’s CX-4100i, CX-5420, CX-6100, CX-6200, CX-6300, CX-6400, CX-8100, CX-8320, CX-8325, CX-8325H, CX-8360, CX-8400, CX-9300, CX-9300S, and CX-10000 Switch Series running AOS-CX version 10.16 are realized in the security functions that it implements. Each of these security functions is summarized below.
\r\n\r\n
Security audit:
\r\nThe TOE is able to generate logs for a wide range of security relevant events. The TOE can be configured to store the logs locally so they can be accessed by an administrator and also to send the logs to a designated log server using TLS to protect the logs while in transit on the network.
\r\nCryptographic support:
\r\nThe TOE provides CAVP certified cryptography in support of its SSHv2 and TLS v1.2/TLS v1.3 protocol implementations. Cryptographic services include key management, random bit generation, encryption/decryption, digital signature and secure hashing.
\r\nIdentification and authentication:
\r\nThe TOE requires users to be identified and authenticated before they can use functions mediated by the TOE, with the exception of passing network traffic in accordance with its configured switching rules and reading the login banner. It provides the ability to both assign attributes (user names, passwords and roles) and to authenticate users against these attributes.
\r\nSecurity management:
\r\nThe TOE provides Command Line Interface (CLI) commands over SSH and an HTTP over TLS (HTTPS) Graphical User Interface (GUI) to access the wide range of security management functions to manage its security policies. The TOE also offers HTTP over TLS protection for REST API interfaces that can be used for administration. All administrative activity and functions including security management commands are limited to authorized users (i.e., administrators) only after they have provided acceptable user identification and authentication data to the TOE. The security management functions are controlled through the use of roles that can be assigned to TOE users. The TOE supports the following roles: Administrators, Operators. The Administrator role can make changes to the TOE configuration while the Operator role is a read-only role.
\r\nProtection of the TSF:
\r\nThe TOE implements a number of measures to protect the integrity of its security features. The TOE protects stored passwords and cryptographic keys so they are not directly accessible in plaintext. The TOE also ensures that reliable time information is available for both log accountability and synchronization with the operating environment by providing a hardware clock. The TOE employs both dedicated communication channels as well as cryptographic means to protect communication between itself and other components in the operating environment. The TOE performs self-tests to detect failure and protect itself from malicious updates.
\r\nTOE access:
\r\nThe TOE can be configured to display a logon banner before and after (a post-login banner) a user session is established. The TOE also enforces inactivity timeouts for local and remote sessions.
\r\nTrusted path/channels:
\r\nThe TOE protects communication channels between itself and remote administrators using HTTPS/TLS and SSH. The SSH protocol is used to protect administrative connections utilizing the TOE’s command line interface (CLI). Additionally, web-based GUI and REST API programmatic interfaces are available for remote administration which are protected using HTTP over TLS (HTTPS/TLS).
\r\nThe TOE protects communication with network peers, such as a log server, using TLS connections to prevent unintended disclosure or modification of logs.
\r\n\r\n
\r\n
","features":[{"id":5625,"feature_name":"Auditing"},{"id":5626,"feature_name":"Certificate Validation"},{"id":5628,"feature_name":"Cryptograhic Key Generation"},{"id":5627,"feature_name":"Cryptographic Hashing"},{"id":5630,"feature_name":"Cryptographic Signature Generation"},{"id":5629,"feature_name":"Cryptographic Signature Verification"},{"id":5638,"feature_name":"Keyed-hash message authentication"},{"id":5637,"feature_name":"Network Device"},{"id":5636,"feature_name":"SSH Server"},{"id":5634,"feature_name":"TLS 1.2"},{"id":5635,"feature_name":"TLS 1.3"},{"id":5633,"feature_name":"TLS Client with Mutual Authentication"},{"id":5632,"feature_name":"TLS Server without Mutual Authentication"},{"id":5631,"feature_name":"Trusted Update Function"}]}