What privilege escalation method is used when you create SSH credentials for a scan?

• A. sudo
• B. No privilege escalation was used
• C. .su
• D. su + sudo

Answer: (A)

When you create SSH credentials for a scan, the common approach is to use sudo for privilege escalation. You log in over SSH as a regular user and then elevate to root as needed by running commands with sudo. This fits typical security models because sudo lets you grant just the needed privileges, keeps root credentials out of automated tools, and provides an auditable trail of what was elevated and when. If no privilege escalation is used, the scan won't be able to perform many privileged checks and results would be incomplete. Using su would require handling a root password and is harder to automate, and combining su with sudo is unnecessary because sudo alone handles the elevation after login.