If 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.
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.
soon as Cortex XDR starts to receive logs, the app can begin analyzing
and raising Analytics alerts. Cortex XDR stores Analytics alerts
according to your Cortex Data Lake storage retention policy but
does not store the Cisco ASA firewall logs. As a result, you cannot
query or apply IOC and BIOC rule matching to Cisco ASA firewall
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.
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.