Extend Cortex XDR visibility into logs from Cisco ASA
logs and data requires a Cortex XDR Pro per TB license.
you use Cisco ASA firewalls, you can still take advantage of Cortex
XDR investigation and detection capabilities by forwarding your
firewall logs to Cortex XDR. This enables Cortex XDR to examine
your network traffic to detect anomalous behavior. Cortex XDR can
use Cisco ASA firewall logs as the sole data source, but can also
use Cisco ASA firewall logs in conjunction with Palo Alto Networks firewall
logs. For additional endpoint context, you can also use Cortex XDR
to collect and alert on endpoint data.
As soon as Cortex
XDR starts to receive logs, the app can begin stitching network
connection logs with other logs to form network stories. Cortex
XDR can also analyze your logs to raise Analytics alerts and can
apply IOC and BIOC rule matching. You can also use queries to search
your network connection logs.
To integrate your logs, you
first need to set up an applet in a broker VM within your network
to act as a Syslog Collector. You then configure forwarding on your
log devices to send logs to the Syslog Collector.
Verify that your Cisco ASA firewall meets the
Syslog in Cisco-ASA format
Only supports messages: 302013, 302014, 302015, 302016
As an estimate for initial sizing, note that the average
Cisco ASA log size is roughly 180 bytes. For proper sizing calculations, test
the log sizes and log rates produced by your Cisco ASA firewalls.
For more information, see Allocate Log Storage for Cortex XDR.
Configure the Cisco ASA firewall or the log device forwarding
logs from it to log to the Syslog Collector.
Configure your firewall policy to log all traffic and forward
the traffic logs to the Syslog Collector. By logging all traffic,
you enable Cortex XDR to detect anomalous behavior from Cisco ASA
firewall logs. For more information on setting up Log Forwarding
on Cisco ASA firewalls, see the Cisco ASA Series documentation.