Configure system logging on your Cisco ASA device
Configure your Cisco ASA devices to capture event fields and send security-related log information over TCP or UDP to a server running a syslog.
Prerequisites
- Determine which syslog messages to log. Use the Cisco ASA Series General Operations CLI Configuration Guide to filter generated syslog messages so that only certain syslog messages are sent to a particular output destination.
- Use the Cisco ASA Series General Operations CLI Configuration Guide to specify syslog message severity levels.
- Configure the ASA and Adaptive Service Appliance Service Modules (ASASM) so that syslog messages are directed to an output destination according to the following criteria:
- Syslog message ID number
- Syslog message severity level
- Syslog message class (equivalent to a functional area of the ASA and ASASM)
Customize these criteria by creating a message list that you can specify when you set the output destination. Alternatively, you can configure the ASA or ASASM to send a particular message class to each type of output destination independent of the message list.
Configure your Cisco ASA devices to send log information to the Splunk Enterprise platform over TCP or UDP
To configure the ASA and to send system log messages to a syslog server, execute the following command:
hostname(config)# logging host interface_name ip_address [tcp[/port] | udp[/port]] [format emblem]
For more information about syslog configuration, see the Cisco ASA Series General Operations CLI Configuration Guide.
Configure the Splunk Add-on for Cisco ASA on your Splunk platform deployment | Verify your data |
This documentation applies to the following versions of Splunk® Enterprise: 7.2.0, 7.2.1, 7.2.2, 7.2.3, 7.2.4, 7.2.5, 7.2.6, 7.2.7, 7.2.8, 7.2.9, 7.2.10, 7.3.0, 7.3.1, 7.3.2, 7.3.3, 7.3.4, 7.3.5, 7.3.6, 7.3.7, 7.3.8, 7.3.9, 8.0.0, 8.0.1, 8.0.2, 8.0.3, 8.0.4, 8.0.5, 8.0.6, 8.0.7, 8.0.8, 8.0.9, 8.0.10
Feedback submitted, thanks!