Skip to main content
Category: Pentest
Load this context Ask your agent:

Summary

An unauthenticated infrastructure pentest simulates an attacker with no credentials and no prior access, starting only from network reachability. The goal is to determine how far an attacker can get before obtaining any credentials, and whether AD misconfigurations allow privilege escalation from zero.
  • Phase 1–2 build a complete host and service map, identifying Domain Controllers via port fingerprinting
  • Phase 3–4 enumerate SMB shares via null and guest sessions, hunt for credentials in SYSVOL, GPP files, and accessible share contents
  • Phase 5 enumerates domain users, groups, and password policy without credentials via RPC null sessions and LDAP anonymous bind
  • Phase 6 performs AS-REP Roasting against accounts with Kerberos pre-auth disabled, producing offline-crackable hashes
  • Phase 7 performs Kerberoasting against SPN accounts using any credentials obtained in earlier phases
  • Phase 8 runs background attacks in parallel: Responder for NTLM hash capture, DNS zone transfer, NBT-NS enumeration
  • Phases 9–11 enforce a validation gate, false positive filter, and structured finding output

CONTEXT.md

When to Use This Context

Load this context when:
  • Starting a black-box or unauthenticated internal network pentest
  • The scope includes Active Directory and Windows infrastructure
  • No credentials have been provided (testing pre-auth attack surface)
  • Assessing SMB exposure, null sessions, and Kerberos pre-auth weaknesses
Key focus areas: host and port discovery, SMB null sessions, AD user enumeration, AS-REP Roasting, Kerberoasting, offline hash cracking. Out of scope for this context: post-exploitation, lateral movement after credential gain, authenticated enumeration beyond initial foothold. Typical flow: Discover → Enumerate SMB → Enumerate AD → Attack Kerberos → Crack → Report

Phase 1: Host Discovery

Windows hosts often block ICMP but respond to TCP 445. Always combine methods.

Phase 2: Port and Service Enumeration


Phase 3: SMB Enumeration

High-priority share names: SYSVOL, NETLOGON, backup, backups, it, admin, scripts, tools

Phase 4: SMB Share Content Analysis


Phase 5: AD Enumeration (Unauthenticated)


Phase 6: AS-REP Roasting

Accounts with DONT_REQUIRE_PREAUTH set in userAccountControl are vulnerable. Often misconfigured service accounts or legacy accounts.

Phase 7: Kerberoasting

Requires at least one valid domain credential (from SMB analysis, GPP decrypt, or AS-REP cracking).
AES256 (etype 18) hashes crack significantly slower than RC4 (etype 23).

Phase 8: Background and Supplementary Attacks

Responder NTLM Hash Capture

Start at engagement launch and leave running throughout. Peak capture windows: morning logon (08:00–09:30) and post-lunch (13:00–14:00).
Relay instead of crack (if SMB signing is not required):
Note: -d (DHCP poisoning) can disrupt the entire subnet. Confirm explicit client approval before using it.

Other Checks


Validation Gate

Before reporting any finding, confirm all of the following:
  • Reproduced in a clean session with no cached credentials
  • Null/guest session confirmed explicitly, not assumed from tool output
  • Cracked hashes verified by re-authenticating with the cracked credential
  • AS-REP / Kerberoast hashes are from accounts in scope
  • SMB file access confirmed by actually reading a file, not just listing the share
  • Impact articulated: what can an attacker specifically do with this finding?
  • Evidence captured: full command, output, timestamp, source IP

False Positive Filter

Do not report without further verification:
  • Share listed but not accessible: listing a share name is not the same as read access, always confirm by reading a file
  • EternalBlue flagged by Nmap but unconfirmed: the smb-vuln-ms17-010 script has false positive cases, confirm before reporting as exploitable
  • Hash captured but not cracked: an uncracked AS-REP or TGS hash is a misconfiguration finding, not a credential compromise
  • LDAP anonymous bind returning empty results: a successful bind with 0 results is not the same as useful enumeration
  • Password spray without confirmed lockout policy: do not spray without knowing the lockout threshold

web-app-pentest

Full web application pentest methodology, recon through reporting

cloud-audit

AWS, Azure, and GCP security audit, IAM, storage, networking, secrets, and logging

code-audit

Source code security review, secrets, auth logic, injection sinks, crypto, dependencies