Internal Penetration Testing

Once a single endpoint is compromised, how far does the attacker get? We assume that breach has already happened — then test exactly how an adversary would move laterally, escalate privileges, and reach domain admin in your Active Directory environment.

Assume-breach methodology

We start where real attackers end up: a foothold. From a single workstation, we trace every attack path that leads to your most sensitive assets.

Active Directory attack chains

Kerberoasting, AS-REP roasting, NTLM relay, ACL abuse, ADCS misconfiguration, GPO weaknesses — the techniques actively exploited by ransomware operators.

Production-safe by design

Written rules of engagement, change windows, immediate escalation on high-impact findings, and zero destructive techniques on production data.

What an internal pentest reveals that nothing else does

Vulnerability scanners find missing patches. EDR finds known-bad binaries. An internal penetration test finds the chain — the trust relationships, weak credentials, and overlooked permissions that let an attacker turn one compromised laptop into domain-wide compromise.

Lateral movement & pivoting

SMB, WinRM, WMI, RDP, and PsExec-based lateral movement testing across workstations, file servers, and application hosts — exactly the techniques ransomware affiliates use after initial access.

Active Directory privilege escalation

Kerberoasting, AS-REP roasting, NTLM relay (LLMNR/NBT-NS poisoning), ACL abuse, unconstrained delegation, ADCS ESC1–ESC11, and shadow credentials attacks against your live AD.

Network segmentation validation

VLAN-to-VLAN reachability testing, firewall rule efficacy verification, and east-west traffic analysis — confirming that "isolated" segments actually are.

Detection & response validation

Optional collaborative purple-team mode tests whether your SIEM, EDR, and SOC actually detect each technique — turning the engagement into measurable defensive uplift.

How does it work?

iSECTECH establishes a controlled internal foothold — typically a hardened jump host placed inside your network or a low-privileged domain account simulating a phished employee. From that starting position, our OSCP/OSEP-certified operators perform reconnaissance, credential harvesting, lateral movement, and privilege escalation under written rules of engagement, with daily status updates and immediate notification of any critical finding.

An internal penetration test is the single most effective control validation an enterprise can run. It is recommended annually as a baseline, and after any significant change: domain consolidation, AD migration, M&A activity, or major application rollout.

A structured, repeatable, auditor-accepted process

Aligned to PTES (Penetration Testing Execution Standard), NIST SP 800-115, and OSSTMM — the same standards your auditors, regulators, and cyber insurance carriers expect for compliance evidence.

01

Scoping & ROE

Targets, IP ranges, exclusions, foothold strategy, and escalation protocols agreed in writing before any traffic is sent.

02

Foothold & recon

Internal positioning, asset discovery, AD enumeration, BloodHound graph collection, and trust relationship mapping.

03

Privilege escalation

Kerberos, NTLM, ACL, ADCS, GPO, and credential-based escalation paths — manually validated and chained.

04

Lateral movement

Pivoting across hosts, services, and trust boundaries — demonstrating impact through proof-of-exploit, never destructive payloads.

05

Reporting & retest

Executive and technical reports delivered, plus complimentary retest of remediated findings within 90 days.

Every layer of your internal estate — under hands-on adversarial pressure

Comprehensive coverage from the user workstation through to the domain controller. External perimeter testing is handled separately under our dedicated External Penetration Testing service.

BloodHound · Impacket · Certipy

Active Directory Attack Path Analysis

BloodHound graph collection is the starting point — not the destination. From the graph we manually validate every attack path leading to Tier-0 assets: Kerberoasting and AS-REP roasting against weak service accounts, NTLM relay via LLMNR/NBT-NS poisoning, ACL abuse and DCSync paths, ADCS ESC1–ESC11 certificate template misconfigurations, GPP credential exposure, and shadow credentials. We don't just report theoretical paths — we demonstrate the working exploit and provide remediation guidance specific to your AD design.

MITRE ATT&CK® TA0008 · TA0004

Lateral Movement & Privilege Escalation

Hands-on lateral movement using the same techniques mapped in MITRE ATT&CK Lateral Movement (TA0008) and Privilege Escalation (TA0004) tactics: pass-the-hash, pass-the-ticket, overpass-the-hash, NTLM relay, RBCD attacks, token impersonation, and constrained delegation abuse. Every action is timestamped, attributed, and reproducible — giving your blue team a precise replay of how an adversary would have moved, ranked by which paths cause the largest blast radius.

PCI DSS 4.0 Req. 1.3 · NIST SP 800-207

Network Segmentation & Trust-Boundary Testing

VLAN-to-VLAN reachability testing, firewall rule verification, and east-west traffic analysis. We confirm whether your "isolated" segments — cardholder data environments, OT/ICS networks, IoT VLANs, executive subnets — are actually isolated, or whether ACL gaps allow lateral traversal that would bypass your firewall investment. Findings are mapped directly to PCI DSS 4.0 Requirement 1.3 (segmentation testing) and NIST SP 800-207 zero-trust principles.

CVSS 3.1 · MITRE ATT&CK® mapped

Executive & Technical Reporting

You receive an executive narrative for the board, a detailed technical report for engineering with reproducible exploitation steps, an attack-path graph showing the shortest route to domain admin, MITRE ATT&CK® technique mapping for every finding, and a compliance appendix covering PCI DSS 4.0, SOC 2 Type II, HIPAA, ISO 27001, and NIST SP 800-53. Every report goes through a senior peer review before delivery — no boilerplate, no copy-paste, no auto-generated content.

Not every quarter — but more often than once

Internal penetration testing is most valuable when it follows a meaningful change in your environment or precedes an audit cycle. Here are the three scenarios where it consistently pays for itself.

Annual baseline (compliance-driven)

Required by PCI DSS 4.0, recommended by SOC 2 Type II auditors, and increasingly mandated by cyber insurance underwriters. Annual cadence is the floor — most regulated organizations run two or more per year.

After a major infrastructure change

Domain consolidations, AD migrations, M&A integration, major application rollouts, data center moves, or a cloud lift-and-shift. Each one introduces new trust paths — and new chances for adversaries.

Before an audit or insurance renewal

Closing critical findings 60–90 days ahead of your audit window means a clean report the first time. Underwriters specifically reward organizations with recent, documented internal pentest evidence.

Scope-driven engagements, fixed-fee quotes

Every internal pentest is quoted as a firm fixed price after a 30-minute scoping call — there is no published price tier because the cost is driven entirely by your environment: live host count, VLAN count, AD complexity (forest vs single domain, ADCS deployment, trust relationships), and whether purple-team detection validation is included. We benchmark our quotes quarterly against published 2026 rates from Compass IT Compliance, Bright Defense, Astra Security, BSG, RedBot, and DeepStrike, and price our engagements approximately 20% below the mid-market median. Ask for our scope-comparison worksheet — we'll send it with your quote so you can compare like-for-like.

Frequently asked questions

The questions we get most from CISOs and IT directors evaluating internal pentest providers. Need more detail? Talk to a senior offensive security engineer.

What's the difference between internal pentest, external pentest, and red team?
External pentesting tests your internet-facing perimeter — firewalls, VPNs, exposed services. Internal pentesting assumes the perimeter is already breached and tests how far an attacker can move inside your network — lateral movement, privilege escalation, AD compromise. Red teaming is a longer, stealthier, objective-based exercise that tests not just your controls but your detection and response capability. Most organizations need annual external + internal pentests for compliance; red teaming is added once detection capability is mature enough to be measured.
How is an internal pentest different from a vulnerability scan?
A vulnerability scan is automated — it lists missing patches and known CVEs against a signature database, often with significant false positives. An internal pentest is human-led — certified operators chain misconfigurations, weak credentials, and trust-relationship abuse into working attack paths and demonstrate real impact. PCI DSS, SOC 2, HIPAA, and cyber insurance carriers all require penetration testing — not scanning — as evidence of due diligence.
How long does an internal pentest take?
Small environments (1–2 VLANs, single AD domain, under 200 hosts) typically run 1–2 weeks of active testing plus 1 week of reporting. Mid-market (5–10 VLANs, 200–1,000 hosts) runs 2–3 weeks plus reporting. Large enterprises (multiple forests, geographically distributed, 1,000+ hosts) typically run 3–5 weeks. These timeframes include kickoff, foothold establishment, testing, internal QA review, delivery, and the live readout session.
Will testing disrupt production or trigger our SOC?
Disruption avoidance is a contractual obligation. Every engagement runs under written rules of engagement with defined out-of-scope assets, blackout windows, and production-safe techniques. Your SOC should see some of our activity — that's part of the value. We can run in fully transparent mode (your team knows in advance and we collaborate as a purple team), partially transparent mode (security leadership knows, frontline SOC does not), or fully covert mode (only the engagement sponsor knows). All three are common; we recommend the right one based on your detection-validation goals.
How do you establish the internal foothold?
Three options. (1) Hardened jump host: we ship a small appliance you place inside your network, or you spin up a dedicated VM we connect to via VPN. (2) Domain account: you create a low-privilege user and we authenticate as that user from a remote testing system, simulating a phished employee. (3) Hybrid: low-privilege account plus jump host. We pick the option that best matches the threat scenario you want to validate — and the choice is documented in the rules of engagement.
What certifications do your operators hold?
Every engineer on the iSECTECH internal testing team holds OSCP at minimum. Senior leads additionally hold OSEP (Offensive Security Experienced Penetration Tester), CRTO (Certified Red Team Operator), and either CEH or CISSP. We provide redacted operator CVs as part of procurement, and our reports are accepted by Big Four auditors and major cyber insurance underwriters as evidence of qualified testing.
Will this satisfy PCI DSS, SOC 2, HIPAA, and our cyber insurance?
Yes. Every report includes a compliance mapping appendix covering PCI DSS 4.0 (Requirement 11.4), SOC 2 Type II (CC4.1, CC7.1), HIPAA Security Rule (§164.308), ISO 27001 A.5.30 / A.8.8 / A.8.29, and NIST SP 800-53 RA-5 / CA-8. If your auditor requests specific language or formatting, we accommodate it at no extra cost. PCI DSS 4.0 specifically calls out internal penetration testing and segmentation validation — both of which our engagements cover by default.
Do you offer collaborative purple team mode?
Yes — and for organizations with mature SOC capability we strongly recommend it. In purple team mode, your blue team has visibility into our timeline as it unfolds. We pause after each technique, confirm whether your detection fired (and if not, which gap caused the miss), and document the gap with specific tuning recommendations for your SIEM and EDR. The output is both a pentest report and a defensive-tuning roadmap — without doubling the cost.

Learn more about internal penetration testing

Buyer guides, case studies, and technical deep-dives from the iSECTECH offensive security team.

Buyer Guide

Internal pentest pricing in 2026: what you should actually be paying

A market analysis of internal pentest pricing, the variables that legitimately move the price, and the red flags that signal a vulnerability scan rebranded as a penetration test.

Read more
Case Study

From phished user to domain admin in 8 hours: a healthcare engagement

How we chained an LLMNR-poisoned NTLM relay, a Kerberoastable service account, and an ADCS ESC1 misconfiguration to reach domain admin — and how the client closed every gap within 60 days.

Read more
Checklist

Scoping an internal pentest: a CISO's 12-point checklist

The twelve questions you should answer before signing a statement of work — and the specific vendor responses that should raise red flags during procurement.

Read more

See your network the way an attacker would — from the inside

Three ways to start the conversation — pick whichever fits your stage.

Request a scoping call

A 30-minute confidential conversation with a senior penetration testing engineer. You'll receive a firm fixed-price quote within 48 hours, benchmarked at ~20% below market.

Request a sample report

See exactly what you receive — an anonymized executive summary, technical findings section, attack-path graph, and compliance mapping appendix.

Explore all services

Internal pentesting is one pillar of our offensive security practice. Explore external pentest, red team operations, and web application testing.

Name

Office

443 Western AV.  #1033 
SOUTH PORTLAND ME,04106

Hours

M-F: 24/H
S-S: Closed

Call Us

+1(800) 325-1874