<?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: No syslog blocking in asa. in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/no-syslog-blocking-in-asa/m-p/4194278#M1076471</link>
    <description>&lt;P&gt;&lt;SPAN&gt;If so, is it that syslog is still communicating even if udp blocking policy is put in the state of session being established?&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Mon, 07 Dec 2020 01:37:51 GMT</pubDate>
    <dc:creator>jbseong</dc:creator>
    <dc:date>2020-12-07T01:37:51Z</dc:date>
    <item>
      <title>No syslog blocking in asa.</title>
      <link>https://community.cisco.com/t5/network-security/no-syslog-blocking-in-asa/m-p/4194271#M1076469</link>
      <description>&lt;PRE&gt;&lt;SPAN&gt;We have 1 asa product and fwsm product.

fwsm-asa
      ㅣ          
  syslog server

It has this configuration.

While sending syslog from fwsm to syslog server, asa set the policy to block fwsm syslog.

But still fwsm is sending logs to syslog server and hit count doesn't go up in asa.

But from the moment fwsm reboots, it is blocked in asa.

What the hell is this happening for?

Can't asa block blocking while in session?&lt;/SPAN&gt;&lt;/PRE&gt;</description>
      <pubDate>Mon, 07 Dec 2020 01:01:49 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/no-syslog-blocking-in-asa/m-p/4194271#M1076469</guid>
      <dc:creator>jbseong</dc:creator>
      <dc:date>2020-12-07T01:01:49Z</dc:date>
    </item>
    <item>
      <title>Re: No syslog blocking in asa.</title>
      <link>https://community.cisco.com/t5/network-security/no-syslog-blocking-in-asa/m-p/4194272#M1076470</link>
      <description>&lt;P&gt;syslog is UDP and have entry in conn,&lt;/P&gt;&lt;P&gt;you config policy after the conn have entry&amp;nbsp;&lt;BR /&gt;so it will bypass policy&amp;nbsp;&lt;BR /&gt;the only chance it will go through policy is delete from conn and this happened if you delete manually or as you mention reboot device initiate the syslog so that the entry is timeout and delete from conn table.&lt;/P&gt;</description>
      <pubDate>Mon, 07 Dec 2020 01:07:57 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/no-syslog-blocking-in-asa/m-p/4194272#M1076470</guid>
      <dc:creator>MHM Cisco World</dc:creator>
      <dc:date>2020-12-07T01:07:57Z</dc:date>
    </item>
    <item>
      <title>Re: No syslog blocking in asa.</title>
      <link>https://community.cisco.com/t5/network-security/no-syslog-blocking-in-asa/m-p/4194278#M1076471</link>
      <description>&lt;P&gt;&lt;SPAN&gt;If so, is it that syslog is still communicating even if udp blocking policy is put in the state of session being established?&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 07 Dec 2020 01:37:51 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/no-syslog-blocking-in-asa/m-p/4194278#M1076471</guid>
      <dc:creator>jbseong</dc:creator>
      <dc:date>2020-12-07T01:37:51Z</dc:date>
    </item>
    <item>
      <title>Re: No syslog blocking in asa.</title>
      <link>https://community.cisco.com/t5/network-security/no-syslog-blocking-in-asa/m-p/4194279#M1076472</link>
      <description>&lt;P&gt;Yes if you config &amp;nbsp;policy after session established then ASA will bypass policy and the only way is clear conn entry manually in ASA&lt;/P&gt;</description>
      <pubDate>Mon, 07 Dec 2020 01:51:50 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/no-syslog-blocking-in-asa/m-p/4194279#M1076472</guid>
      <dc:creator>MHM Cisco World</dc:creator>
      <dc:date>2020-12-07T01:51:50Z</dc:date>
    </item>
  </channel>
</rss>

