<?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: Forwarding IPS events via Syslog in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/forwarding-ips-events-via-syslog/m-p/3729823#M1013567</link>
    <description>&lt;P&gt;Not as far as I know.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Cisco encourages customers to press their SIEM vendor to support eStreamer as it is considered architecturally capable to handle to potential volume of event coming from an FMC in a reliable and secure manner&lt;/P&gt;</description>
    <pubDate>Mon, 22 Oct 2018 13:55:02 GMT</pubDate>
    <dc:creator>Marvin Rhoads</dc:creator>
    <dc:date>2018-10-22T13:55:02Z</dc:date>
    <item>
      <title>Forwarding IPS events via Syslog</title>
      <link>https://community.cisco.com/t5/network-security/forwarding-ips-events-via-syslog/m-p/3729688#M1013564</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;We are using the IPS module on the Cisco ASA 5525-X Firewalls and we’re running version 6.2.0.6.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;We would like to forward detailed logs to a Syslog server.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;We followed&amp;nbsp;these&amp;nbsp;procedures:&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;&lt;A href="https://www.cisco.com/c/en/us/support/docs/security/firesight-management-center/118464-configure-firesight-00.html" target="_blank"&gt;https://www.cisco.com/c/en/us/support/docs/security/firesight-management-center/118464-configure-firesight-00.html&lt;/A&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;&lt;A href="https://www.cisco.com/c/en/us/support/docs/security/asa-firepower-services/200328-Configure-Logging-in-Firepower-Module-fo.html" target="_blank"&gt;https://www.cisco.com/c/en/us/support/docs/security/asa-firepower-services/200328-Configure-Logging-in-Firepower-Module-fo.html&lt;/A&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;We are indeed receiving logs in our Syslog server. However, we are only receiving&amp;nbsp;Block and Allow events. We are not receiving&amp;nbsp;the detailed IPS events (i.e the reason behind a block). Here is an example:&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Oct 21 13:00:00 somename SFIMS: Protocol: TCP, SrcIP: x.x.x.x, OriginalClientIP: ::, DstIP: y.y.y.y, SrcPort: 28971,&lt;BR /&gt;DstPort: 443, TCPFlags: 0x0, IngressInterface: internet, EgressInterface: dmz, DE: Primary Detection Engine&lt;BR /&gt;(9c902a8c), Policy: YY-Firewalls, ConnectType: End, AccessControlRuleName: XX-rule,&lt;BR /&gt;AccessControlRuleAction: Block, &lt;STRONG&gt;AccessControlRuleReason: Intrusion Block&lt;/STRONG&gt;, Prefilter Policy: Unknown, UserName: No Authentication Required,&lt;BR /&gt;Client: SSL client, ApplicationProtocol: HTTPS, IPSCount: 1, InitiatorPackets: 6, ResponderPackets: 5, InitiatorBytes: 661, ResponderBytes:&lt;BR /&gt;5511, NAPPolicy: Balanced Security and Connectivity, DNSResponseType: No Error, Sinkhole: Unknown, URLCategory: Unknown, URLReputation: Risk&lt;BR /&gt;unknown&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;As you can see, the log line indicates a block but we don't see the reason.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;In the FireSight Management&amp;nbsp;console, we can see the reason behind a block, but we would like to see it in our Syslog server.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;1- Can the FirePower module forward IPS events to a Syslog server? or only Connection Events?&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;2- If yes, what else should we do?&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Thank you.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2019 14:02:50 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/forwarding-ips-events-via-syslog/m-p/3729688#M1013564</guid>
      <dc:creator>Nethariel</dc:creator>
      <dc:date>2019-03-12T14:02:50Z</dc:date>
    </item>
    <item>
      <title>Re: Forwarding IPS events via Syslog</title>
      <link>https://community.cisco.com/t5/network-security/forwarding-ips-events-via-syslog/m-p/3729737#M1013565</link>
      <description>&lt;P&gt;As you observed, IPS events via syslog only show a subset of the entire data set.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;To get all the metadata you need to use an application like Splunk that connects as an eStreamer client to feed the event data.&lt;/P&gt;</description>
      <pubDate>Mon, 22 Oct 2018 12:11:18 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/forwarding-ips-events-via-syslog/m-p/3729737#M1013565</guid>
      <dc:creator>Marvin Rhoads</dc:creator>
      <dc:date>2018-10-22T12:11:18Z</dc:date>
    </item>
    <item>
      <title>Re: Forwarding IPS events via Syslog</title>
      <link>https://community.cisco.com/t5/network-security/forwarding-ips-events-via-syslog/m-p/3729778#M1013566</link>
      <description>&lt;P&gt;Thank you for your quick reply Marvin.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The thing that confuses me is that AlienVault has a plugin to parse all kind of FirePower events. So you would expect that there should be a way to get these events to AlienVault.&lt;/P&gt;
&lt;P&gt;Do you know if it is possible to do that without using additional applications?&lt;/P&gt;</description>
      <pubDate>Mon, 22 Oct 2018 12:55:15 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/forwarding-ips-events-via-syslog/m-p/3729778#M1013566</guid>
      <dc:creator>Nethariel</dc:creator>
      <dc:date>2018-10-22T12:55:15Z</dc:date>
    </item>
    <item>
      <title>Re: Forwarding IPS events via Syslog</title>
      <link>https://community.cisco.com/t5/network-security/forwarding-ips-events-via-syslog/m-p/3729823#M1013567</link>
      <description>&lt;P&gt;Not as far as I know.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Cisco encourages customers to press their SIEM vendor to support eStreamer as it is considered architecturally capable to handle to potential volume of event coming from an FMC in a reliable and secure manner&lt;/P&gt;</description>
      <pubDate>Mon, 22 Oct 2018 13:55:02 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/forwarding-ips-events-via-syslog/m-p/3729823#M1013567</guid>
      <dc:creator>Marvin Rhoads</dc:creator>
      <dc:date>2018-10-22T13:55:02Z</dc:date>
    </item>
    <item>
      <title>Re: Forwarding IPS events via Syslog</title>
      <link>https://community.cisco.com/t5/network-security/forwarding-ips-events-via-syslog/m-p/3731378#M1013568</link>
      <description>&lt;P&gt;Thanks again for your reply.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Do you know if using SNMP could work?&lt;/P&gt;
&lt;P&gt;In this image, taken from the official guide, it says that Syslog sends Connection Events only, while SNMP doesn't say that. Could that be the reason/solution?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;IMG src="https://www.cisco.com/c/dam/en/us/support/docs/security/asa-firepower-services/200328-Configure-Logging-in-Firepower-Module-fo-02.png" border="0" /&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 24 Oct 2018 07:58:47 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/forwarding-ips-events-via-syslog/m-p/3731378#M1013568</guid>
      <dc:creator>Nethariel</dc:creator>
      <dc:date>2018-10-24T07:58:47Z</dc:date>
    </item>
  </channel>
</rss>

