Cisco ASA

Cisco ASA is one of the few event sources that can handle multiple types of logs on a single port because it hosts Firewall and VPN logs.

For the InsightIDR parser to work, make sure that your Cisco ASA appliance has "logging timestamp" turned on and the "logging host" has been configured for the InsightIDR collector.

For the complete use of detection capabilities in InsightIDR, set the logging level on the device to Severity 6 (Informational Messages). Read the Cisco ASA Configuration Guide for more information:

Learn how Cisco logging is configured:

To forward logs from Cisco's Adaptive Security Device Manager:

  1. In the ADSM, select Configuration.
  2. Select Device Management, and choose Logging from the dropdown menu.
  3. Select Syslog servers.
  4. Click Add and then in "Syslog Servers," enter the information for your InsightIDR collector.
  5. Ensure the Collector is reachable from Cisco ASA.

For more details instructions on syslog configuration, read this information:

Configure InsightIDR to collect data from the event source

After you complete the prerequisite steps and configure the event source to send data, you must add the event source in InsightIDR.

To configure the new event source in InsightIDR:

  1. From the left menu, go to Data Collection and click Setup Event Source > Add Event Source.
  2. Do one of the following:
    • Search for Cisco ASA Firewall VPN in the event sources search bar.
    • In the Product Type filter, select Firewall.
  3. Select the Cisco ASA Firewall VPN event source tile.
  4. Choose your collector.
  5. In the Select Event Source Type field, choose the option that corresponds to your Cisco Security Solution as outlined in the following table:
Cisco Security SolutionInsightIDR Event Source Type
ASACisco ASA event-source
NGIPSCisco ASA event-source
NGFWCisco ASA event-source
Any other firepower serviceCisco ASA event-source
Cisco ASA with FirePower servicesCisco ASA event-source
Cisco FirePower Threat Defense (FTD)Cisco FTD event-source
Sourcefire 3DCisco FirePower (Sourcefire 3D) event-source
  1. Choose the timezone that matches the location of your event source logs.
  2. Optionally choose to send unparsed logs.
  3. Select an attribution source.
  4. Configure your default domain and any Advanced Event Source Settings.
  5. Select a collection method and specify a port and a protocol.
  • Optionally choose to Encrypt the event source if choosing TCP by downloading the Rapid7 Certificate.
  1. Click Save.

Verify the Configuration

To see Cisco ASA logs in InsightIDR: From the left menu, click Log Search to view your logs to ensure events are being forwarded to the Collector. Select the applicable Log Sets and the Log Names within them. The Log Name will be the event source name or “Cisco ASA” if you did not name the event source. Cisco ASA logs flow into these Log Sets:

  • Unified Asset Authentication
  • Ingress Authentication
  • Firewall
  • VPN Session
  • Web Proxy
  • Intrusion Detection System (IDS)

Please note that logs take at least 7 minutes to appear in Log Search after you set up the event source.

Example Input Logs

The following table contains the events from Cisco ASA that are parsed by InsightIDR. You may also select to send unfiltered logs to InsightIDR to collect and store additional events.

To learn about what these codes mean, see the Cisco documentation here:

For additional examples of syslog, see this documentation:

Event ID


Log Example


Deny firewall connection

<13>Feb 26 11:59:40 Feb 26 11:59:40 usiadasa101 %ASA-4-106023: Deny udp src LSI-TEST-TRANSIT: dst DC-TRANSIT: by access-group \"LSI-TEST-TRANSIT_ACCESS_IN\" [0x257f55e5, 0xe5b85413]


Allow Firewall connection

<189>Feb 27 14:11:58 %ASA-5-106100: access-list inside_access_in permitted tcp inside/ -> outside/ hit-cnt 1 first hit [0x4e0b70da, 0x386bad81]


VPN Authentication failed with bad password

<166>Aug 07 2014 10:00:03 FW2-COMPANY : %ASA-6-113005: AAA user authentication Rejected : reason = Invalid password : server = : user = foobar : user IP =


TCP connection created

<189>Mar 25 19:00:02 %ASA-4-302013: Built outbound TCP connection 139684278 for ( to (


TCP connection completed

<166>Sep 23 2015 16:12:37 : %ASA-6-302014: Teardown TCP connection 115466298 for to duration 0:00:02 bytes 8040 TCP FINs


UDP connection created

<166>Mar 25 19:00:02 %ASA-6-302015: Built outbound UDP connection 145221138078637354 for ( to (


UDP connection completed

<166>Dec 14 2013 16:59:36 : %ASA-6-302016: Teardown UDP connection 823803842 for to duration 0:00:00 bytes 121 (reyga)


URL accessed

<13>Mar 5 14:23:11 %ASA-5-304001: Accessed URL


URL access denied

<189>Feb 27 14:42:23 %ASA-5-304002: Access denied URL SRC DEST xx.xx.xx.xx on interface inside


VPN Access denied

<187>Jul 21 2014 07:21:22: %ASA-3-713167: Group = AGROUP, Username = jsmith, IP =, Remote peer has failed user authentication - check configured username and password


VPN Assigned IP

<134>Aug 19 2013 13:09:20: %ASA-6-713228: Group = vpnusers, Username = jsmith, IP =, Assigned private IP address to remote user


WebVPN Authentication failed

<166>Aug 07 2014 10:00:03 FW2-COMPANY : %ASA-6-716039: Group <DfltGrpPolicy> User <foobar> IP <> Authentication: rejected, Session Type: WebVPN.


VPN Session Termination

<164>Feb 11 2013 06:00:52 : %ASA-7-722029: Group <Operations> User <jsmith> IP <xxx.xx.x.xx> SVC Session Termination: Conns: 1, DPD Conns: 0, Comp resets: 0, Dcmp resets: 0.


VPN Assign IP

<164>Jan 13 2014 08:47:27: %ASA-4-722051: Group <SGC-VPN> User <aguerlain> IP <> IPv4 Address <> IPv6 address <::> assigned to session


Displays the assigned IP address information for the AnyConnect IKEv2 connection of the specified user

<167>Apr 30 2019 01:20:21: %ASA-7-751025: Local: Remote: Username:r7user IKEv2 Group:GroupPolicy_SAMB IPv4 Address= IPv6 address=invalid-addr-2- assigned to session

Cisco ASA logs can also produce logs in the same format as some Sourcefire 3D log entries. These log entries do not contain the ASA Event ID. Here is an example of these logs:

<113>Mar 18 11:38:39 Sourcefire3D sfdc1500avc: [Primary Detection Engine (11727814-7b90-11e2-b768-a8d573eb9cc3)][MHPSA] Connection Type: Start, User: Unknown, Client: SSL client, Application Protocol: HTTPS, Web App: Unknown, Access Control Rule Name: CatchAll-Scan_for_Malware, Access Control Rule Action: Allow, Access Control Rule Reasons: Unknown, URL Category: Parked Domains, URL Reputation: Well known, URL:, Interface Ingress: s1p1, Interface Egress: s1p2, Security Zone Ingress: Internal, Security Zone Egress: External, Security Intelligence Matching IP: None, Security Intelligence Category: None, Client Version: (null), Number of File Events: 0, Number of IPS Events: 0, TCP Flags: 0x0, NetBIOS Domain: (null), Initiator Packets: 4, Responder Packets: 4, Initiator Bytes: 608, Responder Bytes: 4368, Context: Unknown, SSL Rule Name: N/A, SSL Flow Status: N/A, SSL Cipher Suite: N/A, SSL Certificate: 0000000000000000000000000000000000000000, SSL Subject CN: N/A, SSL Subject Country: N/A, SSL Subject OU: N/A, SSL Subject Org: N/A, SSL Issuer CN: N/A, SSL Issuer Country: N/A, SSL Issuer OU: N/A, SSL Issuer Org: N/A, SSL Valid Start Date: N/A, SSL Valid End Date: N/A, SSL Version: N/A, SSL Server Certificate Status: N/A, SSL Actual Action: N/A, SSL Expected Action: N/A, SSL Server Name: (null), SSL URL Category: N/A, SSL Session ID: 0000000000000000000000000000000000000000000000000000000000000000, SSL Ticket Id: 0000000000000000000000000000000000000000, {TCP} ->


If you are experiencing issues with Cisco ASA, the problem may be with parsing or with Log Configuration.

Problems Parsing

Ensure timestamps are turned on, otherwise the Rapid7 parser will not work.

Problem with Log Configuration

Ensure the following:

  • The 'logging timestamp' is turned on
  • The 'logging host' has been configured for the InsightIDR collector.

Make sure to set the logging level on the device to Severity 6 (Informational Messages). Use this guide for instructions:

Cisco devices running versions < 9.2.1 have a bug (CSCui82751) where ASA-6-113005 events are not logged with the source IP address, preventing them from being used for detection within InsightIDR.