Compliant Product - Cisco FTD (NGFW) 7.0 on Firepower 4100 and 9300 Series with FMC/FMCv
Certificate Date: 2023.02.13CC Certificate Security Target Validation Report
Validation Report Number: CCEVS-VR-VID11292-2023
Product Type: Firewall
Virtual Private Network
Conformance Claim: Protection Profile Compliant
PP Identifier: collaborative Protection Profile for Network Devices Version 2.2e
collaborative Protection Profile Module for Stateful Traffic Filter Firewalls v1.4 + Errata 20200625
PP-Module for Intrusion Prevention Systems (IPS), Version 1.0
PP-Module for Virtual Private Network (VPN) Gateways Version 1.1
CC Testing Lab: Gossamer Security Solutions
Administrative Guide: Firepower Management Center Configuration Guide, Version 7.0
Administrative Guide: FTD v7.0 on Firepower 4100 and 9300 Series with FMC and FMCv Common Criteria User Guide Supplement IPS & VPN Functionality
Administrative Guide: Cisco FTD v7.0 on Firepower 4100 and 9300 Series with FMC and FMCv Common Criteria Supplemental User Guide
Administrative Guide: Cisco FXOS 2.10 on Firepower 4100/9300 for FTD Preparative Procedures & Operational User Guide for the Common Criteria Certified Configuration
Administrative Guide: Cisco Firepower 4100/9300 FXOS Firepower Chassis Manager Configuration Guide, 2.10(1)
Administrative Guide: Cisco Firepower 4100/9300 Upgrade Guide, Firepower 6.0.1–7.0.x or ASA 9.4(1)–9.16(x) with FXOS 1.1.1–2.10.1
Administrative Guide: Cisco Firepower 4100 Getting Started Guide
Administrative Guide: Cisco Firepower 4110, 4120, 4140, and 4150 Hardware Installation Guide
Administrative Guide: Cisco Firepower 4112, 4115, 4125, and 4145 Hardware Installation Guide
Administrative Guide: Cisco Firepower 9300 Hardware Installation Guide
Administrative Guide: Cisco Firepower 9300 Getting Started Guide
Administrative Guide: Cisco Firepower 4100/9300 FXOS CLI Configuration Guide, 2.10(1)
Administrative Guide: Cisco Firepower Management Center 1000, 2500, and 4500 Hardware Installation Guide
Administrative Guide: Cisco Firepower Management Center 1600, 2600, and 4600 Hardware Installation Guide
Administrative Guide: Cisco Firepower Management Center Upgrade Guide, Version 6.0–7.0
Administrative Guide: Cisco Firepower Release Notes, Version 7.0
Administrative Guide: Cisco Secure Firewall Management Center Virtual Getting Started Guide
Administrative Guide: Cisco Secure Firewall Threat Defense Command Reference
Administrative Guide: Cisco Secure Firewall Threat Defense Syslog Messages
Administrative Guide: Cisco Secure Firewall Threat Defense/Firepower Hotfix ReleaseNotes
Administrative Guide: Cisco Firepower 4100/9300 FXOS Command Reference
The TOE is comprised of both software and hardware. The models are comprised of the following: FP 4110, 4112, 4115, 4120, 4125, 4140, 4145, 4150, 9300 and Firepower Management Center (FMC) (FMC1000-K9, FMC2500-K9, FMC4500-K9, FMC1600-K9, FMC2600-K9, FMC4600-K9 and FMCv). The software is comprised of the FTD software image Release 7.0 (running directly on a 4100 series, or on a security module in a 9300), FXOS 2.10 (running on 4100 series or on the Supervisor blade of a 9300), and FMC (or FMCv) version 7.0.
The Cisco Firepower 9300 security appliance is a modular, scalable, carrier-grade appliance that includes the Chassis (including fans and power supply), Supervisor Blade (to manage the security application running on the security module), network module (optional) and security module that contains the FTD software. The FP4100 Series appliance is a complete standalone, bundle unit that contains everything required above in one appliance.
The Firepower eXtensible Operating System (FXOS) is used to manage the FTD. All the platforms run an instance of FXOS that provides management of the hardware and loads FTD. The 4k/9k chassis runs on its supervisor engine a fully featured build of FXOS referred to as the Management Input Output (MIO) build of FXOS. A separate, more limited build of FXOS runs on any Security Module (SM) installed within the chassis (the Firepower 4100 models contain one fixed Security Module, while the Firepower 9300 chassis supports up to three removable Security Modules). The SM hardware is a form of Cisco UCS server (based on a UCS B-series blade server), and as such it includes a Cisco Integrated Management Controller (CIMC), which is firmware running on a CIMC daughterboard on the server blade. The FTD software runs on FXOS on the SM. The FXOS software running on the chassis supervisor maintains a list of administrative accounts that are able to log in to the supervisor via CLI or WebUI/GUI, called Firepower Chassis Manager (FCM). All administrative accounts can be managed via both CLI and GUI, and the same authentication mechanisms can be used at the CLI or GUI.
The FMC is a fault-tolerant, purpose-built network appliance that provides a centralized management console and database repository for the Sensors (i.e., FTD). The FMC is a key component in the Cisco NGIPS system. Administrators can use the FMC to manage the full range of Sensors that comprise the Cisco NGIPS system, and to aggregate, analyze, and respond to the threats they detect on their network. By using the FMC to manage Sensors, administrators can:
The FMC aggregates and correlates intrusion events, anomaly, network discovery information, and Sensor performance data, allowing administrators to monitor the information the Sensors are reporting in relation to one another, and to assess the overall activity occurring on their network. The following illustration lists what is transmitted between a FMC and its managed Sensors.
The UCS hardware components, which provide the platform for the FMCv, in the TOE have common hardware characteristics. These differing characteristics affect only non-TSF relevant functionality (such as throughput, processing speed, number and type of network connections supported, number of concurrent connections supported, and amount of storage) and therefore support security equivalency of the FMCv in terms of hardware.
 Also known as the Cisco FXOS chassis.
The TOE consists of at least one Firepower device (Firepower 4K/9K series) running the FXOS and FTD software and one physical FMC device running the FMC software or virtual devices running FMCv software.
Security Evaluation Summary
The evaluation was carried out in accordance to the Common Criteria Evaluation and Validation Scheme (CCEVS) requirements and guidance. The evaluation demonstrated that the TOE meets the security requirements contained in the Security Target. The criteria against which the TOE was judged are described in the Common Criteria for Information Technology Security Evaluation, Version 3.1, Revision 5, April 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, April 2017. The product, when delivered and configured as identified in the Cisco FTD v7.0 on Firepower 4100 and 9300 Series with FMC and FMCv Common Criteria Supplemental User Guide, Version 0.6, February 8, 2023, the Cisco FXOS 2.10 on Firepower 4100/9300 for FTD Preparative Procedures & Operational User Guide for the Common Criteria Certified Configuration, Version 0.5, January 23, 2023 and the FTD v7.0 on Firepower 4100 and 9300 Series with FMC and FMCv Common Criteria User Guide Supplement IPS & VPN Functionality, Version 0.5, January 23, 2023 documents, satisfies all of the security functional requirements stated in the Cisco FTD (NGFW) 7.0 on Firepower 4100 and 9300 Series with FMC/FMCv Security Target, Version 0.9, February 9, 2023. The project underwent CCEVS Validator review. The evaluation was completed in February 2023. Results of the evaluation can be found in the Common Criteria Evaluation and Validation Scheme Validation Report (report number CCEVS-VR-VID11292-2023) prepared by CCEVS.
The logical boundaries of the Cisco FTD (NGFW) 7.0 on Firepower 4100 and 9300 Series with FMC/FMCv are realized in the security functions that it implements. Each of these security functions is summarized below.
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. The administrator configures auditable events, performs back-up operations, and manages audit data storage. The TOE provides the administrator with a circular audit trail where the TOE overwrites the oldest audit record with the newest audit record when space is full. Audit logs are backed up over an encrypted channel to an external audit server.
The TOE allows authorized administrators to control which FTD device is managed by the FMC. This is performed through a registration process over TLS. The administrator can also de-register a FTD device if he or she wish to no longer manage it through the FMC.
The TOE provides cryptography in support of other TOE security functionality. The TOE provides cryptography in support of secure connections using IPsec and TLS, and remote administrative management via SSHv2, and TLS/HTTPS. The cryptographic random bit generators (RBGs) are seeded by an entropy noise source.
Full residual information 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 X509v3 certificate based authentication or pre-shared key methods.
The TOE provides authentication services for administrative users wishing to connect to the TOEs secure CLI and GUI administrator interfaces. 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 also implements a lockout mechanism when the number of unsuccessful authentication attempts exceeds the configured threshold.
The TOE provides administrator authentication against a local user database. Password-based authentication can be performed on the serial console or SSH and HTTPS interfaces. The SSHv2 interface also supports authentication using SSH keys.
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 or TLS/HTTPS 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; and the information flow control policies enforced by the TOE including encryption/decryption of information flows for VPNs. The TOE supports an “authorized administrator” role, which equates to any account authenticated to an administrative interface (CLI or GUI, but not VPN), and possessing sufficient privileges to perform security-relevant administrative actions.
When an administrative session is initially established, the TOE displays an administrator- configurable warning banner. This is used to provide any information deemed necessary by the administrator. After a configurable period of inactivity, administrative sessions will be terminated, requiring administrators to re-authenticate.
Protection of the TSF:
The TOE protects against interference and tampering by untrusted subjects by implementing identification, authentication, and administrator roles to limit configuration to authorized administrators. The TOE prevents reading of cryptographic keys and passwords.
Additionally, the TOE is not a general-purpose operating system and access to the TOE memory space is restricted to only TOE functions.
The TOE 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. Administrators can update the TOE’s clock manually via FMC or FXOS or can configure the TOE (FXOS) to use NTP via an IPsec tunnel to synchronize the TOE’s clock with an external time source. Additionally, the TOE performs testing to verify correct operation of the appliance itself and that of the cryptographic module. Whenever any system failures occur within the TOE the TOE will cease operation.
When an administrative session is initially established, the TOE displays an administrator- configurable warning banner. This is used to provide any information deemed necessary by the administrator. After a configurable period of inactivity, administrator and VPN client sessions will be terminated, requiring re-authentication. 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 and can be configured to deny sessions based on IP, time, and day, and to NAT external IPs of connecting VPN clients to internal network addresses.
The TOE supports establishing trusted paths between itself and remote administrators using SSHv2 for CLI access, and TLS/HTTPS for GUI access. The TOE supports use of TLS and/or IPsec for connections with remote syslog servers and use of IPsec for connections with NTP servers. The TOE can establish trusted paths of peer-to-peer VPN tunnels using IPsec, and VPN client tunnels using IPsec or TLS. Note that the VPN client is in the operational environment.
The TOE provides stateful traffic firewall functionality including IP address-based filtering (for IPv4 and IPv6) to address the issues associated with unauthorized disclosure of information, inappropriate access to services, misuse of services, disruption or denial of services, and network-based reconnaissance. Address filtering can be configured to restrict the flow of network traffic between protected networks and other attached networks based on source and/or destination IP addresses. Port filtering can be configured to restrict the flow of network traffic between protected networks and other attached networks based on the originating (source) and/or receiving (destination) port (service). Stateful packet inspection is used to aid in the performance of packet flow through the TOE and to ensure that only packets are only forwarded when they’re part of a properly established session. The TOE supports protocols that can spawn additional sessions in accordance with the protocol RFCs where a new connection will be implicitly permitted when properly initiated by an explicitly permitted session. The File Transfer Protocol is an example of such a protocol, where a data connection is created as needed in response to an explicitly allowed command connection. System monitoring functionality includes the ability to generate audit messages for any explicitly defined (permitted or denied) traffic flow. TOE administrators have the ability to configure permitted and denied traffic flows, including adjusting the sequence in which flow control rules will be applied, and to apply rules to any network interface of the TOE.
The TOE also provides packet filtering and secure IPsec tunneling. The tunnels can be established between two trusted VPN peers as well as between remote VPN clients 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 set.
Intrusion prevention system:
The TOE provides intrusion policies consisting of rules and configurations invoked by the access control policy. The intrusion policies are the last line of defense before the traffic is allowed to its destination. All traffic permitted by the access control policy is then inspected by the designated intrusion policy. Using intrusion rules and other preprocessor settings, these policies inspect traffic for security violations and, in inline deployments, can block or alter malicious traffic.
If the vendor-provided intrusion policies do not fully address the security needs of the organization, custom policies can improve the performance of the system in the environment and can provide a focused view of the malicious traffic and policy violations occurring on the network. By creating and tuning custom policies, the administrators can configure, at a very granular level, how the system processes and inspects the traffic on the network for intrusions.
Using Security Intelligence, the administrators can blacklist—deny traffic to and from—specific IP addresses, URLs, and DNS domain names, before the traffic is subjected to analysis by the access control rules. Optionally, the administrators can use a “monitor-only” setting for Security Intelligence filtering.
Cisco Systems, Inc.