Firepower Management Center Configuration Guide, Version 6.1

About System Configuration

System configuration settings apply to either a Firepower Management Center or a Classic managed device (7000 and 8000 Series, ASA FirePOWER, NGIPSv):

For the Firepower Management Center these configuration settings are part of a "local" system configuration. Note that system configuration on the Firepower Management Center is specific to a single system, and changes to a FMC's system configuration affect only that system.

For a Classic managed device, you apply a configuration from the Firepower Management Center as part of a platform settings policy. You create a shared policy to configure a subset of the system configuration settings, appropriate for managed devices, that are likely to be similar across a deployment.

Tip

For 7000 and 8000 Series devices, you can perform limited system configuration tasks from the local web interface, such as console configuration and remote management. These are not the same configurations that you apply to a 7000 or 8000 Series device using a platform settings policy.

Navigating the Firepower Management Center System Configuration


Smart License	Classic License	Supported Devices	Supported Domains	Access
Any	Any	FMC	Global only	Admin

The system configuration identifies basic settings for a Firepower Management Center.

Procedure

Step 1	Choose System > Configuration.
Step 2	Use the navigation panel to choose configurations to change; see Table 1 for more information.

System Configuration Settings

Note that for managed devices, many of these configurations are handled by a platform settings policy applied from the FMC; see Platform Settings Policies. For 7000/8000 series devices, you can also log into the local web interface for non-policy based system configurations; see Local System Configuration for 7000/8000 Series Devices.

Table 1. System Configuration Settings
Setting	Description
Access Control Preferences	Configure the system to prompt users for a comment when they add or modify an access control policy; see Policy Change Comments.
Access List	Control which computers can access the system on specific ports; see Access List.
Audit Log	Configure the system to send an audit log to an external host; see Audit Logs.
Audit Log Certificate	Configure the system to secure the channel when streaming the audit log to an external host; see Audit Log Certificate .
Change Reconciliation	Configure the system to send a detailed report of changes to the system over the last 24 hours; see Change Reconciliation.
Console Configuration	Configure console access via VGA or serial port, or via Lights-Out Management (LOM); see Remote Console Access Management.
Dashboard	Enable Custom Analysis widgets on the dashboard; see Dashboard Settings.
Database	Specify the maximum number of each type of event that the Firepower Management Center can store; see Database Event Limits.
DNS Cache	Configure the system to resolve IP addresses automatically on event view pages; see DNS Cache.
Email Notification	Configure a mail host, select an encryption method, and supply authentication credentials for email-based notifications and reporting; see Email Notifications.
External Database Access	Enable external read-only access to the database, and provide a client driver to download; see External Database Access Settings.
HTTPS Certificate	Request an HTTPS server certificate, if needed, from a trusted authority and upload certificates to the system; see HTTPS Certificates.
Information	View current information about the appliance and edit the display name; see Appliance Information.
Intrusion Policy Preferences	Configure the system to prompt users for a comment when they modify an intrusion policy; see Policy Change Comments.
Language	Specify a different language for the web interface; see Language Selection.
Login Banner	Create a custom login banner that appears when users log in; see Login Banners.
Management Interfaces	Change options such as the IP address, hostname, and proxy settings of the appliance; see Management Interfaces.
Network Analysis Policy Preferences	Configure the system to prompt users for a comment when they modify a network analysis policy; see Policy Change Comments.
Process	Shut down, reboot, or restart Firepower processes; see Shut Down or Restart.
Remote Storage Device	Configure remote storage for backups and reports; see Remote Storage Management.
REST API Preferences	Enable or disable access to the Firepower Management Center via the Firepower REST API; see REST API Preferences.
Shell Timeout	Configure the amount of idle time, in minutes, before a user’s login session times out due to inactivity; see Session Timeouts.
SNMP	Enable Simple Network Management Protocol (SNMP) polling; see SNMP Polling.
Time	View and change the current time setting; see Time and Time Synchronization.
Time Synchronization	Manage time synchronization on the system; see Time and Time Synchronization.
UCAPL/CC Compliance	Enable compliance with specific requirements set out by the United States Department of Defense; see Enable Security Certifications Compliance.
VMware Tools	Enable and use VMware Tools on a Firepower Management Center Virtual; see VMware Tools and Virtual Systems.
Vulnerability Mapping	Map vulnerabilities to a host IP address for any application protocol traffic received or sent from that address; see Vulnerability Mapping.

Appliance Information

The System > Configuration page of the web interface includes the information listed in the table below. Unless otherwise noted, all fields are read-only.

Note

See also the Help > About page, which includes similar but slightly different information.


Field	Description
Name	A name you assign to the appliance. Note that this name is only used within the context of the Firepower System. Although you can use the host name as the name of the appliance, entering a different name in this field does not change the host name.
Product Model	The model name of the appliance.
Serial Number	The serial number of the appliance.
Software Version	The version of the software currently installed on the appliance.
Prohibit Packet Transfer to the Firepower Management Center	Specifies whether the managed device sends packet data with events, allowing the data to be stored on the Firepower Management Center. This setting is available on the local web interface on 7000 and 8000 Series devices.
Operating System	The operating system currently running on the appliance.
Operating System Version	The version of the operating system currently running on the appliance.
IPv4 Address	The IPv4 address of the default (`eth0`) management interface. If IPv4 management is disabled, this field indicates that.
IPv6 Address	The IPv6 address of the default (`eth0`) management interface. If IPv6 management is disabled, this field indicates that.
Current Policies	The system-level policies currently deployed. If a policy has been updated since it was last deployed, the name of the policy appears in italics.
Model Number	The appliance-specific model number stored on the internal flash drive. This number may be important for troubleshooting.

HTTPS Certificates

Secure Sockets Layer (SSL)/TLS certificates enable Firepower Management Centers and 7000 and 8000 Series devices to establish an encrypted channel between the system and a web browser. A default certificate is included with all Firepower devices, but it is not generated by a certificate authority (CA) trusted by any globally known CA. For this reason, consider replacing it with a custom certificate signed by a globally known or internally trusted CA.

Caution

The FMC supports 2048-bit HTTPS certificates. If the certificate used by the FMC was generated using a public server key larger than 2048 bits, you will not be able to log in to the FMC web interface. If this happens, contact Cisco TAC.

Default HTTPS Server Certificates

If you use the default server certificate provided with an appliance, do not configure the system to require a valid HTTPS client certificate for web interface access because the default server certificate is not signed by the CA that signs your client certificate.

The default server certificate provided with an appliance expires 20 years from when it was first generated.

Custom HTTPS Server Certificates

You can use the Firepower Management Center web interface to generate a server certificate request based on your system information and the identification information you supply. You can use that request to sign a certificate if you have an internal certificate authority (CA) installed that is trusted by your browser. You can also send the resulting request to a certificate authority to request a server certificate. After you have a signed certificate from a certificate authority (CA), you can import it.

HTTPS Server Certificate Requirements

When you use HTTPS certificates to secure the connection between your web browser and the Firepower appliance web interface, you must use certificates that comply with the Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile (RFC 5280). When you import a server certificate to the appliance, the system rejects the certificate if it does not comply with version 3 (X.509 v3) of that standard.

Before importing an HTTPS server certificate, be certain it includes the following fields:


Certificate Field	Description
Version	Version of the encoded certificate. Use version `3`. See RFC 5280, section 4.1.2.1.
Serial number	A positive integer assigned to the certificate by the issuing CA. Issuer and serial number together uniquely identify the certificate. See RFC 5280, section 4.1.2.2.
Signature	Identifier for the algorithm used by the CA to sign the certificate. Must match the signatureAlgorithm field. See RFC 5280, section 4.1.2.3.
Issuer	Identifies the entity that signed and issued the certificate. See RFC 5280, section 4.1.2.4.
Validity	Interval during which the CA warrants that it will maintain information about the status of the certificate. See RFC 5280, section 4.1.2.5.
Subject	Identifies the entitity associated with the public key stored in the subject public key field; must be an X.500 disinguished name (DN). See RFC 5280, section 4.1.2.6.
Subject Public Key Info	Public key and an identifier for its algorithm. See RFC 5280, section 4.1.2.7.
Authority Key Identifier	Provides a means of identifying the public key corresponding to the private key used to sign a certificate. See RFC 5280, section 4.2.1.1.
Subject Key Identifier	Provides a means of identifying certificates that contain a particular public key. See RFC 5280, section 4.2.1.2.
Key Usage	Defines the purpose of the key contained in the certificates. See RFC 5280, section 4.2.1.3.
Basic Constraints	Identifies whether the certificate Subject is a CA, and the maximum depth of validation certification paths that include this certificate. See RFC 5280, section 4.2.1.9. For server certificates used in Firepower appliances, use `critical CA:FALSE`.
Extended Key Usage extension	Indicates one or more purposes for which the certified public key may be used, in addition to or in place of the basic purposes indicated in the Key Usage extension. See RFC 5280, section 4.2.1.12. Be certain you import certificates that can be used as server certificates.
signatureAlgorithm	Identifier for the algorithm the CA used to sign the certificate. Must match the Signature field. See RFC 5280, section 4.1.1.2.
signatureValue	Digital signature. See RFC 5280, section 4.1.1.3.

HTTPS Client Certificates

You can restrict access to the Firepower System web server using client browser certificate checking. When you enable user certificates, the web server checks that a user’s browser client has a valid user certificate selected. That user certificate must be generated by the same trusted certificate authority that is used for the server certificate. The browser cannot load the web interface under any of the following circumstances:

The user selects a certificate in the browser that is not valid.
The user selects a certificate in the browser that is not generated by the certificate authority that signed the server certificate.
The user selects a certificate in the browser that is not generated by a certificate authority in the certificate chain on the device.

To verify client browser certificates, configure the system to use the online certificate status protocol (OCSP) or load one or more certificate revocation lists (CRLs). Using the OCSP, when the web server receives a connection request it communicates with the certificate authority to confirm the client certificate's validity before establishing the connection. If you configure the server to load one or more CRLs, the web server compares the client certificate against those listed in the CRLs. If a user selects a certificate that is listed in a CRL as a revoked certificate, the browser cannot load the web interface.

Note

If you choose to verify certificates using CRLs, the system uses the same CRLs to validate both client browser certificates and audit log server certificates.

Viewing the Current HTTPS Server Certificate


Smart License	Classic License	Supported Devices	Supported Domains	Access
Any	Any	FMC 7000 and 8000 Series	Global only	Admin

You can only view server certificates for the appliance you are logged in to.

Procedure

Step 1	Choose System > Configuration.
Step 2	Click HTTPS Certificate.

Generating an HTTPS Server Certificate Signing Request


Smart License	Classic License	Supported Devices	Supported Domains	Access
N/A	Any	FMC 7000 and 8000 Series	Global only	Admin

If you install a certificate that is not signed by a globally known or internally trusted CA, the user's browser displays a security warning when they try to connect to the web interface.

A certificate signing request (CSR) is unique to the appliance or device from which you generated it. You cannot generate a CSR for multiple devices from a single appliance. Although all fields are optional, we recommend entering values for the following: CN, Organization, Organization Unit, City/Locality, State/Province, Country/Region.

The key generated for the certificate request is in Base-64 encoded PEM format.

Procedure

Step 1

Choose System > Configuration.

Step 2

Click HTTPS Certificate.

Step 3

Click Generate New CSR.

Step 4

Enter a country code in the Country Name (two-letter code) field.

Step 5

Enter a state or province postal abbreviation in the State or Province field.

Step 6

Enter a Locality or City.

Step 7

Enter an Organization name.

Step 8

Enter an Organizational Unit (Department) name.

Step 9

Enter the fully qualified domain name of the server for which you want to request a certificate in the Common Name field.

Note

Enter the fully qualified domain name of the server exactly as it should appear in the certificate in the Common Name field. If the common name and the DNS hostname do not match, you receive a warning when connecting to the appliance.

Step 10

Click Generate.

Step 11

Open a text editor.

Step 12

Copy the entire block of text in the certificate request, including the BEGIN CERTIFICATE REQUEST and END CERTIFICATE REQUEST lines, and paste it into a blank text file.

Step 13

Save the file as servername.csr, where servername is the name of the server where you plan to use the certificate.

Step 14

Click Close.

What to do next

Submit the certificate request to the certificate authority.
When you receive the signed certificate, import it to the Firepower Management Center; see Importing HTTPS Server Certificates.

Importing HTTPS Server Certificates


Smart License	Classic License	Supported Devices	Supported Domains	Access
Any	Any	FMC 7000 and 8000 Series	Global only	Admin

If the signing authority that generated the certificate requires you to trust an intermediate CA, you must also supply a certificate chain (or certificate path).

If you require client certificates, accessing an appliance via the web interface will fail when the server certificate does not meet either of the following criteria:

The certificate is signed by the same CA that signed the client certificate.
The certificate is signed by a CA that has signed an intermediate certificate in the certificate chain.

Caution

The Firepower Management Center supports 2048-bit HTTPS certificates. If the certificate used by the Firepower Management Center was generated using a public server key larger than 2048 bits, you will not be able to log in to the FMC web interface. For more information about updating HTTPS Certificates to Version 6.0.0, see "Update Management Center HTTPS Certificates to Version 6.0" in Firepower System Release Notes, Version 6.0. If you generate or import an HTTPS Certificate and cannot log in to the FMC web interface, contact Support.

Before you begin

Generate a certificate signing request; see Generating an HTTPS Server Certificate Signing Request.
Upload the CSR file to the certificate authority where you want to request a certificate, or use the CSR to create a self-signed certificate.
Confirm that the certificate meets the requirements described in HTTPS Server Certificate Requirements.

Procedure

Step 1	Choose System > Configuration.
Step 2	Click HTTPS Certificate.
Step 3	Click Import HTTPS Server Certificate.
Step 4	Open the server certificate in a text editor, copy the entire block of text, including the `BEGIN CERTIFICATE` and `END CERTIFICATE` lines. Paste this text into the Server Certificate field.
Step 5	Whether you must supply a Private Key depends on how you generated the Certificate Signing Request: If you generated the Certificate Signing Request using the Firepower Management Center web interface (as described in Generating an HTTPS Server Certificate Signing Request), the system already has the private key and you need not enter one here. If you generated the Certificate Signing Request using some other means, you must supply the private key here. Open the private key file and copy the entire block of text, include the `BEGIN RSA PRIVATE KEY` and `END RSA PRIVATE KEY` lines. Paste this text into the Private Key field.
Step 6	Open any required intermediate certificates, copy the entire block of text for each, and paste it into the Certificate Chain field.
Step 7	Click Save.

Requiring Valid HTTPS Client Certificates


Smart License	Classic License	Supported Devices	Supported Domains	Access
Any	Any	FMC 7000 and 8000 Series	Global only	Admin

The system supports validating HTTPS client certificates using either OCSP or imported CRLs in Privacy-enhanced Electronic Mail (PEM) format.

If you choose to use CRLs, to ensure that the list of revoked certificates stays current, you can create a scheduled task to update the CRLs. The system displays the most recent refresh of the CRLs.

Note

To access the web interface after enabling client certificates, you must have a valid client certificate present in your browser (or a CAC inserted in your reader).

Before you begin

Import a server certificate signed by the same certificate authority that signed the client certificate to be used for the connection; see Importing HTTPS Server Certificates.
Import the server certificate chain if needed; see Importing HTTPS Server Certificates.

Procedure

Step 1

Choose System > Configuration.

Step 2

Click HTTPS Certificate.

Step 3

Choose Enable Client Certificates. If prompted, select the appropriate certificate from the drop-down list.

Step 4

You have three options:

To verify client certificates using one or more CRLS, select Enable Fetching of CRL and continue with Step 5.
To verify client certificates using OCSP, select Enable OCSP and skip to Step 7.

To accept client certificates without checking for revocation, skip to Step 8.

Step 5

Enter a valid URL to an existing CRL file and click Add CRL. Repeat to add up to 25 CRLs.

Step 6

Click Refresh CRL to load the current CRL or CRLs from the specified URL or URLs.

Note

Enabling fetching of the CRL creates a scheduled task to regularly update the CRL or CRLs. Edit the task to set the frequency of the update.

Step 7

Verify that the client certificate is signed by the certificate authority loaded onto the appliance and the server certificate is signed by a certificate authority loaded in the browser certificate store. (These should be the same certificate authority.)

Caution

Saving a configuration with enabled client certificates, with no valid client certificate in your browser certificate store, disables all web server access to the appliance. Make sure that you have a valid client certificate installed before saving settings.

Step 8

Click Save.

External Database Access Settings

You can configure the Firepower Management Center to allow read-only access to its database by a third-party client. This allows you to query the database using SQL using any of the following:

industry-standard reporting tools such as Actuate BIRT, JasperSoft iReport, or Crystal Reports
any other reporting application (including a custom application) that supports JDBC SSL connections
the Cisco-provided command-line Java application called RunQuery, which you can either run interactively or use to obtain comma-separated results for a single query

Use the Firepower Management Center's system configuration to enable database access and create an access list that allows selected hosts to query the database. Note that this access list does not also control appliance access.

You can also download a package that contains the following:

RunQuery, the Cisco-provided database query tool
InstallCert, a tool you can use to retrieve and accept the SSL certificate from the Firepower Management Center you want to access
the JDBC driver you must use to connect to the database

See the Firepower System Database Access Guide for information on using the tools in the package you downloaded to configure database access.

Enabling External Access to the Database


Smart License	Classic License	Supported Devices	Supported Domains	Access
Any	Any	FMC	Global only	Admin

Procedure

Step 1

Choose System > Configuration.

Step 2

Click External Database Access.

Step 3

Select the Allow External Database Access check box.

Step 4

Enter an appropriate value in the Server Hostname field. Depending on your third-party application requirements, this value can be either the fully qualified domain name (FQDN), IPv4 address, or IPv6 address of the Firepower Management Center.

Step 5

Next to Client JDBC Driver, click Download and follow your browser’s prompts to download the client.zip package.

Step 6

To add database access for one or more IP addresses, click Add Hosts. An IP Address field appears in the Access List field.

Step 7

In the IP Address field, enter an IP address or address range, or any.

Step 8

Click Add.

Step 9

Click Save.

Tip

If you want to revert to the last saved database settings, click Refresh.

Database Event Limits

To manage disk space, the FMC periodically prunes the oldest intrusion events, audit records, Security Intelligence data, and URL filtering data from the event database. For each event type, you can specify how many records the FMC retains after pruning; never rely on the event database containing more records of any type than the retention limit configured for that type. To improve performance, tailor the event limits to the number of events you regularly work with. You can optionally choose to receive email notifications when pruning occurs. For some event types, you can disable storage.

To manually delete individual events, use the event viewer. You can also manually purge the database; see FMC Database Purge.

Configuring Database Event Limits


Smart License	Classic License	Supported Devices	Supported Domains	Access
Any	Any	FMC	Global only	Admin

Before you begin

If you want to receive email notifications when events are pruned from the Firepower Management Center's database, you must configure an email server; see Configuring a Mail Relay Host and Notification Address.

Procedure

Step 1	Choose System > Configuration.
Step 2	Choose Database.
Step 3	For each of the databases, enter the number of records you want to store. For information on how many records each database can maintain, see Database Event Limits.
Step 4	Optionally, in the Data Pruning Notification Address field, enter the email address where you want to receive pruning notifications.
Step 5	Click Save.

Database Event Limits

The following table lists the minimum and maximum number of records for each event type that you can store on a Firepower Management Center.

Table 2. Database Event Limits
Event Type	Upper Limit	Lower Limit
Intrusion events	10 million (FMC Virtual)  20 million (MC750)  30 million (MC1500) 60 million (MC2000) 150 million (MC3500)  300 million (MC4000)	10,000
Discovery events	10 million   20 million (MC2000, MC4000)	Zero (disables storage)
Connection events Security Intelligence events	50 million (FMC Virtual)  50 million (MC750)  100 million (MC1500)  300 million (MC2000) 500 million (MC3500)  1 billion (MC4000) Limit is shared between connection events and Security Intelligence events. The sum of the configured maximums cannot exceed this limit.	Zero (disables storage)
Connection summaries (aggregated connection events)	50 million (FMC Virtual)  50 million (MC750)  100 million (MC1500)  300 million (MC2000) 500 million (MC3500)  1 billion (MC4000)	Zero (disables storage)
Correlation events and compliance white list events	1 million   2 million (MC2000, MC4000)	One
Malware events	10 million   20 million (MC2000, MC4000)	10,000
File events	10 million  20 million (MC2000, MC4000)	Zero (disables storage)
Health events	1 million	Zero (disables storage)
Audit records	100,000	One
Remediation status events	10 million	One
White list violation history	a 30-day history of violations	One day’s history
User activity (user events)	10 million	One
User logins (user history)	10 million	One
Intrusion rule update import log records	1 million	One

Management Interfaces

After setup, you can change the management network settings, including adding more management interfaces, hostname, search domains, DNS servers, and HTTP proxy on both the FMC and the managed devices.

About Management Interfaces

By default, the Firepower Management Center manages all devices on a single management interface. Each device includes a single management interface for communicating with the FMC.

You also perform initial setup on the management interface (for both the FMC and managed devices), and log into the FMC on this interface as an administrator.

Management interfaces are also used to communicate with the Smart Licensing server, to download updates, and to perform other management functions.

Management Interfaces on the Firepower Management Center

The Firepower Management Center uses the eth0 interface for initial setup, HTTP access for administrators, management of devices, as well as other management functions such as licensing and updates.

You can also configure additional management interfaces on the same network, or on different networks. When the FMC manages large numbers of devices, adding more management interfaces can improve throughput and performance. You can also use these interfaces for all other management functions. You might want to use each management interface for particular functions; for example, you might want to use one interface for HTTP administrator access and another for device management.

For device management, the management interface carries two separate traffic channels: the management traffic channel carries all internal traffic (such as inter-device traffic specific to managing the device), and the event traffic channel carries all event traffic (such as web events). You can optionally configure a separate event-only interface on the FMC to handle event traffic; you can configure only one event interface. Event traffic can use a large amount of bandwidth, so separating event traffic from management traffic can improve the performance of the FMC. For example, you can assign a 10 GigabitEthernet interface to be the event interface, if available, while using 1 GigabitEthernet interfaces for management. You might want to configure an event-only interface on a completely secure, private network while using the regular management interface on a network that includes Internet access, for example. You can also use both management and event interfaces on the same network if the goal is only to take advantage of increased throughput. If you configure an event-only interface on the FMC, you can support devices with separate management and event-only interfaces, but also devices that do not have separate interfaces. For devices with a single combined management/event interface, all traffic goes to the FMC management interface.

Note

All management interfaces support HTTP administrator access as controlled by your Access List configuration (Configure an Access List). Conversely, you cannot restrict an interface to only HTTP access; management interfaces always support device management (management traffic, event traffic, or both).

Note

Only the eth0 interface supports DHCP IP addressing. Other management interfaces only support static IP addresses.

Management Interfaces on Managed Devices

Some models include an additional management interface that you can configure for event-only traffic, so you can separate management and event traffic when communicating with the FMC.

When you set up your device, you specify the FMC IP address that you want to connect to. Both management and event traffic go to this address at initial registration. Note: In some situations, the FMC might establish the initial connection on a different management interface; subsequent connections should use the management interface with the specified IP address.

If both the device and the FMC have separate event interfaces, then after they learn about each other's event interfaces during management communication, subsequent event traffic is sent between these interfaces if the network allows. If the event network goes down, then event traffic reverts to the regular management interface. The device uses a separate event interface when possible, but the management interface is always the backup. If you use only one management interface on the managed device, then you cannot send management traffic to the FMC management interface, and then send event traffic to the separate FMC event interface; both FMC and managed device must have separate event interfaces. In this case, both management and event traffic go to the FMC management interface, and the FMC event interface is not used for this device.

Management Interface Support

See the hardware installation guide for your model for the management interface locations.

Note

For the Firepower 4100/9300 chassis, the MGMT interface is for chassis management, not for FTD logical device management. You must configure a separate NIC interface to be of type mgmt (and/or firepower-eventing), and then assign it to the FTD logical device.

Note

For FTD on any chassis, the physical management interface is shared between the Diagnostic logical interface, which is useful for SNMP or syslog, and is configured along with data interfaces in the FMC, and the Management logical interface for FMC communication. See Management/Diagnostic Interface for more information.

See the following tables for supported management interfaces on each Firepower Management Center and managed device model.

Table 3. Management Interface Support on the Firepower Management Center
Model	Management Interfaces
MC750, MC1500, MC3500	eth0 (Default) eth1
MC2000, MC4000	eth0 (Default) eth1 eth2 eth3
	eth0 (Default) eth1 eth2 eth3
Firepower Management Center Virtual	eth0 (Default)

Table 4. Management Interface Support on Managed Devices

Model

Management Interface

Optional Event Interface

7000 series

eth0

No support

8000 series

eth0

eth1

NGIPSv

eth0

No support

ASA FirePOWER services module on the ASA 5585-X

eth0

Note

eth0 is the internal name of the Management 1/0 interface.

eth1

Note

eth1 is the internal name of the Management 1/1 interface.

ASA FirePOWER services module on the ASA 5506-X, 5508-X, or 5516-X

eth0

Note

eth0 is the internal name of the Management 1/1 interface.

No support

ASA FirePOWER services module on the ASA 5512-X through 5555-X

eth0

Note

eth0 is the internal name of the Management 0/0 interface.

No support

Firepower Threat Defense on the Firepower 4100 and 9300

management0

Note

management0 is the internal name of this interface, regardless of the physical interface ID.

management1

Note

management1 is the internal name of this interface, regardless of the physical interface ID.

Firepower Threat Defense on the ASA 5506-X, 5508-X, or 5516-X

br1

Note

br1 is the internal name of the Management 1/1 interface.

No support

Firepower Threat Defense on the 5512-X through 5555-X

br1

Note

br1 is the internal name of the Management 0/0 interface.

No support

Firepower Threat Defense Virtual

br1

No support

Network Routes on Management Interfaces

Management interfaces (including event-only interfaces) support only static routes to reach remote networks. When you set up your FMC or managed device, the setup process creates a default route to the gateway IP address that you specify. You cannot delete this route; you can only modify the gateway address.

The default route always uses the lowest-numbered management interface (e.g. eth0).

At least 1 static route is recommended per management interface to access remote networks, including when multiple interfaces are on the same network.

For example, on the FMC both eth0 and eth1 are on the same network, but you want to manage a different group of devices on each interface. The default gateway is 192.168.45.1. If you want eth1 to manage devices on the remote 10.6.6.0/24 destination network, you can create a static route for 10.6.6.0/24 through eth1 with the same gateway of 192.168.45.1. Traffic to 10.6.6.0/24 will hit this route before it hits the default route, so eth1 will be used as expected.

If you want to use 2 FMC interfaces to manage remote devices that are on the same network, then static routing on the FMC may not scale well, because you need separate static routes per device IP address.

Another example includes separate management and event-only interfaces on both the FMC and the managed device. The event-only interfaces are on a separate network from the management interfaces. In this case, add a static route through the event-only interface for traffic destined for the remote event-only network, and vice versa.

Note

The routing for management interfaces is completely separate from routing that you configure for data interfaces.

Management and Event Traffic Channel Examples

The following example shows the Firepower Management Center and managed devices using only the default management interfaces.

Figure 1. Single Management Interface on the Firepower Management Center

The following example shows the Firepower Management Center using separate management interfaces for devices; and each managed device using 1 management interface.

Figure 2. Mutliple Management Interfaces on the Firepower Management Center

The following example shows the Firepower Management Center and managed devices using a separate event interface.

Figure 3. Separate Event Interface on the Firepower Management Center and Managed Devices

The following example shows a mix of multiple management interfaces and a separate event interface on the Firepower Management Center and a mix of managed devices using a separate event interface, or using a single management interface.

Figure 4. Mixed Management and Event Interface Usage

Configure Management Interfaces

You can change management interface settings for Firepower appliances:

Firepower Management Center—Use the web interface. (We strongly recommend that you do not use the Firepower Management Center Linux shell unless directed by Cisco TAC or by explicit instructions in the FMC documentation.)
FTD devices, NGIPSv, ASA FirePOWER—Use the CLI
7000 & 8000 Series devices—Use the limited web interface or the CLI.

See the following sections.

Configure Firepower Management Center Management Interfaces


Smart License	Classic License	Supported Devices	Supported Domains	Access
Any	Any	FMC	Global only	Admin

Modify the management interface settings on the Firepower Management Center. You can optionally enable additional management interfaces or configure an event-only interface.

Caution

Be careful when making changes to the management interface to which you are connected; if you cannot re-connect because of a configuration error, you need to access the FMC console port to re-configure the network settings in the Linux shell. You must contact Cisco TAC to guide you in this operation.

Note

If you change the FMC IP address, then see the following tasks to ensure device management connectivity depending on how you added the device to the FMC:

IP address—No action. If you added the device to the FMC using a reachable device IP address, then the management connection will be reestablished automatically after several minutes. Note: If you specified a device IP address that is unreachable, then you must contact Cisco TAC, who can advise you how to restore connectivity for your devices.
NAT ID only—Contact Cisco TAC. If you added the device using only the NAT ID, then the connection cannot be reestablished. In this case, you must contact Cisco TAC, who can advise you how to restore connectivity for your devices.

Before you begin

If you use a proxy:

Proxies that use NT LAN Manager (NTLM) authentication are not supported.
If you use or will use Smart Licensing, the proxy FQDN cannot have more than 64 characters.

Procedure

Step 1

Choose System > Configuration, and then choose Management Interfaces.

Step 2

In the Interfaces area, click Edit next to the interface that you want to configure.

All available interfaces are listed in this section. You cannot add more interfaces.

You can configure the following options on each management interface:

Enabled—Enable the management interface. Do not disable the default eth0 management interface. Some processes require the eth0 interface.
Channels—Configure an event-only interface; you can configure only one event interface on the FMC. To do so, uncheck the Management Traffic check box, and leave the Event Traffic check box checked. You can optionally disable Event Traffic for the management interface(s). In either case, the device will try to send events to the event-only interface, and if that interface is down, it will send events on the management interface even if you disable the event channel. You cannot disable both event and management channels on an interface.
Mode—Specify a link mode. Note that any changes you make to auto-negotiation are ignored for GigabitEthernet interfaces.
MDI/MDIX—Set the Auto-MDIX setting.
MTU—Set the maximum transmission unit (MTU). The default is 1500. The range within which you can set the MTU can vary depending on the model and interface type.

Because the system automatically trims 18 bytes from the configured MTU value, any value below 1298 does not comply with the minimum IPv6 MTU setting of 1280, and any value below 594 does not comply with the minimum IPv4 MTU setting of 576. For example, the system automatically trims a configured value of 576 to 558.
IPv4 Configuration—Set the IPv4 IP address. Choose:
- Static—Manually enter the IPv4 Management IP address and IPv4 Netmask.
- DHCP—Set the interface to use DHCP (eth0 only).
- Disabled—Disable IPv4. Do not disable both IPv4 and IPv6.
IPv6 Configuration—Set the IPv6 IP address. Choose:
- Static—Manually enter the IPv6 Management IP address and IPv6 Prefix Length.
- DHCP—Set the interface to use DHCPv6 (eth0 only).
- Router Assigned—Enable stateless autoconfiguration.
- Disabled—Disable IPv6. Do not disable both IPv4 and IPv6.

Step 3

In the Routes area, edit a static route by clicking edit (), or add a route by clicking add (). View the route statistics by clicking view ().

You need a static route for each additional interface to reach remote networks. For more information about when new routes are needed, see Network Routes on Management Interfaces.

Note

For the default route, you can change only the gateway IP address. The default route always uses the eth0 interface.

You can configure the following settings for a static route:

Destination—Set the destination address of the network to which you want to create a route.
Netmask or Prefix Length—Set the netmask (IPv4) or prefix length (IPv6) for the network.
Interface—Set the egress management interface.
Gateway—Set the gateway IP address.

Step 4

In the Shared Settings area, set network parameters shared by all interfaces.

Note

If you selected DHCP for the eth0 interface, you cannot manually specify some shared settings derived from the DHCP server.

You can configure the following shared settings:

Hostname—Set the FMC hostname. If you change the hostname, reboot the FMC if you want the new hostname reflected in syslog messages. Syslog messages do not reflect a new hostname until after a reboot.
Domains—Set the search domain(s) for the FMC, separated by commas. These domains are added to hostnames when you do not specify a fully-qualified domain name in a command, for example, ping system . The domains are used only on the management interface, or for commands that go through the management interface.
Primary DNS Server, Secondary DNS Server, Tertiary DNS Server—Set the DNS servers to be used in order of preference.

Remote Management Port—Set the remote management port for communication with managed devices. The FMC and managed devices communicate using a two-way, SSL-encrypted communication channel, which by default is on port 8305.

Note

Cisco strongly recommends that you keep the default settings for the remote management port, but if the management port conflicts with other communications on your network, you can choose a different port. If you change the management port, you must change it for all devices in your deployment that need to communicate with each other.

Step 5

In the Proxy area, configure HTTP proxy settings.

The FMC is configured to directly-connect to the internet on ports TCP/443 (HTTPS) and TCP/80 (HTTP). You can use a proxy server, to which you can authenticate via HTTP Digest.

See proxy requirements in the prerequisites to this topic.

Check the Enabled check box.
In the HTTP Proxy field, enter the IP address or fully-qualified domain name of your proxy server.

See requirements in the prerequisites to this topic.
In the Port field, enter a port number.
Supply authentication credentials by choosing Use Proxy Authentication, and then provide a User Name and Password.

Step 6

Click Save.

Step 7

If you change the FMC IP address, then see the following tasks for device management connectivity depending on how you added the device to the FMC.

IP address—No action. If you added the device to the FMC using a reachable device IP address, then the management connection will be reestablished automatically after several minutes. Note: If you specified a device IP address that is unreachable, then you must contact Cisco TAC, who can advise you how to restore connectivity for your devices.
NAT ID only—Contact Cisco TAC. If you added the device using only the NAT ID, then the connection cannot be reestablished. In this case, you must contact Cisco TAC, who can advise you how to restore connectivity for your devices.

Configure Device Management Interfaces at the CLI


Smart License	Classic License	Supported Devices	Supported Domains	Access
Any	Any	Any	Global only	Admin

Modify the management interface settings on the managed device using the CLI. Many of these settings are ones that you set when you performed the initial setup; this procedure lets you change those settings, and set additional settings such as enabling an event interface if your model supports it, or adding static routes.

For information about the FTD CLI, see Command Reference for Firepower Threat Defense.

For information about the classic device CLI, see Classic Device Command Line Reference in this guide.

The FTD and classic devices use the same commands for management interface configuration. Other commands may differ between the platforms.

Note

When using SSH, be careful when making changes to the management interface; if you cannot re-connect because of a configuration error, you will need to access the device console port.

Note

If you change the device management IP address, then see the following tasks for FMC connectivity depending on how you identified the FMC during initial device setup using the configure manager add command (see Identify a New FMC):

IP address—No action. If you identified the FMC using a reachable IP address, then the management connection will be reestablished automatically after several minutes. To establish the connection faster, you can change the device IP address shown in FMC; see Editing Device Management Settings. Note: If you specified an unreachable FMC IP address, then see the procedure for NAT ID below.
NAT ID only—Manually reestablish the connection. If you identified the FMC using only the NAT ID, then the connection cannot be automatically reestablished. In this case, change the device management IP address in FMC according to Editing Device Management Settings.

Before you begin

For Firepower Threat Defense devices, you can create user accounts that can log into the CLI using the configure user add command; see Creating Local User Accounts for the FTD CLI.
For the 7000 & 8000 Series devices, you can create user accounts at the web interface as described in Creating a User Account.

Procedure

Step 1

Connect to the device CLI, either from the console port or using SSH.

See Logging Into the Command Line Interface on FTD Devices or Logging Into the CLI on 7000/8000 Series, ASA FirePOWER, and NGIPSv Devices.

Step 2

Log in with the Admin username and password.

Step 3

Enable an event-only interface (for supported models; see Management Interface Support):

configure network management-interface enable management_interface

configure network management-interface disable-management-channel management_interface

Example:

This example is for a Firepower 4100 or 9300 device; valid interface names differ by device type.


> configure network management-interface enable management1
Configuration updated successfully

> configure network management-interface disable-management-channel management1
Configuration updated successfully

>

The Firepower Management Center event-only interface cannot accept management channel traffic, so you should simply disable the management channel on the device event interface.

You can optionally disable events for the management interface using the configure network management-interface disable-events-channel command. In either case, the device will try to send events on the event-only interface, and if that interface is down, it will send events on the management interface even if you disable the event channel.

You cannot disable both event and management channels on an interface.

Step 4

Configure the network settings of the management interface and/or event interface:

If you do not specify the management_interface argument, then you change the network settings for the default management interface. When configuring an event interface, be sure to specify the management_interface argument. The event interface can be on a separate network from the management interface, or on the same network. If you are connected to the interface you are configuring, you will be disconnected. You can re-connect to the new IP address.

Configure the IPv4 address:
- Manual configuration:
  
  configure network ipv4 manual ip_address netmask gateway_ip [management_interface]
  
  Note that the gateway_ip in this command is only used to create the default route for the primary management interface. If you set the gateway for an event-only interface, then this command ignores the gateway and does not create a default or static route for it. You must create a static route separately using the configure network static-routes command.
  
  Example:
```
> configure network ipv4 manual 10.10.10.45 255.255.255.0 management1
Setting IPv4 network configuration.
Network settings changed.

>
```
- DHCP (supported on the default management interface only):
  
  configure network ipv4 dhcp
Configure the IPv6 address:
- Stateless autoconfiguration:
  
  configure network ipv6 router [management_interface]
  
  Example:
```
> configure network ipv6 router management0
Setting IPv6 network configuration.
Network settings changed.

>
```
- Manual configuration:
  
  configure network ipv6 manual ip6_address ip6_prefix_length [ip6_gateway_ip] [management_interface]
  
  Note that the ipv6_gateway_ip in this command is only used to create the default route for the primary management interface. If you set the gateway for an event-only interface, then this command ignores the gateway and does not create a default or static route for it. You must create a static route separately using the configure network static-routes command.
  
  Example:
```
> configure network ipv6 manual 2001:0DB8:BA98::3210 64 management1
Setting IPv6 network configuration.
Network settings changed.

>
```
- DHCPv6 (supported on the default management interface only):
  
  configure network ipv6 dhcp

Step 5

Add a static route for the event-only interface if the Firepower Management Center is on a remote network; otherwise, all traffic will match the default route through the management interface.

configure network static-routes {ipv4 | ipv6}add management_interface destination_ip netmask_or_prefix gateway_ip

For the default route, do not use this command; you can only change the default route gateway IP address when you use the configure network ipv4 or ipv6 commands for the default management interface (see step 4).

For information about routing, see Network Routes on Management Interfaces.

Example:


> configure network static-routes ipv4 add management1 192.168.6.0 255.255.255.0 10.10.10.1
Configuration updated successfully

> configure network static-routes ipv6 add management1 2001:0DB8:AA89::5110 64 2001:0DB8:BA98::3211
Configuration updated successfully

>

To display static routes, enter show network-static-routes (the default route is not shown):


> show network-static-routes
---------------[ IPv4 Static Routes ]---------------
Interface                 : management1
Destination               : 192.168.6.0
Gateway                   : 10.10.10.1
Netmask                   : 255.255.255.0
[…]

Step 6

Set the hostname:

configure network hostname name

Example:


> configure network hostname farscape1

Syslog messages do not reflect a new hostname until after a reboot.

Step 7

Set the search domains:

configure network dns searchdomains domain_list

Example:


> configure network dns searchdomains example.com,cisco.com

Set the search domain(s) for the device, separated by commas. These domains are added to hostnames when you do not specify a fully-qualified domain name in a command, for example, ping system . The domains are used only on the management interface, or for commands that go through the management interface.

Step 8

Set up to 3 DNS servers, separated by commas:

configure network dns servers dns_ip_list

Example:


> configure network dns servers 10.10.6.5,10.20.89.2,10.80.54.3

Step 9

Set the remote management port for communication with the FMC:

configure network management-interface tcpport number

Example:


> configure network management-interface tcpport 8555

The FMC and managed devices communicate using a two-way, SSL-encrypted communication channel, which by default is on port 8305.

Note

Cisco strongly recommends that you keep the default settings for the remote management port, but if the management port conflicts with other communications on your network, you can choose a different port. If you change the management port, you must change it for all devices in your deployment that need to communicate with each other.

Step 10

Configure an HTTP proxy. The device is configured to directly-connect to the internet on ports TCP/443 (HTTPS) and TCP/80 (HTTP). You can use a proxy server, to which you can authenticate via HTTP Digest. After issuing the command, you are prompted for the HTTP proxy address and port, whether proxy authentication is required, and if it is required, the proxy username, proxy password, and confirmation of the proxy password.

configure network http-proxy

Example:


> configure network http-proxy
Manual proxy configuration
Enter HTTP Proxy address: 10.100.10.10
Enter HTTP Proxy Port: 80
Use Proxy Authentication? (y/n) [n]: Y
Enter Proxy Username: proxyuser
Enter Proxy Password: proxypassword
Confirm Proxy Password: proxypassword

Step 11

If you change the device management IP address, then see the following tasks for FMC connectivity depending on how you identified the FMC during initial device setup using the configure manager add command (see Identify a New FMC):

IP address—No action. If you identified the FMC using a reachable IP address, then the management connection will be reestablished automatically after several minutes. To establish the connection faster, you can change the device IP address shown in FMC; see Editing Device Management Settings. Note: If you specified an unreachable FMC IP address, then you must manually reestablish the connection using Editing Device Management Settings.
NAT ID only—Manually reestablish the connection. If you identified the FMC using only the NAT ID, then the connection cannot be automatically reestablished. In this case, change the device management IP address in FMC according to Editing Device Management Settings.

Shut Down or Restart

Use the web interface to control the shut down and restart of processes on the FMC. You can:

Shut down: Initiate a graceful shutdown of the appliance.

Caution

Do not shut off Firepower appliances using the power button; it may cause a loss of data. Using the web interface (or CLI) prepares the system to be safely powered off and restarted without losing configuration data.

Reboot: Shut down and restart gracefully.
Restart the console: Restart the communications, database, and HTTP server processes. This is typically used during troubleshooting.

Tip

For information on shutting down/restarting a 7000/8000 series device, including restarting the Snort process, see Shut Down or Restart a 7000/8000 Series Device. For virtual devices, refer to the documentation for your virtual platform. For VMware in particular, custom power options are part of VMware Tools.

Shut Down or Restart the FMC


Smart License	Classic License	Supported Devices	Supported Domains
Any	Any	FMC	Global only	Admin

Procedure

Step 1

Choose System > Configuration.

Step 2

Choose Process.

Step 3

Do one of the following:

Shut down

Click Run Command next to Shutdown Management Center.

Reboot

Click Run Command next to Reboot Management Center.

Note

Rebooting logs you out, and the system runs a database check that can take up to an hour to complete.

Restart the console

Click Run Command next to Restart Management Center Console.

Note

Restarting may cause deleted hosts to reappear in the network map.

Remote Storage Management

On Firepower Management Centers, you can use the following for local or remote storage for backups and reports:

Network File System (NFS)
Server Message Block (SMB)/Common Internet File System (CIFS)
Secure Shell (SSH)

You cannot send backups to one remote system and reports to another, but you can choose to send either to a remote system and store the other on the Firepower Management Center.

Tip

After configuring and selecting remote storage, you can switch back to local storage only if you have not increased the connection database limit.

Configuring Local Storage


Smart License	Classic License	Supported Devices	Supported Domains	Access
Any	Any	FMC	Global only	Admin

Procedure

Step 1	Choose System > Configuration.
Step 2	Choose Remote Storage Device.
Step 3	Choose Local (No Remote Storage) from the Storage Type drop-down list.
Step 4	Click Save.

Configuring NFS for Remote Storage


Smart License	Classic License	Supported Devices	Supported Domains	Access
Any	Any	FMC	Global only	Admin

Before you begin

Ensure that your external remote storage system is functional and accessible from your FMC.

Procedure

Step 1	Choose System > Configuration.
Step 2	Click Remote Storage Device.
Step 3	Choose NFS from the Storage Type drop-down list.
Step 4	Add the connection information: Enter the IPv4 address or hostname of the storage system in the Host field. Enter the path to your storage area in the Directory field.
Step 5	Optionally, check the Use Advanced Options check box and enter any required command line options; see Remote Storage Management Advanced Options.
Step 6	Under System Usage: Choose Use for Backups to store backups on the designated host. Choose Use for Reports to store reports on the designated host. Enter Disk Space Threshold for backup to remote storage. Default is 90%.
Step 7	To test the settings, click Test.
Step 8	Click Save.

Configuring SMB for Remote Storage


Smart License	Classic License	Supported Devices	Supported Domains	Access
Any	Any	FMC	Global only	Admin

Before you begin

Ensure that your external remote storage system is functional and accessible from your FMC:

The system recognizes top-level SMB shares, not full file paths. You must use Windows to share the exact directory you want to use.
Make sure the Windows user you will use to access the SMB share from the FMC has ownership of and read/change access to the share location.

Procedure

Step 1	Choose System > Configuration.
Step 2	Click Remote Storage Device.
Step 3	Choose SMB from the Storage Type drop-down list.
Step 4	Add the connection information: Enter the IPv4 address or hostname of the storage system in the Host field. Enter the share of your storage area in the Share field. Optionally, enter the domain name for the remote storage system in the Domain field. Enter the user name for the storage system in the Username field and the password for that user in the Password field.
Step 5	Optionally, check the Use Advanced Options check box and enter any required command line options; see Remote Storage Management Advanced Options.
Step 6	Under System Usage: Choose Use for Backups to store backups on the designated host. Choose Use for Reports to store reports on the designated host.
Step 7	To test the settings, click Test.
Step 8	Click Save.

Configuring SSH for Remote Storage


Smart License	Classic License	Supported Devices	Supported Domains	Access
Any	Any	FMC	Global only	Admin

Before you begin

Ensure that your external remote storage system is functional and accessible from your Firepower Management Center.

Procedure

Step 1	Choose System > Configuration.
Step 2	Click Remote Storage Device.
Step 3	Choose SSH from the Storage Type drop-down list.
Step 4	Add the connection information: Enter the IP address or host name of the storage system in the Host field. Enter the path to your storage area in the Directory field. Enter the storage system’s user name in the Username field and the password for that user in the Password field. To specify a network domain as part of the connection user name, precede the user name with the domain followed by a forward slash (/). To use SSH keys, copy the content of the SSH Public Key field and place it in your authorized_keys file.
Step 5	Optionally, check the Use Advanced Options check box and enter any required command line options; see Remote Storage Management Advanced Options.
Step 6	Under System Usage: Choose Use for Backups to store backups on the designated host. Choose Use for Reports to store reports on the designated host.
Step 7	If you want to test the settings, you must click Test.
Step 8	Click Save.

Remote Storage Management Advanced Options

If you select the Network File System (NFS) protocol, Server Message Block (SMB) protocol, or SSH to use secure file transfer protocol (SFTP) to store your reports and backups, you can select the Use Advanced Options check box to use one of the mount binary options as documented in an NFS, SMB, or SSH mount man page.

If you select SMB, you can enter the security mode in the Command Line Options field using the following format:


sec=mode

where mode is the security mode you want to use for remote storage.

Table 5. SMB Security Mode Settings
Mode	Description
[none]	Attempt to connect as null user (no name).
`krb5`	Use Kerberos version 5 authentication.
`krb5i`	Use Kerberos authentication and packet signing.
`ntlm`	Use NTLM password hashing. (Default)
`ntlmi`	Use NTLM password hashing with signing (may be Default if `/proc/fs/cifs/PacketSigningEnabled` is on or if server requires signing).
`ntlmv2`	Use NTLMv2 password hashing.
`ntlmv2i`	Use NTLMv2 password hashing with packet signing.

Change Reconciliation

To monitor the changes that users make and ensure that they follow your organization’s preferred standard, you can configure the system to send, via email, a detailed report of changes made over the past 24 hours. Whenever a user saves changes to the system configuration, a snapshot is taken of the changes. The change reconciliation report combines information from these snapshots to present a clear summary of recent system changes.

The following sample graphic displays a User section of an example change reconciliation report and lists both the previous value for each configuration and the value after changes. When users make multiple changes to the same configuration, the report lists summaries of each distinct change in chronological order, beginning with the most recent.

You can view changes made during the previous 24 hours.

Configuring Change Reconciliation


Smart License	Classic License	Supported Devices	Supported Domains	Access
Any	Any	FMC 7000 and 8000 Series	Global only	Admin

Before you begin

Configure an email server to receive emailed reports of changes made to the system over a 24 hour period; see Configuring a Mail Relay Host and Notification Address for more information.

Procedure

Step 1

Choose System > Configuration.

Step 2

Click Change Reconciliation.

Step 3

Check the Enable check box.

Step 4

Choose the time of day you want the system to send out the change reconciliation report from the Time to Run drop-down lists.

Step 5

Enter email addresses in the Email to field.

Tip

Once you have added email addresses, click Resend Last Report to send recipients another copy of the most recent change reconciliation report.

Step 6

If you want to include policy changes, check the Include Policy Configuration check box.

Step 7

If you want to include all changes over the past 24 hours, check the Show Full Change History check box.

Step 8

Click Save.

Change Reconciliation Options

The Include Policy Configuration option controls whether the system includes records of policy changes in the change reconciliation report. This includes changes to access control, intrusion, system, health, and network discovery policies. If you do not select this option, the report will not show changes to any policies. This option is available on Firepower Management Centers only.

The Show Full Change History option controls whether the system includes records of all changes over the past 24 hours in the change reconciliation report. If you do not select this option, the report includes only a consolidated view of changes for each category.

Policy Change Comments

You can configure the Firepower System to track several policy-related changes using the comment functionality when users modify access control, intrusion, or network analysis policies.

With policy change comments enabled, administrators can quickly assess why critical policies in a deployment were modified. Optionally, you can have changes to intrusion and network analysis policies written to the audit log.

Configuring Comments to Track Policy Changes


Smart License	Classic License	Supported Devices	Supported Domains	Access
Any	Any	FMC	Global only	Admin

You can configure the Firepower System to prompt users for comments when they modify an access control policy, intrusion policy, or network analysis policy. You can use comments to track users’ reasons for policy changes. If you enable comments on policy changes, you can make the comment optional or mandatory. The system prompts the user for a comment when each new change to a policy is saved.

Procedure

Step 1	Choose System > Configuration. The system configuration options appear in the left navigation panel.
Step 2	Configure the policy comment preferences for any of the following: Click Access Control Preferences for comment preferences for access control policies. Click Intrusion Policy Preferences for comment preferences for intrusion policies. Click Network Analysis Policy Preferences for comment preferences for network analysis policies.
Step 3	You have the following choices for each policy type: Disabled—Disables change comments. Optional—Gives users the option to describe their changes in a comment. Required—Requires users to describe their changes in a comment before saving.
Step 4	Optionally for intrusion or network analysis policy comments: Check Write changes in Intrusion Policy to audit log to write all intrusion policy changes to the audit log. Check Write changes in Network Analysis Policy to audit log to write all network analysis policy changes to the audit log.
Step 5	Click Save.

Access List

You can limit access to the FMC by IP address and port. By default, the following ports are enabled for any IP address:

443 (HTTPS) for web interface access.
22 (SSH) for CLI access.

You can also add access to poll for SNMP information over port 161. Because SNMP is disabled by default, you must first enable SNMP before you can add SNMP access rules. For more information, see Configure SNMP Polling.

Caution

By default, access is not restricted. To operate in a more secure environment, consider adding access for specific IP addresses and then deleting the default any option.

Configure an Access List


Smart License	Classic License	Supported Devices	Supported Domains	Access
Any	Any	FMC	Any	Admin

This access list does not control external database access. See Enabling External Access to the Database.

Caution

If you delete access for the IP address that you are currently using to connect to the FMC, and there is no entry for “IP=any port=443”, you will lose access when you save.

To configure access lists for Classic devices, use device platform settings. See Configure Access Lists for Classic Devices.

Before you begin

By default, the access list includes rules for HTTPS and SSH. To add SNMP rules to the access list, you must first enable SNMP. For more information, see Configure SNMP Polling.

Procedure

Step 1	Choose System > Configuration.
Step 2	(Optional) Click SNMP to configure SNMP if you want to add SNMP rules to the access list. By default, SNMP is disabled; see Configure SNMP Polling.
Step 3	Click Access List.
Step 4	To add access for one or more IP addresses, click Add Rules.
Step 5	In the IP Address field, enter an IP address or address range, or `any.`
Step 6	Choose SSH, HTTPS, SNMP, or a combination of these options to specify which ports you want to enable for these IP addresses.
Step 7	Click Add.
Step 8	Click Save.

Audit Logs

The Firepower Management Center records user activity in read-only audit logs. You can review audit log data in several ways:

Use the web interface: Auditing the System.

Audit logs are presented in a standard event view where you can view, sort, and filter audit log messages based on any item in the audit view. You can easily delete and report on audit information and you can view detailed reports of the changes that users make.
Stream audit log messages to the syslog: Stream Audit Logs to Syslog..
Stream audit log messages to an HTTP server: Stream Audit Logs to an HTTP Server.

Streaming audit log data to an external server allows you to conserve space on the FMC. Note that sending audit information to an external URL may affect system performance.

Optionally, you can secure the channel for audit log streaming, enable TLS and mutual authentication using TLS certificates; see Audit Log Certificate.

Classic devices also maintain audit logs. To stream audit logs from a Classic devices, see Stream Audit Logs from Classic Devices.

Stream Audit Logs to Syslog


Smart License	Classic License	Supported Devices	Supported Domains	Access
Any	Any	FMC	Any	Admin

When this feature is enabled, audit log records appear in the syslog in the following format :

Date Time Host [Tag] Sender: User_Name@User_IP, Subsystem, Action

Where the local date, time, and originating hostname precede the bracketed optional tag, and the sending device name precedes the audit log message.

For example, if you specify a tag of FMC-AUDIT-LOG for audit log messages from your management center, a sample audit log message from your FMC could appear as follows:

Mar 01 14:45:24 localhost [FMC-AUDIT-LOG] Dev-MC7000: admin@10.1.1.2, Operations > Monitoring, Page View

If you specify a severity and facility, these values do not appear in syslog messages; instead, they tell the system that receives the syslog messages how to categorize them.

To stream audit logs from Classic devices, use device platform settings: Stream Audit Logs from Classic Devices.

Before you begin

Make sure the FMC can communicate with the syslog server. When you save your configuration, the system uses port 7/UDP to verify that the syslog server is reachable. Then, the system uses port 514/UDP to stream audit logs. If you secure the channel (optional, see Audit Log Certificate), the system uses 6514/TCP.

Procedure

Step 1

Choose System > Configuration.

Step 2

Click Audit Log.

Step 3

Choose Enabled from the Send Audit Log to Syslog drop-down menu.

Step 4

The following fields are applicable only for audit logs sent to syslog:


Option	Description
Host	The IP address or the fully qualified name of the syslog server to which you will send audit logs.
Facility	The subsystem that creates the message. Choose a facility described in Syslog Alert Facilities. For example, choose AUDIT.
Severity	The severity of the message. Choose a severity described in Syslog Severity Levels.
Tag	An optional tag to include in audit log syslog messages. Best practice: Enter a value in this field to easily differentiate audit log messages from other, similar syslog messages such as health alerts. For example, if you want all audit log records sent to the syslog to be labeled with `FMC-AUDIT-LOG`, enter `FMC-AUDIT-LOG` in the field.

Step 5

Click Save.

The system attempts to reach the syslog server on port 7/UDP.

Stream Audit Logs to an HTTP Server


Smart License	Classic License	Supported Devices	Supported Domains	Access
Any	Any	FMC	Any	Admin

When this feature is enabled, the appliance sends audit log records to an HTTP server in the following format:

Date Time Host [Tag] Sender: User_Name@User_IP, Subsystem, Action

Where the local date, time, and originating hostname precede the bracketed optional tag, and the sending appliance or device name precedes the audit log message.

For example, if you specify a tag of FROMMC, a sample audit log message could appear as follows:

Mar 01 14:45:24 localhost [FROMMC] Dev-MC7000: admin@10.1.1.2, Operations > Monitoring, Page View

To stream audit logs from Classic devices, use device platform settings: Stream Audit Logs from Classic Devices.

Before you begin

Make sure the device can communicate with the HTTP server. Optionally, secure the channel; see Audit Log Certificate.

Procedure

Step 1

Choose System > Configuration.

Step 2

Click Audit Log.

Step 3

Optionally, in the Tag field, enter the tag name that you want to appear with the message. For example, if you want all audit log records to be preceded with FROMMC, enter FROMMC in the field.

Step 4

Choose Enabled from the Send Audit Log to HTTP Server drop-down list.

Step 5

In the URL to Post Audit field, designate the URL where you want to send the audit information. Enter a URL that corresponds to a Listener program that expects the HTTP POST variables as listed:

subsystem
actor
event_type
message
action_source_ip
action_destination_ip
result
time
tag (if defined; see Step 3)

Caution

To allow encrypted posts, use an HTTPS URL. Sending audit information to an external URL may affect system performance.

Step 6

Click Save.

Audit Log Certificate

You can use Transport Layer Security (TLS) certificates to secure communications between Firepower appliances and a trusted audit log server.

Client Certificates (Required)

For each appliance (client certificates are unique), you must generate a certificate signing request (CSR), submit it to a Certificate Authority (CA) for signing, then import the signed certificate onto the appliance.

You cannot use the FMC to import audit log certificates onto its managed devices. These certificates are unique to each appliance, and you must log into each appliance to import them locally:

For the FMC, use the local system configuration: Obtain a Signed Audit Log Client Certificate for the FMC and Import an Audit Log Client Certificate into the FMC.
For 7000/8000 series devices, use the local system configuration: Obtain a Signed Client Certificate for Secure Audit Log Streaming on a 7000/8000 Series Device.
For ASA FirePOWER and NGIPSv, generate a CSR with a tool like OpenSSL, then use the CLI to import the signed certificate: configure audit_cert import .

Server Certificates (Optional)

For additional security, we recommend you require mutual authentication between Firepower appliances and the audit log server. To accomplish this, load one or more certificate revocation lists (CRLs). You cannot stream audit logs to servers with revoked certificates listed in those CRLs.

Firepower supports CRLs encoded in Distinguished Encoding Rules (DER) format. Note that these are the same CRLs that the system uses to validate HTTPS client certificates for the FMC web interface.

To require valid audit log server certificates, use the FMC web interface:

For the FMC, use the local system configuration: Require Valid Audit Log Server Certificates.
For Classic devices (including 7000/8000 series), use device platform settings: Require Valid Audit Log Server Certificates for Classic Devices.

Securely Stream Audit Logs


Smart License	Classic License	Supported Devices	Supported Domains	Access
Any	Any	FMC	Any	Admin

If you stream the audit log to a trusted HTTP server or syslog server, you can use Transport Layer Security (TLS) certificates to secure the channel between the FMC and the server. You must generate a unique client certificate for each appliance you want to audit.

To securely stream audit logs to Classic devices, see Stream Audit Logs from Classic Devices.

Before you begin

See ramifications of requiring client and server certificates at Audit Log Certificate.

Procedure

Step 1

Obtain and install a signed client certificate on the FMC:

Obtain a Signed Audit Log Client Certificate for the FMC:

Generate a Certificate Signing Request (CSR) from the FMC based on your system information and the identification information you supply.

Submit the CSR to a recognized, trusted certificate authority (CA) to request a signed client certificate.

If you will require mutual authentication between the FMC and the audit log server, the client certificate must be signed by the same CA that signed the server certificate to be used for the connection.
After you receive the signed certificate from the certificate authority, import it into the FMC. See Import an Audit Log Client Certificate into the FMC.

Step 2

Configure the communication channel with the server to use Transport Layer Security (TLS) and enable mutual authentication.

See Require Valid Audit Log Server Certificates.

Step 3

Configure audit log streaming if you have not yet done so.

See Stream Audit Logs to Syslog or Stream Audit Logs to an HTTP Server.

Obtain a Signed Audit Log Client Certificate for the FMC


Smart License	Classic License	Supported Devices	Supported Domains	Access
N/A	Any	FMC	Global only	Admin

To obtain a certificate for a managed Classic device, see Obtain a Signed Client Certificate for Secure Audit Log Streaming on a 7000/8000 Series Device.

The system generates certificate request keys in Base-64 encoded PEM format.

Before you begin

Keep the following in mind:

You must generate a certificate signing request (CSR) from the device or appliance on which you will install the certificate. (For example, you cannot generate a certificate signing request for Device B from Appliance A.) You must generate a unique certificate signing request from each device and appliance.
To ensure security, use a globally recognized and trusted Certificate Authority (CA) to sign your certificate.
If you will require mutual authentication between the appliance and the audit log server, the same Certificate Authority must sign both the client certificate and the server certificate.

Procedure

Step 1

Choose System > Configuration.

Step 2

Click Audit Log Certificate.

Step 3

Click Generate New CSR.

Step 4

Enter a country code in the Country Name (two-letter code) field.

Step 5

Enter a state or province postal abbreviation in the State or Province field.

Step 6

Enter a Locality or City.

Step 7

Enter an Organization name.

Step 8

Enter an Organizational Unit (Department) name.

Step 9

Enter the fully qualified domain name of the server for which you want to request a certificate in the Common Name field.

Note

If the common name and the DNS hostname do not match, audit log streaming will fail.

Step 10

Click Generate.

Step 11

Open a new blank file with a text editor.

Step 12

Copy the entire block of text in the certificate request, including the BEGIN CERTIFICATE REQUEST and END CERTIFICATE REQUEST lines, and paste it into a blank text file.

Step 13

Save the file as clientname.csr, where clientname is the name of the appliance where you plan to use the certificate.

Step 14

Click Close.

What to do next

Submit the certificate signing request to the certificate authority that you selected using the guidelines in the "Before You Begin" section of this procedure.
When you receive the signed certificate, import it to the appliance; see Import an Audit Log Client Certificate into the FMC.

Import an Audit Log Client Certificate into the FMC


Smart License	Classic License	Supported Devices	Supported Domains	Access
Any	Any	FMC	Global only	Admin

For ASA FirePOWER and NGIPSv, use the CLI to import a signed certificate: configure audit_cert import . For 7000/8000 series devices, use the system configuration (System > Configuration) on the device's local web interface: Obtain a Signed Client Certificate for Secure Audit Log Streaming on a 7000/8000 Series Device.

Before you begin

Obtain a Signed Audit Log Client Certificate for the FMC.
Make sure you are importing the signed certificate for the correct appliance. Each certificate is unique to a specific appliance or device.
If the signing authority that generated the certificate requires you to trust an intermediate CA, be prepared to provide the necessary certificate chain (or certificate path). The CA that signed the client certificate must be the same CA that signed any intermediate certificates in the certificate chain.

Procedure

Step 1	On the FMC, choose System > Configuration.
Step 2	Click Audit Log Certificate.
Step 3	Click Import Audit Client Certificate.
Step 4	Open the client certificate in a text editor, copy the entire block of text, including the `BEGIN CERTIFICATE` and `END CERTIFICATE` lines. Paste this text into the Client Certificate field.
Step 5	To upload a private key, open the private key file and copy the entire block of text, including the `BEGIN RSA PRIVATE KEY` and `END RSA PRIVATE KEY` lines. Paste this text into the Private Key field.
Step 6	Open any required intermediate certificates, copy the entire block of text for each, and paste it into the Certificate Chain field.
Step 7	Click Save.

Require Valid Audit Log Server Certificates


Smart License	Classic License	Supported Devices	Supported Domains	Access
Any	Any	FMC	Global only	Admin

The system supports validating audit log server certificates using imported CRLs in Distinguished Encoding Rules (DER) format.

Note

If you choose to verify certificates using CRLs, the system uses the same CRLs to validate both audit log server certificates and certificates used to secure the HTTP connection between an appliance and a web browser.

Before you begin

Understand the ramifications of requiring mutual authentication and of using certificate revocation lists (CRLs) to ensure that certificates are still valid. See Audit Log Certificate.
Obtain and import the client certificate following the steps in Securely Stream Audit Logs and the topics referenced in that procedure.

Procedure

Step 1

On the FMC, choose System > Configuration.

Step 2

Click Audit Log Certificate.

Step 3

To use Transport Layer Security to securely stream the audit log to an external server, choose Enable TLS.

Step 4

If you want to accept server certificates without verification (not recommended):

Deselect Enable Mutual Authentication.
Click Save and skip the remainder of this procedure.

Step 5

To verify the certificate of the audit log server, choose Enable Mutual Authentication.

Step 6

(If you enabled mutual authentication) To automatically recognize certificates that are no longer valid:

Select Enable Fetching of CRL.

Note

Enabling fetching of the CRL creates a scheduled task to regularly update the CRL or CRLs.

Enter a valid URL to an existing CRL file and click Add CRL.

Repeat to add up to 25 CRLs.
Click Refresh CRL to load the current CRL or CRLs from the specified URL or URLs.

Step 7

Verify that you have a valid server certificate generated by the same certificate authority that created the client certificate.

Step 8

Click Save.

What to do next

(Optional) Set the frequency of CRL updates. See Configuring Certificate Revocation List Downloads.

View the Audit Log Client Certificate on the FMC


Smart License	Classic License	Supported Devices	Supported Domains	Access
Any	Any	FMC	Global only	Admin

You can view the audit log client certificate only for the appliance that you are logged in to.

To view audit log certificates on Classic devices, use the system configuration on a 7000/8000 series device's web interface, or the CLI: show audit_cert .

Procedure

Step 1	Choose System > Configuration.
Step 2	Click Audit Log Certificate.

Dashboard Settings

Dashboards provide you with at-a-glance views of current system status through the use of widgets: small, self-contained components that provide insight into different aspects of the Firepower System. The Firepower System is delivered with several predefined dashboard widgets.

You can configure the Firepower Management Center so that Custom Analysis widgets are enabled on the dashboard.

Enabling Custom Analysis Widgets for Dashboards


Smart License	Classic License	Supported Devices	Supported Domains	Access
Any	Any	FMC	Global only	Admin

Use Custom Analysis dashboard widgets to create a visual representation of events based on a flexible, user-configurable query.

Procedure

Step 1	Choose System > Configuration.
Step 2	Click Dashboard.
Step 3	Check the Enable Custom Analysis Widgets check box to allow users to add Custom Analysis widgets to dashboards.
Step 4	Click Save.

DNS Cache

You can configure the system to resolve IP addresses automatically on the event view pages. You can also configure basic properties for DNS caching performed by the appliance. Configuring DNS caching allows you to identify IP addresses you previously resolved without performing additional lookups. This can reduce the amount of traffic on your network and speed the display of event pages when IP address resolution is enabled.

Configuring DNS Cache Properties


Smart License	Classic License	Supported Devices	Supported Domains	Access
Any	Any	FMC	Global only	Admin

DNS resolution caching is a system-wide setting that allows the caching of previously resolved DNS lookups.

Procedure

Step 1	Choose System > Configuration.
Step 2	Choose DNS Cache.
Step 3	From the DNS Resolution Caching drop-down list, choose one of the following: Enabled—Enable caching. Disabled—Disable caching.
Step 4	In the DNS Cache Timeout (in minutes) field, enter the number of minutes a DNS entry remains cached in memory before it is removed for inactivity. The default setting is 300 minutes (five hours).
Step 5	Click Save.

Email Notifications

Configure a mail host if you plan to:

Email event-based reports
Email status reports for scheduled tasks
Email change reconciliation reports
Email data-pruning notifications
Use email for discovery event, impact flag, correlation event alerting, intrusion event alerting, and health event alerting

When you configure email notification, you can select an encryption method for the communication between the system and mail relay host, and can supply authentication credentials for the mail server if needed. After configuring, you can test the connection.

Configuring a Mail Relay Host and Notification Address


Smart License	Classic License	Supported Devices	Supported Domains	Access
Any	Any	FMC	Global only	Admin

Procedure

Step 1

Choose System > Configuration.

Step 2

Click Email Notification.

Step 3

In the Mail Relay Host field, enter the hostname or IP address of the mail server you want to use. The mail host you enter must allow access from the appliance.

Step 4

In the Port Number field, enter the port number to use on the email server.

Typical ports include:

25, when using no encryption
465, when using SSLv3
587, when using TLS

Step 5

Choose an Encryption Method:

TLS—Encrypt communications using Transport Layer Security.
SSLv3—Encrypt communications using Secure Socket Layers.
None—Allow unencrypted communication.

Note

Certificate validation is not required for encrypted communication between the appliance and mail server.

Step 6

In the From Address field, enter the valid email address you want to use as the source email address for messages sent by the appliance.

Step 7

Optionally, to supply a user name and password when connecting to the mail server, choose Use Authentication. Enter a user name in the Username field. Enter a password in the Password field.

Step 8

To send a test email using the configured mail server, click Test Mail Server Settings.

A message appears next to the button indicating the success or failure of the test.

Step 9

Click Save.

Language Selection

You can use the Language page to specify a different language for the web interface.

Set the Language for the Web Interface


Smart License	Classic License	Supported Devices	Supported Domains	Access
Any	Any	FMC	Global only	Admin

The language you specify here is used for the web interface for every user. You can choose from:

English
Chinese (simplified)
Japanese
Korean

To set the language for 7000/8000 series devices, use device platform settings: Set the Language for the 7000/8000 Series Web Interface.

Procedure

Step 1	Choose System > Configuration.
Step 2	Click Language.
Step 3	Choose the language you want to use.
Step 4	Click Save.

Login Banners

You can use the Login Banner page to specify session, login, or custom message banners for a security appliance or shared policy.

You can use spaces but not tabs in banner text. You can specify multiple lines of text for the banner. If your text includes empty lines, the system displays this as a carriage return (CR) in the banner. You can only use ASCII characters, including new-line (press the Enter key), which counts as two characters.

When you access the security appliance through Telnet or SSH, the session closes if there is not enough system memory available to process the banner messages, or if a TCP write error occurs when attempting to display the banner messages.

Customize the Login Banner


Smart License	Classic License	Supported Devices	Supported Domains	Access
Any	Any	FMC	Any	Admin

To customize login banners for Classic devices, use device platform settings. See Customize the Login Banner for Classic Devices.

Procedure

Step 1	Choose System > Configuration.
Step 2	Choose Login Banner.
Step 3	In the Custom Login Banner field, enter the login banner text you want to use.
Step 4	Click Save.

SNMP Polling

You can enable Simple Network Management Protocol (SNMP) polling. This feature supports use of versions 1, 2, and 3 of the SNMP protocol. This feature allows access to the standard management information base (MIB), which includes system details such as contact, administrative, location, service information, IP addressing and routing information, and transmission protocol usage statistics.

Note

When selecting SNMP versions for the SNMP protocol, note that SNMPv2 only supports read-only communities and SNMPv3 only supports read-only users. SNMPv3 also supports encryption with AES128.

Enabling SNMP polling does not cause the system to send SNMP traps; it only makes the information in the MIBs available for polling by your network management system.

Configure SNMP Polling


Smart License	Classic License	Supported Devices	Supported Domains	Access
Any	Any	FMC	Any	Admin

To configure SNMP polling on Classic managed devices, use the device platform settings. See Configure SNMP Polling on Classic Devices.

Before you begin

Add SNMP access for each computer you plan to use to poll the system. See Configure an Access List.

Note

The SNMP MIB contains information that could be used to attack your deployment. We recommend that you restrict your access list for SNMP access to the specific hosts that will be used to poll for the MIB. We also recommend you use SNMPv3 and use strong passwords for network management access.

Procedure

Step 1

Choose System > Configuration.

Step 2

Click SNMP.

Step 3

From the SNMP Version drop-down list, choose the SNMP version you want to use:

Version 1 or Version 2: Enter a read-only SNMP community name in the Community String field, then skip to the end of the procedure.

Note

Do not include special characters (< > / % # & ? ', etc.) in the SNMP community string name.

Version 3: Click Add User to display the user definition page. SNMPv3 only supports read-only users and encryption with AES128.

Step 4

Enter a Username.

Step 5

Choose the protocol you want to use for authentication from the Authentication Protocol drop-down list.

Step 6

Enter the password required for authentication with the SNMP server in the Authentication Password field.

Step 7

Re-enter the authentication password in the Verify Password field.

Step 8

Choose the privacy protocol you want to use from the Privacy Protocol list, or choose None to not use a privacy protocol.

Step 9

Enter the SNMP privacy key required by the SNMP server in the Privacy Password field.

Step 10

Re-enter the privacy password in the Verify Password field.

Step 11

Click Add.

Step 12

Click Save.

Security Certifications Compliance

Your organization might be required to use only equipment and software complying with security standards established by the U.S. Department of Defense and global certification organizations. Firepower supports compliance with the following security certifications standards:

Common Criteria (CC): a global standard established by the international Common Criteria Recognition Arrangement, defining properties for security products

Unified Capabilities Approved Products List (UCAPL): a list of products meeting security requirements established by the U.S. Defense Information Systems Agency (DISA)

Note

The U.S. Government has changed the name of the Unified Capabilities Approved Products List (UCAPL) to the Department of Defense Information Network Approved Products List (DODIN APL). References to UCAPL in this documentation and the Firepower Management Center web interface can be interpreted as references to DODIN APL.

Federal Information Processing Standards (FIPS) 140: a requirements specification for encryption modules

You can enable security certifications compliance in CC mode or UCAPL mode. Enabling security certifications compliance does not guarantee strict compliance with all requirements of the security mode selected. For more information on hardening procedures, refer to the guidelines for this product provided by the certifying entity.

Caution

After you enable this setting, you cannot disable it. If you need to take an appliance out of CC or UCAPL mode, you must reimage.

Security Certifications Compliance Characteristics

The following table describes behavior changes when you enable CC or UCAPL mode. (Restrictions on login accounts refers to command line or shell access, not web interface access. )


System Change	CC Mode	UCAPL Mode
FIPS compliance is enabled.	Yes	Yes
The system does not allow remote storage for backups or reports.	Yes	Yes
The system starts an additional system audit daemon.	No	Yes
The system boot loader is secured.	No	Yes
The system applies additional security to login accounts.	No	Yes
The system disables the reboot key sequence Ctrl-Alt-Del.	No	Yes
The system enforces a maximum of ten simultaneous login sessions.	No	Yes
The system automtically rekeys an SSH session with an appliance: After a key has been in use for one hour of session activity After a key has been used to transmit 1 GB of data over the connection This applies to Version 6.1.0.4 or a subsequent 6.1.0.x patch.	Yes	Yes
The system supports exporting event data using eStreamer only for Version 6.1.0.6 or subsequent 6.1.0.x patches.	Yes	Yes
The system applies more stringent safeguards for login accounts: Passwords must be at least fifteen alphanumeric characters of mixed case and must include at least one numeric character. Passwords cannot be a word that appears in a dictionary or include consecutive repeating characters. The system locks out a user after three failed login attempts in a row. In this case, the password must be reset by an administrator. The system stores password history.	No	Yes

Security Certifications Compliance Recommendations

Cisco recommends that you observe the following best practices when using a system with security certifications compliance enabled:

To enable security certifications compliance in your deployment, enable it first on the Firepower Management Center, then enable it in the same mode on all managed devices.

Caution

The Firepower Management Center will not receive event data from a managed device unless both are operating in the same security certifications compliance mode.

For all users, enable password strength checking and set the minimum password length to the value required by the certifying agency.
If you are using Firepower Management Centers in a high-availability configuration, configure them both to use the same security certifications compliance mode.
Do not configure the system to use any of the following features:
- Email reports, alerts, or data pruning notifications.
- Nmap Scan, Cisco IOS Null Route, Set Attribute Value, or ISE EPS remediations.
- Remote storage for backups or reports.
- Third-party client access to the system database.
- External notifications or alerts transmitted via email, SNMP trap, or syslog.
- Audit log messages transmitted to an HTTP server or to a syslog server without using SSL certificates to secure the channel between the appliance and the server.
You may configure the system to export event data to an external client using eStreamer only for Version 6.1.0.6 and subsequent 6.1.0.x patches.
Do not enable external authentication using LDAP or RADIUS in deployments using CC mode.
Do not enable CACs in deployments using CC mode.
Disable access to the Firepower Management Center and managed devices via the Firepower REST API in deployments using CC or UCAPL mode.
Enable CACs in deployments using UCAPL mode.

Note

The Firepower System does not support CC or UCAPL mode for classic devices in stacks or high availability pairs.

Enable Security Certifications Compliance


Smart License	Classic License	Supported Devices	Supported Domains	Access
N/A	Any	FMC Classic	Any	Admin

This configuration applies to either a Firepower Management Center or a Classic managed device:

For the Firepower Management Center, this configuration is part of the system configuration.
For a managed device, you apply this configuration from the FMC as part of a platform settings policy.

In either case, the configuration does not take effect until you save your system configuration changes or deploy the shared platform settings policy.

Caution

After you enable this setting, you cannot disable it. If you need to take the appliance out of CC or UCAPL mode, you must reimage.

Before you begin

We recommend you register all devices that you plan to be part of your deployment to the FMC before enabling security certifications compliance on any appliances.

Procedure

Step 1

Depending on whether you are configuring an FMC or a managed device:

FMC: Choose System > Configuration.
Classic device: Choose Devices > Platform Settings and create or edit a Firepower policy.

Step 2

Click UCAPL/CC Compliance.

Note

Appliances reboot when you enable UCAPL or CC compliance. The FMC reboots when you save the system configuration; managed devices reboot when you deploy configuration changes.

Step 3

To permanently enable security certifications compliance on the appliance, you have two choices:

To enable security certifications compliance in Common Criteria mode, choose CC from the drop-down list.
To enable security certifications compliance in Unified Capabilities Approved Products List mode, choose UCAPL from the drop-down list.

Step 4

Click Save.

What to do next

If you have not already, apply Control and Protection licenses to all Classic devices in your deployment.
If your appliances were updated from versions earlier than Version 5.2.0, enabling security certifications compliance regenerates appliance certificates. After you enable security certifications compliance in the same mode across your deployment, reregister managed devices to the FMC.
Deploy configuration changes; see Deploy Configuration Changes.

Time and Time Synchronization

Synchronizing the system time on your Firepower Management Center (FMC) and its managed devices is essential to successful operation of your Firepower System. We recommend that you specify NTP servers during FMC initial configuration, but you can use the information in this section to establish or change time sychronization settings after intial configuration is complete.

Use a Network Time Protocol (NTP) server to synchronize system time on the FMC and all devices.

Caution

Unintended consequences can occur when time is not synchronized between the FMC and managed devices.

To synchronize time on FMC and managed devices, see:

Recommended: Synchronize Time on the FMC with an NTP Server

This topic includes links for instructions on configuring managed devices to synchronize with your FMC.
Otherwise: Synchronize Time Without Access to a Network NTP Server

This topic includes links for instructions on configuring managed devices to synchronize with your FMC.

Synchronize Time on the FMC with an NTP Server


Smart License	Classic License	Supported Devices	Supported Domains	Access
Any	Any	FMC	Global only	Admin Network Admin

Time synchronization among all of the components of your system is critically important.

The best way to ensure proper time synchronization between Firepower Management Center and all managed devices is to use an NTP server on your network.

Before you begin

Note the following:

If your FMC and managed devices cannot access a network NTP server, do not use this procedure. Instead, see Synchronize Time Without Access to a Network NTP Server.
Do not specify an untrusted NTP server.
Connections to NTP servers do not use configured proxy settings.
Firepower 4100 Series devices and Firepower 9300 devices cannot use this procedure to set the system time. Instead, configure those devices to use the same NTP server(s) that you configure using this procedure. For instructions, see the documentation for your hardware model.

Caution

If the Firepower Management Center is rebooted and your DHCP server sets an NTP server record different than the one you specify here, the DHCP-provided NTP server will be used instead. To avoid this situation, configure your DHCP server to use the same NTP server.

Procedure

Step 1	Choose System > Configuration.
Step 2	Click Time Synchronization.
Step 3	If Serve Time via NTP is Enabled, choose Disabled to disable the FMC as an NTP server.
Step 4	For the Set My Clock option, choose Via NTP from and enter the hostname or IP address of an NTP server. If your organization has corroborative NTP servers, enter multiple NTP servers as a comma-separated list.
Step 5	Click Save.

What to do next

Set managed devices to synchronize with the same NTP server or servers:

Configure device platform settings: Configure NTP Time Synchronization for Threat Defense and Synchronize Time on Classic Devices with an NTP Server.
Deploy configuration changes; see Deploy Configuration Changes.

Synchronize Time Without Access to a Network NTP Server


Smart License	Classic License	Supported Devices	Supported Domains	Access
Any	Any	FMC	Global only	Admin

If your devices cannot directly reach the network NTP server, or your organization does not have a network NTP server, a physical-hardware Firepower Management Center can serve as an NTP server.

Important

Do not use this procedure unless you have no other NTP server. Instead, use the procedure in Synchronize Time on the FMC with an NTP Server.
Do not use a virtual Firepower Management Center as an NTP server.

Procedure

Step 1

Manually set the system time on the Firepower Management Center:

Choose System > Configuration.
Click Time Synchronization.
If Serve Time via NTP is Enabled, choose Disabled.
Click Save.
For Set My Clock, choose Manually in Local Configuration.
Click Save.
In the navigation panel at the left side of the screen, click Time.
Use the Set Time drop-down lists to set the time.
If the time zone displayed is not UTC, click it and set the time zone to UTC.
Click Save.
Click Done.
Click Apply.

Step 2

Set the Firepower Management Center to serve as an NTP server:

In the navigation panel at the left side of the screen, click Time Synchronization.
For Serve Time via NTP, choose Enabled.
Click Save.

Step 3

Set managed devices to synchronize with the Firepower Management Center NTP server:

In the Time Synchronization settings for the platform settings policy assigned to your managed devices, set the clock to synchronize Via NTP from Management Center.
Deploy the change to managed devices.

For instructions:

For Firepower Threat Defense devices, see Configure NTP Time Synchronization for Threat Defense
For all other devices, see Synchronize Time on Classic Devices with an NTP Server

About Changing Time Synchronization Settings

Your Firepower Management Center and its managed devices are heavily dependent on accurate time. The system clock is a system facility that maintains the time of the Firepower System. The system clock is set to Universal Coordinated Time (UTC), which is the primary time standard by which the world regulates clocks and time.

DO NOT ATTEMPT TO CHANGE THE SYSTEM TIME. Changing the system time zone from UTC is NOT supported, and doing so will require you to reimage the device to recover from an unsupported state.
If you configure the FMC to serve time using NTP, and then later disable it, the NTP service on managed devices still attempts to synchronize time with the FMC. You must update and redeploy any applicable platform settings policies to establish a new time source.
To change the time manually after configuring the Firepower Management Center as an NTP server, you must disable the NTP option, change the time manually, and then re-enable the NTP option.

View Current System Time, Source, and NTP Server Connection Status


Smart License	Classic License	Supported Devices	Supported Domains	Access
Any	Any	FMC	Global only	Admin

Time settings are displayed on most pages in local time using the time zone you set on the Time Zone page in User Preferences (the default is America/New York), but are stored on the appliance using UTC time.

Restriction

The Time Zone function (in User Preferences) assumes that the default system clock is set to UTC time. DO NOT ATTEMPT TO CHANGE THE SYSTEM TIME. Be advised that changing the system time from UTC is NOT supported, and doing so will require you to reimage the device to recover from an unsupported state.

Note

To view time and time source information on your 7000- and 8000-Series hardware device, see View System Time for 7000/8000 Series Devices.

Procedure

Step 1

Choose System > Configuration.

Step 2

Click Time.

The current time is displayed using the time zone specified for your account in User Preferences.

If your appliance uses an NTP server: For information about the table entries, see NTP Server Status.

NTP Server Status

If you are synchronizing time from an NTP server, you can view connection status on the Time page (choose System > Configuration).

Table 6. NTP Status
Column	Description
NTP Server	The IP address or name of the configured NTP server.
Status	The status of the NTP server time synchronization: Being Used indicates that the appliance is synchronized with the NTP server. Available indicates that the NTP server is available for use, but time is not yet synchronized. Not Available indicates that the NTP server is in your configuration, but the NTP daemon is unable to use it. Pending indicates that the NTP server is new or the NTP daemon was recently restarted. Over time, its value should change to Being Used, Available, or Not Available. Unknown indicates that the status of the NTP server is unknown.
Offset	The number of milliseconds of difference between the time on the appliance and the configured NTP server. Negative values indicate that the appliance is behind the NTP server, and positive values indicate that it is ahead.
Last Update	The number of seconds that have elapsed since the time was last synchronized with the NTP server. The NTP daemon automatically adjusts the synchronization times based on a number of conditions. For example, if you see larger update times such as 300 seconds, that indicates that the time is relatively stable and the NTP daemon has determined that it does not need to use a lower update increment.

Session Timeouts

Unattended login sessions may be security risks. You can configure the amount of idle time before a user’s login session times out due to inactivity.

Note that you can exempt specific web interface users from timeout, for scenarios where you plan to passively, securely monitor the system for long periods of time. Users with the Administrator role, whose complete access to menu options poses an extra risk if compromised, cannot be made exempt from session timeouts.

Configure Session Timeouts


Smart License	Classic License	Supported Devices	Supported Domains	Access
Any	Any	FMC	Any	Admin

To configure session timeouts for Classic devices, use device platform settings. See Configure Session Timeouts for Classic Devices.

Procedure

Step 1	Choose System > Configuration.
Step 2	Click Shell Timeout.
Step 3	Configure session timeouts: Web interface (FMC only): Configure the Browser Session Timeout (Minutes). The default value is `60`; the maximum value is `1440` (24 hours). To exempt users from this session timeout, see User Account Login Options. CLI: Configure the Shell Timeout (Minutes) field. The default value is `0`; the maximum value is `1440` (24 hours).
Step 4	Click Save.

Vulnerability Mapping

The Firepower System automatically maps vulnerabilities to a host IP address for any application protocol traffic received or sent from that address, when the server has an application ID in the discovery event database and the packet header for the traffic includes a vendor and version.

For any servers which do not include vendor or version information in their packets, you can configure whether the system associates vulnerabilities with server traffic for these vendor and versionless servers.

For example, a host serves SMTP traffic that does not have a vendor or version in the header. If you enable the SMTP server on the Vulnerability Mapping page of a system configuration, then save that configuration to the Firepower Management Center managing the device that detects the traffic, all vulnerabilities associated with SMTP servers are added to the host profile for the host.

Although detectors collect server information and add it to host profiles, the application protocol detectors will not be used for vulnerability mapping, because you cannot specify a vendor or version for a custom application protocol detector and cannot select the server for vulnerability mapping.

Mapping Vulnerabilities for Servers


Smart License	Classic License	Supported Devices	Supported Domains	Access
Any	Protection	FMC	Global only	Admin

Procedure

Step 1

Choose System > Configuration.

Step 2

Choose Vulnerability Mapping.

Step 3

You have the following choices:

To prevent vulnerabilities for a server from being mapped to hosts that receive application protocol traffic without vendor or version information, clear the check box for that server.
To cause vulnerabilities for a server to be mapped to hosts that receive application protocol traffic without vendor or version information, check the check box for that server.

Tip

You can check or clear all check boxes at once using the check box next to Enabled.

Step 4

Click Save.

Remote Console Access Management

You can use a Linux system console for remote access on supported systems via either the VGA port (which is the default) or the serial port on the physical appliance. Use the Console Configuration page to choose the option most suitable to the physical layout of your organization’s Firepower deployment.

On supported physical-hardware-based Firepower systems, you can use Lights-Out Management (LOM) on the default (eth0) management interface on a Serial Over LAN (SOL) connection to remotely monitor or manage the system without logging into the management interface of the system. You can perform limited tasks, such as viewing the chassis serial number or monitoring such conditions as fan speed and temperature, using a command line interface on an out-of-band management connection.

You must enable LOM for both the system and the user you want to manage the system. After you enable the system and the user, you use a third-party Intelligent Platform Management Interface (IPMI) utility to access and manage your system.

Configuring Remote Console Settings on the System


Smart License	Classic License	Supported Devices	Supported Domains	Access
Any	Any	FMC 7000 & 8000 Series	Global only	Admin with LOM access

Before you begin

Disable Spanning Tree Protocol (STP) on any third-party switching equipment connected to the device’s management interface.

Procedure

Step 1

Choose System > Configuration.

Step 2

Click Console Configuration.

Step 3

Choose a remote console access option:

Choose VGA to use the appliance’s VGA port.
Choose Physical Serial Port to use the appliance’s serial port, or to use LOM/SOL on a Firepower Management Center, Firepower 7050, or 8000 Series device.
Choose Lights-Out Management to use LOM/SOL on a 7000 Series device (except the Firepower 7050). On these devices, you cannot use SOL and a regular serial connection at the same time.

Note

When you change your remote console from Physical Serial Port to Lights-Out Management or from Lights-Out Management to Physical Serial Port on the 70xx Family of devices (except the Firepower 7050), you may have to reboot the appliance twice to see the expected boot prompt.

Step 4

To configure LOM via SOL, enter the necessary IPv4 settings:

Choose the address Configuration for the system (DHCP or Manual)

Enter the IP Address to be used for LOM.

Note

The LOM IP address must be different from the management interface IP address of the system.

Enter the Netmask for the system.
Enter the Default Gateway for the system.

Step 5

Click Save.

What to do next

If you configured Lights-Out Management, enable a Lights-Out Management user; see Lights-Out Management User Access Configuration.

Lights-Out Management User Access Configuration

You must explicitly grant Lights-Out Management permissions to users who will use the feature. LOM users also have the following restrictions:

You must assign the Administrator role to the user.
The username may have up to 16 alphanumeric characters. Hyphens and longer user names are not supported for LOM users.
The password may have up to 20 alphanumeric characters, except when set on 71xx Family devices. If LOM is enabled on a Firepower 7110, 7115, 7120, or 7125 device, the password may have up to 16 alphanumeric characters. A user’s LOM password is the same as that user’s system password. Cisco recommends that you use a complex, non-dictionary-based password of the maximum supported length for your appliance and change it every three months.
Physical Firepower Management Centers and 8000 Series devices can have up to 13 LOM users. 8000 Series devices can have up to eight LOM users.

Note that if you deactivate, then reactivate, a role with LOM while a user with that role is logged in, or restore a user or user role from a backup during that user’s login session, that user must log back into the web interface to regain access to IPMItool commands.

Enabling Lights-Out Management User Access


Smart License	Classic License	Supported Devices	Supported Domains	Access
Any	Any	FMC 7000 & 8000 Series	Global only	Admin with LOM access

You configure LOM and LOM users on a per-system basis using each system’s local web interface. You cannot use the Firepower Management Center to configure LOM on a managed device. Similarly, because users are managed independently per appliance, enabling or creating a LOM-enabled user on the Firepower Management Center does not transfer that capability to users on managed devices.

Procedure

Step 1	Choose System > Configuration.
Step 2	Click Console Configuration.
Step 3	Click Lights Out Management.
Step 4	You have the following choices: To grant LOM user access to an existing user, click edit () next to a user name in the list. To grant LOM user access to a new user, click Create User.
Step 5	Under User Configuration, enable the Administrator role.
Step 6	Check the Allow Lights-Out Management Access check box.
Step 7	Click Save.

Serial Over LAN Connection Configuration

You use a third-party IPMI utility on your computer to create a Serial Over LAN connection to the appliance. If your computer uses a Linux-like or Mac environment, use IPMItool; for Windows environments, use IPMIutil.

Note

Cisco recommends using IPMItool version 1.8.12 or greater.

Linux

IPMItool is standard with many distributions and is ready to use.

Mac

You must install IPMItool on a Mac. First, confirm that your Mac has Apple's XCode Developer tools installed, making sure that the optional components for command line development are installed (UNIX Development and System Tools in newer versions, or Command Line Support in older versions). Then you can install macports and the IPMItool. Use your favorite search engine for more information or try these sites:


	https://developer.apple.com/technologies/tools/
	http://www.macports.org/

Windows

You must compile IPMIutil on Windows. If you do not have access to a compiler, you can use IPMIutil itself to compile. Use your favorite search engine for more information or try this site:


	http://ipmiutil.sourceforge.net/

Understanding IPMI Utility Commands

Commands used for IPMI utilities are composed of segments as in the following IPMItool example:


ipmitool -I lanplus -H IP_address -U user_name command

where:

ipmitool invokes the utility
-I lanplus enables encryption for the session
-H IP_address indicates the IP address of the appliance you want to access
-U user_name is the name of an authorized user

- command is the name of the command you want to give

Note

Cisco recommends using IPMItool version 1.8.12 or greater.

The same command for Windows looks like this:


ipmiutil command -V 4 -J 3 -N IP_address -Uuser_name

This command connects you to the command line on the appliance where you can log in as if you were physically present at the appliance. You may be prompted to enter a password.

Configuring Serial Over LAN with IPMItool


Smart License	Classic License	Supported Devices	Supported Domains	Access
Any	Any	FMC 7000 & 8000 Series	Any	Admin with LOM access

Procedure

Using IPMItool, enter the following command, and a password if prompted:


ipmitool -I lanplus -H IP_address -U user_name sol activate

Configuring Serial Over LAN with IPMIutil


Smart License	Classic License	Supported Devices	Supported Domains	Access
Any	Any	FMC 7000 & 8000 Series	Any	Admin with LOM access

Procedure

Using IPMIutil, enter the following command, and a password if prompted:


ipmiutil -J 3 -H IP_address -U username sol -a

Lights-Out Management Overview

Lights-Out Management (LOM) provides the ability to perform a limited set of actions over an SOL connection on the default (eth0) management interface without the need to log into the system. You use the command to create a SOL connection followed by one of the LOM commands. After the command is completed, the connection ends. Note that not all power control commands are valid on 70xx Family devices.

Note

The baseboard management controller (BMC) for a Firepower 71xx, Firepower 82xx, or a Firepower 83xx device is only accessible via 1 Gbps link speeds when the host is powered on. When the device is powered down, the BMC can only establish Ethernet link at 10 and 100 Mbps. Therefore if LOM is being used to remotely power the device, connect the device to the network using 10 and 100 Mbps link speeds only.

Caution

In rare cases, if your computer is on a different subnet than the system's management interface and the system is configured for DHCP, attempting to access LOM features can fail. If this occurs, you can either disable and then re-enable LOM on the system, or use a computer on the same subnet as the system to ping its management interface. You should then be able to use LOM.

Caution

Cisco is aware of a vulnerability inherent in the Intelligent Platform Management Interface (IPMI) standard (CVE-2013-4786). Enabling Lights-Out Management (LOM) on an system exposes this vulnerability. To mitigate this vulnerability, deploy your systems on a secure management network accessible only to trusted users and use a complex, non-dictionary-based password of the maximum supported length for your system and change it every three months. To prevent exposure to this vulnerability, do not enable LOM.

If all attempts to access your system have failed, you can use LOM to restart your system remotely. Note that if a system is restarted while the SOL connection is active, the LOM session may disconnect or time out.

Caution

Do not restart your system unless it does not respond to any other attempts to restart. Remotely restarting does not gracefully reboot the system and you may lose data.

Table 7. Lights-Out Management Commands
IPMItool	IPMIutil	Description
(not applicable)	`-V 4`	Enables admin privileges for the IPMI session
`-I lanplus`	`-J 3`	Enables encryption for the IPMI session
`-H`	`-N`	Indicates the IP address of the remote appliance
`-U`	`-U`	Indicates the username of an authorized LOM account
`sol activate`	`sol -a`	Starts the SOL session
`sol deactivate`	`sol -d`	Ends the SOL session
`chassis power cycle`	`power -c`	Restarts the appliance (not valid on 70xx Family devices)
`chassis power on`	`power -u`	Powers up the appliance
`chassis power off`	`power -d`	Powers down the appliance (not valid on  70xx Family devices)
`sdr`	`sensor`	Displays appliance information, such as fan speeds and temperatures

For example, to display a list of appliance information, the IPMItool command is:


ipmitool -I lanplus -H IP_address -U user_name sdr

Note

Cisco recommends using IPMItool version 1.8.12 or greater.

The same command with the IPMIutil utility is:


ipmiutil sensor -V 4 -J 3 -N IP_address -U user_name

Configuring Lights-Out Management with IPMItool


Smart License	Classic License	Supported Devices	Supported Domains	Access
Any	Any	FMC 7000 & 8000 Series	Any	Admin with LOM access

Procedure

Enter the following command for IPMItool and a password if prompted:


ipmitool -I lanplus -H IP_address -U user_name command

Configuring Lights-Out Management with IPMIutil


Smart License	Classic License	Supported Devices	Supported Domains	Access
Any	Any	FMC 7000 & 8000 Series	Any

Bias-Free Language

Results

Chapter: System Configuration

System Configuration

About System Configuration

Navigating the Firepower Management Center System Configuration

Procedure

System Configuration Settings

Appliance Information

HTTPS Certificates

Default HTTPS Server Certificates

Custom HTTPS Server Certificates

HTTPS Server Certificate Requirements

HTTPS Client Certificates

Viewing the Current HTTPS Server Certificate

Procedure

Generating an HTTPS Server Certificate Signing Request

Procedure

What to do next

Importing HTTPS Server Certificates

Before you begin

Procedure

Requiring Valid HTTPS Client Certificates

Before you begin

Procedure

External Database Access Settings

Enabling External Access to the Database

Procedure

Database Event Limits

Configuring Database Event Limits

Before you begin

Procedure

Database Event Limits

Management Interfaces

About Management Interfaces

Management Interfaces on the Firepower Management Center

Management Interfaces on Managed Devices

Management Interface Support

Network Routes on Management Interfaces

Management and Event Traffic Channel Examples

Configure Management Interfaces

Configure Firepower Management Center Management Interfaces

Before you begin

Procedure

Configure Device Management Interfaces at the CLI

Before you begin

Procedure

Example:

Example:

Example:

Example:

Example:

Example:

Example:

Shut Down or Restart

Shut Down or Restart the FMC

Procedure

Remote Storage Management

Configuring Local Storage

Procedure

Configuring NFS for Remote Storage

Before you begin

Procedure

Configuring SMB for Remote Storage

Before you begin

Procedure

Configuring SSH for Remote Storage

Before you begin

Procedure

Remote Storage Management Advanced Options

Change Reconciliation

Configuring Change Reconciliation

Before you begin

Procedure

Change Reconciliation Options

Policy Change Comments

Configuring Comments to Track Policy Changes

Procedure

Access List