Supported Versions
Firepower Device Manager(FDM) 6.7
Firepower Management Center(FMC) 6.1

Introduction

Cisco Firepower Threat Defense is an integrative software image combining Cisco ASA and Firepower features into one hardware and software inclusive system.

The Cisco Firepower NGIPS is a next generation intrusion prevention system that shares a management console with the Cisco firewall offerings, called the Firepower Management Center.

Cisco ASA Firepower Services provides the following key capabilities:

  1. Access control: This policy based capability allows a network security administrator to define, inspect, and log the traffic that traverses a firewall. Access control policies determine how traffic is permitted or denied in a network. For instance, you can configure a default action to inspect all traffic or block or trust all traffic without further inspection. You can achieve a more complete access control policy with enrichment data based on security threat intelligence. Whether you configure simple or complex rules, you can control traffic based on security zones, network or geographical locations, ports, applications, requested URLs, and per user.

  2. Intrusion detection and prevention: Intrusion detection and prevention help you detect attempts from an attacker to gain unauthorized access to a network or host, create performance degradation, or steal information. You define intrusion detection and prevention policies based on your access control policies. Create and tune custom policies at a very granular level to specify how traffic is inspected in a network.

  3. AMP and file control: You can detect, track, capture, analyze, and optionally block the transmission of files, including malware files and nested files inside archive files in network traffic. File control enables you to detect and block users from sending or receiving files of different specific types over a multitude of application protocols. You can configure file control as part of the overall access control policies and application inspection.

  4. Application programming interfaces (APIs): Cisco ASA Firepower Services supports several ways to interact with the system using APIs.

Pre-Requisites

OpsRamp Classic Gateway 12.0.1 and above.

Default monitoring configurations

Cisco Firepower Threat Defense has default Global Device Management Policies, Global Templates, Global Monitors and Global metrics in OpsRamp. You can customize these default monitoring configurations as per your business use case by cloning respective Global Templates and Global Device Management Policies. OpsRamp recommends doing this activity before installing the app to avoid noise alerts and data.

  1. Default Global Device Management Policies available

    OpsRamp has a Global Device Management Policy for each Native Type of Cisco FTD. You can find these Device Management Policies at Setup -> Resources -> Device Management Policies -> Search with suggested names in global scope. Each Device Management Policy follows below naming convention:

    {appName nativeType - version}

    Ex: cisco-firepower-threat-defense Cisco FTD Interfaces - 1 (i.e, appName =cisco-firepower-threat-defense, nativeType = Cisco FTD Interfaces, version = 1)

  2. Default Global Templates available

    OpsRamp has a Global Template for each Native Type of Cisco FirePower Threat Defense. You can find these templates at Setup -> Monitoring -> Templates -> Search with suggested names in global scope. Each template follows below naming convention:

    {appName nativeType 'Template' - version}

    Ex: cisco-firepower-threat-defense Cisco FTD Interfaces Template - 1 (i.e, appName = cisco-firepower-threat-defense, nativeType = Cisco FTD Interfaces Template, version = 1)

  3. Default Global Monitors available

    OpsRamp has a Global Monitors for each Native Type which has monitoring support. We can find those monitors at Setup -> Monitoring -> Monitors -> Search with suggested names in global scope. Each Monitors follows below naming convention:

    {monitorKey appName nativeType - version}

    Ex: Cisco FTD Interface Monitor cisco-firepower-threat-defense Cisco FTD Interfaces 1(i.e, monitorKey =Cisco FTD Interface Monitor, appName = cisco-firepower-threat-defense, nativeType = Cisco FTD Interfaces, version = 1)

Configure and install the integration

  1. From All Clients, select a client.
  2. Go to Setup > Integrations and Apps.
  3. Click + ADD on the INSTALLED APP page. The AVAILABLE APPS page displays all the available applications along with the newly created application with the version.
    Notes:
    • If there are already installed applications, it will redirect to the INSTALLED APPS page, where all the installed applications are displayed.
    • If there are no installed applications, it will navigate to the ADD APP page.
    • You can even search for the application using the search option available. Also you can use the All Categories option to search.
Cisco FirePower
Cisco FirePower
  1. Click ADD in the Cisco Firepower Threat Defense application.
  2. In the Configurations page, click + ADD. The Add Configuration page appears.
  3. Enter the below mentioned BASIC INFORMATION:
FuntionalityDescription
NameEnter the name for the configuration.
IP Address/Host NameIP address/host name of the target.
PortPort

Note: By default 443 is added.
Managed BySelect Managed By from the drop-down list.

Note: As of now the application only supports discovery and monitoring for FTDs managed by:
- Firepower management Center (FMC)
- Firepower device manager (FDM)
CredentialsSelect the credentials from the drop-down list.

Note: Click + Add to create a credential.

Notes:

  • By default the Is Secure checkbox is selected. Select the following:
    • App Failure Notifications: if turned on, you will be notified in case of an application failure that is, Connectivity Exception, Authentication Exception.
    • Alert Configuration: map alert configuration for third party alerts into OpsRamp.
  • Below are the default values set for:
    • Alert Severity: possible values of Alert Severity filter configuration property are “RED”,“YELLOW”.
    • Alert Severity Mapping: possible values of Alert Severity Mapping filter configuration property are “RED”:“Critical”,“YELLOW”:“Warning”.
  1. In the RESOURCE TYPE section, select:
    • ALL: All the existing and future resources will be discovered.
    • SELECT: You can select one or multiple resources to be discovered.
  2. In the DISCOVERY SCHEDULE section, select Recurrence Pattern to add one of the following patterns:
    • Minutes
    • Hourly
    • Daily
    • Weekly
    • Monthly
  3. Click ADD.
Cisco FirePower
  1. Now the configuration is saved and displayed on the configurations page after you save it.
    Note: From the same page, you may Edit and Remove the created configuration.
  2. Click NEXT
  3. In the Installation page, select an existing registered gateway profile, and click FINISH.
Cisco FirePower

The application is now installed and displayed on the Installed Integration page. Use the search field to find the installed application.

Modify the Configuration

View the Cisco Firepower Threat Defense device details

The Cisco Firepower Threat Defense application integration is displayed in the below navigation:

  • FMC: Infrastructure > Resources > Server.
Cisco FirePower
Cisco FirePower
  • FTD: Infrastructure > Resources > Network Device > Firewall.
Cisco FirePower
Cisco FirePower

Supported Metrics

Metric NameUnitDescription
cisco_ftd_health_statusHealth status of Ftd device
cisco_ftd_mem_freeBytesThe total free memory.
mem_usedBytesThe total memory available.
cisco_ftd_mem_used_percentage_lina%The percent of memory used by the data plane.
cisco_ftd_mem_used_percentage_snort%The percent of memory used by the Snort process.
cisco_ftd_mem_used_percentage_system_and_swap%The percent of memory used by the system and swap combined.
cisco_ftd_cpu_lina_cp_avg%The average CPU utilization for the control plane
cisco_ftd_cpu_lina_dp_avg%The average CPU utilization for the data plane.
cisco_ftd_cpu_snort_avg%The average CPU utilization for the Snort process.
cisco_ftd_cpu_system_avg%The average CPU utilization for the system processes.
cisco_ftd_cpu_lina_avg%The average CPU utilization for all the cores.
cisco_ftd_packets_bypassed_snort_busycountThe number of packets that bypassed inspection when Snort was too busy to handle the packets.
cisco_ftd_packets_bypassed_snort_downcountThe number of packets that bypassed inspection when Snort was down.
cisco_ftd_packets_drops_rxq_fullcountThe number of packets bypassed due to a receive queue full.
cisco_ftd_disk_total_usedBytesThe total space used on the device disk.
cisco_ftd_disk_used_percentage%The percent of disk space used by different partitions.
cisco_ftd_critical_process_restart_countcountRestart count of each critical processes.
cisco_ftd_critical_process_cpu_util%Cpu utilization of each critical process.
cisco_ftd_critical_process_statusThe status of critical processes
cisco_ftd_critical_process_used_memBytesThe memory used for each critical process
cisco_ftd_critical_process_uptimesThe uptime of each critical process.
cisco_ftd_connection_in_usecountShows the number of connections in use
cisco_ftd_connection_most_usedcountShows the maximum number of simultaneous connections.
cisco_ftd_cps_udpcountThe connections-per-second for UDP connection types.
cisco_ftd_cps_tcpcountThe connections-per-second for TCP connection types.
cisco_ftd_interface_drop_packetscountThe number of packets dropped.
cisco_ftd_interface_input_bytesBytesThe total incoming bytes.
cisco_ftd_interface_input_packetscountThe total incoming packets.
cisco_ftd_interface_output_bytesBytesThe total outgoing bytes.
cisco_ftd_interface_output_packetscountThe total outgoing packets.

Risks, Limitations & Assumptions

  • As of now the application only supports discovery and monitoring for FTDs managed by FMC or FDM.
  • Application can handle Critical/Recovery failure notifications for below two cases when user enables App Failure Notifications in configuration:
    • Connectivity Exception (ConnectTimeoutException, HttpHostConnectException, UnknownHostException)
    • Authentication Exception (UnauthorizedException)
  • Application will not send any duplicate/repeat failure alert notification until the already existed critical alert is recovered.
  • Application cannot control monitoring pause/resume actions based on above alerts.
  • Metrics can be used to monitor FTD resources and can generate alerts based on the threshold values.
  • Event/Alert polling will start only if the user enables Event/Alert Polling in configuration.
  • Possible values of Event/Alert Severity filter configuration property are kWarning, kCritical, kInfo.
  • OpsRamp has given sample mappings to map FTD Severity with OpsRamp Severities as part of the Event/Alert Severity Mapping configuration file. You can modify them as per their use case at any point of time from the SDK application configuration page. Possible OpsRamp Severities are Critical, Warning, Ok, Info.
  • Macro replacement limitation (i.e, customization for threshold breach alert subject, description).
  • Component level thresholds can be configured on each resource level.
  • No support of showing activity log and applied time.
  • No support for the option to get Latest snapshot metric.
  • Application is not compatible with Cluster Gateway.
  • Interfaces under FTD are represented as Network devices in Opsramp.