\r\n
\r\nSyslog Server (Mandatory)
\r\nThe Cisco Aggregation Services Router 1000 Series (ASR1K), Cisco Aggregation Services Router 1000 Series (ASR1K), Cisco Catalyst 8200, 8300, 8500 Series Edge Routers (Cat8K) are purpose-built, routing platforms that includes VPN functionality and MACsec encryption provided by the TOE hardware and the Cisco IOS-XE software.
\r\nThe TOE is a Network Device that includes VPN functionality and MACsec encryption as defined in NDcPPv3.0e, PKG_SSH_V1.0, MOD_VPNGW v1.3, and MOD_MACSEC_V1.0. The TOE is comprised of software, firmware and hardware. The hardware is comprised of the Cat8500 routers. The software is comprised of the Cisco Internet Operating System (IOS) XE software image Release IOS-XE 17.15. The firmware is comprised of the IOS Common Cryptographic Module (IC2M) Rel5a and the CoMira Mentor Questa Sim 10.7.
\r\nThe ASR1K routers aggregate multiple WAN connections and network services including encryption and traffic management, and forward them across WAN connections at line speeds. The routers contain both hardware and software redundancy in an industry-leading high-availability design. The ASR1K supports dual route processors, embedded services processors, and up to 200 Gbps throughput. The ASR1K provides IPsec connection capabilities to facilitate secure communications with external entities as required. The ASR1K is a purpose-built, routing platform that includes VPN functionality and MACsec encryption.
\r\nThe Cat8200, Cat8300 and Cat8500 Series Edge routers are purpose built for high performance and integrated services. They provide higher WAN port density, and redundant power supply capability. The Cat8300 and Cat8500 provide IPsec connection capabilities to facilitate secure communications with external entities as required. The Cat8300 and Cat8500 are purpose-built, routing platform that includes VPN functionality and MACsec encryption.
","evaluation_configuration":"The TOE consists of the models specified in Secuirty Target section 1.7 and includes Cisco IOS-XE version 17.15 software. Security Target Table 4 adds additional details on the physical characteristics of the TOE models. The TOE has two or more network interfaces and is connected to at least one internal and one external network.
\r\nThe following figure provides a visual depiction of an example TOE deployment:
\r\n\r\n
| \r\n \r\n \r\nTOE Boundary \r\n | \r\n
| \r\n \r\n \r\nSyslog Server (Mandatory) \r\n | \r\n
| \r\n \r\n \r\nManagement Workstation (Mandatory) \r\n | \r\n
| \r\n \r\n \r\nAAA Server (Mandatory) \r\n | \r\n
| \r\n \r\n \r\nVPN Peer | \r\n
| \r\n \r\n \r\nCA (Mandatory) \r\n | \r\n
| \r\n \r\n \r\nLocal Console (Mandatory) \r\n | \r\n
| \r\n \r\n \r\nMACsec Peer | \r\n
| \r\n \r\n \r\n
| \r\n
| \r\n \r\n \r\nNTP Server (Mandatory) \r\n | \r\n
\r\n
\r\n
The Figure 1 includes the following:
\r\nNOTE: While the previous figure includes several non-TOE IT environment devices, the TOE is only the Cat8500 devices. Only one TOE device is required for deployment of the TOE in the evaluated configuration.
","security_evaluation_summary":"The evaluation was carried out in accordance with the Common Criteria Evaluation and Validation Scheme (CCEVS) process and scheme. The evaluation demonstrated that the product meets the security requirements contained in the Security Target. The criteria against which the Cisco Aggregation Services Router 1000 Series (ASR1K), Cisco Catalyst 8200, 8300, 8500 Series Edge Routers (Cat8K) running IOS-XE 17.15 was judged are described in the Common Criteria for Information Technology Security Evaluation, Version 3.1, Revision 5. The evaluation methodology used by the evaluation team to conduct the evaluation is the Common Methodology for Information Technology Security Evaluation, Version 3.1, Revision 5. The product, when configured as identified in the Cisco Aggregation Services Router 1000 Series (ASR1K), Cisco Catalyst 8200, 8300, 8500 Series Edge Routers (Cat8K) running IOS-XE 17.15 Operational User Guidance and Preparative Procedures, Version 1.0, satisfies all of the security functional requirements stated in the Cisco Aggregation Services Router 1000 Series (ASR1K), Cisco Catalyst 8200, 8300, 8500 Series Edge Routers (Cat8K) running IOS-XE 17.15 Security Target, Version 1.2. The project underwent CCEVS Validator review. The evaluation was completed in September 2025. Results of the evaluation can be found in the Common Criteria Evaluation and Validation Scheme Validation Report (report number CCEVS-VR-VID11642-2025) prepared by CCEVS.
","environmental_strengths":"The TOE is comprised of several security features. Each of the security features identified above consists of several security functionalities, as identified below.
\r\nThese features are described in more detail in the subsections below. In addition, the TOE implements all RFCs of the NDcPPv3.0e, PKG_SSH_V1.0, MOD_VPNGW v1.3 and MOD_MACSEC_V1.0 as necessary to satisfy testing/assurance measures prescribed therein.
\r\nSecurity Audit
\r\nThe TOE provides extensive auditing capabilities. The TOE can audit events related to cryptographic functionality, identification and authentication, and administrative actions. 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 the administrator with a circular audit trail stored in persistent memory, with a configurable maximum size. When the log reaches the configured threshold, the TOE overwrites the oldest records. Audit logs are backed up over an encrypted channel to an external audit server.
\r\nCryptographic Support
\r\nThe TOE provides cryptography in support of other TOE security functionality. All the algorithms claimed have CAVP certificates for all processors listed in Security Target Table 4. The TOE leverages the IOS Common Cryptographic Module (IC2M) Rel5a (see table 5 in the Security Target for certificate references).
\r\nThe TOE provides cryptography in support of VPN connections and remote administrative management via SSHv2 and IPsec to secure the transmission of audit records to the remote syslog server. In addition, IPsec is used to secure the session between the TOE and the authentication servers.
\r\nThe cryptographic services provided by the TOE are described in the Table below:
\r\n| \r\n Cryptographic Method \r\n | \r\n\r\n Use within the TOE \r\n | \r\n
| \r\n Internet Key Exchange \r\n | \r\n\r\n Used to establish initial IPsec session. \r\n | \r\n
| \r\n Secure Shell Establishment \r\n | \r\n\r\n Used to establish initial SSH session. \r\n | \r\n
| \r\n RSA Signature Services \r\n | \r\n\r\n Used in IPsec session establishment. \r\nUsed in SSH session establishment. \r\n | \r\n
| \r\n SP 800-90 RBG \r\n | \r\n\r\n Used in IPsec session establishment. \r\nUsed in SSH session establishment. \r\nUsed for random number generation, key generation and seeds to asymmetric key generation \r\n | \r\n
| \r\n SHS \r\n | \r\n\r\n Used to provide IPsec traffic integrity verification \r\nUsed to provide SSH traffic integrity verification \r\nUsed for keyed-hash message authentication \r\n | \r\n
| \r\n AES \r\n | \r\n\r\n Used to encrypt IPsec session traffic. \r\nUsed to encrypt SSH session traffic. \r\nUsed to encrypt MACsec traffic | \r\n
| \r\n HMAC \r\n | \r\n\r\n Used for keyed hash, integrity services in IPsec and SSH session establishment. \r\n | \r\n
| \r\n RSA \r\n | \r\n\r\n Used in IKE protocols peer authentication \r\nUsed to provide cryptographic signature services | \r\n
| \r\n ECDSA \r\n | \r\n\r\n Used to provide cryptographic signature services | \r\n
| \r\n FFC DH \r\n | \r\n\r\n Used as the Key exchange method for IPsec \r\n | \r\n
| \r\n ECC DH \r\n | \r\n\r\n Used as the Key exchange method for SSH and IPsec \r\n | \r\n
\r\n
The TOE authenticates and encrypts packets between itself and a MACsec peer. The MACsec Key Agreement (MKA) Protocol provides the required session keys and manages the required encryption keys to protect data exchanged by the peers.
\r\nIdentification and authentication
\r\nThe TOE performs two types of authentication: device-level authentication of the remote device (VPN peers) and user authentication for the Authorized Administrator of the TOE. Device-level authentication allows the TOE to establish a secure channel with a trusted peer. The secure channel is established only after each device authenticates the other. Device-level authentication is performed via IKE/IPsec mutual authentication. The TOE supports use of IKEv2 pre-shared keys for authentication of IPsec tunnels. The TOE uses X.509v3 certificates as defined by RFC 5280 to support authentication for IPsec connections. The IKE phase authentication for the IPsec communication channel between the TOE and authentication server and between the TOE and syslog server is considered part of the Identification and Authentication security functionality of the TOE.
\r\nThe TOE provides authentication services for administrative users 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 can be configured to require a minimum password length of 15 characters. 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. The TOE supports the use of a RADIUS AAA server (part of the IT Environment) for authentication of administrative users attempting to connect to the TOE’s CLI.
\r\nThe TOE provides an automatic lockout when a user attempts to authenticate and enters invalid information. After a defined number of authentication attempts fail exceeding the configured allowable attempts, the user is locked out until an authorized administrator can enable the user account.
\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
Management of the TSF data is restricted to Security Administrators. The ability to enable, disable, determine and modify the behavior of all of the security functions of the TOE is restricted to authorized administrators.
\r\nAdministrators can create configurable login banners to be displayed at time of login and can also define an inactivity timeout for each admin interface to terminate sessions after a set period of inactivity.
\r\nThe TOE provides packet filtering and secure IPsec tunneling. The tunnels can be established between two trusted VPN peers. More accurately, these tunnels are sets of security associations (SAs). The SAs define the protocols and algorithms to be applied to sensitive packets and specify the keying material to be used. SAs are unidirectional and are established per the ESP security protocol. An authorized administrator can define the traffic that needs to be protected via IPsec by configuring access lists (permit, deny, log) and applying these access lists to interfaces using crypto map sets.
\r\nThe TOE is also capable of rejecting any MACsec PDUs in a given session that contain a SCI that is different from the one that is used to establish that session. The SCI is derived from the MACsec peer’s MAC address and port to uniquely identify the originator of the MACsec PDU. Only EAPOL (PAE EtherType 88-8E), MACsec frames (EtherType 88-E5), MAC control frames EtherType 0x876F are permitted in the MACsec communication between peers and others are discarded.
\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 IOS-XE is not a general-purpose operating system and access to Cisco IOS-XE memory space is restricted to only Cisco IOS-XE functions.
\r\nThe TOE is also able to detect replay of information received via secure channels (MACsec). The detection applied to network packets that terminate at the TOE, such as trusted communications between the TOE and an IT entity (e.g., MACsec peer). If replay is detected, the packets are discarded.
\r\nThe TOE has an internal clock; however, the TOE synchronizes time with an NTP server and then 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.
\r\nThe TOE is able to verify any software updates prior to the software updates being installed on the TOE to avoid the installation of unauthorized software. Whenever a failure occurs within the TOE that results in the TOE ceasing operation, the TOE securely disables its interfaces to prevent the unintentional flow of any information to or from the TOE and reloads.
\r\nFinally, the TOE performs testing to verify correct operation of the router itself and that of the cryptographic module.
\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. Sessions can also be terminated if an Authorized Administrator enters the “exit” or “logout” command.
\r\nThe TOE can also display a Security Administrator specified banner on the CLI management interface prior to allowing any administrative access to the TOE.
\r\nThe TOE allows trusted paths to be established to itself from remote administrators over SSHv2 which has the ability to be encrypted further using IPsec and initiates outbound IPsec tunnels to transmit audit messages to remote syslog servers. The TOE can also establish trusted paths of peer-to-peer IPsec sessions. The peer-to-peer IPsec sessions can be used for securing the communications between the TOE and authentication server/syslog server, as well as to protect communications with a CA. In addition, IPsec is used to secure communications between the TOE and external entities, including remote authentication servers and NTP servers (via NTPv4 over IPsec).
","features":[{"id":2394,"feature_name":"Asymmetric Key Generation"},{"id":2634,"feature_name":"Auditing"},{"id":2405,"feature_name":"Certificate Authentication"},{"id":2404,"feature_name":"Certificate Validation"},{"id":2402,"feature_name":"Cryptographic Hashing"},{"id":2395,"feature_name":"Cryptographic Key Establishment"},{"id":2399,"feature_name":"Cryptographic Signature Generation"},{"id":2400,"feature_name":"Cryptographic Signature Verification"},{"id":2397,"feature_name":"DRBG"},{"id":2392,"feature_name":"Flaw Remediation"},{"id":2408,"feature_name":"IKEv2"},{"id":2407,"feature_name":"IPsec"},{"id":2396,"feature_name":"Key Destruction"},{"id":2403,"feature_name":"Keyed-hash message authentication"},{"id":2412,"feature_name":"MACsec"},{"id":27,"feature_name":"Network Router"},{"id":2406,"feature_name":"SSH Server"},{"id":2417,"feature_name":"VPN Gateway"}]}