<?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 So guys, in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/ssl-decryption-with-firepower-physical-sensors/m-p/2860102#M1030600</link>
    <description>&lt;P&gt;So guys,&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;I opened case in TAC and got my answer. Traffic flow as follows:&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;The client hello passes through to the end server. The end server sends&lt;/P&gt;
&lt;P&gt;back the server hello with the chosen cipher suite. Then when the&lt;/P&gt;
&lt;P&gt;client sends the premaster secret we intercept that and send the client&lt;/P&gt;
&lt;P&gt;our master secret and the server our premaster secret. This is how we&lt;/P&gt;
&lt;P&gt;own the key and can decrypt resign the traffic.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;That means you can't control negotiated cipher suite. If firepower doesn't support negotiated cipher you can't decrypt it... All you can do - do not decrypt and left users unprotected because large number of sites using cipher suites currently not supported by firepower.&lt;/P&gt;</description>
    <pubDate>Tue, 14 Jun 2016 14:12:19 GMT</pubDate>
    <dc:creator>Valery Denisov</dc:creator>
    <dc:date>2016-06-14T14:12:19Z</dc:date>
    <item>
      <title>SSL decryption with Firepower Physical sensors</title>
      <link>https://community.cisco.com/t5/network-security/ssl-decryption-with-firepower-physical-sensors/m-p/2860097#M1030595</link>
      <description>&lt;P&gt;Hello&amp;nbsp;!&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;We have physical sensors&amp;nbsp;and want to use ssl inspection for users traffic.&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;When we deploy this function we have (almost on any site) - unknown cipher error.&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;From SSL workflow we know that cipher suite selected by SERVER HELLO which in our case must be Firepower.&lt;/P&gt;
&lt;P&gt;So how can we strictly set which cipher to use on Firepower to negotiate SSL connection and remove this error ?&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Thank you!&lt;/P&gt;</description>
      <pubDate>Tue, 26 Mar 2019 01:16:22 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ssl-decryption-with-firepower-physical-sensors/m-p/2860097#M1030595</guid>
      <dc:creator>Valery Denisov</dc:creator>
      <dc:date>2019-03-26T01:16:22Z</dc:date>
    </item>
    <item>
      <title>Hi,</title>
      <link>https://community.cisco.com/t5/network-security/ssl-decryption-with-firepower-physical-sensors/m-p/2860098#M1030596</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Check : http://www.cisco.com/c/en/us/support/docs/security/firesight-management-center/200202-Configuration-of-an-SSL-Inspection-Polic.html&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Make sure you have the certificate etc in place.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Regards,&lt;/P&gt;
&lt;P&gt;Aastha Bhardwaj&lt;/P&gt;
&lt;P&gt;Rate if that helps!!!&lt;/P&gt;</description>
      <pubDate>Thu, 02 Jun 2016 13:12:17 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ssl-decryption-with-firepower-physical-sensors/m-p/2860098#M1030596</guid>
      <dc:creator>Aastha Bhardwaj</dc:creator>
      <dc:date>2016-06-02T13:12:17Z</dc:date>
    </item>
    <item>
      <title>Sure i have it.</title>
      <link>https://community.cisco.com/t5/network-security/ssl-decryption-with-firepower-physical-sensors/m-p/2860099#M1030597</link>
      <description>&lt;P&gt;Sure i have it.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Without cert or key you cannot create ssl policy.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;We tested several sites and some of them allow ssl inspecton while most of them require not supported cipher suite by firepower.&lt;/P&gt;</description>
      <pubDate>Thu, 02 Jun 2016 16:38:21 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ssl-decryption-with-firepower-physical-sensors/m-p/2860099#M1030597</guid>
      <dc:creator>Valery Denisov</dc:creator>
      <dc:date>2016-06-02T16:38:21Z</dc:date>
    </item>
    <item>
      <title>Folks,</title>
      <link>https://community.cisco.com/t5/network-security/ssl-decryption-with-firepower-physical-sensors/m-p/2860100#M1030598</link>
      <description>&lt;P&gt;Folks,&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;any tips ? Task seems be obvious but no luck with configuration. For example, i can see chrome use&amp;nbsp;&lt;SPAN&gt;CHACHA20_POLY1305 for cipher and firepower can do nothing about this. How to prevent this situation ? How to force use firepower supported ciphers?&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 06 Jun 2016 08:13:38 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ssl-decryption-with-firepower-physical-sensors/m-p/2860100#M1030598</guid>
      <dc:creator>Valery Denisov</dc:creator>
      <dc:date>2016-06-06T08:13:38Z</dc:date>
    </item>
    <item>
      <title>Hello Valery,</title>
      <link>https://community.cisco.com/t5/network-security/ssl-decryption-with-firepower-physical-sensors/m-p/2860101#M1030599</link>
      <description>&lt;P&gt;Hello Valery,&lt;/P&gt;
&lt;P&gt;There are few issues reported with the Cipher errors in past month . Thus could you please contact Cisco TAC so that they can validate it and provide you a solution.&lt;/P&gt;
&lt;P&gt;Regards&lt;BR /&gt;Jetsy&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 07 Jun 2016 05:47:17 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ssl-decryption-with-firepower-physical-sensors/m-p/2860101#M1030599</guid>
      <dc:creator>Jetsy Mathew</dc:creator>
      <dc:date>2016-06-07T05:47:17Z</dc:date>
    </item>
    <item>
      <title>So guys,</title>
      <link>https://community.cisco.com/t5/network-security/ssl-decryption-with-firepower-physical-sensors/m-p/2860102#M1030600</link>
      <description>&lt;P&gt;So guys,&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;I opened case in TAC and got my answer. Traffic flow as follows:&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;The client hello passes through to the end server. The end server sends&lt;/P&gt;
&lt;P&gt;back the server hello with the chosen cipher suite. Then when the&lt;/P&gt;
&lt;P&gt;client sends the premaster secret we intercept that and send the client&lt;/P&gt;
&lt;P&gt;our master secret and the server our premaster secret. This is how we&lt;/P&gt;
&lt;P&gt;own the key and can decrypt resign the traffic.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;That means you can't control negotiated cipher suite. If firepower doesn't support negotiated cipher you can't decrypt it... All you can do - do not decrypt and left users unprotected because large number of sites using cipher suites currently not supported by firepower.&lt;/P&gt;</description>
      <pubDate>Tue, 14 Jun 2016 14:12:19 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ssl-decryption-with-firepower-physical-sensors/m-p/2860102#M1030600</guid>
      <dc:creator>Valery Denisov</dc:creator>
      <dc:date>2016-06-14T14:12:19Z</dc:date>
    </item>
  </channel>
</rss>

