26-7
Cisco ASA Series Firewall ASDM Configuration Guide
Chapter26 Configuring the Botnet Traffic Filter
Configuring the Botnet Traffic Filter
Configuring the Botnet Traffic Filter
This section includes the following topics:
•Task Flow for Configuring the Botnet Traffic Filter, page26-7
•Configuring the Dynamic Database, page26-8
•Enabling DNS Snooping, page26-9
•Adding Entries to the Static Database, page26-9
•Enabling Traffic Classification and Actions for the Botnet Traffic Filter, page26-10
•Blocking Botnet Traffic Manually, page26-12
•Searching the Dynamic Database, page26-13

Task Flow for Configuring the Botnet Traffic Filter

To configure the Botnet Traffic Filter, perform the following steps:
Step1 Enable use of the dynamic database. See the “Configuring the Dynamic Database” section on page26-8.
This procedure enables database updates from the Cisco update server, and also enables use of the
downloaded dynamic database by the ASA. Disallowing use of the downloaded database is useful in
multiple context mode so you can configure use of the database on a per-context basis.
Step2 (Optional) Add static entries to the database. See the “Adding Entries to the Static Database” section on
page 26-9.
This procedure lets you augment the dynamic database with domain names or IP addresses that you want
to blacklist or whitelist. You might want to use the static database instead of the dynamic database if you
do not want to download the dynamic database over the Internet.
Step3 Enable DNS snooping. See the “Enabling DNS Snooping” section on page26-9.
This procedure enables inspection of DNS packets, compares the domain name with those in the
dynamic database or the static database (when a DNS server for the ASA is unavailable), and adds the
name and IP address to the DNS reverse lookup cache. This cache is then used by the Botnet Traffic
Filter when connections are made to the suspicious address.
Step4 Enable traffic classification and actions for the Botnet Traffic Filter. See the “Enabling Traffic
Classification and Actions for the Botnet Traffic Filter” section on page26-10.
This procedure enables the Botnet Traffic Filter, which compares the source and destination IP address
in each initial connection packet to the IP addresses in the dynamic database, static database, DNS
reverse lookup cache, and DNS host cache, and sends a syslog message or drops any matching traffic.
Step5 (Optional) Block traffic manually based on syslog message information. See the “Blocking Botnet
Traffic Manually” section on page26-12.
If you choose not to block malware traffic automatically, you can block traffic manually by configuring
an access rule to deny traffic, or by using the shun command in the Command Line Interface tool to
block all traffic to and from a host.