A city engagement yields a low-privilege Linux shell on an internal host. What should the tester do first for privilege-escalation situational awareness?
Select an answer to reveal the explanation.
Short Explanation
Before you rummage the entire toolbox, check whose boots you are wearing and what room you are in. On a fresh low-priv Linux shell, identity, host role, and obvious misconfig checks beat random exploit downloads. Skipping the whole phase or silencing audit without approval is not the move.
Full Explanation
Linux privilege-escalation methodology starts with situational awareness: current user and groups, host purpose, kernel/OS details, and high-signal misconfiguration classes such as sudo rights listings. Blind exploit shopping wastes time and raises risk. Unauthorized logging disablement violates engagement norms. Structured enumeration guides whether misconfig classes or other paths are realistic before deeper attempts.