Courseiva

CCNA Active Directory Attacks Questions

43 questions · Active Directory Attacks topic · All types, answers revealed

1
MCQmedium

When executing BloodHound to map Active Directory attack paths, which collector option should be specified via SharpHound to gather computer local admin rights without requiring Domain Admin privileges?

A.SharpHound.exe -CollectionMethod LocalAdmin
B.SharpHound.exe -CollectionMethod GPOChanges
C.SharpHound.exe -CollectionMethod TrustList
D.SharpHound.exe -CollectionMethod DCOptions
AnswerA

The LocalAdmin collection method queries each computer's local Administrators group via SAM-R, harvesting local admin mappings without needing Domain Admin rights. This directly satisfies the stem's constraint of gathering local admin rights non-privileged, since SAM-R reads rely on standard remote access rather than elevated directory permissions.

Why this answer

SharpHound's LocalAdmin collection method enumerates local administrator rights on computers by querying each machine (via SAM-R, remote registry, or NetSessionEnum depending on privileges) and records which principals have admin access. This data feeds BloodHound's 'AdminTo' edges, which are essential for finding privilege-escalation paths from a low-privileged user to Domain Admin — and it can be collected with only the rights of the invoking user, not Domain Admin.

Exam trap

CPENT often tests whether candidates know the specific SharpHound -CollectionMethod values and what each one gathers — picking a method that sounds related (GPOChanges, TrustList) instead of LocalAdmin is the common error.

How to eliminate wrong answers

Option B (GPOChanges) is wrong because it collects Group Policy object modifications and affected users/computers, not local admin rights. Option C (TrustList) is wrong because it enumerates domain trust relationships, which is unrelated to local admin membership. Option D (DCOptions) is wrong because it collects domain controller configuration and password policy data, not local admin rights on workstations and servers.

2
MCQeasy

Which native Windows command-line tool can be used by a penetration tester to view cached Kerberos tickets currently loaded in the user session?

A.ticketmgr
B.winrm get tickets
C.kerbuse
D.klist
AnswerD

`klist` queries the local Kerberos credential cache and lists tickets currently held in the logon session, including the initial TGT and any service tickets. This directly satisfies the stem's requirement to view cached Kerberos tickets natively, without external tooling or elevated privileges.

Why this answer

klist is the native Windows command-line utility that displays currently cached Kerberos tickets (TGTs and service tickets) for the logged-on user session. Penetration testers use it to enumerate available tickets before attempting pass-the-ticket or Kerberoasting. It is built into Windows and requires no additional tooling.

Exam trap

CPENT often tests whether candidates recognize the actual native Windows Kerberos tooling versus plausible-sounding fabricated command names, so memorize klist as the canonical ticket viewer.

How to eliminate wrong answers

Option A is wrong because ticketmgr is not a native Windows command — no such built-in utility exists for Kerberos ticket enumeration. Option B is wrong because 'winrm get tickets' is not a valid WinRM subcommand; WinRM is a remote management protocol, not a ticket viewer. Option C is wrong because kerbuse is not a real Windows command-line tool for viewing Kerberos tickets.

3
Multi-Selecthard

An advanced adversary has gained Domain Administrator privileges and wants to establish stealthy, long-term persistence in Active Directory without relying solely on traditional user accounts or standard scheduled tasks. Which THREE advanced persistence mechanisms can be deployed in an Active Directory environment? (Choose THREE)

Select 3 answers
A.AD CS Certificate Mapping (mapping a rogue certificate to a domain account for persistent PKINIT authentication)
B.SID History Injection (appending a high-privileged SID to a standard user account's sIDHistory attribute)
C.DCShadow (registering a rogue Domain Controller to inject objects directly into the AD database without triggering standard event logs)
D.Running the standard Windows Disk Defragmenter (defrag.exe) on the Domain Controller C: drive
E.Modifying the Windows TCP/IP stack registry keys to disable DHCP client notifications
AnswersA, B, C

AD CS certificate mapping lets an attacker with CA access issue a certificate tied to a domain account, enabling persistent PKINIT authentication. This survives password resets and evades traditional account-based detection, satisfying the requirement for stealthy persistence beyond standard user accounts or scheduled tasks.

Why this answer

Option A is correct because AD CS certificate mapping lets an attacker who controls a rogue CA or template map a certificate to a domain account, enabling persistent PKINIT authentication that survives password resets and is hard to detect. Option B is correct because SID History Injection appends a high-privileged SID (e.g., Domain Admins) to a standard user's sIDHistory attribute, granting that account privileged access that persists across sessions and is often overlooked by standard account reviews. Option C is correct because DCShadow registers a rogue Domain Controller via replication (using DRSUAPI) to inject objects and attribute changes directly into the AD database, bypassing normal change-tracking and many standard event logs.

Option D is not a persistence mechanism—defrag.exe is a routine disk maintenance utility with no security or persistence impact on AD. Option E is also unrelated to persistence; modifying TCP/IP registry keys to disable DHCP client notifications is a network configuration tweak, not an Active Directory persistence technique.

Exam trap

CPENT often tests whether candidates can distinguish genuine AD persistence primitives from unrelated system maintenance or network tweaks, luring them toward plausible-sounding but ineffective options.

4
Multi-Selectmedium

Which TWO configuration checks should a penetration tester perform when auditing an Active Directory domain for potential NTLM Relay vulnerabilities?

Select 2 answers
A.Verify if LDAP signing is disabled or set to 'Not Required' on domain controllers.
B.Check whether SMB signing is enforced on domain member workstations and servers.
C.Check if the domain functional level is set to Windows 2000 native.
D.Verify that all user accounts have Kerberos pre-authentication disabled.
E.Enumerate the total number of Service Principal Names registered to machine accounts.
AnswersA, B

LDAP signing, when disabled or set to 'Not Required', lets attackers relay NTLM authentication to the domain controller over unsigned LDAP, enabling rogue directory operations. Checking this setting on domain controllers directly identifies a primary NTLM relay exposure during an Active Directory audit.

Why this answer

Option A is correct because when LDAP signing is disabled or set to 'Not Required' on domain controllers, an attacker who has coerced or relayed NTLM authentication can relay it to LDAP/LDAPS and perform operations such as adding a computer or modifying ACLs, which is a classic NTLM relay path. Option B is correct because SMB signing enforcement determines whether relayed NTLM authentication can be used against SMB services; if signing is not required on member workstations and servers, captured NTLM authentication can be relayed to those hosts to execute commands or access resources. Option C is not relevant because the domain functional level does not directly determine whether NTLM relay is possible; modern functional levels can still be vulnerable if signing and channel binding are not enforced.

Option D is incorrect because disabling Kerberos pre-authentication enables AS-REP roasting, not NTLM relay, and it is not a standard NTLM relay audit check. Option E is incorrect because the number of SPNs on machine accounts relates to Kerberoasting and service account exposure, not directly to NTLM relay vulnerability.

Exam trap

The trap here is confusing NTLM relay prerequisites with other Active Directory attack vectors like Kerberoasting or AS-REP roasting, leading candidates to select options about SPNs or Kerberos pre-authentication instead of the signing configurations that directly enable relay.

5
MCQeasy

When generating a Silver Ticket using Impacket's ticketer.py, what specific piece of cryptographic material is required instead of the KRBTGT hash?

A.The plaintext password of the Domain Administrator
B.The Domain Controller's computer account machine password
C.The NTLM password hash of the specific service account
D.The domain root CA private key (.pfx)
AnswerC

A Silver Ticket is forged with the target service account's NTLM hash, which encrypts the service ticket's PAC and signature. The KRBTGT hash is only needed for Golden Tickets, so the service account hash satisfies the stem's substitution.

Why this answer

A Silver Ticket is forged for a specific service using the NTLM hash of the service account running that service (e.g., MSSQL or CIFS service account), rather than the KRBTGT hash.

6
MCQeasy

During a post-exploitation phase on a Windows workstation, a tester dumps LSASS memory and extracts an NTLM password hash. The tester then uses the CrackMapExec tool to authenticate to other workstations using this hash without cracking it first. What attack technique is being executed?

A.Pass-the-Ticket
B.Kerberoasting
C.Over-Pass-the-Hash
D.Pass-the-Hash
AnswerD

Pass-the-Hash exploits NTLM's design, where the password hash itself authenticates without needing the plaintext. CrackMapExec submits the captured NTLM hash directly to SMB or other services, granting access to remote workstations, which matches the described post-exploitation behaviour.

Why this answer

Pass-the-Hash (PtH) abuses the NTLM authentication protocol by replaying a captured NTLM hash directly to authenticate to remote systems without ever cracking it to plaintext. CrackMapExec's smb/wmi/winrm modules accept the -H flag to inject the hash into the NTLM challenge-response, which is exactly the technique described. Because NTLMv1/NTLMv2 authentication only requires knowledge of the hash (not the password), the tester gains access to other workstations.

Exam trap

CPENT often tests the distinction between Pass-the-Hash (NTLM hash replay) and Over-Pass-the-Hash (using the hash to obtain a Kerberos TGT), since both start from a dumped NTLM hash but diverge in the authentication protocol used.

How to eliminate wrong answers

Option A (Pass-the-Ticket) is wrong because it involves injecting a stolen Kerberos TGT or TGS (.kirbi/.ccache) into a session, not replaying an NTLM hash. Option B (Kerberoasting) is wrong because it requests service tickets for SPNs and cracks them offline — it does not use a dumped LSASS hash to authenticate. Option C (Over-Pass-the-Hash) is wrong because it is a distinct technique that uses an NTLM hash to request a Kerberos TGT via the AS-REQ (converting hash to Kerberos ticket), not direct NTLM authentication to workstations.

7
MCQeasy

A penetration tester is evaluating an Active Directory environment and discovers that LDAP signing is not enforced. Which attack technique does this misconfiguration directly facilitate?

A.Kerberoasting
B.LDAP NTLM Relay
C.AS-REP Roasting
D.Golden Ticket forgery
AnswerB

Without LDAP signing enforced, the server accepts unsigned LDAP binds, so an attacker who captures or coerces NTLM authentication can relay those credentials to the domain controller over LDAP and perform directory operations as the victim. Signing would reject the relayed session.

Why this answer

When LDAP signing is not enforced, an attacker can perform an NTLM relay attack against the LDAP service. By relaying NTLM authentication attempts to a domain controller's LDAP endpoint, the attacker can gain access to directory services, potentially creating or modifying objects, and escalating privileges. This is because without signing, the LDAP server accepts unsigned authentication requests, making it vulnerable to relay.

Exam trap

The trap is confusing LDAP signing with other AD attack techniques like Kerberoasting or AS-REP Roasting; candidates must recognize that missing LDAP signing specifically enables NTLM relay to LDAP.

How to eliminate wrong answers

Option A is wrong because Kerberoasting targets service accounts with SPNs and does not rely on LDAP signing; it exploits weak service account passwords. Option C is wrong because AS-REP Roasting targets accounts with pre-authentication disabled, not LDAP signing. Option D is wrong because Golden Ticket forgery requires the KRBTGT hash, which is unrelated to LDAP signing.

8
MCQmedium

A tester has located a domain user account configured with Constrained Delegation (S4U2Self / S4U2Proxy) pointing to a target service. What tool and module in Impacket can be used to leverage this delegation to obtain a TGS for a privileged user (e.g., Administrator)?

A.getST.py
B.psexec.py
C.GetUserSPNs.py
D.addcomputer.py
AnswerA

getST.py exploits the S4U2Self and S4U2Proxy extensions to request a service ticket impersonating a privileged user, satisfying the Constrained Delegation scenario. It requires the delegated account's credentials or hash plus the SPN of the target service, returning a usable TGS for that service.

Why this answer

Impacket's getST.py is purpose-built to abuse Kerberos delegation by performing the S4U2Self and S4U2Proxy extensions. Given a constrained-delegation account's credentials (or hash) and the target SPN, it requests a service ticket impersonating an arbitrary user such as Administrator, which can then be used with other Impacket tools. This directly leverages the delegation trust configured on the account.

Exam trap

The trap is confusing Kerberoasting (GetUserSPNs.py, offline cracking of service tickets) with delegation abuse (getST.py, online ticket forging via S4U) — both involve TGS tickets but require entirely different preconditions and tools.

How to eliminate wrong answers

Option B (psexec.py) is wrong because it is a remote execution tool that uploads a service binary over SMB — it does not perform S4U2Self/S4U2Proxy delegation abuse. Option C (GetUserSPNs.py) is wrong because it performs Kerberoasting: it enumerates accounts with SPNs and requests their TGS tickets for offline cracking, not delegation abuse. Option D (addcomputer.py) is wrong because it adds a machine account to the domain (useful for RBCD attacks) but does not itself request delegated service tickets.

9
MCQhard

When executing a DCSync attack programmatically via Impacket's secretsdump.py, how does the tool interact with Active Directory to request password data without running code on the domain controller?

A.It connects via RPC and invokes the DRSUAPI protocol (DsGetNCChanges) to request replication data.
B.It executes an LDAP search request asking for the plaintext password attribute.
C.It queries the Active Directory Web Services (ADWS) REST API on port 9389.
D.It reads the NTDS.dit file directly over standard SMB file shares using administrator credentials.
AnswerA

Impacket's secretsdump.py authenticates as a privileged account and invokes the DRSUAPI DsGetNCChanges RPC call, impersonating a domain controller's replication request. This extracts password hashes remotely over the network, satisfying the constraint of harvesting credentials without executing any code on the domain controller itself.

Why this answer

Impacket's secretsdump.py performs DCSync by authenticating to a domain controller and invoking the DRSUAPI (Directory Replication Service Remote Protocol) interface, specifically the DsGetNCChanges method. This RPC call is the same mechanism legitimate DCs use to replicate directory data, so the DC treats the request as a normal replication pull and returns password hashes (NTLM, Kerberos keys) without the attacker ever executing code on the DC.

Exam trap

CPENT often tests the misconception that DCSync reads NTDS.dit directly or uses LDAP — candidates who do not understand the DRSUAPI replication protocol pick option D or B.

How to eliminate wrong answers

Option B is wrong because LDAP does not expose plaintext passwords — the unicodePwd attribute is write-only and stored as an NT hash, so an LDAP search cannot retrieve it. Option C is wrong because ADWS on port 9389 is a SOAP/REST-like interface for PowerShell remoting and management, not a password extraction channel. Option D is wrong because NTDS.dit is locked by the ESE database engine while the DC is running; reading it over SMB requires Volume Shadow Copy or a reboot into DSRM, which is a different technique (not DCSync).

10
MCQmedium

A penetration tester is performing an attack utilizing the PetitPotam (MS-EFSR) vulnerability against a domain controller. What is the primary objective of forcing the domain controller to authenticate via PetitPotam?

A.To corrupt the NTDS.dit database file on the remote domain controller.
B.To extract the plaintext password of the domain administrator from the LSASS process memory.
C.To coerce the domain controller's machine account to authenticate to an NTLM relay listener targeting AD CS.
D.To bypass Kerberos pre-authentication requirements on user accounts.
AnswerC

PetitPotam abuses MS-EFSRPC to trigger the DC's machine account authentication. Relaying that NTLM authentication to AD CS, which lacks NTLM relay protections by default, lets the attacker obtain a certificate for the DC machine account and then impersonate the domain controller via Kerberos.

Why this answer

PetitPotam (CVE-2021-36942) abuses the MS-EFSRPC interface (EfsRpcOpenFileRaw) to force a Windows host — including a domain controller — to initiate an outbound NTLM authentication to an attacker-controlled UNC path. The attacker's real goal is not to read files or dump memory, but to capture that machine-account NTLM authentication and relay it to a service that accepts NTLM, most classically Active Directory Certificate Services (AD CS) via the ESC8 web enrollment endpoint. Relaying the DC's machine account to AD CS allows the attacker to request a certificate on behalf of the DC, which can then be used for domain takeover (e.g., via PKINIT to obtain a TGT for the DC).

Exam trap

CPENT often tests whether candidates confuse the coercion primitive (PetitPotam forcing authentication) with the end goal (NTLM relay to AD CS for certificate abuse), so many pick memory-dumping or database-corruption answers that describe unrelated post-exploitation techniques.

How to eliminate wrong answers

Option A is wrong because PetitPotam does not write to or corrupt NTDS.dit — it only triggers an authentication attempt via the EFSRPC interface, leaving the AD database untouched. Option B is wrong because LSASS memory dumping (e.g., via Mimikatz sekurlsa::logonpasswords or ProcDump) is a separate credential-theft technique; PetitPotam itself does not read LSASS and Windows does not store the domain administrator's plaintext password there by default. Option D is wrong because Kerberos pre-authentication bypass (AS-REP roasting) targets user accounts configured with 'Do not require Kerberos preauthentication' and is unrelated to the MS-EFSRPC coercion primitive used by PetitPotam.

11
MCQmedium

An operator is conducting an Active Directory penetration test and has obtained domain admin credentials. To maintain persistence, they want to create a backdoor that allows them to authenticate as any user without knowing their password, even if the domain admin password is changed. Which of the following techniques would BEST achieve this?

A.Create a new domain admin account with a known password.
B.Forge a Golden Ticket using the KRBTGT account hash.
C.Set the 'AdminCount' attribute to 1 on a standard user account.
D.Enable the 'Do not require Kerberos preauthentication' flag on a service account.
AnswerB

A Golden Ticket is a forged TGT signed with the KRBTGT account's NTLM hash. With domain admin credentials, the operator can extract the KRBTGT hash and forge tickets that grant access to any resource. This backdoor remains valid even if the domain admin password is changed, as long as the KRBTGT hash is not reset. It provides long-term persistence.

Why this answer

A Golden Ticket is a forged Kerberos TGT that is signed with the KRBTGT account's hash. Once an operator has domain admin access, they can extract the KRBTGT hash and generate Golden Tickets at will. These tickets can be used to impersonate any user, including domain admins, and they remain valid until the KRBTGT password is changed twice (to invalidate all existing tickets).

This makes it a powerful persistence mechanism that survives password changes of individual accounts.

Exam trap

The trap here is confusing persistence mechanisms that rely on account modifications with those that use cryptographic keys, such as the KRBTGT hash, which are not affected by password changes.

12
MCQmedium

An operator has compromised an account with GenericAll permissions over a computer object in Active Directory. How can this permission be leveraged to achieve code execution on the target host?

A.Modify the user's PrimaryGroupID to map to Domain Admins directly.
B.Execute a DCSync attack against the computer object's registry hive.
C.Directly modify the local SAM database of the target computer over RPC without credentials.
D.Configure msDS-AllowedToActOnBehalfOfOtherIdentity to point to a controlled account, enabling Resource-Based Constrained Delegation.
AnswerD

Writing msDS-AllowedToActOnBehalfOfOtherIdentity on the target computer object grants a controlled account resource-based constrained delegation, letting it impersonate any user to that host's service. Combined with GenericAll's write access, the operator obtains a service ticket as a privileged user, then executes code via SMB or WinRM on the target.

Why this answer

GenericAll on a computer object allows full control, including the ability to write to the msDS-AllowedToActOnBehalfOfOtherIdentity attribute. By setting this attribute to a controlled account, an attacker can configure Resource-Based Constrained Delegation (RBCD), enabling that account to impersonate any user to the target computer and achieve code execution via Kerberos delegation. This is a well-known privilege escalation path in Active Directory.

Exam trap

The trap here is confusing GenericAll on a computer with permissions needed for DCSync or direct SAM modification; candidates may overlook RBCD as a viable escalation path.

How to eliminate wrong answers

Option A is wrong because modifying PrimaryGroupID to Domain Admins is not possible with GenericAll on a computer object; PrimaryGroupID is an attribute of user objects, and even if it were, it would not directly grant code execution on the host. Option B is wrong because DCSync requires Replicating Directory Changes permissions, not GenericAll on a computer, and it targets domain controllers, not computer registry hives. Option C is wrong because directly modifying the local SAM database over RPC without credentials is not feasible; it requires administrative access to the target, which is what the attacker is trying to achieve.

13
MCQhard

During an Active Directory penetration test, an operator has compromised a user account and discovered that the account has GenericAll permissions on a computer object. The operator wants to abuse this permission to gain administrative access to the computer. Which technique should the operator use?

A.DCSync
B.AS-REP Roasting
C.Kerberoasting
D.Resource-Based Constrained Delegation (RBCD)
AnswerD

With GenericAll on a computer object, the operator can modify the msDS-AllowedToActOnBehalfOfOtherIdentity attribute to set up Resource-Based Constrained Delegation. This allows the operator to impersonate any user to that computer, achieving administrative access. This is a direct abuse of the permission granted.

Why this answer

The correct answer is Resource-Based Constrained Delegation (RBCD) because GenericAll on a computer object allows the operator to modify the msDS-AllowedToActOnBehalfOfOtherIdentity attribute. By setting this attribute to include a controlled account, the operator can impersonate any user to that computer, gaining administrative access. Other techniques like Kerberoasting or DCSync do not directly abuse this specific permission.

Exam trap

The trap here is assuming that GenericAll on a computer object can be used for DCSync, when in fact DCSync requires domain-level replication permissions.

14
MCQhard

An operator has compromised a domain user account and wants to perform a Kerberoasting attack to extract service account hashes. The operator uses Rubeus with the kerberoast command. Which encryption type should the operator request to maximize the chance of cracking the extracted tickets?

A.RC4 (etype 23)
B.DES (etype 1)
C.AES256 (etype 18)
D.AES128 (etype 17)
AnswerA

RC4 is the weakest encryption type for Kerberos tickets and is easier to crack because it uses the NT hash of the service account as the key. Requesting RC4 tickets increases the likelihood of successful offline cracking, especially if the service account password is weak. This is why attackers often downgrade to RC4 when possible.

Why this answer

The correct answer is RC4 (etype 23) because it is the weakest encryption type for Kerberos tickets and is easier to crack. By requesting RC4 tickets, the operator increases the chances of successfully cracking the service account hash offline, especially if the password is weak. This is a common tactic in Kerberoasting attacks.

Exam trap

The trap here is assuming that any encryption type can be requested and that DES is still viable, when in fact RC4 is the most practical weak option that is widely supported.

15
MCQhard

A pentester needs to exploit an AD CS vulnerability where a low-privileged user can enroll in a template that permits Client Authentication and has the 'ENROLLEE_SUPPLIES_SUBJECT' flag set. Which tool from Certipy can be used to request a certificate and subsequently authenticate as a high-privileged user?

A.certipy req -u user@corp.local -p password -target ca.corp.local -template VulnerableTemplate -upn administrator@corp.local
B.certipy shadow -username user -target dc01
C.certipy ca -backup -ca "corp-CA-1"
D.certipy template -update VulnerableTemplate -enrollee-supplies-subject True
AnswerA

The `-upn` flag injects an arbitrary subjectAltName during enrolment, exploiting the ENROLLEE_SUPPLIES_SUBJECT flag on a Client Authentication template. Certipy's `req` command submits the CSR to the CA, returning a certificate bearing administrator's UPN, which is then usable for Kerberos PKINIT authentication as that high-privileged account.

Why this answer

The Certipy tool's 'req' command is used to request a certificate from a Certificate Authority (CA). By specifying the vulnerable template and the '-upn' flag with a high-privileged user's UPN (e.g., administrator@corp.local), the pentester can request a certificate that allows authentication as that privileged user. This exploits the ESC1 misconfiguration where the template allows the enrollee to supply the subject and permits client authentication.

The other options do not perform this specific action.

Exam trap

The trap is confusing the steps: candidates might think they need to first modify the template (option D) to enable the flag, but the question states the flag is already set, so the immediate action is to request the certificate.

How to eliminate wrong answers

Option B is wrong because 'certipy shadow' is used to add a shadow credential to a user or computer account, not to request a certificate for privilege escalation via a vulnerable template. Option C is wrong because 'certipy ca -backup' is used to back up the CA's private key and certificate, which is a post-exploitation step after compromising the CA, not the initial request. Option D is wrong because 'certipy template -update' is used to modify a template's settings (e.g., to enable ENROLLEE_SUPPLIES_SUBJECT), but the question states the template already has that flag set; the goal is to request a certificate, not modify the template.

16
MCQhard

During an internal penetration test, an operator gains access to a domain-joined Windows workstation and discovers that the current user has local administrator rights on that machine. The operator wants to extract the NTLM hash of the domain administrator who previously logged into this workstation. Which of the following locations is MOST likely to contain this credential material?

A.LSASS process memory
B.Group Policy Preferences XML files
C.SAM registry hive
D.NTDS.dit file
AnswerA

LSASS (Local Security Authority Subsystem Service) caches credential material, including NTLM hashes and Kerberos tickets, for users who have logged on interactively or via RDP. If a domain administrator has logged into the workstation, their credentials may reside in LSASS memory. Tools like Mimikatz or ProcDump can extract these, making it the most likely location for the domain admin hash.

Why this answer

LSASS memory is the primary location where Windows caches credential material for logged-on users, including NTLM hashes and Kerberos tickets. When a domain administrator logs into a workstation, their credentials are cached in LSASS, allowing tools like Mimikatz to extract them if the operator has local admin rights and can access LSASS. This is a common privilege escalation path in Active Directory environments.

Exam trap

The trap here is assuming that domain credentials are stored in the SAM hive or NTDS.dit on a workstation; these are local and domain controller databases, respectively, and do not contain cached domain admin credentials on a member server.

17
MCQmedium

An operator has obtained a valid Kerberos Ticket Granting Ticket (TGT) in the form of a .kirbi file from a compromised domain-joined Linux host. They want to convert this .kirbi file into a .ccache file so that it can be used with Impacket tools on their attack VM. Which of the following tools is specifically designed for this conversion?

A.secretsdump.py
B.getTGT.py
C.ticketConverter.py
D.kekeo.exe
AnswerC

ticketConverter.py is a script from the Impacket suite that converts between .kirbi and .ccache formats. It is the standard tool for this purpose in AD penetration testing, allowing an operator to take a TGT extracted from Windows (often in .kirbi format) and convert it for use with Impacket tools like psexec.py or wmiexec.py that expect a .ccache credential cache.

Why this answer

When an operator has a TGT in .kirbi format and needs to use it with Impacket tools on Linux, they must convert it to .ccache format. ticketConverter.py is specifically built for this conversion, accepting a .kirbi file as input and outputting a .ccache file. This enables the use of tools like psexec.py or wmiexec.py with the -k -no-pass option and the KRB5CCNAME environment variable pointing to the converted cache.

Exam trap

The trap here is confusing the conversion tool with tools that request or dump tickets, such as getTGT.py or secretsdump.py, which serve entirely different purposes.

18
MCQeasy

An ethical hacker has obtained the NTLM password hash of a local administrator account on a Windows workstation and wants to perform lateral movement using Pass-the-Hash (PtH). Which tool allows executing a command or spawning an interactive prompt on a remote system using only the NTLM hash without knowing the plaintext password?

A.Windows Remote Desktop Connection (mstsc.exe)
B.Standard Windows net use command
C.WinRM standard client via browser
D.psexec.py from the Impacket toolkit
AnswerD

Pass-the-Hash exploits NTLM's challenge-response authentication, where the hash itself serves as the credential, so no plaintext is needed. Impacket's psexec.py injects that hash via SMB to create a service on the remote host, spawning a shell. This directly satisfies the stem's constraint: lateral movement using only the captured local administrator NTLM hash.

Why this answer

Pass-the-Hash relies on injecting or using the NTLM hash directly in place of the user's password during authentication. Impacket's psexec.py (or crackmapexec / netexec) natively supports NTLM hash authentication.

19
MCQmedium

A pentester successfully compromises a machine and obtains a valid Kerberos Ticket Granting Ticket (TGT) file (.ccache). To use this ticket for lateral movement on Linux using Impacket, which environment variable must be exported?

A.KRB_TICKET_PATH
B.KERBEROS_CACHE
C.KRB5CCNAME
D.AD_TICKET_FILE
AnswerC

KRB5CCNAME tells Kerberos client libraries which credential cache file to use. Exporting it to point at the stolen .ccache lets Impacket tools such as psexec.py authenticate with the TGT for lateral movement, satisfying the stem's requirement.

Why this answer

KRB5CCNAME is the standard MIT Kerberos environment variable that tells Kerberos-aware tools where to find the credential cache (ccache) file. Exporting it to point at the stolen .ccache lets Impacket tools like psexec.py, wmiexec.py, and smbclient.py authenticate using the ticket. This is the canonical pass-the-ticket workflow on Linux.

Exam trap

CPENT often tests whether candidates know the exact MIT Kerberos environment variable name, so memorize KRB5CCNAME rather than plausible-sounding alternatives like KERBEROS_CACHE.

How to eliminate wrong answers

Option A is wrong because KRB_TICKET_PATH is not a recognized Kerberos environment variable. Option B is wrong because KERBEROS_CACHE is not a standard variable — the real one is KRB5CCNAME. Option D is wrong because AD_TICKET_FILE is fabricated and has no meaning in MIT Kerberos or Impacket.

20
MCQhard

During an Active Directory Certificate Services (AD CS) assessment, a tester discovers that the 'ESC1' vulnerability is present. What specific misconfiguration defines ESC1 on a certificate template?

A.The template grants WriteDACL permissions to authenticated users over the Certificate Authority object.
B.The template publishes certificates to Active Directory user objects automatically.
C.The template has Manager Approval enabled and requires enterprise admin signatures.
D.The template allows enrollees to supply alternate subject names (SAN) and authorizes low-privileged users to enroll with client authentication EKUs.
AnswerD

ESC1 requires a template flag permitting the requester to specify subjectAltName plus enrolment rights for low-privileged users, combined with a client authentication EKU. That combination lets any enrolled user request a certificate impersonating a domain administrator.

Why this answer

ESC1 is defined by a certificate template that permits the enrollee to specify a Subject Alternative Name (SAN) and is enrollable by low-privileged users, while also including a client authentication EKU (e.g., Client Authentication, Smart Card Logon). This lets an attacker request a certificate with an arbitrary SAN (e.g., a Domain Admin's UPN) and authenticate as that user via PKINIT.

Exam trap

CPENT often tests the exact combination of template flags that define ESC1 — candidates pick options about CA-level permissions (ESC7) or approval settings, missing that ESC1 is specifically about enrollee-supplied SAN plus client-auth EKU plus low-priv enrollment.

How to eliminate wrong answers

Option A is wrong because WriteDACL over the CA object relates to ESC7 (CA-level permission abuse), not ESC1 template misconfiguration. Option B is wrong because auto-enrollment/publishing certificates to AD user objects is a normal template setting and does not by itself define ESC1. Option C is wrong because Manager Approval and enterprise admin signature requirements are hardening controls that would actually prevent ESC1-style abuse, not define it.

21
MCQeasy

When analyzing BloodHound output, what visual edge or relationship indicates that user 'A' can modify the membership or attributes of group 'B'?

A.AllowedToDelegate
B.ReadLAPSPassword
C.AddMember
D.CoerceTo
AnswerC

AddMember edges represent the specific access right to add principals to a group, which directly satisfies the stem's requirement for modifying group membership. BloodHound draws this edge when a user holds WriteMembers or GenericWrite over the target group, enabling privilege escalation through group population.

Why this answer

In BloodHound, the 'AddMember' edge indicates that a user or group has the ability to add members to a group. This is a direct privilege escalation path because adding a user to a high-privileged group (e.g., Domain Admins) grants that user the group's privileges. Therefore, the visual edge that indicates user 'A' can modify the membership of group 'B' is 'AddMember'.

Exam trap

The trap is confusing 'AddMember' with other edges like 'GenericAll' or 'WriteDacl', which also allow modification but are broader; the question specifically asks for the edge that indicates ability to modify membership, which is 'AddMember'.

How to eliminate wrong answers

Option A is wrong because 'AllowedToDelegate' indicates that a user or computer can delegate credentials to another service, which is related to Kerberos delegation, not group membership modification. Option B is wrong because 'ReadLAPSPassword' indicates the ability to read the local administrator password from LAPS, which is a different privilege. Option D is wrong because 'CoerceTo' is not a standard BloodHound edge; it might refer to coercion techniques, but it does not represent group membership modification.

22
Multi-Selecteasy

Which TWO of the following Active Directory enumeration methods or tools can be used by an unprivileged domain user to identify accounts configured with 'Do not require Kerberos preauthentication' (AS-REP roasting candidates)? (Choose TWO)

Select 2 answers
A.Windows Disk Cleanup utility (cleanmgr.exe)
B.Mimikatz (lsadump::dcsync)
C.Rubeus (rubeus.exe asreproast)
D.Local Security Policy snap-in (secpol.msc)
E.PowerView (Get-DomainUser -PreauthNotRequired)
AnswersC, E

Rubeus with the `asreproast` action queries LDAP for user objects whose userAccountControl attribute has the DONT_REQ_PREAUTH bit (0x400000) set, then requests AS-REPs for them. It runs under the invoking unprivileged domain user's own token, satisfying the stem's no-elevated-rights constraint.

Why this answer

Option C is correct because Rubeus is a dedicated Kerberos attack toolkit, and its `asreproast` command specifically enumerates and extracts AS-REP hashes from accounts whose UserAccountControl flag does not have Kerberos preauthentication required (UF_DONT_REQUIRE_PREAUTH, 0x400000), which an unprivileged domain user can perform. Option E is correct because PowerView's `Get-DomainUser -PreauthNotRequired` queries Active Directory via LDAP for user objects with the DONT_REQUIRE_PREAUTH flag set, directly identifying AS-REP roasting candidates without elevated privileges. Option A is wrong because cleanmgr.exe is a disk cleanup utility with no AD enumeration capability.

Option B is wrong because Mimikatz's `lsadump::dcsync` requires DCSync rights (typically Domain Admin or Replicating Directory Changes permissions), so it is not usable by an unprivileged domain user. Option D is wrong because secpol.msc edits local security policy on a single host and does not enumerate domain accounts.

23
MCQmedium

During a Red Team assessment against an enterprise network, an operator wants to execute a Silver Ticket attack against a specific service (e.g., CIFS) on a target server. What is a key operational advantage of a Silver Ticket compared to a Golden Ticket?

A.It can only be detected by physically inspecting the NTDS.dit file on the Domain Controller
B.It does not require interaction with the Domain Controller to generate and does not alert the KDC for a TGT request
C.It grants full Domain Administrator privileges across all domain controllers
D.It automatically updates the KRBTGT password to maintain persistence
AnswerB

A Silver Ticket is forged with the service account's NTLM hash and encrypted directly with that key, so the KDC is never contacted. This satisfies the scenario's advantage: no TGT request reaches the Domain Controller, avoiding that associated detection.

Why this answer

A Silver Ticket is forged for a specific service using the NTLM hash of that specific service account (or computer account), meaning it does not require interaction with the Domain Controller's KDC for creation, and it does not generate a TGT request that might alert domain-level monitoring.

24
MCQhard

An attacker has retrieved the KRBTGT account hash and wants to forge a Golden Ticket. Which tool from the Impacket suite is specifically designed to perform this forgery offline and inject the ticket?

A.getTGT.py
B.goldenPac.py
C.ticketer.py
D.raiseChild.py
AnswerC

ticketer.py forges Kerberos tickets offline from a supplied key or hash, including Golden Tickets built from the KRBTGT hash, then writes the ticket to a ccache file for injection. It requires no live domain controller interaction.

Why this answer

ticketer.py from Impacket forges Kerberos tickets offline, including Golden Tickets (using the KRBTGT hash) and Silver Tickets (using a service account hash). It accepts the domain SID, krbtgt NTLM hash, and target username to produce a valid .ccache that can be injected via KRB5CCNAME. This is the standard tool for offline Golden Ticket creation.

Exam trap

CPENT often tests whether candidates distinguish tools that request tickets with credentials (getTGT.py) from tools that forge tickets offline with hashes (ticketer.py), so match 'forge Golden Ticket offline' to ticketer.py.

How to eliminate wrong answers

Option A is wrong because getTGT.py requests a TGT from the KDC using valid credentials — it does not forge tickets offline from a hash. Option B is wrong because goldenPac.py is a wrapper that automates Golden Ticket creation and PsExec-style execution but relies on ticketer.py internally; it is not the core forgery tool. Option D is wrong because raiseChild.py is used to escalate from a child domain to a parent domain using a Golden Ticket, not to forge the ticket itself.

25
MCQhard

A pentester wants to execute a Shadow Credentials attack (Key Credential Link abuse) against a high-value user account in Active Directory. What permission on the target user object is required to successfully perform this attack?

A.ReadLAPSPassword extended right
B.WriteProperty, GenericAll, or GenericWrite over the msDS-KeyCredentialLink attribute / target object
C.DS-Replication-Get-Changes-All domain right
D.SeEnableDelegationPrivilege on the domain controller
AnswerB

Shadow Credentials abuse requires the ability to write the msDS-KeyCredentialLink attribute on the target account. WriteProperty scoped to that attribute, GenericAll, or GenericWrite all grant this, letting the attacker inject a rogue key credential and later authenticate via PKINIT as the victim.

Why this answer

Shadow Credentials abuse requires write access to the target object's msDS-KeyCredentialLink attribute. Permissions such as GenericAll, GenericWrite, or the specific WriteProperty right over that attribute allow an attacker to inject a Key Credential, which can then be used with PKINIT to obtain a TGT for the target account without knowing its password.

Exam trap

CPENT often tests the specific attribute and permission for Shadow Credentials — candidates confuse it with DCSync rights or LAPS read rights, missing that it requires write access to msDS-KeyCredentialLink.

How to eliminate wrong answers

Option A is wrong because ReadLAPSPassword is a read-only extended right for LAPS passwords and does not permit writing to msDS-KeyCredentialLink. Option C is wrong because DS-Replication-Get-Changes-All enables DCSync, a different attack that replicates secrets rather than injecting key credentials. Option D is wrong because SeEnableDelegationPrivilege allows configuring Kerberos delegation, which is unrelated to the Key Credential Link attribute abuse used in Shadow Credentials.

26
Multi-Selectmedium

Which TWO Active Directory mechanisms or configurations are commonly targeted during lateral movement to bypass traditional perimeter security and leverage built-in domain trust relationships?

Select 2 answers
A.Local Administrator Password Solution (LAPS)
B.Kerberos Constrained and Unconstrained Delegation
C.NTLMv2 hash signing enforcement
D.Account lockout threshold policies
E.External and Forest Trust relationships (with or without SID filtering)
AnswersB, E

Delegation lets a service impersonate users to downstream resources. Unconstrained delegation caches TGTs in memory, harvestable via credential theft, while constrained delegation can be abused through protocol transition to reach services the attacker otherwise could not, enabling lateral movement across the domain.

Why this answer

Option B is correct because Kerberos delegation — both unconstrained (where a service can impersonate users to any service) and constrained (where it is limited to specified services) — is a classic lateral-movement and privilege-escalation target: an attacker who compromises a delegation-enabled service account can obtain forwardable TGTs or service tickets and impersonate high-privileged users across the domain without touching perimeter defenses. Option E is correct because external and forest trust relationships extend authentication across domain/forest boundaries, and when SID filtering is disabled or trusts are misconfigured, attackers can abuse SIDHistory injection or cross-trust Kerberos referrals to move laterally into trusted domains while appearing as legitimate internal authentication traffic. Option A (LAPS) is not a lateral-movement bypass mechanism; it is a defensive control that randomizes local administrator passwords to prevent pass-the-hash reuse.

Option C (NTLMv2 hash signing enforcement) is a hardening measure that restricts NTLM relay/credential reuse rather than a trust-abuse vector. Option D (account lockout threshold policies) is a defensive policy that limits brute-force attempts and does not itself enable lateral movement or trust abuse.

Exam trap

CPENT often tests whether candidates can separate offensive lateral-movement mechanisms (delegation, trusts) from defensive hardening controls (LAPS, lockout policies, signing), so always ask 'does this help the attacker move, or stop them?'

27
Multi-Selecthard

Which THREE methods or attack primitives can be used to achieve domain escalation when an attacker has compromised an account with 'GenericAll' permissions over a Group Policy Object (GPO)?

Select 3 answers
A.Adding a startup script or service configuration within the GPO file share path in SYSVOL
B.Creating restricted local user accounts or modifying local administrator groups across target OUs via GPO settings
C.Modifying the KRBTGT account password directly through Group Policy settings
D.Injecting immediate scheduled tasks into the GPO via Group Policy Preferences (GPP)
E.Directly modifying the NTDS.dit database via unauthenticated LDAP write operations
AnswersA, B, D

Writing a startup script or service configuration into the GPO's SYSVOL share lets the compromised account push code execution to every machine or user the GPO applies to, including domain controllers, converting GenericAll over the GPO into domain-wide escalation.

Why this answer

With GenericAll over a GPO, an attacker can edit the GPO's contents and have them applied to all linked OUs, computers, or users. Option A is correct because writing a startup script or service configuration into the GPO's SYSVOL path (\\<domain>\SYSVOL\<domain>\Policies\{GUID}\Machine\Scripts\Startup or the GptTmpl.inf service section) causes the script/service to execute as SYSTEM on every affected machine at boot. Option B is correct because GPO security settings (e.g., Restricted Groups or Group Policy Preferences local users/groups) can add a controlled account to the local Administrators group or create local users across all machines in the linked OU, yielding broad local admin and lateral movement.

Option D is correct because Group Policy Preferences support Immediate Scheduled Tasks (ScheduledTasks.xml in SYSVOL), which execute on the next policy refresh as SYSTEM, giving code execution on target hosts. Option C is wrong because the KRBTGT password is stored in AD (NTDS.dit) and cannot be changed through GPO settings; GPOs do not manage domain account credentials. Option E is wrong because NTDS.dit is not writable via unauthenticated LDAP, and LDAP writes require authenticated, authorized access to AD objects, not merely GPO GenericAll.

Exam trap

CPENT often tests whether candidates know the actual boundaries of GPO abuse, luring them toward impossible actions like resetting KRBTGT or editing NTDS.dit via LDAP, which are not GPO-driven.

28
Multi-Selecthard

During an Active Directory security review, an assessor examines Kerberos delegation configurations. Which THREE delegation misconfigurations or vulnerabilities represent high-risk attack vectors if exploited? (Choose THREE)

Select 3 answers
A.Standard Kerberos pre-authentication enabled on all standard user accounts with strong passwords
B.Unconstrained Delegation on a computer account, allowing any user's TGT to be cached when they authenticate to the host
C.Resource-Based Constrained Delegation (RBCD) where a compromised machine account has write access to the msDS-AllowedToActOnBehalfOfOtherIdentity attribute of a higher-privileged target
D.Constrained Delegation with Protocol Transition (S4U2Self/S4U2Proxy) enabled on a service account without proper restrictions
E.Automatic workstation registration limits set to allow zero new domain-joined machines
AnswersB, C, D

Unconstrained Delegation lets a host cache any authenticating user's TGT in memory. An attacker who compromises that computer can extract those tickets and replay them, impersonating privileged users across the domain — far broader than constrained variants, which limit impersonation to specified services.

Why this answer

Option B is correct because Unconstrained Delegation (TrustedForDelegation) causes the host to cache the TGT of every authenticating user in LSASS memory; an attacker who compromises that host can extract those TGTs (e.g., via Mimikatz) and impersonate privileged users across the domain. Option C is correct because RBCD abuse occurs when an attacker controls a principal with write access to a target's msDS-AllowedToActOnBehalfOfOtherIdentity attribute, letting them configure the target to trust their controlled account and then obtain service tickets via S4U2Self/S4U2Proxy to impersonate any user to that target. Option D is correct because Constrained Delegation with Protocol Transition allows a service to obtain a forwardable ticket for a user without that user's credentials (S4U2Self) and then use S4U2Proxy to access downstream services, so a compromised service account can pivot to any resource listed in msDS-AllowedToDelegateTo.

Option A is not a vulnerability—Kerberos pre-authentication with strong passwords is a hardening best practice that resists AS-REP roasting. Option E is unrelated to delegation; it concerns machine account quota (ms-DS-MachineAccountQuota) and does not by itself constitute a Kerberos delegation attack vector.

29
Multi-Selecthard

Which THREE tactics or actions are effective in defending against or detecting Golden Ticket attacks in an enterprise Active Directory environment?

Select 3 answers
A.Enabling unconstrained delegation on all workstation computer objects
B.Enforcing Tiered Administration models to protect domain controller access
C.Disabling LDAP channel binding on all domain controllers
D.Monitoring Kerberos Ticket Granting Service (TGS) requests with abnormal lifetime values (Event ID 4769)
E.Performing a double-rotation of the KRBTGT account password
AnswersB, D, E

Tiered administration limits where credential material can be exposed, preventing attackers from acquiring KRBTGT hashes.

Why this answer

Option B is correct because enforcing Tiered Administration models restricts who can log on to and administer Tier 0 assets such as domain controllers, limiting the credential exposure that enables an attacker to obtain the KRBTGT hash needed to forge a Golden Ticket. Option D is correct because Golden Tickets are forged TGTs, and their abuse surfaces in Kerberos service ticket activity; monitoring TGS requests (Event ID 4769) for anomalous ticket lifetimes, encryption types, or account patterns helps detect forged tickets that bypass normal TGT issuance. Option E is correct because the KRBTGT account's password hash signs all TGTs, so a double-rotation (resetting the password twice, with replication in between) invalidates existing Golden Tickets and prevents their continued use.

Option A is wrong because enabling unconstrained delegation on workstations expands attack surface and lets compromised hosts impersonate users to services, which aids attackers rather than defending against Golden Tickets. Option C is wrong because disabling LDAP channel binding weakens protection against relay and credential-theft attacks on domain controllers, making the environment less secure, not more.

Exam trap

CPENT often tests whether candidates can distinguish between offensive techniques (e.g., unconstrained delegation) and defensive measures (e.g., Tiered Administration, KRBTGT rotation) in the context of Golden Ticket attacks.

30
MCQmedium

An operator has gained administrative access to a subordinate domain in a multi-domain Active Directory forest and wishes to escalate privileges to Enterprise Admin across the entire forest. What object or group must be compromised to achieve forest-wide control?

A.The Enterprise Admins group in the forest root domain
B.The Cert Publishers group on any workstation
C.The Domain Admins group of the subordinate domain
D.The Account Operators group in the builtin container
AnswerA

The Enterprise Admins group in the forest root domain holds forest-wide administrative rights, so compromising it grants control over every domain in the forest. Subordinate-domain Domain Admin rights alone do not confer Enterprise Admin privileges.

Why this answer

The Enterprise Admins group resides in the forest root domain and grants full administrative control over all domains in the forest. Compromising this group (or adding an account to it) is the definitive way to achieve forest-wide privilege escalation. In a multi-domain forest, even Domain Admin in a child domain does not automatically confer Enterprise Admin rights, so the attacker must target the forest root's Enterprise Admins group.

Exam trap

The trap is assuming that Domain Admin in a child domain equates to Enterprise Admin; candidates must remember that forest-wide control requires the Enterprise Admins group in the forest root domain.

How to eliminate wrong answers

Option B is wrong because Cert Publishers is a group that manages certificate publication and has no forest-wide administrative privileges. Option C is wrong because Domain Admins in a subordinate domain only grants full control over that specific domain, not the entire forest. Option D is wrong because Account Operators is a built-in group with limited account management rights in a single domain and cannot escalate to forest-wide control.

31
Multi-Selecthard

When analyzing a compromised Active Directory environment using BloodHound, which THREE common node properties or paths typically signify a high-value target or an immediate path to Domain Admin?

Select 3 answers
A.Principals with GenericAll or WriteDACL over the Domain object
B.Standard users with 'MemberOf' a departmental security group
C.Standard domain user accounts with default password policies
D.Members of the Domain Admins group
E.Computers configured with Unconstrained Delegation
AnswersA, D, E

GenericAll or WriteDACL over the Domain object grants full control or the ability to modify the domain's ACLs, letting an attacker grant themselves DCSync rights or escalate directly to Domain Admin, marking it as an immediate high-value path in BloodHound.

Why this answer

Option A is correct because GenericAll or WriteDACL rights over the Domain object allow an attacker to modify the domain's ACLs or grant themselves DCSync rights, effectively leading to full domain compromise. Option D is correct because members of Domain Admins inherently possess the highest privileges in the domain, making them direct high-value targets and a clear path to Domain Admin. Option E is correct because computers configured with Unconstrained Delegation cache TGTs of any user who authenticates to them, so compromising such a host can yield Domain Admin credentials when a privileged account connects.

Option B is not correct because membership in a departmental security group typically grants only limited, scoped access and does not by itself indicate a high-value target or Domain Admin path. Option C is not correct because default password policies on standard user accounts are a general hygiene weakness, not a specific BloodHound node property or path that directly signifies Domain Admin escalation.

Exam trap

CPENT often tests the confusion between generic group membership and genuinely dangerous ACL/delegation edges — candidates pick any 'admin-looking' group instead of recognizing the specific BloodHound edges (GenericAll, WriteDACL, Unconstrained Delegation) that create real attack paths.

32
MCQhard

An auditor is reviewing Active Directory Certificate Services and identifies ESC8. What exact AD CS endpoint is exploited during an ESC8 attack vector?

A.The Kerberos Key Distribution Center service on port 88
B.The HTTP-based Web Enrollment (certsrv/) or Certificate Enrollment Web Service endpoints
C.The LDAP signing and LDAP channel binding endpoints on port 636
D.The RPC-based DCOM interface on port 135
AnswerB

ESC8 abuses NTLM relay against AD CS HTTP enrolment interfaces — the certsrv/ web enrolment pages or the Certificate Enrollment Web Service — letting an attacker request a certificate as the relayed machine or user.

Why this answer

ESC8 exploits AD CS HTTP enrollment endpoints — specifically the Web Enrollment interface (certsrv/) and the Certificate Enrollment Web Service (CES) — which are vulnerable to NTLM relay when they accept HTTP-based authentication without requiring HTTPS or Extended Protection for Authentication (EPA). An attacker relays a coerced machine account authentication to these endpoints to obtain a certificate for that machine, enabling domain privilege escalation.

Exam trap

CPENT often tests the specific endpoint exploited by ESC8 — candidates confuse it with Kerberos (port 88) or LDAP (636) endpoints, but ESC8 is strictly about HTTP-based AD CS enrollment services.

How to eliminate wrong answers

Option A is wrong because the KDC on port 88 handles Kerberos ticket exchange (AS-REQ/TGS-REQ), which is unrelated to certificate enrollment and is the target of attacks like Kerberoasting or AS-REP Roasting, not ESC8. Option C is wrong because LDAP signing and channel binding on port 636 address LDAP relay protections, not AD CS HTTP enrollment — they relate to ESC8 mitigations only tangentially via EPA concepts. Option D is wrong because the RPC/DCOM interface on port 135 is used for remote management and is not the AD CS enrollment endpoint exploited by ESC8.

33
MCQhard

An attacker has identified an Active Directory Certificate Services (AD CS) template configured with the 'Enrollee Supplies Subject' flag enabled (EDITF_ATTRIBUTESUBJECTALTNAME2 is enabled on the CA), and the template permissions allow low-privileged domain users to enroll. Furthermore, the template allows client authentication. How can this misconfiguration (ESC1) be exploited?

A.Request a certificate specifying an arbitrary SAN (e.g., Domain Admin) and use it for PKINIT authentication
B.Execute a DCSync attack directly against the Certification Authority web enrollment endpoint
C.Force the CA machine account to authenticate to an attacker-controlled SMB share using PetitPotam
D.Perform a Silver Ticket attack by decrypting the CA database with a captured machine hash
AnswerA

With EDITF_ATTRIBUTESUBJECTALTNAME2 enabled, the requester can embed an arbitrary SAN in the CSR, and the CA copies it into the issued certificate. Because the template permits client authentication, the resulting certificate authenticates via PKINIT as the impersonated account, such as Domain Admin.

Why this answer

ESC1 is the AD CS misconfiguration where a template allows the enrollee to supply the subject (including SAN) and permits client authentication, while low-privileged users can enroll. An attacker requests a certificate with an arbitrary SAN such as the Domain Admin's UPN, then uses it for PKINIT (Kerberos certificate logon) to obtain a TGT as that user — effectively impersonating Domain Admin without knowing their password.

Exam trap

CPENT often tests whether candidates can distinguish ESC1 (SAN impersonation via PKINIT) from ESC8 (NTLM relay to AD CS web enrollment) and other AD CS attacks — picking PetitPotam or DCSync instead of the SAN/PKINIT path is the classic mistake.

How to eliminate wrong answers

Option B is wrong because DCSync is a replication-rights abuse (DS-Replication-Get-Changes) against a domain controller, not an attack against a CA web enrollment endpoint, and it does not exploit ESC1. Option C is wrong because PetitPotam coerces machine-account authentication (NTLM relay to AD CS for ESC8), which is a different AD CS attack path, not the ESC1 SAN-impersonation technique. Option D is wrong because a Silver Ticket forges a service ticket using a compromised service/machine account hash; it does not involve decrypting the CA database, and it is unrelated to ESC1's certificate-based impersonation.

34
Multi-Selecthard

Which THREE techniques or remediation steps are recommended to secure Active Directory Certificate Services (AD CS) against certificate-based abuse vectors like ESC1 through ESC8?

Select 3 answers
A.Disable HTTP-based web enrollment or enforce HTTPS with Extended Protection for Authentication (EPA) enabled.
B.Regularly audit AD CS infrastructure and templates using tools like Certipy or BloodHound.
C.Disable Kerberos pre-authentication across all domain controller computer accounts.
D.Enforce unconstrained delegation on all certificate authority servers.
E.Remove the 'ENROLLEE_SUPPLIES_SUBJECT' flag from certificate templates unless strictly required.
AnswersA, B, E

Disabling HTTP web enrolment or enforcing HTTPS with Extended Protection for Authentication blocks NTLM relay to the CA web interface, directly mitigating ESC8. EPA binds the authentication exchange to the TLS channel, so a relayed credential cannot be reused against the enrolment endpoint.

Why this answer

Option A is correct because ESC8 abuses the HTTP-based web enrollment endpoints (certsrv) via NTLM relay, so disabling HTTP enrollment or enforcing HTTPS with Extended Protection for Authentication (EPA) and disabling NTLM on those endpoints blocks that relay vector. Option B is correct because continuous auditing of AD CS templates, CAs, and ACLs with tools like Certipy or BloodHound (e.g., Certipy's 'find' and 'template' checks) surfaces misconfigurations such as ESC1-ESC8 before attackers exploit them. Option E is correct because removing the ENROLLEE_SUPPLIES_SUBJECT flag prevents low-privileged enrollees from specifying an arbitrary subject/SAN (e.g., a domain admin UPN), which is the core of ESC1 template abuse.

Option C is wrong because disabling Kerberos pre-authentication on domain controller computer accounts would weaken authentication and enable AS-REP roasting, not secure AD CS. Option D is wrong because enforcing unconstrained delegation on CA servers increases exposure to credential theft and relay/impersonation attacks rather than mitigating certificate abuse.

Exam trap

The trap is that candidates pick options that sound like 'hardening' (disabling pre-auth, enabling delegation) but actually weaken security, confusing attack-surface reduction with attack-surface expansion.

35
MCQeasy

An internal penetration tester is performing reconnaissance using BloodHound to map out attack paths in an Active Directory domain. Which automated data collection tool is officially supported and widely utilized to gather ACLs, session information, and object relationships for BloodHound ingestion?

A.BloodHound-Collector-GUI
B.AD-Collector-Pro
C.Responder
D.SharpHound
AnswerD

SharpHound is the official BloodHound collector, gathering ACLs, sessions and object relationships via LDAP and SMB into JSON for ingestion. It satisfies the reconnaissance requirement by automating collection that would otherwise need manual enumeration, mapping attack paths across the Active Directory domain.

Why this answer

SharpHound is the official data collector for BloodHound, written in C#, designed to query Active Directory via LDAP and WinAPI to gather telemetry for mapping attack paths.

36
MCQhard

You have compromised a domain user account and discovered that the user has 'WriteDACL' permission on a sensitive Organizational Unit (OU). You want to escalate privileges by modifying the OU's ACL to grant yourself full control. Which built-in Windows command-line utility can you use to modify the ACL of the OU?

A.dsacls
B.set-acl
C.icacls
D.cacls
AnswerA

dsacls is a built-in Windows command-line tool that allows viewing and modifying ACLs on Active Directory objects, including OUs. With WriteDACL permission, you can use dsacls to grant yourself Full Control on the OU, then further compromise objects within it. It is part of the AD DS tools and is available on domain controllers and administrative workstations.

Why this answer

dsacls is the correct tool because it is specifically designed to manage ACLs on Active Directory objects, including OUs. With WriteDACL permission, you can use dsacls to grant yourself Full Control on the OU, enabling further privilege escalation. The other tools either target file system ACLs or are not command-line utilities.

Exam trap

The trap here is assuming that icacls or cacls can be used on AD objects, when they only work on file system objects.

37
MCQmedium

During an internal penetration test, you compromise a domain-joined Windows 10 workstation and obtain a SYSTEM-level shell. You extract the NTLM hash of a domain user from LSASS but cannot crack it. Which technique allows you to authenticate to a remote server as that domain user without knowing the plaintext password?

A.Overpass-the-Hash
B.Pass-the-Ticket
C.Pass-the-Hash
D.Kerberoasting
AnswerC

Pass-the-Hash uses the NTLM hash directly in the authentication process, bypassing the need for the plaintext password. In this scenario, you have extracted the hash from LSASS, and since the domain user has an active logon session, the hash is valid for NTLM authentication. Tools like Mimikatz or Impacket's psexec.py can perform PtH to access remote resources.

Why this answer

Pass-the-Hash is the correct technique because it allows authentication using the NTLM hash directly, without needing the plaintext password. This is particularly useful when you have extracted a hash from LSASS but cannot crack it. The other options either require different credential material (Kerberos tickets) or are more complex and less direct.

Exam trap

The trap here is confusing Pass-the-Hash with Overpass-the-Hash, which converts the hash to a Kerberos ticket and may not work in all scenarios.

38
MCQeasy

Which Active Directory right or permission allows a security principal to perform a DCSync attack, thereby replicating domain secrets?

A.GenericAll over thekrbtgt account
B.DS-Replication-Get-Changes and DS-Replication-Get-Changes-All
C.FullControl over the Domain Controllers OU
D.WriteDACL on the builtin Administrators group
AnswerB

DS-Replication-Get-Changes and DS-Replication-Get-Changes-All extended rights permit a principal to invoke directory replication, letting it pull password hashes and other secrets directly from a domain controller without touching its filesystem. Granting both satisfies the replication requirement that makes DCSync possible, unlike ordinary read or logon rights.

Why this answer

DCSync abuses the Directory Replication Service (DRS) Remote Protocol by impersonating a domain controller and requesting replication of directory changes. The specific rights required are the extended rights DS-Replication-Get-Changes and DS-Replication-Get-Changes-All (GUIDs 1131f6aa-9c07-11d1-f79f-00c04fc2dcd2 and 1131f6ad-9c07-11d1-f79f-00c04fc2dcd2), typically granted to Domain Admins, Enterprise Admins, and the DC computer accounts themselves.

Exam trap

CPENT often tests the confusion between generic AD permissions (GenericAll, WriteDACL) and the specific extended replication rights — candidates assume any high privilege enables DCSync, but only the DS-Replication-Get-Changes* rights do.

How to eliminate wrong answers

Option A is wrong because GenericAll over the krbtgt account allows password reset or attribute modification of that account but does not grant the replication extended rights needed to pull secrets via DRS. Option C is wrong because FullControl over the Domain Controllers OU is an organisational-unit permission that does not itself confer the DS-Replication extended rights on the domain naming context. Option D is wrong because WriteDACL on the builtin Administrators group only lets you modify that group's ACL — it does not grant the replication rights required to invoke DRS GetNCChanges.

39
MCQmedium

During a penetration test, you have compromised a workstation and obtained the NTLM hash of a domain user who is logged in. You want to move laterally to a server where this user has administrative rights. Which technique would allow you to authenticate to the server without knowing the plaintext password?

A.Pass-the-Hash (PtH) using the NTLM hash.
B.Pass-the-Ticket (PtT) using the user's Kerberos TGT.
C.Overpass-the-Hash to convert the NTLM hash into a Kerberos ticket.
D.Kerberoasting to obtain a service ticket for the server.
AnswerA

Pass-the-Hash allows an attacker to authenticate using the NTLM hash directly, without needing the plaintext password. This works because NTLM authentication can use the hash as proof of identity. Tools like Mimikatz or Impacket's psexec can leverage the hash to access remote systems where the user has administrative privileges.

Why this answer

Pass-the-Hash is the most direct method to authenticate using an NTLM hash without the plaintext password. It exploits the NTLM challenge-response protocol, allowing the hash to be used as a credential. This technique is widely used in lateral movement when administrative rights are present on the target.

Exam trap

The trap here is confusing Pass-the-Hash with Overpass-the-Hash, which converts the hash to a Kerberos ticket and requires additional steps.

40
MCQmedium

A penetration tester has gained access to a workstation and wants to move laterally to a server using a Golden Ticket. The tester has the KRBTGT hash and the domain SID. Which tool from the Impacket suite should be used to forge and inject the Golden Ticket?

A.psexec.py
B.ticketer.py
C.getTGT.py
D.secretsdump.py
AnswerB

ticketer.py is specifically designed to create Golden and Silver tickets. It takes the KRBTGT hash and domain SID as input to forge a TGT that can be used for authentication. This tool allows the tester to generate a ticket file that can be injected into the session, enabling lateral movement with domain admin privileges.

Why this answer

The correct answer is ticketer.py because it is the Impacket tool specifically designed to forge Golden and Silver tickets. It takes the KRBTGT hash and domain SID to create a TGT that can be used for authentication, enabling lateral movement. Other tools like getTGT.py only request legitimate tickets, while secretsdump.py extracts secrets but does not forge tickets.

Exam trap

The trap here is confusing tools that obtain tickets with those that forge them; getTGT.py requests legitimate tickets, while ticketer.py creates forged ones.

41
MCQmedium

An operator captures a valid Ticket Granting Ticket (TGT) for a domain user from memory and wants to inject it into their current session to access network resources without re-authenticating. Which tool and command syntax should be used to import this ticket into the local LSASS session on Windows?

A.Rubeus: golden /ticket:ticket.kirbi
B.PowerView: Invoke-TicketInjection -Path ticket.kirbi
C.Mimikatz: kerberos::ptt ticket.kirbi
D.Impacket: ticketer.py -nthash ...
AnswerC

Mimikatz's `kerberos::ptt` passes the ticket into the current logon session by injecting it into LSASS, satisfying the requirement to import a captured TGT without re-authentication. The `.kirbi` file holds the Kerberos ticket; `ptt` (pass-the-ticket) loads it so the session presents it for network resource access.

Why this answer

Pass-the-Ticket involves injecting exported ticket files (such as .kirbi or .ccache format) into memory. Mimikatz uses the 'kerberos::ptt' command to inject a ticket into the current Windows logon session.

42
Multi-Selectmedium

Which TWO native Windows tools or Sysinternals utilities can be used by an operator during post-exploitation to dump credentials from the LSASS process memory?

Select 2 answers
A.tasklist.exe /v
B.Sysinternals ProcDump.exe
C.gpresult.exe /h report.html
D.rundll32.exe comsvcs.dll, MiniDump
E.netstat.exe -ano
AnswersB, D

ProcDump.exe captures a full memory dump of a running process, and targeting lsass.exe yields credential material such as NTLM hashes and Kerberos tickets for offline extraction. It satisfies the scenario's requirement for a Sysinternals utility usable post-exploitation, since it runs natively on Windows without installing additional agents.

Why this answer

Sysinternals ProcDump.exe (option B) is correct because it can create a memory dump of a running process, including lsass.exe, using syntax such as procdump -ma lsass.exe lsass.dmp, which can then be parsed offline with Mimikatz to extract credentials. Option D is also correct because rundll32.exe can invoke the native comsvcs.dll MiniDump export, e.g. rundll32.exe C:\Windows\System32\comsvcs.dll, MiniDump <LSASS_PID> C:\lsass.dmp full, producing an LSASS memory dump without external tooling. Option A (tasklist.exe /v) only lists running processes with verbose details and cannot dump memory.

Option C (gpresult.exe /h report.html) generates a Group Policy Resultant Set of Policy HTML report and has no credential-dumping capability. Option E (netstat.exe -ano) only displays network connections with owning PIDs and cannot read LSASS memory.

Exam trap

CPENT often tests whether candidates confuse process enumeration or network inspection tools (tasklist, netstat) with actual credential-dumping techniques, so the trap is selecting any tool that merely lists processes or connections instead of one that reads LSASS memory.

43
MCQmedium

An operator has discovered a computer object with Unconstrained Delegation enabled in Active Directory. How can this configuration be abused if a Domain Administrator account can be coerced to authenticate to it?

A.Extract the NTLM hash of the domain controller directly from the SYSVOL share.
B.Forge a Kerberos ticket using the machine account's local SAM database.
C.Modify group policy objects via unauthenticated LDAP queries.
D.Capture the coerced Domain Admin's TGT from the machine's memory to impersonate them across the domain.
AnswerD

Unconstrained Delegation lets the host cache any authenticating user's TGT in LSASS. Coercing a Domain Administrator to authenticate deposits their TGT there, which the operator extracts and injects to impersonate them domain-wide — satisfying the scenario's requirement to abuse the delegation flag for full-domain privilege escalation.

Why this answer

When Unconstrained Delegation is enabled on a computer, the machine caches the TGT of any user who authenticates to it in LSASS memory so it can reuse that TGT for downstream services. If a Domain Admin is coerced (e.g., via PrinterBug/SpoolSample or PetitPotam) into authenticating to that host, the attacker can extract the DA's TGT and inject it to impersonate the administrator domain-wide.

Exam trap

The trap is assuming unconstrained delegation yields password hashes or GPO write access; in reality it yields cached Kerberos TGTs, which are used for ticket injection (Pass-the-Ticket), not hash extraction.

How to eliminate wrong answers

Option A is wrong because SYSVOL contains Group Policy files and scripts, not domain controller NTLM hashes — those live in NTDS.dit and are extracted via DCSync, not SYSVOL. Option B is wrong because the local SAM database only holds local account hashes, not domain machine-account Kerberos keys, and SAM cannot be used to forge domain Kerberos tickets. Option C is wrong because modifying GPOs requires authenticated LDAP write privileges (typically Domain Admin or delegated rights), not unauthenticated LDAP queries — and it is unrelated to unconstrained delegation abuse.

Ready to test yourself?

Try a timed practice session using only Active Directory Attacks questions.