index int64 0 4.08k | text stringlengths 34 4.9k ⌀ | url stringclasses 38
values |
|---|---|---|
97 | Step 5 Specify the amount of time before a user is considered idle, meaning the ASA has not received traffic from
the user's IP address for the specified amount of time.
user-identity inactive-user-timer minutes minutes
Example:
ciscoasa(config)# user-identity inactive-user-timer minutes 120
When the timer expires, the... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa96/configuration/firewall/asa-96-firewall-config.pdf |
98 | Example:
ciscoasa(config)# user-identity user-not-found enable
Only the last 1024 IP addresses are tracked.
Step 10 Specify the action when the AD Agent is not responding.
user-identity action ad-agent-down disable-user-identity-rule
Example:
ciscoasa(config)# user-identity action ad-agent-down disable-user-identity-ru... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa96/configuration/firewall/asa-96-firewall-config.pdf |
99 | The hello timer between the ASA and the AD Agent defines how frequently the ASA exchanges hello packets.
The ASA uses the hello packet to obtain ASA replication status (in-sync or out-of-sync) and domain status
(up or down). If the ASA does not receive a response from the AD Agent, it resends a hello packet after the
s... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa96/configuration/firewall/asa-96-firewall-config.pdf |
100 | access-list 100 ex permit ip user CISCO\xyz any any
access-list 100 ex deny ip user CISCO\abc any any
access-list 100 ex permit ip user NONE any any
access-list 100 ex deny any any
access-group 100 in interface inside
access-list 200 ex deny ip user ANY any any
access-list 200 ex permit user NONE any any
aaa authentica... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa96/configuration/firewall/asa-96-firewall-config.pdf |
101 | Examples for the Identity Firewall
This section provides examples for the Identity Firewall.
AAA Rule and Access Rule Example 1
This example shows a typical cut-through proxy configuration to allow a user to log in through the ASA. In
this example, the following conditions apply:
• The ASA IP address is 172.1.1.118.
• ... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa96/configuration/firewall/asa-96-firewall-config.pdf |
102 | ciscoasa(config)# aaa authentication match listenerAuth inside ldap
ciscoasa(config)# aaa authentication listener http inside port 8888
ciscoasa(config)# access-list 100 ex permit ip user SAMPLE\user1 any any
ciscoasa(config)# access-list 100 ex deny ip user SAMPLE\user2 any any
ciscoasa(config)# access-list 100 ex per... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa96/configuration/firewall/asa-96-firewall-config.pdf |
103 | Although you can use user specifications in VPN filter ACLs, the user-based rules are interpreted
uni-directionally rather than bi-directionally, which is how VPN filter usually works. That is, you can filter
based on user-initiated traffic, but the filter does not apply for going from the destination back to the user.... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa96/configuration/firewall/asa-96-firewall-config.pdf |
104 | History for the Identity Firewall
Table 3: History for the Identity Firewall
Feature Name Releases Description
The Identity Firewall feature was
introduced.
We introduced or modified the following
commands: user-identity enable,
user-identity default-domain,
user-identity domain, user-identity
logout-probe, user-identi... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa96/configuration/firewall/asa-96-firewall-config.pdf |
105 | CLI Book 2: Cisco ASA Series Firewall CLI Configuration Guide, 9.6
84
Access Control
History for the Identity Firewall | https://www.cisco.com/c/en/us/td/docs/security/asa/asa96/configuration/firewall/asa-96-firewall-config.pdf |
106 | CHAPTER 6
ASA and Cisco TrustSec
This chapter describes how to implement Cisco TrustSec for the ASA.
• About Cisco TrustSec, on page 85
• Guidelines for Cisco TrustSec, on page 92
• Configure the ASA to Integrate with Cisco Trustsec, on page 95
• Example for Cisco TrustSec, on page 108
• AnyConnect VPN Support for Cisc... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa96/configuration/firewall/asa-96-firewall-config.pdf |
107 | • Offers exceptional control over activity of network users accessing physical or cloud-based IT resources
• Reducestotal cost of ownership through centralized, highly secure access policy management and scalable
enforcement mechanisms
• For more information, see the following URLs:
Reference Description
Describesthe C... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa96/configuration/firewall/asa-96-firewall-config.pdf |
108 | • Access Requester (AR)—Accessrequesters are endpoint devicesthat request accessto protected resources
in the network. They are primary subjects of the architecture and their access privilege depends on their
Identity credentials.
Access requesters include endpoint devices such PCs, laptops, mobile phones, printers, ca... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa96/configuration/firewall/asa-96-firewall-config.pdf |
109 | Figure 10: Security Group Name-Based Policy Enforcement Deployment
Implementing Cisco TrustSec allows you to configure security policies that support server segmentation and
includes the following features:
• A pool of servers can be assigned an SGT for simplified policy management.
• The SGT information is retained wi... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa96/configuration/firewall/asa-96-firewall-config.pdf |
110 | Figure 11: Security Policy Enforcement
1. An endpoint device connects to an access layer device directly or via remote access and authenticates
with Cisco TrustSec.
2. The access layer device authenticates the endpoint device with the ISE by using authentication methods
such as 802.1X or web authentication. The endpoin... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa96/configuration/firewall/asa-96-firewall-config.pdf |
111 | We recommend that you schedule policy configuration changes on the ISE during a maintenance window,
then manually refresh the security group table on the ASA to make sure the security group changes have been
incorporated.
Tip
Handling policy configuration changes in this way maximizes the chances of security group name... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa96/configuration/firewall/asa-96-firewall-config.pdf |
112 | • Listener mode—Configures the ASA so that it can receive IP-SGT mapping entries from downstream
devices (SGT-capable switches) and use that information to create policy definitions.
If one end of an SXP connection is configured as a Speaker, then the other end must be configured as a
Listener, and vice versa. If both ... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa96/configuration/firewall/asa-96-firewall-config.pdf |
113 | Create a Security Group on the ISE
When configuring the ASA to communicate with the ISE, you specify a AAA server. When configuring the
AAA server on the ASA, you must specify a server group. The security group must be configured to use the
RADIUS protocol. To create a security group on the ISE, perform the following s... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa96/configuration/firewall/asa-96-firewall-config.pdf |
114 | Failover
• You can configure security group-based policies on the ASA in both the Active/Active and Active/Standby
configurations.
• When the ASA is part of a failover configuration, you must import the PAC file to the primary ASA
device. You must also refresh the environment data on the primary device.
• The ASA can c... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa96/configuration/firewall/asa-96-firewall-config.pdf |
115 | • The ASASM does not support Layer 2 Security Group Tagging Imposition.
Additional Guidelines
• The ASA supportsSXP Version 3. The ASA negotiatesSXPversions with differentSXP-capable network
devices.
• You can configure the ASA to refresh the security group table when the SXP reconcile timer expires and
you can downloa... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa96/configuration/firewall/asa-96-firewall-config.pdf |
116 | with the changed security group; however, the ASA generates a syslog message to indicate that those
security policies changed.
• The multi-cast types are not supported in ISE 1.0.
• An SXP connection stays in the initializing state among two SXP peers interconnected by the ASA; as
shown in the following example:
(SXP p... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa96/configuration/firewall/asa-96-firewall-config.pdf |
117 | Procedure
Step 1 Configure the AAA Server for Cisco TrustSec Integration, on page 96
Step 2 Import a PAC File, on page 98
Step 3 Configure the Security Exchange Protocol, on page 99
This task enables and sets the default values for SXP.
Step 4 Add an SXP Connection Peer, on page 101
Step 5 Refresh Environment Data, on ... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa96/configuration/firewall/asa-96-firewall-config.pdf |
118 | Step 3 Configure a AAA server as part of a AAA server group and set host-specific connection data.
ciscoasa(config)# aaa-server server-tag(interface-name) host server-ip
Example:
ciscoasa(config)# aaa-server ISEserver (inside) host 192.0.2.1
The interface-name argument specifies the network interface where the ISE serv... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa96/configuration/firewall/asa-96-firewall-config.pdf |
119 | ciscoasa(config)# cts server-group ISEserver
Import a PAC File
This section describes how to import a PAC file.
Before you begin
• The ASA must be configured as a recognized Cisco TrustSec network device in the ISE before the ASA
can generate a PAC file.
• Obtain the password used to encrypt the PAC file when generatin... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa96/configuration/firewall/asa-96-firewall-config.pdf |
120 | Multi-mode
• http: Path and filename on HTTP
• https: Path and filename on HTTPS
• smb: Path and filename on SMB
• tftp: Path and filename on TFTP
The following example shows how to import a PAC file into the ASA:
ciscoasa(config)# cts import pac disk0:/pac123.pac password hideme
PAC file successfully imported
The foll... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa96/configuration/firewall/asa-96-firewall-config.pdf |
121 | configuration by entering the show running-config command, the command output displays the following
message:
“WARNING: SXP configuration in process, please wait for a few moments and try again.”
Procedure
Step 1 Enable SXP on the ASA. By default, SXP is disabled.
cts sxp enable
Example:
ciscoasa(config)# cts sxp enabl... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa96/configuration/firewall/asa-96-firewall-config.pdf |
122 | cts sxp retry period timervalue
Example:
ciscoasa(config)# cts sxp retry period 60
The ASA continues to make connection attempts until a successful connection is made, waiting the retry
interval before trying again after a failed attempt. You can specify a retry period from 0 to 64000 seconds.
The default is 120 second... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa96/configuration/firewall/asa-96-firewall-config.pdf |
123 | Example:
ciscoasa(config)# cts sxp connection peer 192.168.1.100 password default mode peer speaker
SXP connections are set per IP address; a single device pair can service multiple SXP connections.
The peer_ip_address argument is the IPv4 or IPv6 address of the SXP peer. The peer IP address must be
reachable from the ... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa96/configuration/firewall/asa-96-firewall-config.pdf |
124 | security group table, so refresh the data on the ASA to make sure that any security group changes made on
the ISE are reflected on the ASA.
We recommend that you schedule policy configuration changes on the ISE and the manual data refresh on
the ASA during a maintenance window. Handling policy configuration changes in ... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa96/configuration/firewall/asa-96-firewall-config.pdf |
125 | group-object it-admin // locally defined object-group as nested object
object-group security objgrp-hr-servers
security-group name hr-servers-sg-name
object-group security objgrp-hr-network
security-group tag 2
access-list hr-acl permit ip object-group-security objgrp-hr-admin any
object-group-security objgrp-hr-server... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa96/configuration/firewall/asa-96-firewall-config.pdf |
126 | per-interface configuration. This feature allows inline hop-by-hop propagation of endpoint identity across
network devices and provides seamless Layer 2 SGT Imposition between each hop.
The following figure shows a typical example of Layer 2 SGT Imposition.
Figure 12: Layer 2 SGT Imposition
Usage Scenarios
The followin... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa96/configuration/firewall/asa-96-firewall-config.pdf |
127 | Table 5: Egress Traffic
Interface Configuration Tagged or Untagged Packet Sent
No command is issued. Untagged
The cts manual command is issued. Tagged
The cts manual command and the propagate sgt Tagged
command are both issued.
The cts manual command and the no propagate sgt Untagged
command are both issued.
The follow... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa96/configuration/firewall/asa-96-firewall-config.pdf |
128 | ciscoasa(config)# interface gigabitethernet 0/0
Step 2 Enable Layer 2 SGT Imposition and enter cts manual interface configuration mode.
cts manual
Example:
ciscoasa(config-if)# cts manual
Step 3 Enable propagation of a security group tag on an interface. Propagation is enabled by default.
propagate sgt
Example:
ciscoas... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa96/configuration/firewall/asa-96-firewall-config.pdf |
129 | Example:
ciscoasa(config)# cts role-based sgt-map 10.2.1.2 sgt 50
You can specify an IPv4 or IPv6 host address. You can also specify network addresses by including a subnet
mask or prefix value (for IPv6), such as 10.100.10.0/24. The sgt_value is the SGT number, from 2 to 65519.
Troubleshooting Tips
Use the packet-trac... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa96/configuration/firewall/asa-96-firewall-config.pdf |
130 | cts sxp enable
cts sxp connection peer 192.168.1.100 password default mode peer speaker
//Configure security-group based policies
object-group security objgrp-it-admin
security-group name it-admin-sg-name
security-group tag 1
object-group security objgrp-hr-admin
security-group name hr-admin-sg-name
group-object it-adm... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa96/configuration/firewall/asa-96-firewall-config.pdf |
131 | There is no default SGT for group policies or local users.
Procedure
Step 1 To configure an SGT on a remote access VPN group policy:
a) Enter group-policy configuration mode:
group-policy name
Example:
ciscoasa(config)# group policy Grpolicy1
b) Configure the SGT for the group policy.
security-group-tag {none | value s... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa96/configuration/firewall/asa-96-firewall-config.pdf |
132 | Monitoring Cisco TrustSec
See the following commands for monitoring Cisco TrustSec:
• show running-config cts
• show running-config [all] cts role-based [sgt-map]
This command shows the user-defined IP-SGT binding table entries.
• show cts sxp connections
This command shows the SXP connections on the ASA for a particul... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa96/configuration/firewall/asa-96-firewall-config.pdf |
133 | History for Cisco TrustSec
Table 7: History for Cisco TrustSec
Description
Platform
Feature Name Releases
Cisco TrustSec provides access control that builds on an existing
identity-aware infrastructure to ensure data confidentiality between network
devices and integrate security accessservices on one platform. In the C... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa96/configuration/firewall/asa-96-firewall-config.pdf |
134 | CHAPTER 7
ASA FirePOWER Module
The following topics describe how to configure the ASA FirePOWER module that runs on the ASA.
• About the ASA FirePOWER Module, on page 113
• Licensing Requirements for the ASA FirePOWER Module, on page 117
• Guidelines for ASA FirePOWER, on page 117
• Defaults for ASA FirePOWER, on page ... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa96/configuration/firewall/asa-96-firewall-config.pdf |
135 | • Passive monitor-only (traffic forwarding) mode—If you want to prevent any possibility of the ASA with
FirePOWER Services device impacting traffic, you can configure a traffic-forwarding interface and
connect it to a SPAN port on a switch. In this mode, traffic is sent directly to the ASA FirePOWER
module without ASA ... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa96/configuration/firewall/asa-96-firewall-config.pdf |
136 | 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
bidirectiona... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa96/configuration/firewall/asa-96-firewall-config.pdf |
137 | Figure 15: ASA FirePOWER Passive Monitor-Only, Traffic-Forwarding Mode
ASA FirePOWER Management
The module has a basic command line interface (CLI) for initial configuration and troubleshooting only. You
configure the security policy on the ASA FirePOWER module using one of the following methods:
• Firepower/FireSIGHT ... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa96/configuration/firewall/asa-96-firewall-config.pdf |
138 | Firepower Management Center. This problem also occurs if you configure HTTP inspection on the ASA that
hosts the ASA FirePOWER module (which is a misconfiguration).
To resolve the issues, do any of the following that apply to your situation:
• If you configured HTTP inspection on the ASA that hosts the ASA FirePOWER mo... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa96/configuration/firewall/asa-96-firewall-config.pdf |
139 | ASA Clustering Guidelines
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.
Create the cluster before you configure the ASA FirePOWER modules. If the modules are already configured
on the... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa96/configuration/firewall/asa-96-firewall-config.pdf |
140 | • If the module isstuck in recover/init mode, you cannot reload the ASA gracefully. Instead, use the reload
quick command, so the ASA does not wait for the module to shut down gracefully prior to the system
reload. If quick reload does not work, you will have to force-crash the ASA to reload it.
• On the ASA 5500-X ser... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa96/configuration/firewall/asa-96-firewall-config.pdf |
141 | All management traffic to and from the ASA FirePOWER module must enter and exit the Management 1/0
or 1/1 interface. The ASA FirePOWER module also needs Internet access. Because the Management 1/x
interface is not an ASA data interface, traffic cannot pass through the ASA over the backplane; therefore you
need to physi... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa96/configuration/firewall/asa-96-firewall-config.pdf |
142 | For the ASA 5506-X, 5508-X, and 5516-X, the default configuration enables the above network deployment;
the only change you need to make is to set the module IPaddress to be on the same network as the ASA inside
interface and to configure the module gateway IP address.
For other models, you must remove the ASA-configur... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa96/configuration/firewall/asa-96-firewall-config.pdf |
143 | All management traffic to and from the ASA FirePOWER module must enter and exit the Management 1/0
or 1/1 interface. The ASA FirePOWER module also needs Internet access. Because this interface is not an
ASA data interface, traffic cannot pass through the ASA over the backplane; therefore you need to physically
cable th... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa96/configuration/firewall/asa-96-firewall-config.pdf |
144 | ASA 5506-X through ASA 5555-X, ISA 3000 (Software Module) in Transparent Mode
These models run the ASA FirePOWER module as a software module, and the ASA FirePOWER module
shares the Management 0/0 or Management 1/1 interface (depending on your model) with the ASA.
All management traffic to and from the ASA FirePOWER mo... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa96/configuration/firewall/asa-96-firewall-config.pdf |
145 | Register the ASA FirePOWER Module with a Management Center
To register the module with a Firepower/FireSIGHT Management Center, you must access the ASA
FirePOWER module CLI. The first time you access the CLI, you are prompted for basic configuration
parameters. You must also add the module to the Management Center.
Not... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa96/configuration/firewall/asa-96-firewall-config.pdf |
146 | Before you begin
Access the module CLI according to Access the ASA FirePOWER CLI, on page 124.
Procedure
Step 1 At the ASA FirePOWER CLI, log in with the username admin.
If this is the first time you are logging in, use the default password. See Defaults for ASA FirePOWER, on
page 119.
Step 2 Complete the system config... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa96/configuration/firewall/asa-96-firewall-config.pdf |
147 | > configure manager add {hostname | IPv4_address | IPv6_address | DONTRESOLVE} reg_key [nat_id]
where:
• {hostname | IPv4_address | IPv6_address | DONTRESOLVE} specifies either the fully qualified host
name or IP address of the Management Center. If the Management Center is not directly addressable,
use DONTRESOLVE.
• ... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa96/configuration/firewall/asa-96-firewall-config.pdf |
148 | Set the following values to work with the default configuration:
• IP Address—192.168.1.2
• Subnet Mask—255.255.255.0
• Gateway—192.168.1.1
Step 9 Click I accept the agreement, and click Next or Finish to complete the wizard.
Step 10 Quit ASDM, and then relaunch. You should see ASA Firepower tabs on the Home page.
CLI ... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa96/configuration/firewall/asa-96-firewall-config.pdf |
149 | Configure the ASA FirePOWER Module
Configure the security policy in the ASA FirePOWER module, and then configure the ASA to send traffic to
the module.
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
ap... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa96/configuration/firewall/asa-96-firewall-config.pdf |
150 | Before you begin
• Be sure to configure consistent policies on the ASA and the ASA FirePOWER module. Both policies
should reflect the inline or inline tap mode of the traffic.
• In multiple context mode, perform this procedure within each security context.
Procedure
Step 1 Create an L3/L4 class map to identify the traf... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa96/configuration/firewall/asa-96-firewall-config.pdf |
151 | hostname(config-pmap-c)# sfr fail-close
Step 5 If you created multiple class maps for ASA FirePOWER traffic, you can specify another class for the policy
and apply the sfr redirect action.
See Feature Matching Within a Service Policy, on page 235 for detailed information about how the order of
classes matters within a ... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa96/configuration/firewall/asa-96-firewall-config.pdf |
152 | hostname(config)# interface gigabitethernet 0/5
Step 2 Remove any name configured for the interface. If this interface was used in any ASA configuration, that
configuration is removed. You cannot configure traffic-forwarding on a named interface.
no nameif
Step 3 Enable traffic-forwarding.
traffic-forward sfr monitor-o... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa96/configuration/firewall/asa-96-firewall-config.pdf |
153 | Procedure
Step 1 Enable captive portal.
captive-portal {global | interface name} [port number]
Where:
• global enables captive portal globally on all interfaces.
• interface name enables captive portal on the specified interface only. You can enter the command multiple
times to enable it on more than one interface. You... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa96/configuration/firewall/asa-96-firewall-config.pdf |
154 | • You must shut down any other software module that you might be running; the ASA can run a single
software module at a time. You must do this from the ASA CLI.
• When reimaging the ASA FirePOWER module, use the sw-module module shutdown and uninstall
commands to remove the old image. For example:
sw-module module sfr ... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa96/configuration/firewall/asa-96-firewall-config.pdf |
155 | Step 4 Load the ASA FirePOWER boot image:
sw-module module sfr recover boot
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... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa96/configuration/firewall/asa-96-firewall-config.pdf |
156 | asasfr-boot> system install http://upgrades.example.com/packages/asasfr-sys-5.4.1-58.pkg
Verifying
Downloading
Extracting
Package Detail
Description: Cisco ASA-FirePOWER 5.4.1-58 System Install
Requires reboot: Yes
Do you want to continue with upgrade? [y]: y
Warning: Please do not interrupt the process or turn off the... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa96/configuration/firewall/asa-96-firewall-config.pdf |
157 | Before you begin
To accomplish a TFTP boot, you must:
• Place the Boot Image and a System Software package on a TFTP server that can be accessed through
the Management1/0 interface on the ASA FirePOWER module.
• Connect Management1/0 to the network. You must use this interface to TFTP boot the Boot Image.
Procedure
Ste... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa96/configuration/firewall/asa-96-firewall-config.pdf |
158 | Step 8 Configure the system so that you can install the system software package:
setup
You are prompted for the following. Note that the management address and gateway, and DNS information,
are the key settings to configure.
• Host name—Up to 65 alphanumeric characters, no spaces. Hyphens are allowed.
• Network address... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa96/configuration/firewall/asa-96-firewall-config.pdf |
159 | session {1 | sfr} do password-reset
Use 1 for a hardware module, sfr for a software module.
Reload or Reset the Module
You can reload, or to reset and then reload, the module from the ASA.
Before you begin
In multiple context mode, perform this procedure in the system execution space.
Procedure
Enter one of the followi... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa96/configuration/firewall/asa-96-firewall-config.pdf |
160 | • Software module (all other models):
sw-module module sfr shutdown
Uninstall a Software Module Image
You can uninstall a software module image and its associated configuration.
Before you begin
In multiple context mode, perform this procedure in the system execution space.
Procedure
Step 1 Uninstall the software modul... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa96/configuration/firewall/asa-96-firewall-config.pdf |
161 | session sfr
When in the ASA FirePOWER CLI, to exit back to the ASA CLI, enter any command that would log
you out of the module, such as logout or exit, or press Ctrl-Shift-6, x.
• Console session:
session sfr console
The only way out of a console session is to press Ctrl-Shift-6, x. Logging out of the module leaves you... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa96/configuration/firewall/asa-96-firewall-config.pdf |
162 | The following issample output from the show module command for an ASA 5585-X with an ASA FirePOWER
hardware module installed:
hostname# show module
Mod Card Type Model Serial No.
---- -------------------------------------------- ------------------ -----------
0 ASA 5585-X Security Services Processor-10 wi ASA5585-SSP-1... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa96/configuration/firewall/asa-96-firewall-config.pdf |
163 | Showing Module Statistics
Use the show service-policy sfr command to display 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. ... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa96/configuration/firewall/asa-96-firewall-config.pdf |
164 | • sfr-ha-request—This counter is incremented when the security appliance receives a FirePOWER HA
request packet, but could not process it and the packet is dropped.
• sfr-invalid-encap—This counter is incremented when the security appliance receives a FirePOWER
packet with invalid message header, and the packet is drop... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa96/configuration/firewall/asa-96-firewall-config.pdf |
165 | hostname(config-pmap-c)# service-policy my-sfr-policy global
The following example diverts all IP traffic destined for the 10.1.1.0 network and the 10.2.1.0 network to the
ASA FirePOWER module, and allows all traffic through if the module fails for any reason.
hostname(config)# access-list my-sfr-acl permit ip any 10.1... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa96/configuration/firewall/asa-96-firewall-config.pdf |
166 | Description
Platform
Feature Releases
You can manage the module using ASDM instead of using
FireSIGHT Management Center.
No new screens or commands were added.
ASA 9.4(1)
ASDM 7.4(1)
ASA
FirePOWER
5.4.1
Support for managing the module through ASDM
for the 5506H-X, 5506W-X, 5508-X, and
5516-X.
You can manage the module ... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa96/configuration/firewall/asa-96-firewall-config.pdf |
167 | CLI Book 2: Cisco ASA Series Firewall CLI Configuration Guide, 9.6
146
Access Control
History for the ASA FirePOWER Module | https://www.cisco.com/c/en/us/td/docs/security/asa/asa96/configuration/firewall/asa-96-firewall-config.pdf |
168 | P ART II
Network Address Translation
• Network Address Translation (NAT), on page 149
• NAT Examples and Reference, on page 197 | https://www.cisco.com/c/en/us/td/docs/security/asa/asa96/configuration/firewall/asa-96-firewall-config.pdf |
169 | null | https://www.cisco.com/c/en/us/td/docs/security/asa/asa96/configuration/firewall/asa-96-firewall-config.pdf |
170 | CHAPTER 8
Network Address Translation (NAT)
The following topics explain Network Address Translation (NAT) and how to configure it.
• Why Use NAT?, on page 149
• NAT Basics, on page 150
• Guidelines for NAT, on page 154
• Dynamic NAT, on page 161
• Dynamic PAT, on page 167
• Static NAT, on page 179
• Identity NAT, on p... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa96/configuration/firewall/asa-96-firewall-config.pdf |
171 | • Flexibility—You can change internal IP addressing schemes without affecting the public addresses
available externally; for example, for a server accessible to the Internet, you can maintain a fixed IP
address for Internet use, but internally, you can change the server address.
• Translating between IPv4 and IPv6 (Rou... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa96/configuration/firewall/asa-96-firewall-config.pdf |
172 | • Dynamic NAT—A group of real IP addresses are mapped to a (usually smaller) group of mapped IP
addresses, on a first come, first served basis. Only the real host can initiate traffic. See Dynamic NAT,
on page 161.
• DynamicPort Address Translation (PAT)—A group of real IPaddresses are mapped to a single IPaddress
usin... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa96/configuration/firewall/asa-96-firewall-config.pdf |
173 | For static NAT, the rule is bidirectional, so be aware that “source” and “destination” are used in commands
and descriptions throughout this guide even though a given connection might originate at the “destination”
address.For example, if you configure static NAT with port address translation, and specify the source ad... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa96/configuration/firewall/asa-96-firewall-config.pdf |
174 | a match is found in section 1, sections 2 and 3 are not evaluated. The following table shows the order of rules
within each section.
Table 9: NAT Rule Table
Table Section Rule Type Order of Rules within the Section
Applied on a first match basis, in the order they appear in the
configuration. Because the first match is... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa96/configuration/firewall/asa-96-firewall-config.pdf |
175 | • 192.168.1.0/24 (dynamic)
• 10.1.1.0/24 (static)
• 192.168.1.1/32 (static)
• 172.16.1.0/24 (dynamic) (object def)
• 172.16.1.0/24 (dynamic) (object abc)
The resultant ordering would be:
• 192.168.1.1/32 (static)
• 10.1.1.0/24 (static)
• 192.168.1.0/24 (static)
• 172.16.1.0/24 (dynamic) (object abc)
• 172.16.1.0/24 (dy... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa96/configuration/firewall/asa-96-firewall-config.pdf |
176 | Firewall Mode Guidelines for NAT
NAT is supported in routed and transparent firewall mode.
However, configuring NAT on bridge group member interfaces (interfaces that are part of a Bridge Group
Virtual Interface, or BVI) has the following restrictions:
• When configuring NAT for the members of a bridge group, you speci... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa96/configuration/firewall/asa-96-firewall-config.pdf |
177 | (shown with mixed notation). If the prefix is smaller, such as /64, then the IPv4 address is appended after
the prefix, and a suffix of 0s is appended after the IPv4 address. You can also optionally translate the
addresses net-to-net, where the first IPv4 address mapsto the first IPv6 address, the second to the second,... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa96/configuration/firewall/asa-96-firewall-config.pdf |
178 | • You cannot use an object group with both IPv4 and IPv6 addresses; the object group must include only
one type of address.
• (Twice NAT only.) When using any as the source address in a NAT rule, the definition of “any” traffic
(IPv4 vs. IPv6) depends on the rule. Before the ASA performs NAT on a packet, the packet mus... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa96/configuration/firewall/asa-96-firewall-config.pdf |
179 | option to include the lower range in the flat range. You can avoid this problem by changing the NFS
server configuration to allow all port numbers.
• NAT applies to through traffic only. Traffic generated by the system is not subject to NAT.
• You can improve system performance and reliability by using the transactiona... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa96/configuration/firewall/asa-96-firewall-config.pdf |
180 | • Identity NAT
• Instead of using an object, you can configure an inline address.
• If you use an object, the object must match the real addresses you want to translate.
Twice NAT Guidelines for Real and Mapped Address Objects
For each NAT rule, configure up to four network objects or groups for:
• Source real address
... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa96/configuration/firewall/asa-96-firewall-config.pdf |
181 | • The real and mapped objects must match. You can use the same object for both, or you can create
separate objects that contain the same IP addresses.
• Destination Static NAT or Static NAT with port translation (the destination translation is always static):
• Although the main feature of twice NAT isthe inclusion of ... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa96/configuration/firewall/asa-96-firewall-config.pdf |
182 | object can contain both a source and destination port, but only the destination port is used in this case.
If you specify the source port, it will be ignored.
Dynamic NAT
The following topics explain dynamic NAT and how to configure it.
About Dynamic NAT
Dynamic NAT translates a group of real addresses to a pool of map... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa96/configuration/firewall/asa-96-firewall-config.pdf |
183 | Figure 18: Remote Host Attempts to Initiate a Connection to a Mapped Address
Dynamic NAT Disadvantages and Advantages
Dynamic NAT has these disadvantages:
• If the mapped pool has fewer addresses than the real group, you could run out of addresses if the amount
of traffic is more than expected.
Use PAT or a PAT fall-ba... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa96/configuration/firewall/asa-96-firewall-config.pdf |
184 | Procedure
Step 1 Create a host or range network object (object network command), or a network object group (object-group
network command), for the mapped addresses.
• The object or group cannot contain a subnet; the object must define a range; the group can include hosts
and ranges.
• If a mapped network object contain... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa96/configuration/firewall/asa-96-firewall-config.pdf |
185 | • DNS—(Optional) The dns keyword translates DNS replies. Be sure DNS inspection is enabled (it is
enabled by default). See Rewriting DNS Queries and Responses Using NAT, on page 223 for more
information.
Example:
hostname(config-network-object)# nat (inside,outside) dynamic MAPPED_IPS interface
Examples
The following e... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa96/configuration/firewall/asa-96-firewall-config.pdf |
186 | hostname(config-network-object)# network-object object IPv4_NAT_RANGE
hostname(config-network-object)# network-object object IPv4_PAT
hostname(config-network-object)# object network my_net_obj5
hostname(config-network-object)# subnet 2001:DB8::/96
hostname(config-network-object)# nat (inside,outside) dynamic IPv4_GROUP... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa96/configuration/firewall/asa-96-firewall-config.pdf |
187 | • Section and Line—(Optional.) By default, the NAT rule is added to the end of section 1 of the NAT table
(see NAT Rule Order, on page 152). If you want to add the rule into section 3 instead (after the network
object NAT rules), then use the after-auto keyword. You can insert a rule anywhere in the applicable
section ... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa96/configuration/firewall/asa-96-firewall-config.pdf |
188 | Examples
The following example configures dynamic NAT for inside network 10.1.1.0/24 when accessing
servers on the 209.165.201.1/27 network as well as servers on the 203.0.113.0/24 network:
hostname(config)# object network INSIDE_NW
hostname(config-network-object)# subnet 10.1.1.0 255.255.255.0
hostname(config)# object... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa96/configuration/firewall/asa-96-firewall-config.pdf |
189 | About Dynamic PAT
Dynamic PAT translates multiple real addresses to a single mapped IP address by translating the real address
and source port to the mapped address and a unique port.
Each connection requires a separate translation session because the source port differs for each connection.
For example, 10.1.1.1:1025 ... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa96/configuration/firewall/asa-96-firewall-config.pdf |
190 | For a PAT pool
• If available, the real source port number is used for the mapped port. However, if the real port is not
available, by default the mapped ports are chosen from the same range of ports as the real port number:
0 to 511, 512 to 1023, and 1024 to 65535. Therefore, ports below 1024 have only a small PAT poo... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa96/configuration/firewall/asa-96-firewall-config.pdf |
191 | Procedure
Step 1 (Optional.) Create a host or range network object (object network command), or a network object group
(object-group network command), for the mapped addresses.
• Instead of using an object, you can optionally configure an inline host address or specify the interface
address.
• If you use an object, the... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa96/configuration/firewall/asa-96-firewall-config.pdf |
192 | • interface [ipv6]—The IP address of the mapped interface is used as the mapped address. If you
specify ipv6, then the IPv6 address of the interface is used. For this option, you must configure a
specific interface for the mapped_ifc. (You cannot specify interface when the mapped interface is
a bridge group member.) Yo... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa96/configuration/firewall/asa-96-firewall-config.pdf |
193 | hostname(config)# object network my-inside-net
hostname(config-network-object)# subnet 192.168.2.0 255.255.255.0
hostname(config-network-object)# nat (inside,outside) dynamic 10.2.2.2
The following example configures dynamic PAT that hides the 192.168.2.0 network behind the
outside interface address:
hostname(config)# ... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa96/configuration/firewall/asa-96-firewall-config.pdf |
194 | nat [(real_ifc,mapped_ifc)] [line | after-auto [line]]sourcedynamic {real-obj| any} {mapped_obj [interface
[ipv6]] |pat-pool mapped-obj [round-robin] [extended] [flat [include-reserve]] [block-allocation] [interface
[ipv6]] | interface [ipv6]} [destination static {mapped_obj | interface [ipv6]} real_obj] [service
mappe... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa96/configuration/firewall/asa-96-firewall-config.pdf |
195 | • block-allocation—Enables port block allocation. For carrier-grade or large-scale PAT, you
can allocate a block of ports for each host, rather than have NAT allocate one port translation
at a time. If you allocate a block of ports, subsequent connections from the host use new
randomly-selected ports within the block. ... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa96/configuration/firewall/asa-96-firewall-config.pdf |
196 | hostname(config)# object service TELNET
hostname(config-service-object)# service tcp destination eq 23
hostname(config)# object network SERVERS
hostname(config-network-object)# subnet 203.0.113.0 255.255.255.0
hostname(config)# nat (inside,outside) source dynamic INSIDE_NW interface
destination static TELNET_SVR TELNET... | https://www.cisco.com/c/en/us/td/docs/security/asa/asa96/configuration/firewall/asa-96-firewall-config.pdf |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.