<?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 ASA: Threat-detection scanning-threat SHUN blocking our scan tools in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/asa-threat-detection-scanning-threat-shun-blocking-our-scan/m-p/4585380#M1088922</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I'm trying to assist a neighboring company.&lt;/P&gt;&lt;P&gt;They have Threat-detection scanning-threat SHUN enabled on their ASA devices.&lt;/P&gt;&lt;P&gt;With this enabled they are no longer able to use scanning tools like ACAS to check outside devices they monitor.&lt;/P&gt;&lt;P&gt;Currently I only have "Threat-detection scanning-threat" enabled on our ASA's so i cannot comment on the effects I am seeing.&lt;/P&gt;&lt;P&gt;This is a STIG requirement so I will have to implement it.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Does anyone know a way to get around this command blocking scanning tools?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you&lt;/P&gt;</description>
    <pubDate>Mon, 04 Apr 2022 15:44:37 GMT</pubDate>
    <dc:creator>KGrev</dc:creator>
    <dc:date>2022-04-04T15:44:37Z</dc:date>
    <item>
      <title>ASA: Threat-detection scanning-threat SHUN blocking our scan tools</title>
      <link>https://community.cisco.com/t5/network-security/asa-threat-detection-scanning-threat-shun-blocking-our-scan/m-p/4585380#M1088922</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I'm trying to assist a neighboring company.&lt;/P&gt;&lt;P&gt;They have Threat-detection scanning-threat SHUN enabled on their ASA devices.&lt;/P&gt;&lt;P&gt;With this enabled they are no longer able to use scanning tools like ACAS to check outside devices they monitor.&lt;/P&gt;&lt;P&gt;Currently I only have "Threat-detection scanning-threat" enabled on our ASA's so i cannot comment on the effects I am seeing.&lt;/P&gt;&lt;P&gt;This is a STIG requirement so I will have to implement it.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Does anyone know a way to get around this command blocking scanning tools?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you&lt;/P&gt;</description>
      <pubDate>Mon, 04 Apr 2022 15:44:37 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-threat-detection-scanning-threat-shun-blocking-our-scan/m-p/4585380#M1088922</guid>
      <dc:creator>KGrev</dc:creator>
      <dc:date>2022-04-04T15:44:37Z</dc:date>
    </item>
    <item>
      <title>Re: ASA: Threat-detection scanning-threat SHUN blocking our scan tools</title>
      <link>https://community.cisco.com/t5/network-security/asa-threat-detection-scanning-threat-shun-blocking-our-scan/m-p/4585528#M1088935</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Found the answer to my question.&lt;/P&gt;&lt;P&gt;For anyone who is curious, cisco provides this in their setup guide:&lt;/P&gt;&lt;P&gt;"&lt;/P&gt;&lt;P&gt;In some cases, you may still want to prevent the ASA from shunning certain IPs. In order to do this, create an exception with the &lt;STRONG&gt;threat-detection scanning-threat shun except&lt;/STRONG&gt; command.&lt;/P&gt;&lt;PRE&gt;ciscoasa(config)# &lt;STRONG&gt;threat-detection scanning-threat shun except ip-address 10.1.1.1 255.255.255.255&lt;/STRONG&gt;&lt;BR /&gt;ciscoasa(config)# &lt;STRONG&gt;threat-detection scanning-threat shun except object-group no-shun&lt;/STRONG&gt;&lt;/PRE&gt;</description>
      <pubDate>Mon, 04 Apr 2022 19:20:31 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-threat-detection-scanning-threat-shun-blocking-our-scan/m-p/4585528#M1088935</guid>
      <dc:creator>KGrev</dc:creator>
      <dc:date>2022-04-04T19:20:31Z</dc:date>
    </item>
  </channel>
</rss>

