The TOE is comprised of both software and hardware. The hardware is comprised of the following model series: 9200, 9300, 9400, 9500, and 9800. The software is comprised of the NX-OS software image Release10.4.
\r\nThe Cisco Nexus 9000 Series Switches that comprise the TOE have common hardware characteristics. These characteristics affect only non-TSF relevant functions of the switches (such as throughput and amount of storage) and therefore support security equivalency of the switches in terms of hardware. All security functionality is enforced on the Nexus 9000 Series switches.
\r\nNX-OS is a Cisco-developed highly configurable proprietary operating system that provides for efficient and effective routing and switching. Although NX-OS performs many networking functions, this TOE only addresses the functions that provide for the security of the TOE itself.
","evaluation_configuration":"The TOE consists of one or more switches and includes the NX-OS software. The TOE has two or more network interfaces and is connected to at least one internal and one external network. The Cisco NX-OS configuration determines how packets are handled to and from the TOE’s network interfaces. The switch configuration will determine how traffic flows received on an interface will be handled. Typically, packet flows are passed through the internetworking device and forwarded to their configured destination.
\r\nIf the TOE is to be remotely administered, then the management workstation must be connected to an internal network and SSHv2 must be used to securely connect to the TOE. Audit records are stored locally and are also remotely backed up to a remote syslog server. If these servers are used, they must be attached to the internal (trusted) network. The internal (trusted) network is meant to be separated effectively from unauthorized individuals and user traffic; one that is in a controlled environment where implementation of security policies can be enforced.
\r\nThe following models are included in the TOE:
\r\n| \r\n Series \r\n | \r\n\r\n Models \r\n | \r\n
| \r\n Nexus 9200 \r\n | \r\n\r\n N9K- C92348GC-X \r\n | \r\n
| \r\n Nexus 9300 \r\n | \r\n\r\n N9K-C93108TC-FX, N9K-C9348GC-FXP, N9K-C93216TC-FX2, N9K-C93180YC-FX, \r\nN9K-C93240YC-FX2, N9K-C93360YC-FX2, N9K-C9364C, N9K-C9332C, N9K-C9336C-FX2, \r\nN9K-C9364C-GX, N9K-C9316D-GX, N9K-C93600CD-GX, N9K-C93400LD-H1 \r\n | \r\n
| \r\n Nexus 9400 \r\n | \r\n\r\n N9K-C9400-Sup-A \r\n | \r\n
| \r\n Nexus 9500 \r\n | \r\n\r\n N9K-C9504, N9K-C9508, N9K-C9516, N9K-SUP-A+, N9K-SUP-B+, N9K-SC-A \r\n | \r\n
| \r\n Nexus 9800 \r\n | \r\n\r\n N9K-C9804, N9K-C9808 \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 Cisco Nexus 9000 Series Switches Running NX-OS 10.4 Common Criteria Operational User Guidance and Preparative Procedures, Version 0.9, January 21, 2025 document, satisfies all of the security functional requirements stated in the Cisco Nexus 9000 Series Switches running on NX-OS 10.4 Security Target, Version 0.9, January 21, 2025. The project underwent CCEVS Validator review. The evaluation was completed in January 2025. Results of the evaluation can be found in the Common Criteria Evaluation and Validation Scheme Validation Report (report number CCEVS-VR-VID11514-2025) prepared by CCEVS.
\r\n","environmental_strengths":"
The logical boundaries of the Cisco Nexus 9000 Series Switches Running NX-OS 10.4 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 provides extensive capabilities to generate audit data targeted at detecting such activity. The TOE generates an audit record for each auditable event. Each security relevant audit event has the date, timestamp, event description, and subject identity. The administrator configures auditable events, performs back-up operations, and manages audit data storage. The TOE provides circular audit trail. Audit logs are transmitted to an external audit server over a trusted channel protected with TLS.
\r\nThe auditable events include:
\r\nThe authorized administrator configures auditable events, performs back-up operations, and manages audit data storage. The TOE is configured to transmit the audit messages to an external syslog server. Communication with the syslog server is protected by using TLS and the TOE can determine when communication with the syslog server fails. In the presence of a TLS communication failure, the TOE will continuously and automatically re-attempt to reestablish the syslog connection in case of a network disruption. In the case of a TLS protocol failure the administrator should review the configuration of both the TOE and the syslog server.
\r\nThe audit logs can be viewed on the TOE using the appropriate NX-OS commands. The records include the date/time the event occurred, the event/type of event, the user associated with the event, and additional information of the event and its success and/or failure. The TOE does not have an interface to modify audit records, though there is an interface available for the authorized administrator to clear (delete) audit data stored locally on the TOE.
\r\nCryptographic support:
\r\nThe TOE provides cryptography in support of other TOE security functionality. All the algorithms claimed have CAVP certificates (Operation Environment – Intel Xeon processor). All the algorithms claimed have CAVP certificates.
\r\nThe NX-OS software calls the CiscoSSL FOM Cryptographic implementation version 7.3a and has been validated for conformance to the requirements of FIPS 140-2 Level 1.
\r\nThe TOE provides cryptography in support of remote administrative management via SSHv2 and secure the session between the TOE and remote syslog server using TLS.
\r\nIdentification and authentication:
\r\nThe TOE performs one type of authentication: authentication for the Authorized Administrator of the TOE using a local user database.
\r\nThe TOE provides authentication services for administrative users wishing to connect to the TOE’s secure CLI administrator interface. The TOE requires Authorized Administrators to authenticate prior to being granted access to any of the management functionality. The TOE is configured to require a minimum password length of 8 characters as well as password-strength checking that disables the use of weak passwords. The TOE provides administrator authentication against a local user database. Password-based authentication can be performed on the serial console or SSH interfaces. The SSHv2 interface also supports authentication using SSH keys.
\r\nAfter a configurable number of incorrect login attempts, Cisco Nexus 9K Series will lockout the account until an Authorized Administrator takes action.
\r\nThe TOE uses X.509v3 certificates as defined by RFC 5280 to support authentication for TLS connections.
\r\nSecurity management:
\r\nThe TOE provides secure administrative services for management of general TOE configuration and the security functionality provided by the TOE. All TOE administration occurs either through a secure SSHv2 session or via a local console connection. The TOE provides the ability to securely manage:
\r\n\r\n
The Cisco Nexus 9K Series switch supports the following predefined roles:
\r\nAll administrators are considered to be security administrators in this ST. The Cisco Nexus 9K Series has a CLI that can be administered either remotely using SSHv2 or locally via a console that is directly connected via a serial cable.
\r\nProtection of the TSF:
\r\nThe TOE protects against interference and tampering by untrusted subjects by implementing identification, authentication, and access controls to limit configuration to Authorized Administrators. The TOE prevents reading of cryptographic keys and passwords. Additionally, Cisco NX-OS is not a general-purpose operating system and access to Cisco NX-OS memory space is restricted to only Cisco NX-OS functions.
\r\nThe TOE internally maintains the date and time. This date and time are used as the timestamp that is applied to audit records generated by the TOE. Administrators can update the TOE’s clock manually. Finally, the TOE performs testing to verify correct operation of the router itself and that of the cryptographic module.
\r\nThe TOE can verify any software updates prior to the software updates being installed on the TOE to avoid the installation of unauthorized software.
\r\nTOE access:
\r\nThe TOE can terminate inactive sessions after an Authorized Administrator configurable time-period. Once a session has been terminated the TOE requires the user to re-authenticate to establish a new session. The administrator can also terminate their own session by exiting out of the CLI.
\r\nThe TOE can also display an Authorized Administrator specified banner on the CLI management interface prior to allowing any administrative access to the TOE.
\r\nTrusted path/channels:
\r\nThe TOE allows trusted paths to be established to itself from remote administrators over SSHv2 for remote CLI access. Nexus 9K also allows a trusted channel to be established with a syslog server using TLS.
","features":[{"id":542,"feature_name":"Asymmetric Key Generation"},{"id":539,"feature_name":"Auditing"},{"id":556,"feature_name":"Certificate Authentication"},{"id":547,"feature_name":"Certificate Validation"},{"id":545,"feature_name":"Cryptographic Hashing"},{"id":543,"feature_name":"Cryptographic Key Establishment"},{"id":544,"feature_name":"Cryptographic Signature Verification"},{"id":541,"feature_name":"DRBG"},{"id":540,"feature_name":"Key Destruction"},{"id":546,"feature_name":"Keyed-hash message authentication"},{"id":625,"feature_name":"Network Switch"},{"id":552,"feature_name":"SSH Server"},{"id":549,"feature_name":"TLS 1.2"},{"id":548,"feature_name":"TLS Client"}]}