<?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 firepower -  SSL Block Reason in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/cisco-asa-firepower-ssl-block-reason/m-p/3676411#M1005480</link>
    <description>&lt;P&gt;Misread that initially. Can you show the blocking event it is matching?&lt;/P&gt;</description>
    <pubDate>Fri, 27 Jul 2018 17:31:16 GMT</pubDate>
    <dc:creator>rcmcdermott11</dc:creator>
    <dc:date>2018-07-27T17:31:16Z</dc:date>
    <item>
      <title>cisco asa firepower -  SSL Block Reason</title>
      <link>https://community.cisco.com/t5/network-security/cisco-asa-firepower-ssl-block-reason/m-p/3676233#M1005479</link>
      <description>&lt;P&gt;Hi All&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Our office deployment of Cisco ASA w/ Firepower blocking some whatsapp&amp;nbsp; application feature (send receive image/video/file, call and video call), only text are working&lt;/P&gt;
&lt;P&gt;Connection event log show block reason are SSL Block from internal source to some whatsapp URL/Domain port&amp;nbsp; https and with Do Not decrypt SSL Status.&lt;/P&gt;
&lt;P&gt;Our SSL Policy for this traffic are fall&amp;nbsp; into default action which is Do Not Decrypt and our network access policy allow any any from inside to outside.&lt;/P&gt;
&lt;P&gt;How to un-block/bypass this traffic ?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;thanks before&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Reza&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2019 13:51:16 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/cisco-asa-firepower-ssl-block-reason/m-p/3676233#M1005479</guid>
      <dc:creator>muhammadreza</dc:creator>
      <dc:date>2019-03-12T13:51:16Z</dc:date>
    </item>
    <item>
      <title>Re: cisco asa firepower -  SSL Block Reason</title>
      <link>https://community.cisco.com/t5/network-security/cisco-asa-firepower-ssl-block-reason/m-p/3676411#M1005480</link>
      <description>&lt;P&gt;Misread that initially. Can you show the blocking event it is matching?&lt;/P&gt;</description>
      <pubDate>Fri, 27 Jul 2018 17:31:16 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/cisco-asa-firepower-ssl-block-reason/m-p/3676411#M1005480</guid>
      <dc:creator>rcmcdermott11</dc:creator>
      <dc:date>2018-07-27T17:31:16Z</dc:date>
    </item>
    <item>
      <title>Re: cisco asa firepower -  SSL Block Reason</title>
      <link>https://community.cisco.com/t5/network-security/cisco-asa-firepower-ssl-block-reason/m-p/3677091#M1005481</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;One of the easy way to determine what within the SSL is causing the traffic to be blocked is to navigate to the connection events, click on table view of the events.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;By default, there are certain fields shown up, since we want to know what is causing SSL to determine the block, click on one of the fields at the "X" field to disable the field. You will see a drop down of all the fields available. Select all the SSL related fields and save it.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Upon refresh, it would provide details on what within SSL is marking it as to be blocked.&lt;/P&gt;</description>
      <pubDate>Mon, 30 Jul 2018 03:39:25 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/cisco-asa-firepower-ssl-block-reason/m-p/3677091#M1005481</guid>
      <dc:creator>Raghunath Kulkarni</dc:creator>
      <dc:date>2018-07-30T03:39:25Z</dc:date>
    </item>
  </channel>
</rss>

