The TOE is comprised of both software and hardware. The hardware models included in the evaluation are: ESR-6300-NCP-K9 and ESR-6300-CON-K9. The software is comprised of the Cisco IOS-XE 17.3.
\r\nThe ESR6300 consists of the following architectural features:
\r\n· Compact 3” x 3.75” form factor optimized for custom PC/104 solutions
\r\n· DRAM: 4-GB DDR4 memory capacity
\r\n· Flash Memory: 4-GB usable eMMC flash
\r\n· Interface Support
\r\n· Console: 1 UART RS232 RJ45 console port
\r\n· WAN Interfaces: 2 Combo Layer 3 GE WAN ports
\r\n· LAN Interfaces: 4 Layer 2 GE LAN ports
\r\nThe ESR6300 is an embedded router module with a compact form factor of 3.0 by 3.775 inches. Its compact, modular, ruggedized design allows Cisco partners and integrators to build a wide variety of custom embedded solutions. The TOE can be inserted into an enclosure that can accommodate the TOE's size (3.0 x 3.775 in) and provides no compute capabilities. The ESR6300 is available with a custom-designed cooling plate, as well as without the cooling plate. Both versions of the ESR6300 board include an integrated multi-pin Board-to-Board (BTB) interface connector with pins dedicated for power input, ethernet ports, and console ports. The TOE functionality is implemented inside the ESR 6300 physical chassis, as the chassis includes the underlying board (with or without a cooling plate) and all electronic components attached to it; therefore, no computational capabilities outside of the TOE boundary are required to secure the TOE. .
","evaluation_configuration":"The TOE is comprised of both software and hardware. The hardware models included in the evaluation are: ESR-6300-NCP-K9 and ESR-6300-CON-K9. The software is comprised of the Cisco IOS-XE 17.3.
","security_evaluation_summary":"The evaluation was carried out in accordance to the Common Criteria Evaluation and Validation Scheme (CCEVS) requirements and guidance. The criteria against which the TOE was judged are described in the Common Criteria for Information Technology Security Evaluation, Version 3.1, Revision 5, September 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, July 2017. The product, when delivered and configured as identified in the Cisco Embedded Services Router (ESR) 6300 CC Configuration Guide, Version 1.0, March 15, 2020 document, satisfies all of the security functional requirements stated in the Cisco Embedded Services Router (ESR) 6300 Security Target, Version 1.0, April 28, 2021. The project underwent CCEVS Validator review. The evaluation was completed in May 2021. Results of the evaluation can be found in the Common Criteria Evaluation and Validation Scheme Validation Report prepared by CCEVS.
","environmental_strengths":"The logical boundaries of the TOE are realized in the security functions that it implements. Each of these security functions is summarized below.
\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. The TOE is configured to transmit its audit messages to an external syslog server over an encrypted channel.
\r\nCryptographic support:
\r\nThe TOE provides cryptography in support of other TOE security functionality. All the algorithms claimed have CAVP certificates (Operational Environment – Marvell Armada ARMv8 Cortex A72). The TOE leverages the IOS Common Cryptographic Module (IC2M) Rel5.
\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\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 IKEv1 (ISAKMP) and IKEv2 pre-shared keys for authentication of IPsec tunnels. 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 exceeding the configured allowable attempts, the user is locked out until an authorized administrator can enable the user account.
\r\nThe TOE uses X.509v3 certificates as defined by RFC 5280 to support authentication for IPsec 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\nAdministration of the TOE locally and remotely;
\r\nAll TOE administrative users;
\r\nAll identification and authentication;
\r\nAll audit functionality of the TOE;
\r\nAll TOE cryptographic functionality;
\r\nThe timestamps maintained by the TOE;
\r\nUpdate to the TOE and verification of the updates;
\r\nConfiguration of IPsec functionality.
\r\nThe TOE supports two separate administrator roles: non-privileged administrator and privileged administrator. Only the privileged administrator can perform the above security relevant management functions. 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\nPacket filtering:
\r\nThe TOE provides packet filtering and secure IPsec tunneling. The tunnels can be established between two trusted VPN peers and the TOE. 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\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 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 internally maintains the date and time. This date and time is 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 is able to verify any software updates prior to the software updates being installed on the TOE to avoid the installation of unauthorized software.
\r\nWhenever 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\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\nTrusted path/channels:
\r\nThe TOE allows trusted paths to be established to itself from remote administrators over SSHv2, and initiates outbound IPsec tunnels to transmit audit messages to remote syslog servers. In addition, IPsec is used to secure the session between the TOE and the authentication 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 or remote administrative console.
","features":[]}