<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Ntds on Mike.Horn</title>
    <link>https://mikehorn-git.github.io/tags/ntds/</link>
    <description>Recent content in Ntds on Mike.Horn</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Sun, 22 Sep 2024 00:00:00 +0200</lastBuildDate>
    <atom:link href="https://mikehorn-git.github.io/tags/ntds/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>crownjewel-1</title>
      <link>https://mikehorn-git.github.io/writeups/htb/sherlocks/crownjewel-1/</link>
      <pubDate>Sun, 22 Sep 2024 00:00:00 +0200</pubDate>
      <guid>https://mikehorn-git.github.io/writeups/htb/sherlocks/crownjewel-1/</guid>
      <description>&lt;h1 id=&#34;q1-attackers-can-abuse-the-vssadmin-utility-to-create-volume-shadow-snapshots-and-then-extract-sensitive-files-like-ntdsdit-to-bypass-security-mechanisms-identify-the-time-when-the-volume-shadow-copy-service-entered-a-running-state&#34;&gt;Q1: Attackers can abuse the vssadmin utility to create volume shadow snapshots and then extract sensitive files like NTDS.dit to bypass security mechanisms. Identify the time when the Volume Shadow Copy service entered a running state.&lt;/h1&gt;
&lt;p&gt;Open the &lt;strong&gt;SYSTEM.evtx&lt;/strong&gt; log and search for &lt;strong&gt;Event ID 7036&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;Look for events indicating the &lt;strong&gt;Volume Shadow Copy&lt;/strong&gt; service entering a running state:&lt;/p&gt;
&lt;p&gt;&lt;img alt=&#34;7036&#34; loading=&#34;lazy&#34; src=&#34;../../writeups/htb/sherlocks/crownjewel-1/2024-09-21T11_58_52,679703907+02_00.png&#34;&gt;&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;🕒 Convert the timestamp to &lt;strong&gt;UTC&lt;/strong&gt;.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;hr&gt;
&lt;h1 id=&#34;q2-when-a-volume-shadow-snapshot-is-created-the-volume-shadow-copy-service-validates-the-privileges-using-the-machine-account-and-enumerates-user-groups-find-the-user-groups-it-enumerates-the-subject-account-name-and-also-identify-the-process-idin-decimal-of-the-volume-shadow-copy-service-process&#34;&gt;Q2: When a volume shadow snapshot is created, the Volume shadow copy service validates the privileges using the Machine account and enumerates User groups. Find the User groups it enumerates, the Subject Account name, and also identify the Process ID(in decimal) of the Volume shadow copy service process&lt;/h1&gt;
&lt;p&gt;Search for &lt;strong&gt;Event ID &lt;a href=&#34;https://learn.microsoft.com/en-us/previous-versions/windows/it-pro/windows-10/security/threat-protection/auditing/event-4799&#34;&gt;4799&lt;/a&gt;&lt;/strong&gt; and filter for:&lt;/p&gt;</description>
    </item>
    <item>
      <title>crownjewel-2</title>
      <link>https://mikehorn-git.github.io/writeups/htb/sherlocks/crownjewel-2/</link>
      <pubDate>Sun, 22 Sep 2024 00:00:00 +0200</pubDate>
      <guid>https://mikehorn-git.github.io/writeups/htb/sherlocks/crownjewel-2/</guid>
      <description>&lt;h1 id=&#34;q1-when-utilizing-ntdsutilexe-to-dump-ntds-on-disk-it-simultaneously-employs-the-microsoft-shadow-copy-service-what-is-the-most-recent-timestamp-at-which-this-service-entered-the-running-state-signifying-the-possible-initiation-of-the-ntds-dumping-process&#34;&gt;Q1: When utilizing ntdsutil.exe to dump NTDS on disk, it simultaneously employs the Microsoft Shadow Copy Service. What is the most recent timestamp at which this service entered the running state, signifying the possible initiation of the NTDS dumping process?&lt;/h1&gt;
&lt;p&gt;Open the &lt;strong&gt;SYSTEM.evtx&lt;/strong&gt; log and search for &lt;strong&gt;Event ID 7036&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;Use a search (Ctrl+F) for &lt;strong&gt;Volume Shadow Copy&lt;/strong&gt; service events.&lt;/p&gt;
&lt;p&gt;Identify the most recent entry where the service entered the running state and note the timestamp from the:&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
