Penetration tester kneeling in a network closet, his laptop cabled into a wall patch panel

Internal network

penetration test

We start from one staff laptop and try for domain admin. You learn how far a single stolen login really goes.

7 days

of testing, on site or through a device we post to you

Day 8

report, read through with your team on a call

Day 38

free retest of every Critical and High

§1   What it answers

One login. How far?

Firewalls cover the edge. This test covers what happens after it. Here is how one sample engagement ran, hour by hour.

Hour

What happened

Rated

0h

First packet from a standard staff laptop on the office network.

Start

4h

Name resolution traffic gave us password hashes from the local network.

Low

11h

A service account with a weak password cracked through Kerberoasting.

High

19h

That account was a local admin on a print server nobody had on a list.

Critical

31h

A domain admin session on the print server gave us the domain. We stopped at proof.

Critical

Sample engagement WL-2291. Sample data, client name withheld.

Hands on a keyboard under a network graph on a dark screen, a security key on the desk
Hands on a keyboard under a network graph on a dark screen, a security key on the desk
§2   What's included

Seven things, every time.

  • Two named testers, for the whole engagement
  • Active Directory attack path review
  • Segmentation checks between network zones
  • Password audit of hashes we recover
  • Same-day call on any Critical finding
  • Report with proof, a CVSS score and a fix for each finding
  • Free retest on Day 38, with the result in writing
§3   Scope

Agreed in writing.

Area

We test

We leave alone

Identity

Active Directory, group policy, service accounts, delegation

Real staff passwords in the report: hashes and counts only

Network

Zones and VLANs named in the scope, file shares, printers

Anything not listed, including partner and guest networks

Servers

Patch level, admin paths, stored credentials

Denial of service, and any change to production data

Goal

The target you name, such as domain admin or a finance share

Reading content beyond what proof requires

§4   Related case studies

Two that went far.

Sample data. Client names withheld.
§5   Questions

Before you sign.

Will this take anything down?

We avoid anything likely to disrupt service, and we agree test windows for fragile systems. Your stop contact can end the test with one phone call.

Do you need to come on site?

No. We can post a small test device that your team plugs in, or work from a staff laptop you provide. Either way, the start point matches what a real staff member has.

Should our IT team be told?

Usually yes, since this test measures the network and not the defenders. If you want to measure the defenders too, a red team exercise is the better fit.

What happens to the data you collect?

Recovered credentials and evidence stay encrypted, and we delete them after the retest. You get written confirmation when that is done.

Pick a laptop.

We start there.
Talk to a tester

You get a written scope and a fixed price within two working days.