Why it matters in practice
Within Privilege Escalation, Windows Privilege Escalation changes how scope, prerequisites and evidence should be handled. Focus on the concrete asset or data flow under test, record the assumptions that make the condition exploitable and connect verified behavior to an operational consequence and remediation decision.
This note keeps Windows Privilege Escalation tied to offensive workflow: what to observe, what to prove, what usually goes wrong, and which references remain useful once an assessment moves from planning into active validation.
Primary coverage
The coverage below turns Windows Privilege Escalation into an assessment map for Privilege Escalation: identify the relevant system boundary, select a safe validation path, preserve evidence and record uncertainty before drawing a conclusion.
- Windows privilege escalation theory
- Windows privilege escalation practice
Assessment focus
Apply these decision points when validating Windows Privilege Escalation in an authorized environment. The practical lens is local trust, execution rights, credential material and misconfiguration paths from foothold to stronger control.
- Capture the starting identity, effective permissions and local security context.
- Verify the smallest permission, service or execution weakness needed to demonstrate the path.
- Separate proven elevation from opportunities that remain conditional on configuration or credentials.
Selected public references
- GTFOBinsgtfobins.org/
- LOLBASlolbas-project.github.io/
- book.hacktricks.wiki · Linux Privilege Escalation Checklist.htmlbook.hacktricks.wiki/en/linux-hardening/linux-privilege-escalation-checklist.html
- book.hacktricks.wiki · Checklist Windows Privilege Escalation.htmlbook.hacktricks.wiki/en/windows-hardening/checklist-windows-privilege-escalation.html
- GitHub · carlospolop / PEASS-nggithub.com/carlospolop/PEASS-ng