<?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>AD on Miguel Lameiro | Cybersecurity Blog &amp; Security Writeups</title><link>https://blog.lameiro0x.com/tags/ad/</link><description>Recent content in AD on Miguel Lameiro | Cybersecurity Blog &amp; Security Writeups</description><generator>Hugo -- 0.161.1</generator><language>en-us</language><lastBuildDate>Sat, 25 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://blog.lameiro0x.com/tags/ad/index.xml" rel="self" type="application/rss+xml"/><item><title>Active Directory Enumeration</title><link>https://blog.lameiro0x.com/notes/information-gathering/active-directory-enumeration/</link><pubDate>Sun, 19 Apr 2026 00:00:00 +0000</pubDate><guid>https://blog.lameiro0x.com/notes/information-gathering/active-directory-enumeration/</guid><description>&lt;h1 id="introduction"&gt;Introduction&lt;/h1&gt;
&lt;p&gt;Active Directory enumeration is the process of building a usable map of a Windows enterprise environment so later privilege escalation and lateral movement are based on facts instead of guesses. In a real engagement, the goal is rarely &amp;ldquo;list everything&amp;rdquo; for its own sake. The real goal is to identify valid users, critical hosts, trust relationships, weak controls, exposed services, and data that can be turned into access, escalation, or persistence.&lt;/p&gt;</description></item><item><title>Active Directory Exploitation</title><link>https://blog.lameiro0x.com/notes/exploitation/active-directory-exploitation/</link><pubDate>Sat, 25 Apr 2026 00:00:00 +0000</pubDate><guid>https://blog.lameiro0x.com/notes/exploitation/active-directory-exploitation/</guid><description>&lt;h1 id="introduction"&gt;Introduction&lt;/h1&gt;
&lt;p&gt;Active Directory exploitation is the phase where raw enumeration data becomes actual control over users, hosts, and eventually the domain itself. By this point, the tester is no longer just collecting names, groups, and services, but turning those relationships into passwords, tickets, shells, replication rights, and privileged access. The important shift is strategic: instead of asking &amp;ldquo;what exists,&amp;rdquo; the question becomes &amp;ldquo;which path gives the highest-value access with the least effort and the lowest operational cost.&amp;rdquo;&lt;/p&gt;</description></item></channel></rss>