<?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 Hi Johnny, in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/http-https-ftp-proxy-with-firepower/m-p/3093230#M1005898</link>
    <description>&lt;P&gt;Hi Johnny,&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Looks pretty much fine to me. Have fine connectivity to ASA then redirect the traffic towards SFR module as per this article:&amp;nbsp;http://www.cisco.com/c/en/us/support/docs/security/asa-firepower-services/118644-configure-firepower-00.html&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;NOTE: Please make sure you configure rules and policies on SFR before you put the traffic redirection from ASA to SFR.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Best practices: Redirect one or two TEST Machine's traffic towards SFR and verify if traffic is hitting correct rules and everything is working okay. Also, it is good to put the device in SFR fail-open monitor-only mode for a day or two and analyse the traffic &amp;nbsp;and behaviour (Kind of IDS mode, it won't drop&amp;nbsp;actual packets).&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Hope this helps.&lt;/P&gt;
&lt;P&gt;Regards,&lt;/P&gt;
&lt;P&gt;Dv&lt;/P&gt;</description>
    <pubDate>Tue, 25 Jul 2017 10:11:55 GMT</pubDate>
    <dc:creator>Dinesh Verma</dc:creator>
    <dc:date>2017-07-25T10:11:55Z</dc:date>
    <item>
      <title>HTTP, HTTPS, FTP Proxy with firepower</title>
      <link>https://community.cisco.com/t5/network-security/http-https-ftp-proxy-with-firepower/m-p/3093228#M1005896</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;my costumer wants to dismiss his old proxy server and use ASA5506 with firepower to achieve the same result.&lt;/P&gt;
&lt;P&gt;ASA5506 is fully firepower licensed (CTRL, IPS, URL, AMP) and managed by Firepower virtual Center.&lt;/P&gt;
&lt;P&gt;Which is the best way to do this?&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;(I was thinking about deleting proxy address from users' browsers, create a policy on my asa that let everybody access internet in a free way and then configure rules on firepower to filter internet access based on LDAP group) but I don't know if it's the right way.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Thanks&lt;/P&gt;
&lt;P&gt;Johnny&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2019 13:28:11 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/http-https-ftp-proxy-with-firepower/m-p/3093228#M1005896</guid>
      <dc:creator>l.buschi</dc:creator>
      <dc:date>2019-03-12T13:28:11Z</dc:date>
    </item>
    <item>
      <title>Hello Johnny</title>
      <link>https://community.cisco.com/t5/network-security/http-https-ftp-proxy-with-firepower/m-p/3093229#M1005897</link>
      <description>&lt;P&gt;Hello Johnny&lt;/P&gt;
&lt;P&gt;You can integrate the ASA with Firepower using the following instructions.&lt;/P&gt;
&lt;P&gt;http://www.cisco.com/c/en/us/support/docs/security/asa-firepower-services/118644-configure-firepower-00.html&lt;/P&gt;
&lt;P&gt;Once its integrated you can create the User based policies in Firepower and you can use Active or Passive Authentication. You can also. create the rules based on the LDAP groups.&lt;/P&gt;
&lt;P&gt;If you wish to use Sourcefire User agent then refer to the following link.&lt;/P&gt;
&lt;P&gt;http://www.cisco.com/c/en/us/td/docs/security/firesight/user-agent/23/config-guide/Firepower-User-Agent-Configuration-Guide-v2-3.html&lt;/P&gt;
&lt;P&gt;http://www.cisco.com/c/en/us/td/docs/security/firepower/60/configuration/guide/fpmc-config-guide-v60/Identity_Policies_and_Realms.html&lt;/P&gt;
&lt;P&gt;Rate if this answer helps.&lt;/P&gt;
&lt;P&gt;Regards&lt;/P&gt;
&lt;P&gt;Jetsy&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 25 Jul 2017 09:58:30 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/http-https-ftp-proxy-with-firepower/m-p/3093229#M1005897</guid>
      <dc:creator>Jetsy Mathew</dc:creator>
      <dc:date>2017-07-25T09:58:30Z</dc:date>
    </item>
    <item>
      <title>Hi Johnny,</title>
      <link>https://community.cisco.com/t5/network-security/http-https-ftp-proxy-with-firepower/m-p/3093230#M1005898</link>
      <description>&lt;P&gt;Hi Johnny,&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Looks pretty much fine to me. Have fine connectivity to ASA then redirect the traffic towards SFR module as per this article:&amp;nbsp;http://www.cisco.com/c/en/us/support/docs/security/asa-firepower-services/118644-configure-firepower-00.html&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;NOTE: Please make sure you configure rules and policies on SFR before you put the traffic redirection from ASA to SFR.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Best practices: Redirect one or two TEST Machine's traffic towards SFR and verify if traffic is hitting correct rules and everything is working okay. Also, it is good to put the device in SFR fail-open monitor-only mode for a day or two and analyse the traffic &amp;nbsp;and behaviour (Kind of IDS mode, it won't drop&amp;nbsp;actual packets).&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Hope this helps.&lt;/P&gt;
&lt;P&gt;Regards,&lt;/P&gt;
&lt;P&gt;Dv&lt;/P&gt;</description>
      <pubDate>Tue, 25 Jul 2017 10:11:55 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/http-https-ftp-proxy-with-firepower/m-p/3093230#M1005898</guid>
      <dc:creator>Dinesh Verma</dc:creator>
      <dc:date>2017-07-25T10:11:55Z</dc:date>
    </item>
    <item>
      <title>Many TKS,</title>
      <link>https://community.cisco.com/t5/network-security/http-https-ftp-proxy-with-firepower/m-p/3093231#M1005900</link>
      <description>&lt;P&gt;Many TKS,&lt;/P&gt;
&lt;P&gt;which do you think is the best solution?&lt;/P&gt;
&lt;P&gt;Active, passive or rule based on Group on LDAP?&lt;/P&gt;
&lt;P&gt;The less hard solution.&lt;/P&gt;
&lt;P&gt;My costumer would like to reach the following goal:&lt;/P&gt;
&lt;P&gt;admin users can surf free internet&lt;/P&gt;
&lt;P&gt;normal users can surf filtrated internet&lt;/P&gt;
&lt;P&gt;banned user cannot surf the internet.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 25 Jul 2017 10:52:42 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/http-https-ftp-proxy-with-firepower/m-p/3093231#M1005900</guid>
      <dc:creator>l.buschi</dc:creator>
      <dc:date>2017-07-25T10:52:42Z</dc:date>
    </item>
    <item>
      <title>Hello l.buschi,</title>
      <link>https://community.cisco.com/t5/network-security/http-https-ftp-proxy-with-firepower/m-p/3093232#M1005902</link>
      <description>&lt;P&gt;Hello&amp;nbsp;&lt;A href="https://supportforums.cisco.com/users/lbuschi" title="View user profile." class="username" lang="" about="/users/lbuschi" typeof="sioc:UserAccount" property="foaf:name" datatype=""&gt;l.buschi&lt;/A&gt;,&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Its purely based on what customer requires. You can &amp;nbsp;use &amp;nbsp;Sourcefire User agent and then go ahead with the User based or group based policies and then you achieve the requirement .&lt;/P&gt;
&lt;P&gt;Please refer the configuration guide that I have mentioned in the previous update.&lt;/P&gt;
&lt;P&gt;Also try to use the latest software version available in the Firepower as well.&lt;/P&gt;
&lt;P&gt;Regards&lt;/P&gt;
&lt;P&gt;Jetsy&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 25 Jul 2017 10:59:13 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/http-https-ftp-proxy-with-firepower/m-p/3093232#M1005902</guid>
      <dc:creator>Jetsy Mathew</dc:creator>
      <dc:date>2017-07-25T10:59:13Z</dc:date>
    </item>
  </channel>
</rss>

