{"product_id":10600,"v_id":10600,"product_name":"Cisco Integrated Services Router 4400 Series (ISR-4400), IOS XE 3.13.0","certification_status":"Certified","certification_date":"2015-02-12T00:00:00Z","tech_type":"Network Device, Network Switch, Virtual Private Network","vendor_id":{"name":"Cisco Systems, Inc.","website":"https://www.cisco.com"},"vendor_poc":"Cert Team","vendor_phone":"+1 410-309-4862","vendor_email":"certteam@cisco.com","assigned_lab":{"cctl_name":"Leidos Common Criteria Testing Laboratory"},"product_description":"<p class=\"Default\">The Cisco Integrated Services Router 4400 Series (ISR-4400) TOE is a purpose-built, routing platform that includes VPN functionality. It is a router platform that provides connectivity and security services onto a single, secure device. In support of the VPN capabilities, the Cisco ISR-4400 provides IPsec connection capabilities for VPN enabled clients connecting through the TOE.&nbsp; The TOE offers encryption acceleration, voice- and video-capable architecture, application firewall, call processing, and embedded services. In addition, the platform supports a range of wired connectivity options such as T1/E1, T3/E3, and fiber Gigabit Ethernet</p>","evaluation_configuration":"","security_evaluation_summary":"<p class=\"Default\">The evaluation was carried out in accordance with the Common Criteria Evaluation and Validation Scheme (CCEVS) process and scheme. The criteria against which the Cisco ISR-4400 routers were judged are described in the Common Criteria for Information Technology Security Evaluation, Version 3.1 rev 4.&nbsp; The evaluation methodology used by the evaluation team to conduct the evaluation is the Common Methodology for Information Technology Security Evaluation, Version 3.1 rev 4.&nbsp; Leidos (formerly SAIC) determined that the evaluation assurance level (EAL) for the product is EAL 1.&nbsp; The product, when delivered configured as identified in the <em>Cisco ISR-4400 Common Criteria Operational User Guidance and Preparative Procedures</em> document, satisfies all of the security functional requirements stated in the&nbsp;<em>Cisco Integrated Services Router (ISR-4400) Security Target&nbsp;(Version 0.5).</em> The project underwent CCEVS Validator review.&nbsp; The evaluation was completed in February 2015.&nbsp; Results of the evaluation can be found in the Common Criteria Evaluation and Validation Scheme Validation Report prepared by CCEVS.</p>","environmental_strengths":"<p><strong><em>Security Audit</em></strong></p>\r\n<p>The Cisco ISR-4400 provides extensive auditing capabilities. The TOE can audit events related to cryptographic functionality, identification and authentication, and administrative actions. The Cisco ISR-4400 generates an audit record for each auditable event.&nbsp; 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 audit trail protection by providing remote backup to a syslog server over an encrypted channel.</p>\r\n<p><strong><em>Cryptographic Support</em></strong></p>\r\n<p>The TOE provides cryptography in support of other Cisco ISR-4400 security functionality. This cryptography has been validated for conformance to the requirements of FIPS 140-2 Level 2. The TOE provides cryptography in support of VPN connections and remote administrative management via SSHv2. The cryptographic services provided by the TOE are: Internet Key Exchange, Secure Shell Establishment, RSA/DSA Signature Services, SP 800-90 RBG, SHS, and AES.</p>\r\n<p>The TOE can also use the X.509v3 certificate for securing IPsec and SSH sessions.</p>\r\n<p><strong><em>Full Residual Data Protection</em></strong></p>\r\n<p>The TOE ensures that all information flows from the TOE do not contain residual information from previous traffic.&nbsp; Packets are padded with zeroes.&nbsp; Residual data is never transmitted from the TOE.</p>\r\n<p><strong><em>Identification and Authentication</em></strong></p>\r\n<p>The 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.&nbsp; Device-level authentication allows the TOE to establish a secure channel with a trusted peer.&nbsp; The secure channel is established only after each device authenticates the other.&nbsp; Device-level authentication is performed via IKE/IPsec mutual authentication.&nbsp; 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.&nbsp;&nbsp;</p>\r\n<p>The TOE provides authentication services for administrative users to connect to the TOE&rsquo;s secure CLI administrator interface.&nbsp; The TOE requires Authorized Administrators to authenticate prior to being granted access to any of the management functionality.&nbsp; The TOE can be configured to require a minimum password length of 15 characters as well as mandatory password complexity rules.&nbsp; The TOE provides administrator authentication against a local user database.&nbsp; Password-based authentication can be performed on the serial console or SSH interfaces.&nbsp; The SSHv2 interface also supports authentication using SSH keys.&nbsp; The TOE optionally supports use of a RADIUS or TACACS+ AAA server (part of the IT Environment) for authentication of administrative users attempting to connect to the TOE&rsquo;s CLI.</p>\r\n<p>The TOE provides an automatic lockout when a user attempts to authenticate and enters invalid information.&nbsp; 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.&nbsp;</p>\r\n<p>The TOE uses X.509v3 certificates as defined by RFC 5280 to support authentication for IPsec, and SSH connections.</p>\r\n<p><strong><em>Security Management</em></strong></p>\r\n<p>The TOE provides secure administrative services for management of general TOE configuration and the security functionality provided by the TOE.&nbsp; All TOE administration occurs either through a secure SSHv2 session or via a local console connection.&nbsp; The TOE provides the ability to securely manage: all TOE administrative users, all identification and authentication, all audit functionality of the TOE, all TOE cryptographic functionality, the timestamps maintained by the TOE, update to the TOE and TOE configuration file storage and retrieval.&nbsp;</p>\r\n<p>The TOE supports two separate administrator roles: non-privileged administrator and privileged administrator.&nbsp; Only the privileged administrator can perform the above security relevant management functions.</p>\r\n<p>Administrators 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.</p>\r\n<p><strong><em>Packet Filtering</em></strong></p>\r\n<p>The TOE provides packet filtering and secure IPsec tunneling.&nbsp; The tunnels can be established between two trusted VPN peers as well as between remote VPN clients and the TOE.&nbsp; More accurately, these tunnels are sets of security associations (SAs).&nbsp; The SAs define the protocols and algorithms to be applied to sensitive packets and specify the keying material to be used.&nbsp; SAs are unidirectional and are established per the ESP security protocol.&nbsp; 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.</p>\r\n<p><strong><em>Protection of the TSF</em></strong></p>\r\n<p>The 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.&nbsp;</p>\r\n<p>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.</p>\r\n<p>The TOE internally maintains the date and time.&nbsp; This date and time is used as the timestamp that is applied to audit records generated by the TOE.&nbsp; Administrators can update the TOE&rsquo;s clock manually, or can configure the TOE to use NTP to synchronize the TOE&rsquo;s clock with an external time source.&nbsp; Finally, the TOE performs testing to verify correct operation of the router itself and that of the cryptographic module.</p>\r\n<p>The TOE is able to verify any software updates prior to the software updates being installed on the TOE to avoid the installation of malicious software.</p>\r\n<p>The TOE also supports direct connections from VPN clients, and protects against threats related to those client connections. The TOE disconnects sessions that have been idle too long, can be configured to deny sessions based on IP, time, and day, and can be configured to NAT external IPs of connecting VPN clients to internal network addresses.</p>\r\n<p><strong><em>TOE Access</em></strong></p>\r\n<p>The TOE can terminate inactive sessions after an Authorized Administrator configurable time-period.&nbsp; Once a session has been terminated the TOE requires the user to re-authenticate to establish a new session.&nbsp;</p>\r\n<p>The TOE can also display an Authorized Administrator specified banner on the CLI management interface prior to allowing any administrative access to the TOE.</p>\r\n<p><strong><em>Trusted Path/Channels</em></strong></p>\r\n<p>The 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.&nbsp; In addition, IPsec is used to secure the session between the TOE and the authentication servers.&nbsp; The TOE can also establish trusted channels of peer-to-peer IPsec sessions.&nbsp; The peer-to-peer IPsec sessions can be used for securing the communications between the TOE and authentication server/syslog server.</p>","features":[]}