A county Windows foothold is new. Before choosing a privilege-escalation path, what situational awareness should come first?
Select an answer to reveal the explanation.
Short Explanation
You would not pick a lock before checking which door you are standing at. On Windows, start with who you are, what privileges the token holds, and what build/patch level the box is on. That situational awareness keeps you from firing the wrong technique into the dark.
Full Explanation
Effective Windows privilege escalation begins with identity and environment: whoami-class user context, privilege lists, OS version/build, and patch indicators. Those facts determine which misconfiguration or privilege-abuse classes are even plausible. Blindly running public exploits, disabling defenses, or assuming domain admin skips the judgment CPTS expects. Structured local enumeration reduces noise and RoE risk.