A library engagement opens multiple Metasploit sessions across hosts. What session-management practice best protects scope?
Select an answer to reveal the explanation.
Short Explanation
Sessions are like borrowed keys—if you lose track of which door each one opens, you wander into rooms you were never invited to. Tag them, know the host, and pause at the property line. Scope discipline beats clever pivoting every time.
Full Explanation
Multi-host engagements create operational risk when sessions are anonymous or casually reused for lateral movement. Testers should maintain clear session-to-target mapping, document ownership, and verify that any next hop remains inside Rules of Engagement. Accidental out-of-scope pivots can breach trust and contract terms even when the original foothold was authorized. Hygiene here is both a safety control and a professional reporting foundation.