Essential Active Directory Checks Before Launching Any Penetration Test
Internal penetration tests are easily compromised in the first minutes. Spotting a familiar technique and launching a tool without context can produce log noise, affect services, or yield results that cannot be explained to the client. With Active Directory this problem is especially visible because the domain links users, servers, authentication, and access rights. The approach of “check first, understand later” rarely produces good outcomes.
Before any active testing, a sufficient picture of the environment must be assembled. The goal is not a perfect map but enough understanding to know what is being examined, which risk is being validated, and what may change after an action.
Defining scope and rules of engagement
The phrase “test Active Directory” conveys almost nothing by itself. The scope must clarify whether one or multiple domains are included, whether domain controllers may be contacted, whether scanning is permitted, which service accounts must remain untouched, and who on the client side must be notified of critical findings on the day of discovery.
A working document should record allowed network segments, prohibited actions, escalation paths for critical findings, and the method for logging results. This prevents on-the-fly decisions about touching a particular service or testing a chosen hypothesis.
Inventory before exploitation
After boundaries are agreed, the composition of the assessment area must be determined: how many domains are reachable, where the domain controllers reside, which servers rely on domain authentication, and whether separate segments or trust relationships exist. The resulting map helps separate important objects from background noise. Ordinary user accounts, service accounts, and domain administrators may appear similar in an export, yet the consequences of compromising each are very different.
During inventory, objects that warrant closer attention become visible. A service account cannot be assessed by name alone; its purpose, Service Principal Name settings, rights, and connected systems must be understood before any test begins.
Account roles and Kerberos pre-authentication
Technical objects in Active Directory must be classified by purpose: user accounts, service accounts, privileged accounts, and integration accounts. Accounts with Kerberos pre-authentication disabled should be identified because they are susceptible to AS-REP Roasting. The same disciplined approach applies to NTLM traffic and relay opportunities.
Kerberos ticket-granting mechanisms, DACL permissions, and delegation rights must be examined together. An error in object permissions can form the first link in a privilege-escalation chain even when the account is not a member of an obvious administrative group.
Certificate services and network context
AD CS infrastructure is frequently overlooked until late in an assessment. Testers need to identify who manages certificate templates, how certificates are issued, and which rights are tied to the issuance process. The same sequence applies: configuration first, then hypothesis, then safe validation.
Finally, the engagement format must be aligned with the client. A standard internal pentest seeks to confirm vulnerabilities, while a Red Team exercise also measures detection speed and log visibility. Every action must be logged with timestamp, target object, account used, hypothesis tested, and result obtained so that findings remain reproducible and rollback procedures can be verified.
Related articles
Chrome Researcher Edits Own VRP Reward to $1.3M in Bug Tracker Prank, Triggering AI Misinformation Spread
Security researcher Lyra Rebane, who has disclosed 14 CVEs in Chrome, reported a logical flaw in the Background Fetch API in 2022 that could enable browser-based botnets. Google awarded $1,000 after the issue was fixed in February 2026, but the researcher later received verifier rights in the Buganizer tracker. She jokingly set the vrp-reward field to $1,333,337, the largest amount in Google VRP history. The tweet about the edit went viral and was picked up by AI news generators and Google search, which began listing her as a millionaire. Community Notes initially flagged the post before an experimental AI note incorrectly claimed the screenshot was edited. The incident highlights how social media amplification and AI systems can turn a harmless joke into persistent misinformation across search engines including Kagi, DuckDuckGo, and Bing.
Java4Shell (CVE-2026-114938) Vulnerability Allows Remote Memory Corruption and Code Execution in OpenJDK
Researchers at Calif disclosed Java4Shell (CVE-2026-114938) on 17 November 2026, a critical flaw in the HotSpot JVM that enables memory corruption via a malicious Base64 payload. The issue affects multiple OpenJDK distributions including Oracle Java, Amazon Corretto, Eclipse Temurin and Azul Zulu when running on modern Intel Xeon and AMD EPYC processors supporting AVX-512 VBMI instructions. Rated 9.2 on CVSS 4.0, the vulnerability can lead to data theft and arbitrary code execution without authentication in several widely used products such as Keycloak, Jenkins and Atlassian Jira. Public exploit code and reconnaissance activity were observed within days, although no confirmed successful breaches have been reported yet. Patches are available for supported branches, while older intermediate versions require migration to maintained releases.
F6 Investigates First In-the-Wild Exploitation of Critical CVE-2026-76466 in Cisco Expressway
Russian cybersecurity firm F6 has documented the first confirmed exploitation of the critical CVE-2026-76466 vulnerability (CVSS 9.8) affecting Cisco Expressway devices. Attackers targeted a Russian company and quickly adapted a public proof-of-concept exploit to gain root-level remote command execution on version X15.5.3. The flaw resides in the Erlang distribution authentication mechanism on TCP port 4372, allowing unauthenticated command execution via a hardcoded cookie. After initial access, the threat actors deployed over 100 custom Python scripts for network reconnaissance, lateral movement, and data collection, including tools that abused WinRM, SMB, LDAP, and SQL Server protocols. F6 observed modifications to the original PoC that enabled arbitrary command execution and result retrieval, along with auxiliary scripts for TCP relaying and repeated connection attempts. The incident highlights how quickly public exploits can be weaponized against perimeter devices that bridge external and internal networks.
NGINX2Root Vulnerabilities: Ten Critical Flaws Patched in NGINX Including Remote Code Execution via HTTP/2
On November 18 2026 NGINX developers addressed ten vulnerabilities with five grouped under the NGINX2Root research name by Theori's Xint team. The most severe CVE-2026-123007 enables unauthenticated remote code execution on servers with HTTP/2 enabled by exploiting memory corruption that originated in 2015. Researchers demonstrated full compromise including root escalation via a separate Linux SCTP kernel flaw and escape from Docker containers. Working exploits have been published by Rapid7 and others with specific requirements such as AVX-512 support and substantial traffic volumes. Patches are available in NGINX 1.30.7 1.31.9 and corresponding NGINX Plus releases while temporary mitigations include disabling HTTP/2 or HTTP/3. The issues affect standalone servers reverse proxies Kubernetes ingress controllers and embedded NGINX instances across distributions.