§3   How we work

How a test runs,

Day 0 to Day 38.

Same order every time. These days follow a 7-day test; longer tests stretch the middle and nothing else changes.

Rules
Outside
Foothold
Reach
Report
Retest
§3.1   Engagement steps

Who does what,and when.

Day 0

We write the rules

Scope, test windows and a stop contact, all signed before anything starts.

You name a contact

One person who can reach us and stop the test, and one goal for us to aim at.

Day 1

We map the outside

What the internet can see and what your staff already expose.

You do nothing

Work carries on as normal. We send a short note at the end of each test day.

Day 3

We get a foothold

One weak point is enough. We log the time and exactly how it worked.

You hear first

Your contact gets a call the same day for anything rated Critical.

Day 5

We reach for the goal

We move toward the goal you named, and stop at proof.

You keep control

If a change window moves, tell us and we pause around it.

Day 8

We hand over the report

Findings, proof and fixes, read through with your team on a call.

You bring the fixers

Whoever will do the work joins the call and asks anything.

Day 38

We try again, free

Every Critical and High is run again, with the result in writing.

You get the closing letter

A short summary you can hand to your board or an auditor.

Tester labelling a cable at a steel bench with laptops, a test device and a small switch
Tester labelling a cable at a steel bench with laptops, a test device and a small switch
§3.2   You stay in charge

One call stops it.

Nothing runs outside the signed scope. Your named contact can stop the test at any time.

Test windows are agreed for fragile systems.

Every action is logged with a time, so yours can be matched to ours.

We stop at proof, and never change production data.

§3.3   First 30 days after the report
30

Thirty days to fix it.

The time between report and retest is yours. We stay on hand for questions, at no charge.

Day 8

Read-through call. Each finding gets an owner on your side.

Day 9 to 15

Criticals go first. We check each fix by email if you want a second look.

Day 16 to 30

Highs next, then the Lows you choose to take on.

Day 31 to 37

You tell us what changed. We plan the retest around it.

Day 38

Retest, free. Written result the same week.

§3.4   Deliverables

What you keep.

Our work follows NIST SP 800-115 and PTES, with findings scored in CVSS. Read a sample report

Deliverable

What is in it

Who reads it

Rules of engagement

Scope, windows, contacts and goal, signed on Day 0

Your contact

Executive summary

Two pages: how far we got and what to do first

Board

Technical report

Each finding with proof, a CVSS score and a fix

IT team

Attack path walkthrough

The route we took, step by step and hour by hour

IT and security

Retest letter

Every Critical and High, marked fixed or still open

Auditors

Two penetration testers at a steel bench reading an attack path on dark terminals, server racks behind them
§4   Contact

Day 0 startswith a call.

Thirty minutes with a tester, not a salesperson. You get a written scope and a fixed price within two working days.