Pass the CompTIA PenTest+ PT0-003 Questions and answers with CertsForce

This command uses Mimikatz’ kerberos::golden module to forge a Golden Ticket, which is a fabricated Kerberos Ticket Granting Ticket (TGT) created using the domain’s Kerberos key material (commonly the KRBTGT hash, supplied here as an RC4 key). In PenTest+ post-exploitation tradecraft, a Golden Ticket allows an attacker to impersonate arbitrary users and obtain Kerberos service tickets without performing legitimate logon steps. The inclusion of /service:CIFS and /target: dc01.test.local indicates the tester intends to access the domain controller’s SMB/CIFS service using Kerberos authentication. The /ptt switch (“pass-the-ticket”) injects the forged ticket into the current session so the system will present it automatically to services.

The goal is therefore to bypass normal authentication controls by using a forged Kerberos ticket to gain authorized access to resources (like SMB shares) as a chosen identity. It is not share enumeration itself, not credential harvesting, and not password spraying.

Top of Form

If a penetration tester unintentionally disrupts a critical system, they must immediately follow the client’s escalation process to ensure proper handling.

Follow the escalation process (Option C):

The penetration testing engagement follows a predefined incident response and escalation plan.

The tester documents the issue, informs stakeholders, and works with IT teams to minimize impact.

The script shows:

Use of BlobServiceClient.from_connection_string() — this is Azure Blob Storage interaction.

It opens a local file in binary mode (with open(file_path, " rb " )).

Calls blob_client.upload_blob(data) — clearly indicating uploading the local file to cloud storage.

This matches data exfiltration activity, where stolen or sensitive local files are sent to an external system (cloud storage).

Why not the others?

A. API endpoint: The code uses Azure Blob storage SDK, not a REST API endpoint.

B. Download data from cloud storage: Code uploads, not downloads.

C. Alternate data streams (ADS): That’s a Windows NTFS feature, unrelated to cloud storage.

CompTIA PT0-003 Objective Mapping:

Domain 3.0 Attacks and Exploits

3.2: Post-exploitation techniques (data exfiltration, cloud storage use).

Web shells provide remote access and persistence for attackers. The best mitigation is to remove persistence mechanisms.

Remove the persistence mechanisms (Option A):

Attackers often modify startup scripts, cron jobs, or registry keys to maintain access.

If persistence is not removed, even after the web shell is deleted, attackers can reinstall or reaccess it.

The correct answer is D. Secrets enumeration

When exposed cloud storage buckets are discovered, the tester should enumerate the contents for sensitive data such as API keys, access tokens, private keys, credentials, configuration files, database backups, source code, or other secrets. This is commonly referred to as secrets enumeration and is a key cloud assessment activity.

A is incorrect because protocol fingerprinting identifies protocols or services in use, but it does not help access or review bucket contents.

B is incorrect because credential brute forcing is intrusive, noisy, and often outside the expected safe approach unless explicitly authorized. The question states the buckets are exposed, so brute forcing is not the correct next step.

C is incorrect because service discovery identifies available services, but the storage buckets have already been discovered. The next step is to enumerate their accessible contents.

In PenTest+ terms, this falls under Information Gathering and Vulnerability Scanning, specifically cloud enumeration, exposed storage review, and identifying sensitive information in publicly accessible cloud resources.

Data Loss Prevention (DLP) tools monitor network traffic and files for sensitive information leaks. The most effective way to bypass DLP is to use encryption, since DLP systems cannot inspect encrypted content.

Option A (Encoding) ❌: Base64 or Hex encoding can sometimes bypass filters, but many DLP tools detect common encoding schemes.

Option B (Compression) ❌: Compression can change file signatures, but modern DLP systems can inspect compressed files.

Option C (Encryption) ✅: Correct.

Strong encryption prevents DLP tools from analyzing file contents.

Option D (Obfuscation) ❌: Code obfuscation may work for source code leaks, but DLP solutions use heuristics to detect patterns.

???? Reference: CompTIA PenTest+ PT0-003 Official Guide – Bypassing Security Controls

The correct answer is A. Mimikatz

The KRBTGT account is a special Active Directory account used by the Key Distribution Center to encrypt and sign Kerberos tickets. If the KRBTGT account password has not been changed for a long time, and an attacker obtains the account hash, the attacker can use it to forge Kerberos Ticket Granting Tickets. This is known as a Golden Ticket attack.

Mimikatz is the tool commonly used to extract credentials, obtain Kerberos-related secrets, and create forged Kerberos tickets such as Golden Tickets. With a valid forged ticket, an attacker may maintain long-term domain persistence and impersonate privileged users.

B is incorrect because John the Ripper is primarily used for offline password cracking. It does not create or inject Kerberos Golden Tickets.

C is incorrect because Hashcat is also used for password/hash cracking. It may help crack hashes, but it is not the primary tool used to exploit a stale KRBTGT password through Golden Ticket creation.

D is incorrect because Hydra is an online password brute-force tool. It is not used for Kerberos ticket forgery.

In PenTest+ terms, this falls under Attacks and Exploits, specifically Active Directory attacks, Kerberos abuse, credential attacks, and Golden Ticket persistence.

The correct answer is C. Running Metasploit utilizing the EternalBlue module

The scan results show TCP port 445 open, which indicates SMB is available. The host is also identified with partial confidence as Windows 7 SP0, an older Windows version historically associated with SMB vulnerabilities. EternalBlue targets SMBv1 and is known to be potentially unstable, especially against older or unpatched Windows systems. Exploiting SMB kernel-level vulnerabilities can cause system crashes or blue screens if the exploit fails or is not compatible with the target.

A is incorrect because Responder and Impacket are commonly used for SMB/NTLM relay or credential capture activities. They can be risky in some environments, but they are less likely than EternalBlue to directly crash a target when creating a session.

B is incorrect because Nmap safe scripts are designed to be non-intrusive. Targeting RDP with safe scripts is less likely to cause system instability.

D is incorrect because Hydra at one attempt per second is a slow password attack. It may trigger account lockout depending on policy, but it is not the most likely option to create host stability issues.

In PenTest+ terms, this falls under Attacks and Exploits, specifically exploit selection, exploit safety, and understanding the operational risk of using unstable exploits against production systems.

A reverse shell that is left on a target to maintain access is a form of persistence/backdoor. The action described — removing the reverse shell at the end of the engagement — is specifically the removal of a persistence mechanism. Post-engagement cleanup requires removal of any artifacts that provide continued access (web shells, scheduled tasks, reverse shells, cron jobs, created accounts, etc.) so the environment is returned to its pre-test state and to prevent later compromise.

Why not the others:

B (Uninstalling tools): Removing tools is also a cleanup activity, but the question explicitly references removing the reverse shell (persistence).

C (Preserving artifacts): Preserving artifacts is the opposite (saving logs/evidence) for incident response — not removing access.

D (Reverting configuration changes): Important, but the best single match for removing a reverse shell is “removing persistence mechanisms.”

PT0-003 mapping: Domain 5 — post-engagement cleanup and returning environment to baseline.

Risk scoring is the report element that most directly enables an organization to prioritize remediation work because it translates technical findings into an ordered view of business risk. In PenTest+ reporting guidance, testers are expected to communicate not only what is vulnerable but also how severe the issue is and how likely it is to be exploited, often incorporating factors such as exploitability, impact, exposure, and the presence of compensating controls. This produces a defensible ranking that helps stakeholders decide what to fix first when time and resources are limited.

Proof of concept supports validation by demonstrating that exploitation is possible, but it does not inherently provide comparative urgency across multiple findings. An attack narrative explains the path the tester used to achieve objectives (useful for understanding chaining and scope impact), but it is typically descriptive rather than a prioritization mechanism. The executive summary is aimed at leadership-level communication and overall posture, yet it usually depends on underlying risk ratings to justify what should be addressed first. Therefore, risk scoring most directly drives remediation prioritization.