The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This chapter describes how to configure the ASA FirePOWER module that runs on the ASA.
The ASA FirePOWER module supplies next-generation firewall services, including Next-Generation IPS (NGIPS), Application Visibility and Control (AVC), URL filtering, and Advanced Malware Protection (AMP).You can use the module in single or multiple context mode, and in routed or transparent mode.
The module is also known as ASA SFR.
Although the module has a basic command line interface (CLI) for initial configuration and troubleshooting, you configure the security policy on the device using a separate application, FireSIGHT Management Center, which can be hosted on a separate FireSIGHT Management Center appliance or as a virtual appliance running on a VMware server. (FireSIGHT Management Center is also known as Defense Center.)
You can configure your ASA FirePOWER module using one of the following deployment models:
Be sure to configure consistent policies on the ASA and the ASA FirePOWER. Both policies should reflect the inline or monitor-only mode of the traffic.
In inline mode, traffic goes through the firewall checks before being forwarded to the ASA FirePOWER module. When you identify traffic for ASA FirePOWER inspection on the ASA, traffic flows through the ASA and the module as follows:
2. Incoming VPN traffic is decrypted.
3. Firewall policies are applied.
4. Traffic is sent to the ASA FirePOWER module.
5. The ASA FirePOWER module applies its security policy to the traffic, and takes appropriate actions.
6. Valid traffic is sent back to the ASA; the ASA FirePOWER module might block some traffic according to its security policy, and that traffic is not passed on.
7. Outgoing VPN traffic is encrypted.
The following figure shows the traffic flow when using the ASA FirePOWER module in inline mode. In this example, the module blocks traffic that is not allowed for a certain application. All other traffic is forwarded through the ASA.
Figure 26-1 ASA FirePOWER Module Traffic Flow in the ASA
Note If you have a connection between hosts on two ASA interfaces, and the ASA FirePOWER service policy is only configured for one of the interfaces, then all traffic between these hosts is sent to the ASA FirePOWER module, including traffic originating on the non-ASA FirePOWER interface (because the feature is bidirectional).
This mode sends a duplicate stream of traffic to the ASA FirePOWER module for monitoring purposes only. The module applies the security policy to the traffic and lets you know what it would have done if it were operating in inline mode; for example, traffic might be marked “would have dropped” in events. You can use this information for traffic analysis and to help you decide if inline mode is desirable.
Note You cannot configure both inline tap monitor-only mode and normal inline mode at the same time on the ASA. Only one type of security policy is allowed. In multiple context mode, you cannot configure inline tap monitor-only mode for some contexts, and regular inline mode for others.
The following figure shows the traffic flow when operating in inline tap mode.
Figure 26-2 ASA FirePOWER Inline Tap Monitor-Only Mode
There are two separate layers of access for managing an ASA FirePOWER module: initial configuration (and subsequent troubleshooting) and policy management.
For initial configuration, you must use the CLI on the ASA FirePOWER module. For information on the default management addresses, see Default Settings.
To access the CLI, you can use the following methods:
– ASA FirePOWER console port—The console port on the module is a separate external console port.
– ASA FirePOWER Management 1/0 interface using SSH—You can connect to the default IP address or you can use ASDM to change the management IP address and then connect using SSH. The management interface on the module is a separate external Gigabit Ethernet interface.
Note You cannot access the ASA FirePOWER hardware module CLI over the ASA backplane using the session command.
– ASA session over the backplane—If you have CLI access to the ASA, then you can session to the module and access the module CLI.
– ASA FirePOWER Management 0/0 interface using SSH—You can connect to the default IP address or you can use ASDM to change the management IP address and then connect using SSH. These models run the ASA FirePOWER module as a software module. The ASA FirePOWER management interface shares the Management 0/0 interface with the ASA. Separate MAC addresses and IP addresses are supported for the ASA and ASA FirePOWER module. You must perform configuration of the ASA FirePOWER IP address within the ASA FirePOWER operating system (using the CLI or ASDM). However, physical characteristics (such as enabling the interface) are configured on the ASA. You can remove the ASA interface configuration (specifically the interface name) to dedicate this interface as an ASA FirePOWER-only interface. This interface is management-only.
After you perform initial configuration, configure the ASA FirePOWER security policy using FireSIGHT Management Center. Then configure the ASA policy for sending traffic to the ASA FirePOWER module using ASDM or Cisco Security Manager.
The ASA includes many advanced application inspection features, including HTTP inspection. However, the ASA FirePOWER module provides more advanced HTTP inspection than the ASA provides, as well as additional features for other applications, including monitoring and controlling application usage.
To take full advantage of the ASA FirePOWER module features, see the following guidelines for traffic that you send to the ASA FirePOWER module:
|
|
---|---|
The ASA FirePOWER module and FireSIGHT Management Center require additional licenses. See the Licensing chapter of the FireSIGHT System User Guide or the online help in FireSIGHT Management Center for more information.
Supported in multiple context mode.
Supported in routed and transparent firewall mode.
Does not support failover directly; when the ASA fails over, any existing ASA FirePOWER flows are transferred to the new ASA. The ASA FirePOWER module in the new ASA begins inspecting the traffic from that point forward; old inspection states are not transferred.
You are responsible for maintaining consistent policies on the ASA FirePOWER modules in the high-availability ASA pair (using FireSIGHT Management Center) to ensure consistent failover behavior.
Does not support clustering directly, but you can use these modules in a cluster. You are responsible for maintaining consistent policies on the ASA FirePOWER modules in the cluster using FireSIGHT Management Center. Do not use different ASA-interface-based zone definitions for devices in the cluster.
http://www.cisco.com/en/US/docs/security/asa/compatibility/asamatrx.html
Additional Guidelines and Limitations
The following table lists the default settings for the ASA FirePOWER module.
|
|
---|---|
– ASA 5585-X: Management 1/0 192.168.8.8/24 – ASA 5512-X through ASA 5555-X: Management 0/0 192.168.1.2/24 |
|
This section describes how to configure the ASA FirePOWER module.
Configuring the ASA FirePOWER module is a process that includes configuration of the ASA FirePOWER security policy on the ASA FirePOWER module and then configuration of the ASA to send traffic to the ASA FirePOWER module. To configure the ASA FirePOWER module, perform the following steps:
Step 1 Cable the ASA FirePOWER management interfaces and optionally, the console interface. See Connecting the ASA FirePOWER Management Interface.
Step 2 (ASA 5512-X through ASA 5555-X) Install the software module. See (ASA 5512-X through 5555-X) Installing or Reimaging the Software Module.
Step 3 (ASA 5585-X) Configure the ASA FirePOWER module management IP address for initial SSH access. See Changing the ASA FirePOWER Management IP Address.
Step 4 On the ASA FirePOWER module, configure basic settings. See Configuring Basic ASA FirePOWER Settings at the ASA FirePOWER CLI.
Step 5 Identify the FireSIGHT Management Center that will manage the device. See Adding ASA FirePOWER to the FireSIGHT Management Center.
Step 6 On the ASA FirePOWER module, configure the security policy using FireSIGHT Management Center. See Configuring the Security Policy on the ASA FirePOWER Module.
Step 7 On the ASA, identify traffic to divert to the ASA FirePOWER module. See Redirecting Traffic to the ASA FirePOWER Module.
In addition to providing management access to the ASA FirePOWER module, the ASA FirePOWER management interface needs access to an HTTP proxy server or a DNS server and the Internet for signature updates and more. This section describes recommended network configurations. Your network may differ.
The ASA FirePOWER module includes a separate management and console interface from the ASA. For initial setup, you can connect with SSH to the ASA FirePOWER Management 1/0 interface using the default IP address. If you cannot use the default IP address, you can either use the console port or use ASDM to change the management IP address so you can use SSH. (See Changing the ASA FirePOWER Management IP Address.)
If you have an inside router, you can route between the management network, which can include both the ASA Management 0/0 and ASA FirePOWER Management 1/0 interfaces, and the ASA inside network for Internet access. Be sure to also add a route on the ASA to reach the Management network through the inside router.
If you do not have an inside router
If you have only one inside network, then you cannot also have a separate management network, which would require an inside router to route between the networks. In this case, you can manage the ASA from the inside interface instead of the Management 0/0 interface. Because the ASA FirePOWER module is a separate device from the ASA, you can configure the ASA FirePOWER Management 1/0 address to be on the same network as the inside interface.
These models run the ASA FirePOWER module as a software module, and the ASA FirePOWER management interface shares the Management 0/0 interface with the ASA. For initial setup, you can connect with SSH to the ASA FirePOWER default IP address. If you cannot use the default IP address, you can either session to the ASA FirePOWER over the backplane or use ASDM to change the management IP address so you can use SSH.
If you have an inside router, you can route between the Management 0/0 network, which includes both the ASA and ASA FirePOWER management IP addresses, and the inside network for Internet access. Be sure to also add a route on the ASA to reach the Management network through the inside router.
If you do not have an inside router
If you have only one inside network, then you cannot also have a separate management network. In this case, you can manage the ASA from the inside interface instead of the Management 0/0 interface. If you remove the ASA-configured name from the Management 0/0 interface, you can still configure the ASA FirePOWER IP address for that interface. Because the ASA FirePOWER module is essentially a separate device from the ASA, you can configure the ASA FirePOWER management address to be on the same network as the inside interface.
Note You must remove the ASA-configured name for Management 0/0; if it is configured on the ASA, then the ASA FirePOWER address must be on the same network as the ASA, and that excludes any networks already configured on other ASA interfaces. If the name is not configured, then the ASA FirePOWER address can be on any network, for example, the ASA inside network.
If you purchase the ASA with the ASA FirePOWER module, the module software and required solid state drives (SSDs) come pre-installed and ready to configure. If you want to add the ASA FirePOWER software module to an existing ASA, or need to replace the SSD, you need to install the ASA FirePOWER boot software, partition the SSD, and install the system software according to this procedure.
Reimaging the module is the same procedure, except you should first uninstall the ASA FirePOWER module. You would reimage a system if you replace an SSD.
For information on how to physically install the SSD, see the ASA hardware guide.
Note If you have an active service policy redirecting traffic to an IPS or CX module, you must remove that policy. For example, if the policy is a global one, you would use no service-policy ips_policy global. You can remove the policies using CLI or ASDM.
Step 1 Download the boot image to the device. Do not transfer the system software; it is downloaded later to the SSD. You have the following options:
Step 2 Download the ASA FirePOWER system software from Cisco.com to an HTTP, HTTPS, or FTP server accessible from the ASA FirePOWER management interface.
Step 3 Set the ASA FirePOWER module boot image location in ASA disk0 by entering the following command:
Note If you get a message like “ERROR: Another service (cxsc) is running, only one service is allowed to run at any time,” it means that you already have a different software module configured. You must shut it down and remove it to install a new module as described in the prerequisites section above.
Step 4 Load the ASA FirePOWER boot image by entering the following command:
Step 5 Wait approximately 5-15 minutes for the ASA FirePOWER module to boot up, and then open a console session to the now-running ASA FirePOWER boot image. You might need to press enter after opening the session to get to the login prompt. The default username is admin and the default password is Admin123.
Tip If the module boot has not competed, the session command will fail with a message about not being able to connect over ttyS1. Wait and try again.
Step 6 Use the setup command to configure the system so that you can install the system software package.
You are prompted for the following. Note that the management address and gateway, and DNS information, are the key settings to configure.
Step 7 Install the System Software image using the system install command:
system install [ noconfirm ] url
Include the noconfirm option if you do not want to respond to confirmation messages. Use an HTTP, HTTPS, or FTP URL; if a username and password are required, you will be prompted to supply them.
When installation is complete, the system reboots. Allow 10 or more minutes for application component installation and for the ASA FirePOWER services to start. (The show module sfr output should show all processes as Up.)
Step 8 Open a session to the ASA FirePOWER module. You will see a different login prompt because you are logging into the fully functional module.
Step 9 Log in with the username admin and the password Sourcefire.
Step 10 Complete the system configuration as prompted.
You must first read and accept the end user license agreement (EULA). Then change the admin password, then configure the management address and DNS settings, as prompted. You can configure both IPv4 and IPv6 management addresses. For example:
Step 11 Identify the FireSIGHT Management Center appliance that will manage this device using the configure manager add command.
You come up with a registration key, which you will then use in FireSIGHT Management Center when you add the device to its inventory. The following example shows the simple case. When there is a NAT boundary, the command is different; see Adding ASA FirePOWER to the FireSIGHT Management Center.
Step 12 Log into the FireSIGHT Management Center using an HTTPS connection in a browser, using the hostname or address entered above. For example, https://DC.example.com.
Use the Device Management (Devices > Device Management) page to add the device. For more information, see the online help or the Managing Devices chapter in the FireSIGHT System User Guide.
Tip You also configure NTP and time settings through FireSIGHT Management Center. Use the Time Synchronization settings when editing the local policy from the System > Local > System Policy page.
If you cannot use the default management IP address, then you can set the management IP address from the ASA. After you set the management IP address, you can access the ASA FirePOWER module using SSH to perform additional setup.
If you already configured the management address during initial system setup through the ASA FirePOWER CLI, as described in Configuring Basic ASA FirePOWER Settings at the ASA FirePOWER CLI, then it is not necessary to configure it through the ASA CLI or ASDM.
Note For a software module, you can access the ASA FirePOWER CLI to perform setup by sessioning from the ASA CLI; you can then set the ASA FirePOWER management IP address as part of setup. For a hardware module, you can complete the initial setup through the Console port.
In multiple context mode, perform this procedure in the system execution space.
Step 1 In ASDM, choose Wizards > Startup Wizard.
Step 2 Click Next to advance through the initial screens until you reach the ASA FirePOWER Basic Configuration screen.
Step 3 Enter the new management IP address, subnet mask, and default gateway.
You must also accept the end user license agreement.
Step 4 Click Finish to skip the remaining screens, or click Next to advance through the remaining screens and complete the wizard.
You must configure basic network settings and other parameters on the ASA FirePOWER module before you can configure your security policy. This procedure assumes you have the full system software installed (not just the boot image), either after you installed it directly, or because it is already installed on a hardware module.
Tip This procedure also assumes that you are performing an initial configuration. During initial configuration, you are prompted for these settings. If you need to change these settings later, use the various configure network commands to change the individual settings. For more information on the configure network commands, use the ? command for help, and see the FireSIGHT System User Guide, or the online help in FireSIGHT Management Center.
Step 1 Do one of the following:
Step 2 Log in with the username admin and the password Sourcefire.
Step 3 Complete the system configuration as prompted.
You must first read and accept the end user license agreement (EULA). Then change the admin password, then configure the management address and DNS settings, as prompted. You can configure both IPv4 and IPv6 management addresses. The configuration is complete when you see the message that says the sensor must be managed by a FireSIGHT Management Center.
Step 4 Now you must identify the FireSIGHT Management Center that will manage this device, as explained in Adding ASA FirePOWER to the FireSIGHT Management Center.
You must register the ASA FirePOWER module to a FireSIGHT Management Center, which is the application you use to configure the policies on the module. FireSIGHT Management Center is also known as Defense Center.
To register a device, use the configure manager add command. A unique alphanumeric registration key is always required to register a device to a FireSIGHT Management Center. This is a simple key that you specify, and is not the same as a license key.
In most cases, you must provide the FireSIGHT Management Center’s hostname or the IP address along with the registration key, for example:
However, if the device and the FireSIGHT Management Center are separated by a NAT device, enter a unique NAT ID along with the registration key, and specify DONTRESOLVE instead of the hostname, for example:
Step 1 Do one of the following:
Step 2 Log in with the username admin or another username that has the CLI configuration (Administrator) access level.
Step 3 At the prompt, register the device to a FireSIGHT Management Center using the configure manager add command, which has the following syntax:
configure manager add { hostname | IPv4_address | IPv6_address | DONTRESOLVE } reg_key [ nat_id ]
Step 4 Log into the FireSIGHT Management Center using an HTTPS connection in a browser, using the hostname or address entered above. For example, https://DC.example.com.
Use the Device Management (Devices > Device Management) page to add the device. For more information, see the online help or the Managing Devices chapter in the FireSIGHT System User Guide.
You use FireSIGHT Management Center to configure the security policy on the ASA FirePOWER module. The security policy controls the services provided by the module, such as Next Generation IPS filtering and application filtering. You cannot configure the policy through the ASA FirePOWER CLI, the ASA CLI, or ASDM.
To open FireSIGHT Management Center, use a web browser to open the following URL:
Where DC_address is the DNS name or IP address of the manager you defined in Adding ASA FirePOWER to the FireSIGHT Management Center. For example, https://dc.example.com.
For information about how to configure the security policy, see the FireSIGHT System User Guide or the online help in FireSIGHT Management Center.
Tip You can also open FireSIGHT Management Center from the ASA FirePOWER Status dashboard in ASDM. Choose Home > ASA FirePOWER Status, and click the link at the bottom of the dashboard.
Redirect traffic to the ASA FirePOWER module by creating a service policy that identifies specific traffic that you want to send. ASA policies, such as access rules, are applied to the traffic before it is redirected to the module.
You can configure your device in either an inline or inline tap monitor-only deployment.
Note You cannot configure both monitor-only mode and normal inline mode at the same time on the ASA. Only one type of security policy is allowed. In multiple context mode, you cannot configure monitor-only mode for some contexts, and regular inline mode for others.
Step 1 Choose Configuration > Firewall > Service Policy Rules.
Step 2 Choose Add > Add Service Policy Rule. The Add Service Policy Rule Wizard - Service Policy dialog box appears.
Step 3 Complete the Service Policy dialog box as desired. See the ASDM online help for more information about these screens.
Step 4 Click Next. The Add Service Policy Rule Wizard - Traffic Classification Criteria dialog box appears.
Step 5 Complete the Traffic Classification Criteria dialog box as desired. See the ASDM online help for more information about these screens.
Step 6 Click Next to show the Add Service Policy Rule Wizard - Rule Actions dialog box.
Step 7 Click the ASA FirePOWER Inspection tab.
Step 8 Check the Enable ASA FirePOWER for this traffic flow check box.
Step 9 In the If ASA FirePOWER Card Fails area, click one of the following:
Step 10 (Optional) Check Monitor-only to send a read-only copy of traffic to the module, i.e. inline tap mode.
By default, the traffic is sent in inline mode. Be sure to configure consistent policies on the ASA and the ASA FirePOWER. Both policies should reflect the inline or monitor-only of the traffic.
Step 11 Click Finish and then Apply.
Repeat this procedure to configure additional traffic flows as desired.
This section includes procedures that help you manage the module.
If you forget the password for admin user, another user with CLI Configuration permissions can log in and change the password.
If there are no other users with the required permissions, you can reset the admin password from the ASA using the session do command.
Tip The password-reset option on the ASA hw-module and sw-module commands does not work with ASA FirePOWER.
In multiple context mode, perform this procedure in the system execution space.
To reload or reset the module, enter one of the following commands at the ASA CLI.
In multiple context mode, perform this procedure in the system execution space.
Shutting down the module software prepares the module to be safely powered off without losing configuration data. To gracefully shut down the module, perform the following steps at the ASA CLI.
Note If you reload the ASA, the module is not automatically shut down, so we recommend shutting down the module before reloading the ASA.
In multiple context mode, perform this procedure in the system execution space.
|
|
---|---|
For a hardware module (ASA 5585-X): For a software module (ASA 5512-X through ASA 5555-X): |
To uninstall a software module image and associated configuration, perform the following steps.
In multiple context mode, perform this procedure in the system execution space.
To access the ASA FirePOWER software module CLI from the ASA, you can session from the ASA. You can either session to the module (using Telnet) or create a virtual console session. A console session might be useful if the control plane is down and you cannot establish a Telnet session.
Use the ASA FirePOWER CLI to configure basic network settings and to troubleshoot the module.
If you need to reimage the ASA FirePOWER hardware module in an ASA 5585-X appliance for any reason, you need to install both the Boot Image and a System Software package, in that order. You must install both packages to have a functioning system. Under normal circumstances, you do not need to reimage the system to install upgrade packages.
To install the boot image, you need to TFTP boot the image from the Management-0 port on the ASA FirePOWER SSP by logging into the module’s Console port. Because the Management-0 port is on an SSP in the first slot, it is also known as Management1/0, but rommon recognizes it as Management-0 or Management0/1.
To accomplish a TFTP boot, you must:
Once the boot image is installed, you install the System Software package. You must place the package on an HTTP, HTTPS, or FTP server that is accessible from the ASA FirePOWER.
The following procedure explains how to install the boot image and then install the System Software package.
Step 1 Connect to the Console port. Use the console cable included with the ASA product to connect your PC to the console using a terminal emulator set for 9600 baud, 8 data bits, no parity, 1 stop bit, no flow control. See the hardware guide for your ASA for more information about the console cable.
Step 2 Enter the system reboot command to reload the system.
Step 3 When prompted, break out of the boot by pressing Esc. If you see grub start to boot the system, you have waited too long.
This will place you at the rommon prompt.
Step 4 At the rommon prompt, enter set and configure the following parameters:
Step 5 Enter sync to save the settings.
Step 6 Enter tftp to initiate the download and boot process.
You will see ! marks to indicate progress. When the boot completes after several minutes, you will see a login prompt.
Step 7 Log in as admin, with the password Admin123.
Step 8 Use the setup command to configure the system so that you can install the system software package.
You are prompted for the following. Note that the management address and gateway, and DNS information, are the key settings to configure.
Step 9 Install the System Software image using the system install command:
system install [ noconfirm ] url
Include the noconfirm option if you do not want to respond to confirmation messages.
When installation is complete, the system reboots. Allow 10 or more minutes for application component installation and for the ASA FirePOWER services to start.
Step 10 When the boot completes, log in as admin with the password Sourcefire.
Complete the system configuration as prompted.
You must first read and accept the end user license agreement (EULA). Then change the admin password, then configure the management address and DNS settings, as prompted. You can configure both IPv4 and IPv6 management addresses.
Step 11 Identify the FireSIGHT Management Center appliance that will manage this device using the configure manager add command.
You come up with a registration key, which you will then use in FireSIGHT Management Center when you add the device to its inventory. The following example shows the simple case. When there is a NAT boundary, the command is different; see Adding ASA FirePOWER to the FireSIGHT Management Center.
Step 12 Log into the FireSIGHT Management Center using an HTTPS connection in a browser, using the hostname or address entered above. For example, https://DC.example.com.
Use the Device Management (Devices > Device Management) page to add the device. For more information, see the Managing Devices chapter in the FireSIGHT System User Guide or the online help in FireSIGHT Management Center.
Use FireSIGHT Management Center to apply upgrade images to the ASA FirePOWER module. Before applying an upgrade, ensure that the ASA is running the minimum required release for the new version; you might need to upgrade the ASA prior to upgrading the module.
For more information about applying upgrades, see the FireSIGHT System User Guide or the online help in FireSIGHT Management Center.
Use Tools > Command Line Interface to use monitoring commands.
Note For ASA FirePOWER-related syslog messages, see the syslog messages guide. ASA FirePOWER syslog messages start with message number 434001.
From the Home page, you can select the ASA FirePOWER Status tab to view information about the module. This includes module information, such as the model, serial number, and software version, and module status, such as the application name and status, data plane status, and overall status. If the module is registered to a FireSIGHT Management Center, you can click the link to open the application and do further analysis and module configuration.
To show module statistics, enter the following command:
|
|
---|---|
Displays statistics and status for each service policy that includes the sfr command. Use clear service-policy to clear the counters. |
The following example shows the ASA FirePOWER service policy and the current statistics as well as the module status:
The following example shows a monitor-only policy. In this case, you should see packet input counters increasing, but the packet output counter should stay zero, because no traffic is passing back to the ASA.
To show connections through the ASA FirePOWER module, enter one of the following commands:
The show asp drop command can include the following drop reasons related to the ASA FirePOWER module.
The following is sample output from the show asp table classify domain sfr command:
To configure and view packet captures for the module, enter one of the following commands:
|
|
---|---|
Captures packets between module and the ASA on the backplane. |
|
Note Captured packets contain an additional AFBP header that your PCAP viewer might not understand; be sure to use the appropriate plug-in to view these packets.
The following table lists each feature change and the platform release in which it was implemented. ASDM is backwards-compatible with multiple platform releases, so the specific ASDM release in which support was added is not listed.