<?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 again Marius, thanks for in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/firesight-how-to-identify-source-device-through-a-proxy-server/m-p/2889645#M154547</link>
    <description>&lt;P&gt;Hi again Marius, thanks for your previous replies I really appreciate it! though I do have one more question &lt;span class="lia-unicode-emoji" title=":winking_face:"&gt;😉&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;I guess the best&amp;nbsp;solution in this particular scenario would be to put the Proxy in the DMZ, then the service policy on the ASA should match and send these requests through&amp;nbsp;to the FirePower module and onto FireSight&amp;nbsp;for&amp;nbsp;analysis. If FireSight decides to block the traffic or sees an IOC then this would show up as the actual source address of the host PC on the LAN rather than the proxy.&lt;/P&gt;
&lt;P&gt;I have just noticed a couple of IOC's since removing the network discovery policy this morning and I have no idea what machine is compromised as they all reference the IP address of the proxy server &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;Thanks again!&lt;/P&gt;</description>
    <pubDate>Mon, 25 Apr 2016 13:44:55 GMT</pubDate>
    <dc:creator>doylepaul</dc:creator>
    <dc:date>2016-04-25T13:44:55Z</dc:date>
    <item>
      <title>FireSight: How to identify source device through a proxy server.</title>
      <link>https://community.cisco.com/t5/network-security/firesight-how-to-identify-source-device-through-a-proxy-server/m-p/2889641#M154543</link>
      <description>&lt;P&gt;Hi, I was just wondering how you would be able to identify the source IP addresses of devices on your corporate LAN if all http traffic is going through an internal proxy server?&lt;/P&gt;
&lt;P&gt;I have been running network discovery for over a week now and would like to start running some policies. But when I look under analysis, all I see is the source address of my proxy server!&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Many thanks.&lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2019 07:39:27 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firesight-how-to-identify-source-device-through-a-proxy-server/m-p/2889641#M154543</guid>
      <dc:creator>doylepaul</dc:creator>
      <dc:date>2019-03-12T07:39:27Z</dc:date>
    </item>
    <item>
      <title>You would need to either move</title>
      <link>https://community.cisco.com/t5/network-security/firesight-how-to-identify-source-device-through-a-proxy-server/m-p/2889642#M154544</link>
      <description>&lt;P&gt;You would need to either move the SourceFire appliance / ASA /w FirePower to be between the proxy server and your users or remove the Proxy server all together.&lt;/P&gt;
&lt;P&gt;--&lt;/P&gt;
&lt;P&gt;Please remember to select a correct answer and rate helpful posts&lt;/P&gt;</description>
      <pubDate>Fri, 22 Apr 2016 08:23:52 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firesight-how-to-identify-source-device-through-a-proxy-server/m-p/2889642#M154544</guid>
      <dc:creator>Marius Gunnerud</dc:creator>
      <dc:date>2016-04-22T08:23:52Z</dc:date>
    </item>
    <item>
      <title>Thanks Marius, I appreciate</title>
      <link>https://community.cisco.com/t5/network-security/firesight-how-to-identify-source-device-through-a-proxy-server/m-p/2889643#M154545</link>
      <description>&lt;P&gt;Thanks Marius, I appreciate your help &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;So basically, I need to move the ASA/Firepower to 'intercept' the http requests before they hit the proxy!&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Thanks again.&lt;/P&gt;</description>
      <pubDate>Fri, 22 Apr 2016 09:04:51 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firesight-how-to-identify-source-device-through-a-proxy-server/m-p/2889643#M154545</guid>
      <dc:creator>doylepaul</dc:creator>
      <dc:date>2016-04-22T09:04:51Z</dc:date>
    </item>
    <item>
      <title>Correct</title>
      <link>https://community.cisco.com/t5/network-security/firesight-how-to-identify-source-device-through-a-proxy-server/m-p/2889644#M154546</link>
      <description>&lt;P&gt;Correct&lt;/P&gt;
&lt;P&gt;--&lt;/P&gt;
&lt;P&gt;Please remember to select a correct answer and rate helpful posts&lt;/P&gt;</description>
      <pubDate>Fri, 22 Apr 2016 09:19:02 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firesight-how-to-identify-source-device-through-a-proxy-server/m-p/2889644#M154546</guid>
      <dc:creator>Marius Gunnerud</dc:creator>
      <dc:date>2016-04-22T09:19:02Z</dc:date>
    </item>
    <item>
      <title>Hi again Marius, thanks for</title>
      <link>https://community.cisco.com/t5/network-security/firesight-how-to-identify-source-device-through-a-proxy-server/m-p/2889645#M154547</link>
      <description>&lt;P&gt;Hi again Marius, thanks for your previous replies I really appreciate it! though I do have one more question &lt;span class="lia-unicode-emoji" title=":winking_face:"&gt;😉&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;I guess the best&amp;nbsp;solution in this particular scenario would be to put the Proxy in the DMZ, then the service policy on the ASA should match and send these requests through&amp;nbsp;to the FirePower module and onto FireSight&amp;nbsp;for&amp;nbsp;analysis. If FireSight decides to block the traffic or sees an IOC then this would show up as the actual source address of the host PC on the LAN rather than the proxy.&lt;/P&gt;
&lt;P&gt;I have just noticed a couple of IOC's since removing the network discovery policy this morning and I have no idea what machine is compromised as they all reference the IP address of the proxy server &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;Thanks again!&lt;/P&gt;</description>
      <pubDate>Mon, 25 Apr 2016 13:44:55 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firesight-how-to-identify-source-device-through-a-proxy-server/m-p/2889645#M154547</guid>
      <dc:creator>doylepaul</dc:creator>
      <dc:date>2016-04-25T13:44:55Z</dc:date>
    </item>
    <item>
      <title>Yes that would be a good</title>
      <link>https://community.cisco.com/t5/network-security/firesight-how-to-identify-source-device-through-a-proxy-server/m-p/2889646#M154548</link>
      <description>&lt;P&gt;Yes that would be a good solution. &amp;nbsp;Just keep in mind that unless you exempt the proxy server from being sent to sourcefire traffic will be inspected twice. Or perhaps that is what you want, though it might be overkill.&lt;/P&gt;
&lt;P&gt;--&lt;/P&gt;
&lt;P&gt;Please remember to select a correct answer and rate helpful posts&lt;/P&gt;</description>
      <pubDate>Mon, 25 Apr 2016 13:57:02 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firesight-how-to-identify-source-device-through-a-proxy-server/m-p/2889646#M154548</guid>
      <dc:creator>Marius Gunnerud</dc:creator>
      <dc:date>2016-04-25T13:57:02Z</dc:date>
    </item>
    <item>
      <title>Oh yeah !!! you mean on the</title>
      <link>https://community.cisco.com/t5/network-security/firesight-how-to-identify-source-device-through-a-proxy-server/m-p/2889647#M154549</link>
      <description>&lt;P&gt;Oh yeah !!! you mean on the way back! Hadn't thought of that!&lt;/P&gt;
&lt;P&gt;The way the network is setup, this is the only way we would be able to resolve this issue.&lt;/P&gt;
&lt;P&gt;Thanks again mate, really appreciate your help!&lt;/P&gt;
&lt;P&gt;Cheers.&lt;/P&gt;</description>
      <pubDate>Mon, 25 Apr 2016 14:39:19 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firesight-how-to-identify-source-device-through-a-proxy-server/m-p/2889647#M154549</guid>
      <dc:creator>doylepaul</dc:creator>
      <dc:date>2016-04-25T14:39:19Z</dc:date>
    </item>
  </channel>
</rss>

