Service 03

The 5-day rapid assessment

Most internal compromises come down to a short, well-known list of issues: relay and poisoning exposure, Kerberoasting paths, flat privileged access, weak logging. You do not need a six-week engagement to find out if you have them. You need five focused days and someone who already knows exactly where to look.

Overview

The problem we are solving

This is a different kind of engagement than our full penetration test: tighter scope, fixed five-day timeline, fixed price, no surprises. It exists for teams who want a fast, credible answer about their internal network exposure without the multi-week calendar hold and larger invoice a full-scope engagement requires.

The five days cover testing and reporting. Scoping and the live debrief sit outside that window and are not billed against it, and the finished written report follows three to five business days after testing wraps, not on day five itself. A critical finding is never held for the final write-up; you hear about it the day it is confirmed.

The methodology is built around a well-known, publicly documented checklist of the Active Directory attack paths and hardening gaps responsible for the overwhelming majority of real-world internal compromises: LLMNR/NBT-NS/WPAD poisoning, NTLM relay, Kerberoasting, flat privileged access, weak credential hygiene, and thin logging coverage. We do not review your policy documents against it; we verify each item directly against your live environment, and we exploit what we find to confirm it is real rather than theoretical.

Depth is traded for breadth on purpose. We are not trying to find everything that could theoretically be wrong with your network in five days. We are finding the handful of things most likely to actually get you compromised, ranking them by real impact, and telling you which to fix first.

Coverage

What five days covers

Scope is agreed up front; these are the areas an engagement typically covers.

Name resolution & relay exposure
LLMNR, NBT-NS, and WPAD poisoning exposure; SMB signing enforcement; NTLM relay paths; NTLMv1 and LM hash exposure on the wire.
Kerberos abuse paths
Kerberoastable service accounts, krbtgt hygiene, delegation misconfiguration, and paths from a kerberoastable or low-privilege user to domain admin.
Privileged access architecture
Tiering model (or absence of one), privileged access workstation usage, standing admin rights on end-user workstations, and local admin password reuse across the fleet.
Credential & secrets exposure
Group Policy Preferences and unattended-install artifacts, credentials in shares and scripts, and legacy protocol support: SMBv1, PowerShell v2.
Endpoint & detection controls
Credential Guard, Device Guard, AppLocker, and Sysmon/logging coverage, and whether the techniques above would actually be seen if used against you.
Known high-impact misconfigurations
Print spooler exposure on domain controllers, Exchange privilege-escalation paths, and LDAP signing and channel binding enforcement.

Methodology

How the engagement runs

  1. 01

    Scoping & access

    Rules of engagement, environment access, and scheduling agreed up front. This does not count against the five billable days.

  2. 02

    Days 1 to 3: Active testing

    Each checklist item is verified directly against your live environment, and exploited where it is safe to do so: an actual relayed hash or a confirmed path to domain admin, not a checkbox.

  3. 03

    Days 4 to 5: Validation & report drafting

    Confirmed findings are ranked by real exploitability and business impact, and the write-up begins, all inside the same five-day window. Nothing theoretical gets padded in to make the report look fuller.

  4. 04

    Report delivery

    The finished report follows three to five business days after testing wraps, not on day five itself. A critical finding is flagged the moment it is confirmed, well before then.

  5. 05

    Debrief & presentation

    A live walkthrough of the findings, scheduled once the report is delivered. Like scoping, this sits outside the five billable days.

Deliverables

What you receive

  • Findings ranked by real-world exploitability, not by count
  • Executive summary naming the two or three things to fix first
  • Technical detail and reproduction steps for every confirmed finding
  • Validation steps for every finding, so your team can confirm and close out each fix on its own
  • Live debrief once the report is delivered, not counted against the five billable days

Aligned to

  • Internal AD hardening checklist (github.com/evilmog/ntlmv1-multi)
  • MITRE ATT&CK (lateral movement & credential access)
  • Microsoft Securing Privileged Access

Questions

Frequently asked

Why does this cost less than your full penetration test?

Scope and time are both fixed and tightly bounded: one internal network, five days, no expansion into web, API, or external surfaces. Depth is traded for breadth on purpose, tuned to the handful of issues most likely to matter rather than exhaustive coverage of everything theoretically possible.

Is this a substitute for a full penetration test for compliance purposes?

Not automatically. Many auditors require a specific scope, methodology, and duration that a five-day engagement will not satisfy on its own. This works best as a fast, affordable gut check, or as a recurring health check between full-scope engagements. Ask during scoping if it needs to satisfy a specific requirement.

What if you find something critical?

You hear about it the day it is confirmed, not at the end of day five.

When do we actually get the report?

The five days cover testing and reporting, not the finished document in hand. The written report follows three to five business days after testing concludes, and the live debrief is scheduled after that, not counted against the five billable days.

Does this only work for Windows/AD environments?

It is designed around internal, Active Directory–integrated networks, where this class of findings concentrates. Ask if you want the same fixed-price, fixed-timeline model applied to a different surface.

How can the price be fixed regardless of environment size?

Scope is bounded by time and by network segment, not by asset count. Very large or heavily segmented environments may need more than one rapid assessment, or a broader engagement. We will tell you honestly which makes more sense during scoping.

Related

Often scoped together

Penetration Testing

Manual, objective-driven testing of web applications, APIs, and networks (internal, external, wireless, and physical), built on hands-on consulting experience since 2018, not a scanner with a report template.

AI-Assisted Penetration Testing

Agentic AI accelerates reconnaissance, enumeration, and evidence correlation across an engagement, run through isolated infrastructure: Amazon Bedrock in a dedicated environment, or a private model on in-house bare metal when nothing can leave the building.

Get started

Ready to scope rapid assessment?

Scoping conversations are free and usually take twenty minutes. You will speak directly with the consultant who would do the work.