<?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: How to identify which host the user is trying to access by using windows DC log. in Splunk Enterprise Security</title>
    <link>https://community.splunk.com/t5/Splunk-Enterprise-Security/How-to-identify-which-host-the-user-is-trying-to-access-by-using/m-p/486473#M8021</link>
    <description>&lt;P&gt;This &lt;EM&gt;might&lt;/EM&gt; be possible with NTLM authentication, but Kerberos doesn't work that way.&lt;/P&gt;

&lt;P&gt;With Kerberos, user A interacts with DC B from host A, then proceeds directly to host C with its service ticket in hand for the service(s) running on host C.&lt;/P&gt;

&lt;P&gt;Under NTLM, host C will challenge user A to authenticate, which host C &lt;EM&gt;might&lt;/EM&gt; verify with DC B (it very well could be some other domain controller).  I think only with NTLM will you possibly see host C authenticating user A on DC B, but only if host C uses DC B...&lt;/P&gt;

&lt;P&gt;Check this page for a decent graphic on how NTLM works:&lt;BR /&gt;
&lt;A href="https://medium.com/@m8r0wn/internal-information-disclosure-using-hidden-ntlm-authentication-18de17675666"&gt;https://medium.com/@m8r0wn/internal-information-disclosure-using-hidden-ntlm-authentication-18de17675666&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;And this page for how Kerberos works:&lt;BR /&gt;
&lt;A href="https://www.manageengine.com/products/active-directory-audit/kb/windows-security-log-event-id-4768.html"&gt;https://www.manageengine.com/products/active-directory-audit/kb/windows-security-log-event-id-4768.html&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;I think the only way to make sure you capture this would be to turn on security auditing/logging on host C.&lt;/P&gt;

&lt;P&gt;Hope that helps!&lt;BR /&gt;
rmmiller&lt;/P&gt;</description>
    <pubDate>Thu, 09 Apr 2020 01:19:05 GMT</pubDate>
    <dc:creator>rmmiller</dc:creator>
    <dc:date>2020-04-09T01:19:05Z</dc:date>
    <item>
      <title>How to identify which host the user is trying to access by using windows DC log.</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise-Security/How-to-identify-which-host-the-user-is-trying-to-access-by-using/m-p/486472#M8020</link>
      <description>&lt;P&gt;This question may not 100% related with Splunk but I am sure Splunker had done this many times so I thought I will just ask&lt;/P&gt;

&lt;P&gt;I want to identify the real destination when user logon a host using authenticate through DC like Kerobers or NTLM. I looked at event 4624, 4768,4771 on the DC log, they only have real src information, but I cant find the real dest information in these event. Is there another event I should look at or it is some field is missing on these events? my example as below&lt;/P&gt;

&lt;P&gt;user A using host A to logon to host C by go through DC B. and I only collect log at DC B, so I want to know how to identify the host C information from the log in this scenario.&lt;/P&gt;

&lt;P&gt;Thank you in advanced.&lt;/P&gt;</description>
      <pubDate>Fri, 06 Mar 2020 07:02:21 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise-Security/How-to-identify-which-host-the-user-is-trying-to-access-by-using/m-p/486472#M8020</guid>
      <dc:creator>samlinsongguo</dc:creator>
      <dc:date>2020-03-06T07:02:21Z</dc:date>
    </item>
    <item>
      <title>Re: How to identify which host the user is trying to access by using windows DC log.</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise-Security/How-to-identify-which-host-the-user-is-trying-to-access-by-using/m-p/486473#M8021</link>
      <description>&lt;P&gt;This &lt;EM&gt;might&lt;/EM&gt; be possible with NTLM authentication, but Kerberos doesn't work that way.&lt;/P&gt;

&lt;P&gt;With Kerberos, user A interacts with DC B from host A, then proceeds directly to host C with its service ticket in hand for the service(s) running on host C.&lt;/P&gt;

&lt;P&gt;Under NTLM, host C will challenge user A to authenticate, which host C &lt;EM&gt;might&lt;/EM&gt; verify with DC B (it very well could be some other domain controller).  I think only with NTLM will you possibly see host C authenticating user A on DC B, but only if host C uses DC B...&lt;/P&gt;

&lt;P&gt;Check this page for a decent graphic on how NTLM works:&lt;BR /&gt;
&lt;A href="https://medium.com/@m8r0wn/internal-information-disclosure-using-hidden-ntlm-authentication-18de17675666"&gt;https://medium.com/@m8r0wn/internal-information-disclosure-using-hidden-ntlm-authentication-18de17675666&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;And this page for how Kerberos works:&lt;BR /&gt;
&lt;A href="https://www.manageengine.com/products/active-directory-audit/kb/windows-security-log-event-id-4768.html"&gt;https://www.manageengine.com/products/active-directory-audit/kb/windows-security-log-event-id-4768.html&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;I think the only way to make sure you capture this would be to turn on security auditing/logging on host C.&lt;/P&gt;

&lt;P&gt;Hope that helps!&lt;BR /&gt;
rmmiller&lt;/P&gt;</description>
      <pubDate>Thu, 09 Apr 2020 01:19:05 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise-Security/How-to-identify-which-host-the-user-is-trying-to-access-by-using/m-p/486473#M8021</guid>
      <dc:creator>rmmiller</dc:creator>
      <dc:date>2020-04-09T01:19:05Z</dc:date>
    </item>
  </channel>
</rss>

