Cisco Aggregation Services Router (ASR) 900 Series

Transcription

1 Cisco Aggregation Services Router (ASR) 900 Series Security Target Version March 2015

2 Table of Contents 1 SECURITY TARGET INTRODUCTION ST AND TOE REFERENCE TOE OVERVIEW TOE Product Type Supported non-toe Hardware/ Software/ Firmware TOE DESCRIPTION TOE EVALUATED CONFIGURATION PHYSICAL SCOPE OF THE TOE LOGICAL SCOPE OF THE TOE Security audit Cryptographic support User Data Protection Identification and Authentication Security Management Protection of the TSF TOE Access Trusted path/channels EXCLUDED FUNCTIONALITY CONFORMANCE CLAIMS COMMON CRITERIA CONFORMANCE CLAIM PROTECTION PROFILE CONFORMANCE PROTECTION PROFILE CONFORMANCE CLAIM RATIONALE TOE Appropriateness TOE Security Problem Definition Consistency Statement of Security Requirements Consistency SECURITY PROBLEM DEFINITION ASSUMPTIONS THREATS ORGANIZATIONAL SECURITY POLICIES SECURITY OBJECTIVES SECURITY OBJECTIVES FOR THE TOE SECURITY OBJECTIVES FOR THE ENVIRONMENT SECURITY REQUIREMENTS CONVENTIONS TOE SECURITY FUNCTIONAL REQUIREMENTS Security audit (FAU) Cryptographic Support (FCS) User data protection (FDP) Identification and authentication (FIA) Security management (FMT) Protection of the TSF (FPT) TOE Access (FTA) Page 2 of 52

3 5.2.1 Trusted Path/Channels (FTP) TOE SFR DEPENDENCIES RATIONALE FOR SFRS FOUND IN NDPP SECURITY ASSURANCE REQUIREMENTS SAR Requirements Security Assurance Requirements Rationale ASSURANCE MEASURES TOE SUMMARY SPECIFICATION TOE SECURITY FUNCTIONAL REQUIREMENT MEASURES ANNEX A: KEY ZEROIZATION KEY ZEROIZATION ANNEX B: REFERENCES Page 3 of 52

4 List of Tables TABLE 1: ACRONYMS... 5 TABLE 2 TERMINOLOGY... 6 TABLE 3: ST AND TOE IDENTIFICATION... 8 TABLE 4 IT ENVIRONMENT COMPONENTS... 9 TABLE 5 ASR 902 CHASSIS REFERENCES TABLE 6 ASR 903 CHASSIS REFERENCES TABLE 7 ASR 920 (12CZ-A/12CD-D) CHASSIS REFERENCES TABLE 8 ASR 920 (4SZ/4SZ-A) CHASSIS REFERENCES TABLE 9 FIPS REFERENCES TABLE 10 TOE PROVIDED CRYPTOGRAPHY TABLE 11 EXCLUDED FUNCTIONALITY TABLE 12 PROTECTION PROFILES TABLE 13 TOE ASSUMPTIONS TABLE 14 THREATS TABLE 15 ORGANIZATIONAL SECURITY POLICIES TABLE 16 SECURITY OBJECTIVES FOR THE TOE TABLE 17 SECURITY OBJECTIVES FOR THE ENVIRONMENT TABLE 18 SECURITY FUNCTIONAL REQUIREMENTS TABLE 19 AUDITABLE EVENTS TABLE 20: ASSURANCE MEASURES TABLE 21 ASSURANCE MEASURES TABLE 22 HOW TOE SFRS MEASURES TABLE 23: TOE KEY ZEROIZATION TABLE 24: REFERENCES Page 4 of 52

5 List of Acronyms The following acronyms and abbreviations are common and may be used in this Security Target: Acronyms/Abbreviations AAA AES BGP Bridge Domain BSC BTS CC CE CEM CLI CM DH DHCP EAL EFP ENI EtherChannel EVC FIPS GE HA HMAC HTTPS IS-IS IT LAN MEF MSC NDPP NNI NTP OS OSPF Table 1: Acronyms Definition Administration, Authorization, and Accounting Advanced Encryption Standard Border Gateway Protocol. An inter-domain routing protocol designed to provide loop-free routing between separate routing domains that contain independent routing policies (autonomous systems) A bridge domain is a local broadcast domain that is VLAN-ID-agnostic. Base Station Controllers Base Transceiver Stations Common Criteria for Information Technology Security Evaluation Carrier Ethernet Common Evaluation Methodology for Information Technology Security Command Line Interface Configuration Management Diffie-Hellman Dynamic Host Configuration Protocol Evaluation Assurance Level Ethernet Flow Point. An EFP service instance is a logical interface that connects a bridge domain to a physical port or to an EtherChannel group in a router. Enhanced Network Interfaces (ENIs). An ENI is typically a user-network facing interface and has the same default configuration and functionality as UNIs, but can be configured to support protocol control packets for Cisco Discovery Protocol (CDP), Spanning-Tree Protocol (STP), EtherChannel Link Aggregation Control Protocol (LACP). An EtherChannel bundles individual Ethernet links into a single logical link that provides the aggregate bandwidth of up to eight physical links. Ethernet Virtual Connection., a conceptual service pipe within the service provider network. Federal Information Processing Standard Gigabit Ethernet port High Availability (device or component failover) Hashed Message Authentication Code Hyper-Text Transport Protocol Secure Intermediate System to Intermediate System. An Open System Interconnection (OSI) protocol that specifies how routers communicate with routers in different domains. Information Technology Local Area Network Metro-Ethernet Forum. A MEF defines Ethernet Virtual Connection (EVC) as an association between two or more user network interfaces that identifies a point-topoint or multipoint-to-multipoint path within the service provider network. Mobile Switching Center Network Device Protection Profile Network Node Interfaces (NNIs) to connect to the service provider network Network Time Protocol Operating System Open Shortest Path First. An interior gateway protocol (routes within a single Page 5 of 52

6 Acronyms/Abbreviations Definition autonomous system). A link-state routing protocol which calculates the shortest path to each node. PP Protection Profile RAN Radio Access Network RSP Route Switch Processor QoS Quality of Service SFP Small form-factor pluggable port SHS Secure Hash Standard SSHv2 Secure Shell (version 2) ST Security Target TCP TDM Trunk Port TSC TSF TSP UNI WAN VLAN Transport Control Protocol Time-division multiplexing. Is a method of putting multiple data streams in a single transmission signal, separating the signal into many segments, each having a very short duration, hence each data stream having their own time slot on the channel. A port that sends and receives tagged frames on all VLANs, except the native VLAN, if one is configured. Frames belonging to the native VLAN do NOT carry VLAN tags when sent over the trunk. Conversely, if an untagged frame is received on a trunk port, the frame is associated with the native VLAN configured on that port. TSF Scope of Control TOE Security Function TOE Security Policy User Network Interfaces (UNIs) to connect to customer networks. Wide Area Network Virtual Local Area Network Terminology Term Authorized Administrator Peer router Privilege level Remote VPN Gateway/Peer Security Administrator User Vty Table 2 Terminology Definition Any user which has been assigned to a privilege level that is permitted to perform all TSFrelated functions. Another router on the network that the TOE interfaces with. Assigns a user specific management access to the TOE to run specific commands. The privilege levels are from 1-15 with 15 having full administrator access to the TOE similar to root access in UNIX or Administrator access on Windows. Privilege level 1 has the most limited access to the CLI. By default when a user logs in to the Cisco IOS, they will be in user EXEC mode (level 1). From this mode, the administrator has access to some information about the TOE, such as the status of interfaces, and the administrator can view routes in the routing table. However, the administrator can't make any changes or view the running configuration file. The privilege levels are customizable so that an Authorized Administrator can also assign certain commands to certain privilege levels. A remote VPN Gateway/Peer is another network device that the TOE sets up a VPN connection with. This could be a VPN client or another router. Synonymous with Authorized Administrator for the purposes of this evaluation. Any entity (human user or external IT entity) outside the TOE that interacts with the TOE. vty is a term used by Cisco to describe a single terminal (whereas Terminal is more of a verb or general action term). Page 6 of 52

7 DOCUMENT INTRODUCTION Prepared By: Cisco Systems, Inc. 170 West Tasman Dr. San Jose, CA This document provides the basis for an evaluation of a specific Target of Evaluation (TOE), the Aggregation Services Router (ASR) 900 Series. This Security Target (ST) defines a set of assumptions about the aspects of the environment, a list of threats that the product intends to counter, a set of security objectives, a set of security requirements, and the IT security functions provided by the TOE which meet the set of requirements. Page 7 of 52

8 1 SECURITY TARGET INTRODUCTION The Security Target contains the following sections: Security Target Introduction [Section 1] Conformance Claims [Section 2] Security Problem Definition [Section 3] Security Objectives [Section 4] IT Security Requirements [Section 5] TOE Summary Specification [Section 6] Rationale [Section 7] The structure and content of this ST comply with the requirements specified in the Common Criteria (CC), Part 1, Annex A, and Part 3, Chapter ST and TOE Reference This section provides information needed to identify and control this ST and its TOE. Table 3: ST and TOE Identification Name Description ST Title Cisco Aggregation Services Router (ASR) 900 Series Security Target ST Version 1.0 Publication Date 26 March 2015 Developer and Cisco Systems, Inc. ST Author TOE Reference Cisco Aggregation Services Router (ASR) 900 Series TOE Hardware Models ASR 902 and 903 including the RSP (RSP1A-55, RSP1B-55, RSP2A-64 and RSP2A- 128) and 920 (ASR CZ-A, ASR CZ-D, ASR-920-4SZ-A and ASR SZ-D) TOE Software IOS-XE 3.13.(1)S Version Keywords Audit, Authentication, Encryption, Protection, Router, Traffic 1.2 TOE Overview The Cisco Aggregation Services Router (ASR) 900 Series TOE are full-featured, modular aggregation platforms. They are designed for the cost-effective delivery of converged mobile, residential, and business services. The TOE provides scalable feature set of layer 2 switching and layer 3 routing services, redundancy, low power consumption, and high service scale in routers optimized for small aggregation and remote point-of-presence (POP) applications. The TOE consists of any one of a number of hardware configurations as noted above in Table 3: ST and TOE Identification. Each of the hardware configurations run the same version of IOS- XE software. The Cisco ASR 902 Router uses the same design as the Cisco ASR 903 Router, Page 8 of 52

9 but due to its smaller size, it has four interface module cards and one Route Switch Processor (RSP) card. The RSP card is the centralized card in the system performing the data plane, network timing, and control plane functions for the system. All components support online replacement and field upgrades, with the exception of the RSP card, which requires the system to be brought down for a replacement or upgrade. The Cisco ASR 920 Router comes in multiple versions with different port densities that include ASR CZ-A, ASR CZ-D, ASR-920-4SZ-A and ASR-920-4SZ-D. Cisco IOS-XE is a Cisco-developed highly configurable proprietary operating system that provides for efficient and effective routing. Although IOS-XE performs many networking functions, this TOE only addresses the functions that provide for the security of the TOE itself as described in Section TOE logical scope below TOE Product Type The Cisco Aggregation Services Router (ASR) 900 Series are temperature hardened, highthroughput, small form factor, low-power-consumption routers optimized for mobile backhaul, residential, and business service applications. The ASR 900 Series supports broadband access for delivering voice, video, data, and mobility services. Designed to support thousands of subscribers, QoS on the ASR 920 Series can scale up to a large number of queues per device. The ASR 900 Series are a full-featured Layer 2 switch and Layer 3 router that supports a variety of broadband applications, including IPTV and video on demand Supported non-toe Hardware/ Software/ Firmware The TOE supports (in some cases optionally) the following hardware, software, and firmware in its environment: Table 4 IT Environment Components Component Required Usage/Purpose Description for TOE performance Management Workstation with SSH Client Yes This includes any IT Environment Management workstation with a SSH client installed that is used by the TOE administrator to support TOE administration through SSH protected channels. Any SSH client that supports SSHv2 may be used. NTP Server No The TOE supports communications with an NTP server to synchronize date and time. Syslog server Yes The syslog audit server is used for remote storage of audit records that have been generated by and transmitted from the TOE. RADIUS or TACACS+ AAA Server No This includes any IT environment RADIUS or TACACS+ AAA server that provides authentication services to TOE administrators. Page 9 of 52

10 1.3 TOE DESCRIPTION This section provides an overview of the Cisco Aggregation Services Router (ASR) 900 Series Target of Evaluation (TOE). This section also defines the TOE components included in the evaluated configuration of the TOE. The TOE consists of a number of components including: Chassis: The TOE chassis is designed for low power consumption, line rate performance for all Layer 2 and Layer 3 interfaces, the different hardware configuration options include 3-RU modular chassis and slots to support various cards and processors. There are also flexible clocking options, and redundant power and cooling. The chassis is the component of the TOE in which all other TOE components are housed. Route/Switch Processor (RSP) as noted above, this card the centralized card in the system performing the data plane, network timing, and control plane functions for the system. The four supported RSP cards, RSP1A-55, RSP1B-55, RSP2A-64 and RSP2A- 128 are very similar in their performance, switching capabilities, interface (port) density, can be installed in both the ASR902 and ASR903. The differences are mainly in the services support scalability such as the amount of DRAM, the number of supported IP and multicast routes, MAC addresses, bridge domains and Ethernet flow points. Cisco IOS-XE software is a Cisco-developed highly configurable proprietary operating system that provides for efficient and effective routing and switching. Although IOS-XE performs many networking functions, this TOE only addresses the functions that provide for the security of the TOE itself as described in Section 1.7 Logical Scope of the TOE below. 1.4 TOE Evaluated Configuration The TOE consists of one or more physical devices as specified in section 1.5 below and includes the Cisco IOS-XE software. 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 TOE also provides timing services required in today s converged access networks by offering integrated support for the Building Integrated Timing Supply (BITS), 1 Pulse Per Second (1PPS) and Time Of Day (TOD) interfaces. The ASR 900 Series also supports Synchronous Ethernet (SyncE) and IEEE-1588 and can act as the source for network clocking for time-division multiplexing (TDM), Synchronous Digital Hierarchy (SDH), and Synchronous Optical Network (SONET), SyncE, and Global Positioning Satellite (GPS) interfaces. The ASR 900 Series router configuration will prioritize and process the data and signaling traffic for transport across the available networks. Typically, packet flows are passed through the internetworking device and forwarded to their configured destination. The TOE can optionally connect to an NTP server on its internal network for time services. Also, if the ASR 900 Series is to be remotely administered, then the management workstation station must be connected to an internal network, SSHv2 must be used to connect to the TOE. A syslog server is also used to store audit records. 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. Page 10 of 52

11 The following figure provides a visual depiction of an example TOE deployment. The TOE boundary is surrounded with a hashed red line. =TOE Boundary ASR 900 Series Routers Network 1 ASR902 VPN Peer Management Workstation ASR903 NTP Server ASR920 Network 2 Network 3 AAA Server VPN Peer Syslog Server Figure 1 TOE Example Deployment The previous figure includes the following: Examples of TOE Models (models listed in order of diagram) o Cisco ASR RU modular chassis Dedicated slots in the chassis that support the following: Up to four interface modules One Route Switch Processor (RSP) Page 11 of 52

12 Up to two DC or two AC or a combination of AC and DC power supply units One fan tray o Cisco ASR RU modular chassis Dedicated slots in the chassis that support the following: Up to six interface modules Up to two Route Switch Processors (RSP) Up to two DC power supply units One fan tray o Cisco ASR 920 Indoor version includes ASR CZ-A and ASR CZ-D models that have fixed ENET interfaces (12 x 1GE + 2 x 10GE or 2 x 1GE or any combinations of 1 GE and 10 GE among the two ports available) and dual power supplies (AC/DC) Compact version includes ASR-920-4SZ-A and ASR-920-4SZ-D models that have a compact form factor and configurable ports: 4 x 1 GE or 4 x 10 GE or any combinations of 1 GE and 10 GE among the four ports available. In addition, there are 2 x 1 GE copper ports available. 2 - Peer Routers (IT Environment) Management Workstation Syslog Server AAA Server NTP Server NOTE: While the previous figure includes the available TOE devices and several non-toe IT environment devices, the TOE is only the ASR 900 Series (902, 902 and 920) devices with the Cisco IOS-XE software. Only one TOE device is required in an evaluated configuration. 1.5 Physical Scope of the TOE The TOE is a hardware and software solution that makes up the router models as described above in Section 1.4. The TOE guidance documentation that is considered to be part of the TOE can be found listed in the Cisco Aggregation Services Router (ASR) 900 Series Common Criteria Operational User Guidance and Preparative Procedures document and are downloadable from the web site. The TOE is comprised of the following physical specifications as described below: Page 12 of 52

13 Figure 2 ASR 902 chassis design Table 5 ASR 902 chassis References Label Component 1 Interface modules 2 One RSP unit slot; supports the RSP1A- 55, RSP1B-55, RSP2A-64 and RSP2A Fan tray 4 Redundant power units; two DC power units are shown Figure 3 ASR 902 chassis design Table 6 ASR 903 chassis References Label Component 1 Interface modules 2 Two RSP unit slots; supports the RSP1A-55, RSP1B-55, RSP2A-64 and RSP2A Fan tray 4 Redundant power units; two DC power units are shown ASR 920 chassis design Page 13 of 52

14 Figure 4 Front Panel of Cisco ASR CZ-A Router Figure 5 Front Panel of Cisco ASR CZ-D Router Table 7 ASR 920 (12CZ-A/12CD-D) chassis References Label Component Label Component 1 Power Supply 0 (AC or DC) 10 Eight Copper port 2 Power Supply 1 (AC or DC) 11 1G/10G Dual Rate port 3 Power Supply 0 LED (AC 12 1G/10G Dual Rate port or DC) 4 Power Supply 1 LED (AC 13 USB Console port or DC) 5 RJ-48 slots for BITS (upper 14 Alarm port slot) and ToD (lower slot) 6 Management port 15 USB Memory port 7 Console port (TIA/EIA- 16 Board power LED 232F) 8 Auxiliary Console port 17 Zero Touch Provisioning 9 4x1GE SFP + 8x1GE SFP combo ports button 18 System Status LED Figure 6 Front Panel of Cisco ASR-920-4SZ Router Page 14 of 52

15 Figure 7 Front Panel of Cisco ASR-920-4SZ -A Router Table 8 ASR 920 (4SZ/4SZ-A) chassis References Label Component Label Component 1 Power Supply 0 (AC or DC) 9 2 1GE Copper ports 2 Power Supply 1 (AC or DC) 10 Four 1G/10G Dual Rate ports 3 Power Supply 0 LED (AC 11 USB Console port or DC) 4 Power Supply 1 LED (AC 12 Alarm port or DC) 5 RJ-48 slots for BITS (upper 13 USB Memory port slot) and ToD (lower slot) 6 Management port 14 Board power LED 7 Console port (TIA/EIA- 232F) 15 Zero Touch Provisioning button 8 Auxiliary Console port 16 System Status LED The network, on which the TOE resides, is considered part of the environment. The software is pre-installed and is comprised of the Cisco IOS-XE software image Release IOS-XE 3.13.(1)S. In addition, the software image is also downloadable from the Cisco web site. A login id and password is required to download the software image. 1.6 Logical Scope of the TOE The TOE is comprised of several security features. Each of the security features identified above consists of several security functionalities, as identified below. 1. Security Audit 2. Cryptography Support 3. User Data Protection 4. Identification & Authentication 5. Security Management 6. Protection of the TSF 7. Trusted Path/Channel 8. TOE Access Page 15 of 52

16 These features are described in more detail in the subsections below. In addition, the TOE implements all RFCs of the NDPP as necessary to satisfy testing/assurance measures prescribed therein Security audit The Cisco Aggregation Services Router (ASR) 900 Series provides extensive auditing capabilities. The TOE generates a comprehensive set of audit logs that identify specific TOE operations. For each event, the TOE records the date and time of each event, the type of event, the subject identity, and the outcome of the event. Auditable events include: failure on invoking cryptographic functionality such as establishment, termination and failure of an IPsec SA; establishment, termination and failure of an SSH session; modifications to the group of users that are part of the authorized administrator roles; all use of the user identification mechanism; any use of the authentication mechanism; any change in the configuration of the TOE, changes to time, initiation of TOE update, indication of completion of TSF self-test, maximum sessions being exceeded, termination of a remote session and attempts to unlock a termination session; and initiation and termination of a trusted channel. The TOE is configured to transmit its audit messages to an external syslog server. Communication with the syslog server is protected using IPsec and the TOE can determine when communication with the syslog server fails. If that should occur, the TOE can be configured to block new permit actions. The logs can be viewed on the TOE using the appropriate IOS 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 audit data stored locally on the TOE Cryptographic support The TOE provides cryptography in support of other Cisco Aggregation Services Router (ASR) 900 Series security functionality. The algorithms shown in Table 9 FIPS References are implemented in the Cisco IOS Common Cryptographic Module (IC2M) Algorithm Module firmware version 2.0. This cryptography has been validated for conformance to the requirements of FIPS (see Table 9 for certificate references). Table 9 FIPS References Algorithm Cert. # AES 2817 DRBG 481 SHS (SHA-1, 256, 384, 512) HMAC SHA-1, 256, 384, Page 16 of 52

17 Algorithm Cert. # RSA 1471 ECDSA 493 While the algorithm implementations listed in the preceding table were not tested on the exact processor installed within the ASR 900, the algorithm certificates are applicable to the TOE based on the following, 1. The cryptographic implementation which is tested is identical (unchanged) to the cryptographic implementation on the ASR 900s. 2. The cryptographic implementation does not depend on hardware for cryptographic acceleration I.e. there are no hardware specific cryptographic dependency. The cryptographic algorithms are implemented completely in software. 3. This is consistent with the guidance provided in NIST IG G.5 allowing portability amongst platforms as long as no software modification is required. The ASR 900 platforms contain the following processors, 1. Freescale P2020 using the Freescale instruction set 2. Cisco Carrier Ethernet ASIC using a processor specific instruction set The TOE provides cryptography in support of VPN connections and remote administrative management via SSHv2. The cryptographic services provided by the TOE are described in Table 10 below. Table 10 TOE Provided Cryptography Cryptographic Method Internet Key Exchange Secure Shell Establishment RSA/DSA Signature Services SP RBG SHS AES Use within the TOE Used to establish initial IPsec session. Used to establish initial SSH session. Used in IPsec session establishment. Used in SSH session establishment. Used in IPsec session establishment. Used in SSH session establishment. Used to provide IPsec traffic integrity verification Used to provide SSH traffic integrity verification Used to encrypt IPsec session traffic. Used to encrypt SSH session traffic. Page 17 of 52

18 1.6.1 User Data Protection The TOE ensures that all information flows from the TOE do not contain residual information from previous traffic. Packets are padded with zeros. Residual data is never transmitted from the TOE 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. 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 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. The TOE provides authentication services for administrative users to connect to the TOEs 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 as well as mandatory password complexity rules. The TOE provides administrator authentication against a local user database. Passwordbased authentication can be performed on the serial console or SSH interfaces. The SSHv2 interface also supports authentication using SSH keys. 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 s CLI 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 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. The TOE supports two separate administrator roles: non-privileged administrator and privileged administrator. Only the privileged administrator can perform the above security relevant management functions. Page 18 of 52

19 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 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. Additionally Cisco IOS is not a general-purpose operating system and access to Cisco IOS memory space is restricted to only Cisco IOS functions. The 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, or can configure the TOE to use NTP to synchronize the TOE s clock with an external time source. Finally, the TOE performs testing to verify correct operation of the switch itself and that of the cryptographic module. The TOE is able to verify any software updates prior to the software updates being installed on the TOE to avoid the installation of Authorized Administrator software TOE Access The TOE can terminate inactive sessions after an Authorized Administrator configurable timeperiod. Once a session has been terminated the TOE requires the user to re-authenticate to establish a new session. The TOE can also display an Authorized 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. 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. 1.7 Excluded Functionality The following functionality is excluded from the evaluation. Table 11 Excluded Functionality Excluded Functionality Non-FIPS mode of operation on the Exclusion Rationale This mode of operation includes non-fips allowed operations. Page 19 of 52

20 Telnet Telnet sends authentication data in the clear. This feature is enabled by default and must be disabled in the evaluated configuration. Including this feature would not meet the security policies as defined in the Security Target. The exclusion of this feature has no effect on the operation of the TOE. Refer to the Guidance documentation for configuration syntax and information These services will be disabled by configuration. The exclusion of this functionality does not affect compliance to the compliance to the U.S. Government Protection Profile for Security Requirements for Network Devices Version 1.1 with Security Requirements for Network Devices Errata#2. Page 20 of 52

21 2 CONFORMANCE CLAIMS 2.1 Common Criteria Conformance Claim The TOE and ST are compliant with the Common Criteria (CC) Version 3.1, Revision 4, dated: September For a listing of Assurance Requirements claimed see section 5.4. The TOE and ST are CC Part 2 extended and CC Part 3 conformant. 2.2 Protection Profile Conformance The TOE and ST are conformant with the Protection Profiles as listed in Table 12 below: None (NDPP) Table 12 Protection Profiles Protection Profile Version Date Security Requirements for Network Devices Errata Protection Profile for Network Devices (NDPP) June 8, 2012 #2 13 January Protection Profile Conformance Claim Rationale TOE Appropriateness The TOE provides all of the functionality at a level of security commensurate with that identified in the U.S. Government Protection Profile: U.S. Government Protection Profile for Security Requirements for Network Devices, Version 1.1 Security Requirements for Network Devices Errata# TOE Security Problem Definition Consistency The Assumptions, Threats, and Organization Security Policies included in the Security Target represent the Assumptions, Threats, and Organization Security Policies specified in the U.S. Government Protection Profile for Security Requirements for Network Devices Version 1.1 for which conformance is claimed verbatim. All concepts covered in the Protection Profile Security Problem Definition are included in the Security Target Statement of Security Objectives Consistency. The Security Objectives included in the Security Target represent the Security Objectives specified in the NDPPv1.1, for which conformance is claimed verbatim. All concepts covered in the Protection Profile s Statement of Security Objectives are included in the Security Target. Page 21 of 52

22 2.3.3 Statement of Security Requirements Consistency The Security Functional Requirements included in the Security Target represent the Security Functional Requirements specified in the NDPPv1.1, for which conformance is claimed verbatim. All concepts covered in the Protection Profile s Statement of Security Requirements are included in this Security Target. Additionally, the Security Assurance Requirements included in this Security Target are identical to the Security Assurance Requirements included in section 4.3 of the NDPPv1.1. Page 22 of 52

23 3 SECURITY PROBLEM DEFINITION This chapter identifies the following: Significant assumptions about the TOE s operational environment. IT related threats to the organization countered by the TOE. Environmental threats requiring controls to provide sufficient protection. Organizational security policies for the TOE as appropriate. This document identifies assumptions as A.assumption with assumption specifying a unique name. Threats are identified as T.threat with threat specifying a unique name. Organizational Security Policies (OSPs) are identified as P.osp with osp specifying a unique name. 3.1 Assumptions The specific conditions listed in the following subsections are assumed to exist in the TOE s environment. These assumptions include both practical realities in the development of the TOE security requirements and the essential environmental conditions on the use of the TOE. Table 13 TOE Assumptions Assumption A.NO_GENERAL_PURPOSE A.PHYSICAL A.TRUSTED_ADMIN Assumption Definition It is assumed that there are no general-purpose computing capabilities (e.g., compilers or user applications) available on the TOE, other than those services necessary for the operation, administration and support of the TOE. Physical security, commensurate with the value of the TOE and the data it contains, is assumed to be provided by the environment. TOE Administrators are trusted to follow and apply all administrator guidance in a trusted manner. 3.2 Threats The following table lists the threats addressed by the TOE and the IT Environment. The assumed level of expertise of the attacker for all the threats identified below is Enhanced-Basic. Table 14 Threats Threat T.ADMIN_ERROR T.TSF_FAILURE T.UNDETECTED_ACTIONS Threat Definition An administrator may unintentionally install or configure the TOE incorrectly, resulting in ineffective security mechanisms. Security mechanisms of the TOE may fail, leading to a compromise of the TSF. Malicious remote users or external IT entities may take actions that adversely affect the security of the TOE. These actions may remain undetected and thus their effects cannot be effectively mitigated. Page 23 of 52

24 Threat T.UNAUTHORIZED_ACCESS T.UNAUTHORIZED_UPDATE T.USER_DATA_REUSE Threat Definition A user may gain unauthorized access to the TOE data and TOE executable code. A malicious user, process, or external IT entity may masquerade as an authorized entity in order to gain unauthorized access to data or TOE resources. A malicious user, process, or external IT entity may misrepresent itself as the TOE to obtain identification and authentication data. A malicious party attempts to supply the end user with an update to the product that may compromise the security features of the TOE. User data may be inadvertently sent to a destination not intended by the original sender. 3.3 Organizational Security Policies The following table lists the Organizational Security Policies imposed by an organization to address its security needs. Table 15 Organizational Security Policies Policy Name P.ACCESS_BANNER Policy Definition The TOE shall display an initial banner describing restrictions of use, legal agreements, or any other appropriate information to which users consent by accessing the TOE. Page 24 of 52

25 4 SECURITY OBJECTIVES This Chapter identifies the security objectives of the TOE and the IT Environment. The security objectives identify the responsibilities of the TOE and the TOE s IT environment in meeting the security needs. This document identifies objectives of the TOE as O.objective with objective specifying a unique name. Objectives that apply to the IT environment are designated as OE.objective with objective specifying a unique name. 4.1 Security Objectives for the TOE The following table, Security Objectives for the TOE, identifies the security objectives of the TOE. These security objectives reflect the stated intent to counter identified threats and/or comply with any security policies identified. An explanation of the relationship between the objectives and the threats/policies is provided in the rationale section of this document. Table 16 Security Objectives for the TOE TOE Objective O.PROTECTED_COMMUNICATIONS O.VERIFIABLE_UPDATES O.SYSTEM_MONITORING O.DISPLAY_BANNER O.TOE_ADMINISTRATION O.RESIDUAL_INFORMATION_CLEARING O.SESSION_LOCK O.TSF_SELF_TEST TOE Security Objective Definition The TOE will provide protected communication channels for administrators, other parts of a distributed TOE, and authorized IT entities. The TOE will provide the capability to help ensure that any updates to the TOE can be verified by the administrator to be unaltered and (optionally) from a trusted source. The TOE will provide the capability to generate audit data and send those data to an external IT entity. The TOE will display an advisory warning regarding use of the TOE. The TOE will provide mechanisms to ensure that only administrators are able to log in and configure the TOE, and provide protections for logged-in administrators. The TOE will ensure that any data contained in a protected resource is not available when the resource is reallocated. The TOE shall provide mechanisms that mitigate the risk of unattended sessions being hijacked. The TOE will provide the capability to test some subset of its security functionality to ensure it is operating properly. Page 25 of 52

26 4.2 Security Objectives for the Environment All of the assumptions stated in section 3.1 are considered to be security objectives for the environment. The following are the Protection Profile non-it security objectives, which, in addition to those assumptions, are to be satisfied without imposing technical requirements on the TOE. That is, they will not require the implementation of functions in the TOE hardware and/or software. Thus, they will be satisfied largely through application of procedural or administrative measures. Table 17 Security Objectives for the Environment Environment Security Objective OE.NO_GENERAL_PURPOSE OE.PHYSICAL OE.TRUSTED_ADMIN IT Environment Security Objective Definition There are no general-purpose computing capabilities (e.g., compilers or user applications) available on the TOE, other than those services necessary for the operation, administration and support of the TOE. Physical security, commensurate with the value of the TOE and the data it contains, is provided by the environment. TOE Administrators are trusted to follow and apply all administrator guidance in a trusted manner. Page 26 of 52

27 5 SECURITY REQUIREMENTS This section identifies the Security Functional Requirements for the TOE. The Security Functional Requirements included in this section are derived from Part 2 of the Common Criteria for Information Technology Security Evaluation, Version 3.1, Revision 4, dated: September 2012 and all international interpretations. 5.1 Conventions The CC defines operations on Security Functional Requirements: assignments, selections, assignments within selections and refinements. This document uses the following font conventions to identify the operations defined by the CC: Assignment: Indicated with italicized text; Refinement: Indicated with bold text; Selection: Indicated with underlined text; Iteration: Indicated by appending the iteration number in parenthesis, e.g., (1), (2), (3). Where operations were completed in the NDPP itself, the formatting used in the NDPP has been retained. Explicitly stated SFRs are identified by having a label EXT after the requirement name for TOE SFRs. Formatting conventions outside of operations and iterations matches the formatting specified within the NDPP. 5.2 TOE Security Functional Requirements This section identifies the Security Functional Requirements for the TOE. The TOE Security Functional Requirements that appear in the following table are described in more detail in the following subsections. Class Name Table 18 Security Functional Requirements Component Identification FAU: Security audit FAU_GEN.1 Audit data generation FCS: Cryptographic support FAU_GEN.2 FAU_STG_EXT.1 FCS_CKM.1 FCS_CKM_EXT.4 FCS_COP.1(1) FCS_COP.1(2) FCS_COP.1(3) FCS_COP.1(4) FCS_IPSEC_EXT.1 User Identity Association External Audit Trail Storage Component Name Cryptographic Key Generation (for asymmetric keys) Cryptographic Key Zeroization Cryptographic Operation (for data encryption/decryption) Cryptographic Operation (for cryptographic signature) Cryptographic Operation (for cryptographic hashing) Cryptographic Operation (for keyed-hash message authentication) Explicit: IPSEC Page 27 of 52

28 Class Name FDP: User data protection FIA: Identification and authentication FMT: Security management FPT: Protection of the TSF Component Identification FCS_RBG_EXT.1 FC_SSH_EXT.1 FDP_RIP.2 FIA_PMG_EXT.1 FIA_PSK_EXT.1 FIA_UIA_EXT.1 FIA_UAU_EXT.2 FIA_UAU.7 FMT_MTD.1 FMT_SMF.1 FMT_SMR.2 FPT_SKP_EXT.1 FPT_APW_EXT.1 FPT_STM.1 FPT_TUD_EXT.1 FPT_TST_EXT.1 Component Name Extended: Cryptographic Operation (Random Bit Generation) Explicit: SSH Full Residual Information Protection Password Management Extended: Pre-Shared Key Composition User Identification and Authentication Password-based Authentication Mechanism Protected Authentication Feedback Management of TSF Data (for general TSF data) Specification of Management Functions Restrictions on Security Roles Extended: Protection of TSF Data (for reading of all symmetric keys) Extended: Protection of Administrator Passwords Reliable Time Stamps Extended: Trusted Update TSF Testing FTA: TOE Access FTA_SSL_EXT.1 TSF-initiated Session Locking FTP: Trusted path/channels FTA_SSL.3 FTA_SSL.4 FTA_TAB.1 FTP_ITC.1 FTP_TRP.1 TSF-initiated Termination User-initiated Termination Default TOE Access Banners Trusted Channel Trusted Path Security audit (FAU) FAU_GEN.1: Audit data generation FAU_GEN.1.1 The TSF shall be able to generate an audit record of the following auditable events: a) Start-up and shut-down of the audit functions; b) All auditable events for the not specified level of audit; and c) All administrative actions; d) [Specifically defined auditable events listed in Table 19]. Page 28 of 52

29 FAU_GEN.1.2 The TSF shall record within each audit record at least the following information: a) Date and time of the event, type of event, subject identity, and the outcome (success or failure) of the event; and b) For each audit event type, based on the auditable event definitions of the functional components included in the PP/ST, [information specified in column three of Table 19]. Table 19 Auditable Events SFR Auditable Event Additional Audit Record Contents FAU_GEN.1 None. None. FAU_GEN.2 None. None. FAU_STG_EXT.1 None. None. FCS_CKM.1 None. None. FCS_CKM_EXT.4 None. None. FCS_COP.1(1) None. None. FCS_COP.1(2) None. None. FCS_COP.1(3) None. None. FCS_COP.1(4) None. None. FCS_IPSEC_EXT.1 FCS_SSH_EXT.1 Failure to establish an IPsec SA. Establishment/Termination of an IPsec SA. Failure to establish an SSH session Establishment/Termination of an SSH session. Reason for failure. Non-TOE endpoint of connection (IP address) for both successes and failures. Reason for failure. Non-TOE endpoint of connection (IP address) for both successes and failures. FCS_RBG_EXT.1 None. None. FDP_RIP.2 None. None. FIA_PMG_EXT.1 None. None. FIA_PSK_EXT None. None. FIA_UIA_EXT.1 All use of the identification and authentication mechanism. Provided user identity, origin of the attempt (e.g., IP address). FIA_UAU_EXT.2 All use of the authentication mechanism. Origin of the attempt (e.g., IP address). FIA_UAU.7 None. None. FMT_MTD.1 None. None. FMT_SMF.1 None. None. FMT_SMR.2 None. None. FPT_SKP_EXT.1 None. None. FPT_APW_EXT.1 None. None. Page 29 of 52

30 SFR Auditable Event Additional Audit Record Contents FPT_STM.1 Changes to the time. The old and new values for the time. Origin of the attempt (e.g., IP address). FPT_TUD_EXT.1 Initiation of update. No additional information. FPT_TST_EXT.1 None. None. FTA_SSL_EXT.1 FTA_SSL.3 FTA_SSL.4 Any attempts at unlocking of an interactive session. The termination of a remote session by the session locking mechanism. The termination of an interactive session. No additional information. No additional information. No additional information. FTA_TAB.1 None. None. FTP_ITC.1 FTP_TRP.1 Initiation of the trusted channel. Termination of the trusted channel. Failure of the trusted channel functions. Initiation of the trusted channel. Termination of the trusted channel. Failures of the trusted path functions. Identification of the initiator and target of failed trusted channels establishment attempt Identification of the claimed user identity FAU_GEN.2 User Identity Association FAU_GEN.2.1 For audit events resulting from actions of identified users, the TSF shall be able to associate each auditable event with the identity of the user that caused the event FAU_STG_EXT.1 External Audit Trail Storage FAU_STG_EXT.1.1 The TSF shall be able to [transmit the generated audit data to an external IT entity] using a trusted channel implementing the [IPsec] protocol Cryptographic Support (FCS) FCS_CKM.1 Cryptographic Key Generation (for asymmetric keys) FCS_CKM.1.1 Refinement: The TSF shall generate asymmetric cryptographic keys used for key establishment in accordance with [NIST Special Publication B, Recommendation for Pair-Wise Key Establishment Schemes Using Integer Factorization Cryptography for RSA-based key establishment schemes] and specified cryptographic key sizes equivalent to, or greater than, a symmetric key strength of Page 30 of 52

31 112 bits FCS_CKM_EXT.4 Cryptographic Key Zeroization FCS_CKM_EXT.4.1 The TSF shall zeroize all plaintext secret and private cryptographic keys and CSPs when no longer required FCS_COP.1(1) Cryptographic Operation (for data encryption/decryption) FCS_COP.1.1(1) Refinement: The TSF shall perform [encryption and decryption] in accordance with a specified cryptographic algorithm [AES operating in [CBC] and cryptographic key sizes 128-bits and 256-bits that meets the following: FIPS PUB 197, Advanced Encryption Standard (AES) [NIST SP A, NIST SP D] FCS_COP.1(2) Cryptographic Operation (for cryptographic signature) FCS_COP.1.1(2) Refinement: The TSF shall perform cryptographic signature services in accordance with a [(2) RSA Digital Signature Algorithm (rdsa) with a key size (modulus) of 2048 bits or greater] that meets the following: [Case: Digital Signature Algorithm FIPS PUB 186-3, Digital Signature Standard ] FCS_COP.1(3) Cryptographic Operation (for cryptographic hashing) FCS_COP.1.1(3) Refinement: The TSF shall perform [cryptographic hashing services] in accordance with a specified cryptographic algorithm [SHA-1, SHA-256, SHA-384, SHA-512] and message digest sizes [160, 256, 384, 512] bits that meet the following: FIPS Pub 180-3, Secure Hash Standard FCS_COP.1(4) Cryptographic Operation (for keyed-hash message authentication) FCS_COP.1.1(4) Refinement: The TSF shall perform [keyed-hash message authentication] in accordance with a specified cryptographic algorithm HMAC-[SHA-1], key size [160 bits], and message digest sizes [160] bits that meet the following: FIPS Pub 198-1, "The Keyed-Hash Message Authentication Code, and FIPS Pub 180-3, Secure Hash Standard FCS_IPSEC_EXT.1 Explicit: IPSEC FCS_IPSEC_EXT.1.1 The TSF shall implement the IPsec architecture as specified in RFC FCS_IPSEC_EXT.1.2 The TSF shall implement [tunnel mode]. Page 31 of 52

32 FCS_IPSEC_EXT.1.3 The TSF shall have a nominal, final entry in the SPD that matches anything that is otherwise unmatched, and discards it. FCS_IPSEC_EXT.1.4 The TSF shall implement the IPsec protocol ESP as defined by RFC 4303 using [the cryptographic algorithms AES-CBC-128 (as specified by RFC 3602) together with a Secure Hash Algorithm (SHA)-based HMAC, AES-CBC-256 (as specified by RFC 3602)]. FCS_IPSEC_EXT.1.5 The TSF shall implement the protocol: [IKEv1 as defined in RFCs 2407, 2408, 2409, RFC 4109, [no other RFCs for extended sequence numbers], and [no other RFCs for hash functions]]. FCS_IPSEC_EXT.1.6 The TSF shall ensure the encrypted payload in the [IKEv1] protocol uses the cryptographic algorithms AES-CBC-128, AES-CBC-256 as specified in RFC 6379 and [no other algorithm]. FCS_IPSEC_EXT.1.7 The TSF shall ensure that IKEv1 Phase 1 exchanges use only main mode. FCS_IPSEC_EXT.1.8 The TSF shall ensure that [IKEv1 SA lifetimes can be established based on [number of packets/number of bytes and length of time, where the time values can be limited to: 24 hours for Phase 1 SAs and 8 hours for Phase 2 SAs]. FCS_IPSEC_EXT.1.9 The TSF shall ensure that all IKE protocols implement DH Groups 14 (2048-bit MODP), and [no other DH groups]. FCS_IPSEC_EXT.1.10 The TSF shall ensure that all IKE protocols perform Peer Authentication using the [RSA] algorithm and [Pre-shared Keys] FCS_RBG_EXT.1 Extended: Cryptographic Operation (Random Bit Generation) FCS_RBG_EXT.1.1 The TSF shall perform all random bit generation (RBG) services in accordance with [NIST Special Publication using [CTR_DRBG (AES)] seeded by an entropy source that accumulated entropy from [a TSF-hardware-based noise source]. FCS_RBG_EXT.1.2 The deterministic RBG shall be seeded with a minimum of [256 bits] of entropy at least equal to the greatest security strength of the keys and hashes that it will generate FCS_SSH_EXT.1 Explicit: SSH FCS_SSH_EXT.1.1 The TSF shall implement the SSH protocol that complies with RFCs 4251, 4252, 4253, 4254, and [no other RFCs]. FCS_SSH_EXT.1.2 The TSF shall ensure that the SSH protocol implementation supports the following authentication methods as described in RFC 4252: public key-based, password-based. Page 32 of 52