<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Cisco ASA - Logging from Access-Control Entries. in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Cisco-ASA-Logging-from-Access-Control-Entries/m-p/22817#M3558</link>
    <description>&lt;P&gt;I've solved this in a new and packaged app that is available on Splunkbase as "Splunk for Cisco ASA". &lt;/P&gt;</description>
    <pubDate>Mon, 09 Jul 2012 22:56:33 GMT</pubDate>
    <dc:creator>kenth</dc:creator>
    <dc:date>2012-07-09T22:56:33Z</dc:date>
    <item>
      <title>Cisco ASA - Logging from Access-Control Entries.</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Cisco-ASA-Logging-from-Access-Control-Entries/m-p/22814#M3555</link>
      <description>&lt;P&gt;Hi, &lt;/P&gt;

&lt;P&gt;I am logging directly to Splunk from several Cisco ASA's. I have set my ASA to log ACE entries on the notifications level and I send this level to syslog (Splunk). This should send all permitted and dropped logs to the Splunk. It seems like Splunk only recognizes the syslogs with dropped packets. How come? I have checked with normal syslog and I get both log entries. &lt;/P&gt;

&lt;P&gt;For workaround I have to send syslog level information to splunk to be able to see permitted packets. This is not what I want because information sends the build and teardown of connections and it seems like thats how Splunk considers it's a "permitted" flow. &lt;/P&gt;

&lt;P&gt;I am using the Splunk for Cisco Security. Anyone done this? &lt;/P&gt;</description>
      <pubDate>Fri, 30 Jul 2010 13:54:08 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Cisco-ASA-Logging-from-Access-Control-Entries/m-p/22814#M3555</guid>
      <dc:creator>kenth</dc:creator>
      <dc:date>2010-07-30T13:54:08Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco ASA - Logging from Access-Control Entries.</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Cisco-ASA-Logging-from-Access-Control-Entries/m-p/22815#M3556</link>
      <description>&lt;P&gt;Kenth,&lt;/P&gt;

&lt;P&gt;This is an old post, but I am new to this add on.   I'm having the same issue, and here's what I've discovered.  The field extraction for the "firewall-accept" is keyed upon the words "Built", and "connection".  This phrase is only available when 'logging informational' is on.  This is an obscene amount of logging.&lt;/P&gt;

&lt;P&gt;What would be ideal is if the field extraction used the words "access-list", and "permitted".
Then logging level can be lower, and you can set up the ACL to include logging for those hits to the level you want.&lt;/P&gt;

&lt;P&gt;I did this and it worked, but not all the way.  The access-list log line is different than the built connection log line, and the rest of the fields are not extracted correctly.&lt;/P&gt;

&lt;P&gt;I've been poking around and I cannot determine how to change this area.  I could use some help on that.  If anyone knows, that would be fantastic.&lt;/P&gt;</description>
      <pubDate>Sat, 12 Mar 2011 21:47:25 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Cisco-ASA-Logging-from-Access-Control-Entries/m-p/22815#M3556</guid>
      <dc:creator>jgauthier</dc:creator>
      <dc:date>2011-03-12T21:47:25Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco ASA - Logging from Access-Control Entries.</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Cisco-ASA-Logging-from-Access-Control-Entries/m-p/22816#M3557</link>
      <description>&lt;P&gt;Again,&lt;/P&gt;

&lt;P&gt;This is an old post.  But I have solved it and am happy.&lt;/P&gt;

&lt;P&gt;Filter out the data from the host to only put in the data that the add on needs to process it's reports.&lt;/P&gt;

&lt;P&gt;So, build a regex that captures the build lines, and the deny lines.
Toss the rest!  &lt;/P&gt;</description>
      <pubDate>Sat, 26 Mar 2011 02:07:00 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Cisco-ASA-Logging-from-Access-Control-Entries/m-p/22816#M3557</guid>
      <dc:creator>jgauthier</dc:creator>
      <dc:date>2011-03-26T02:07:00Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco ASA - Logging from Access-Control Entries.</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Cisco-ASA-Logging-from-Access-Control-Entries/m-p/22817#M3558</link>
      <description>&lt;P&gt;I've solved this in a new and packaged app that is available on Splunkbase as "Splunk for Cisco ASA". &lt;/P&gt;</description>
      <pubDate>Mon, 09 Jul 2012 22:56:33 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Cisco-ASA-Logging-from-Access-Control-Entries/m-p/22817#M3558</guid>
      <dc:creator>kenth</dc:creator>
      <dc:date>2012-07-09T22:56:33Z</dc:date>
    </item>
  </channel>
</rss>

