<?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: proxy log name resolution in Security</title>
    <link>https://community.splunk.com/t5/Security/proxy-log-name-resolution/m-p/106506#M3405</link>
    <description>&lt;P&gt;what kind of IP? Public?internal? internal from dhcp?&lt;BR /&gt;
Here an example of dns lookup &lt;A href="http://docs.splunk.com/Documentation/Splunk/4.3.3/Knowledge/Addfieldsfromexternaldatasources#Example_of_external_fields_lookup"&gt;dns lookup external script&lt;/A&gt;&lt;/P&gt;</description>
    <pubDate>Tue, 24 Jul 2012 15:50:55 GMT</pubDate>
    <dc:creator>MarioM</dc:creator>
    <dc:date>2012-07-24T15:50:55Z</dc:date>
    <item>
      <title>proxy log name resolution</title>
      <link>https://community.splunk.com/t5/Security/proxy-log-name-resolution/m-p/106505#M3404</link>
      <description>&lt;P&gt;In the context of proxy logs - could Splunk (via APIs or what not) enable the resolution of IP addresses to the logged in username for a particular log from a proxy?&lt;/P&gt;</description>
      <pubDate>Tue, 24 Jul 2012 06:31:11 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/proxy-log-name-resolution/m-p/106505#M3404</guid>
      <dc:creator>jonathanfalconi</dc:creator>
      <dc:date>2012-07-24T06:31:11Z</dc:date>
    </item>
    <item>
      <title>Re: proxy log name resolution</title>
      <link>https://community.splunk.com/t5/Security/proxy-log-name-resolution/m-p/106506#M3405</link>
      <description>&lt;P&gt;what kind of IP? Public?internal? internal from dhcp?&lt;BR /&gt;
Here an example of dns lookup &lt;A href="http://docs.splunk.com/Documentation/Splunk/4.3.3/Knowledge/Addfieldsfromexternaldatasources#Example_of_external_fields_lookup"&gt;dns lookup external script&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 24 Jul 2012 15:50:55 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/proxy-log-name-resolution/m-p/106506#M3405</guid>
      <dc:creator>MarioM</dc:creator>
      <dc:date>2012-07-24T15:50:55Z</dc:date>
    </item>
    <item>
      <title>Re: proxy log name resolution</title>
      <link>https://community.splunk.com/t5/Security/proxy-log-name-resolution/m-p/106507#M3406</link>
      <description>&lt;P&gt;Assuming the information is actually &lt;STRONG&gt;available&lt;/STRONG&gt;, sure.  But you need to drop a little more detail on us.  The assumption would have to be that there is something that can tie the IP address in the proxy server logs to a logged-in user at the machine that is assigned the IP in the proxy logs themselves.  &lt;/P&gt;

&lt;P&gt;The clearest solution is to have the proxy require authentication.  If you can't do that, then you need to be able to know who is logged into a given machine at a given time.  With a multi-user system, like a Windows Terminal Server or any Unix machine this is far more difficult.&lt;/P&gt;

&lt;P&gt;I think you need to figure out what data you have available to you before you can begin to try to piece together a solution.&lt;/P&gt;</description>
      <pubDate>Tue, 24 Jul 2012 15:58:48 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/proxy-log-name-resolution/m-p/106507#M3406</guid>
      <dc:creator>dwaddle</dc:creator>
      <dc:date>2012-07-24T15:58:48Z</dc:date>
    </item>
  </channel>
</rss>

