NIAP: Compliant Product
NIAP/CCEVS
  NIAP  »»  Product Compliant List  »»  Compliant Product  
Compliant Product - Cisco IR1101 Integrated Services Router

Certificate Date:  2020.02.24

Validation Report Number:  CCEVS-VR-VID11033-2020

Product Type:    Router
   Virtual Private Network
   Network Device

Conformance Claim:  Protection Profile Compliant

PP Identifier:    collaborative Protection Profile for Network Devices Version 2.1
  Extended Package for VPN Gateways Version 2.1

CC Testing Lab:  Acumen Security


CC Certificate [PDF] Security Target [PDF] Validation Report [PDF]

Assurance Activity [PDF]

Administrative Guide [PDF]


Product Description

The Target of Evaluation (TOE) is the IR1101 Integrated Services Router running Cisco IOS-XE 16.12

The TOE is comprised of both software and hardware. The hardware model included in the evaluation is: IR1101-K9.  The software is comprised of the Cisco IOS-XE 16.12.

The IR1101 consists of the following architectural features:

Cisco IOS-XE is a Cisco-developed highly configurable proprietary operating system that provides for efficient and effective routing and switching.  This TOE only addressed those functions that provide for the security of the TOE itself as described in Section 1.6 Logical Scope of the ST.

The TOE has two or more network interfaces and is connected to at least one internal and one external network.  The Cisco IOS-XE configuration determines how packets are handled to and from the TOE’s network interfaces.  The router 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


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 criteria against which the Cisco IR1101 Integrated Services Router was evaluated are described in the Common Criteria for Information Technology Security Evaluation, Version 3.1 rev 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 rev 5. 

The product, when delivered configured as identified in the Cisco IR1101 Integrated Services Router CC Configuration Guide, Version 1.0, Dated January, 30, 2020 satisfies all of the security functional requirements stated in the Cisco IR1101 Integrated Services Router Security Target, Version 1.0, Dated January 30, 2020. The project underwent CCEVS Validator review.  The evaluation was completed in February 2020.  Results of the evaluation can be found in the Common Criteria Evaluation and Validation Scheme Validation Report 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.

Security Audit

The 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 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.

Cryptographic Support

The TOE provides cryptography in support of other TOE security functionality. All the algorithms claimed have CAVP certificates (Operational Environment – ARM A53).  The TOE leverages the IOS Common Cryptographic Module (IC2M) Rel5 (see Table 1 for certificate references).

 Table 1:  FIPS References

Algorithm

Description

Supported Mode

Module

CAVP Cert. #

SFR

AES

Used for symmetric encryption/decryption

CBC (128, 192 and 256)
GCM (128 and 256)

IC2M

C462

FCS_COP.1/DataEncryption

SHS (SHA-1, SHA-256, SHA-384  and SHA-512)

Cryptographic hashing services

Byte Oriented

IC2M

C462

FCS_COP.1/Hash

HMAC (HMAC-SHA-1, SHA-256, SHA-512)

Keyed hashing services and digital signature

Byte Oriented

IC2M

C462

FCS_COP.1/KeyedHash

DRBG

Deterministic random bit generation services in accordance with ISO/IEC 18031:2011

CTR_DRBG (AES 256)

IC2M

C462

FCS_RBG_EXT.1

RSA

Signature Verification and key transport

PKCS#1 v.1.5, 3072 bit key,

FIPS 186-4 Key Gen

IC2M

C462

FCS_CKM.1
FCS_COP.1/SigGen

ECDSA

Cryptographic Signature services

FIPS 186-4, Digital Signature Standard (DSS)

IC2M

C462

FCS_CKM.1
FCS_COP.1/SigGen

CVL-KAS-ECC

Key Agreement

NIST Special Publication 800-56A

IC2M

C462

FCS_CKM.2

The 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.

The cryptographic services provided by the TOE are described in Table 2 below:

 

Table 2 TOE Provided Cryptography

Cryptographic Method

Use within the TOE

Internet Key Exchange

Used to establish initial IPsec session.

Secure Shell Establishment

Used to establish initial SSH session.

RSA Signature Services

Used in IPsec session establishment.

Used in SSH session establishment.

X.509 certificate signing

SP 800-90 RBG

Used in IPsec session establishment.

Used in SSH session establishment.

SHS

Used to provide IPsec traffic integrity verification

Used to provide SSH traffic integrity verification

Used for keyed-hash message authentication

AES

Used to encrypt IPsec session traffic.

Used to encrypt SSH session traffic.

RSA

Used in IKE protocols peer authentication

Used to provide cryptographic signature services

ECDSA

Used to provide cryptographic signature services
Used in Cryptographic Key Generation

FFC DH

Used as the Key exchange method for SSH and IPsec

ECC DH

Used as the Key exchange method for IPsec

 

Identification and authentication

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 The TOE supports use of IKEv1 (ISAKMP) and IKEv2 pre-shared keys for authentication of IPsec tunnels.

The TOE provides authentication services for administrative users to connect to the TOE’s secure CLI administrator interface.  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.

The TOE uses X.509v3 certificates as defined by RFC 5280 to support authentication for IPsec connections.

Security Management

The 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 supports two separate administrator roles: non-privileged administrator and privileged administrator.  Only the privileged administrator can perform the 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.

Packet Filtering

The TOE provides packet filtering and secure IPsec tunneling.  The tunnels can be established between two trusted VPN peers and the TOE.  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.

Protection of the TSF

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.

The TOE internally maintains the date and time.  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. 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.

The 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.

TOE Access

The 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. 

The TOE can also display a Security Administrator specified banner on the CLI management interface prior to allowing any administrative access to the TOE.

Trusted path/Channels

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.  IPsec is used to secure the session between the TOE and the authentication servers.  The TOE can 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. 

Excluded Functionality

The following functionality is excluded from the evaluation:

Table 3 Excluded Functionality

Excluded Functionality

Exclusion Rationale

Non-FIPS 140-2 mode of operation

This mode of operation includes non-FIPS allowed operations.

 

The FIPS 140-2 mode of operation will be enabled by configuration settings as described in the Guidance documents (AGD). The exclusion of non-FIPS 140-2 compliant functionality does not affect compliance to the NDcPP v2.1 and/or VPNGWEP v2.1.

 

 


Vendor Information


Cisco Systems, Inc.
Cert Team
410-309-4862
certteam@cisco.com

www.cisco.com
Site Map              Contact Us              Home