The TOE is the Aruba, a Hewlett Packard Enterprise Company 8320 and 8400 Switch Series running ArubaOS-CX version 10.01. The TOE is a family of switches designed to support scalability, security and high performance for campus networks. For the purpose of evaluation, the TOE was 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).
\r\n","evaluation_configuration":"\r\n\r\n
The evaluated configuration consists of the following devices running ArubaOS-CX version 10.01:
\r\n| \r\n Series Identifier \r\n | \r\n\r\n Hardware Models \r\n | \r\n
| \r\n Aruba 8320 Switch Series \r\n | \r\n\r\n JL479A – Aruba 8320 48p 10G SFP/SFP+ and 6p 40G QSFP+ Switch \r\nJL579A - Aruba 8320 32p 40G QSFP+ Switch \r\nJL581A - Aruba 8320 48p 1G/10GBase-T and 6p 40G QSFP+ Switch \r\n | \r\n
| \r\n Aruba 8400 Switch Series \r\n | \r\n\r\n JL376A – Aruba 8400 Bundle includes: \r\n· JL375A – Aruba 8400 8-slot chassis \r\n· JL363A – Aruba 8400 32p 10G SFP+ MACsec \r\n· JL365A – Aruba 8400 8p 40G QSFP+ Adv Module \r\n· JL367A – Aruba 7.2Tbps Fabric Module \r\n· JL368A – Management Module \r\nJL366A – Aruba 8400 6p 40G/100G QFSP 28p Adv Module \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 4, September 2012. 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 4, July 2012. The product, when delivered and configured as identified in the Common Criteria Admin Guide Network Device Collaboration Protection Profile, Target of Evaluation: Aruba 8320 and 8400 Switch Series, Version 1.1, October 24, 2018 document, satisfies all of the security functional requirements stated in the Aruba, a Hewlett Packard Enterprise Company 8320 and 8400 Switch Series (NDcPP20E) Security Target, Version 0.3, October 22, 2018. The project underwent CCEVS Validator review. The evaluation was completed in October 2018. Results of the evaluation can be found in the Common Criteria Evaluation and Validation Scheme Validation Report (report number CCEVS-VR-VID10919-2018) prepared by CCEVS.
","environmental_strengths":"\r\n\r\nThe logical boundaries of the Aruba, a Hewlett Packard Enterprise Company Aruba 8320 and 8400 Switches are realized in the security functions that it implements. Each of these security functions is summarized below.
\r\n\r\n\r\nSecurity 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 SSH to protect the logs while in transit on the network. Once configured to export audit records, the TOE attempts to transmit all logs in real-time, will temporarily maintain unsent records in the event of a disrupted syslog connection, and send those records when the remote audit server successfully reestablishes the connection.
\r\nCryptographic support:
\r\nThe TOE provides CAVP certified cryptography in support of its SSHv2 protocol implementation. 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 to access the wide range of security management functions to manage its security policies. 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 Administrators role can make changes to the TOE configuration while the Operators 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. The TOE employs both dedicated communication channels as well as cryptographic means to protect communication between itself and other components in the operation 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 interactive communication with administrators using SSH to protect the CLI interface, ensuring integrity and preventing disclosure. If the negotiation of an encrypted session fails or if the user does not have authorization for remote administration, an attempted connection will not be established.
\r\nThe TOE protects communication with network peers, such as a log server, using SSH connections to prevent unintended disclosure or modification of logs.
\r\n","features":[]}