Skip to content

Close your penetration testing
requirement in 72 hours

Buy the engagement that satisfies the testing clause your framework puts on you. Run by AI, validated by people, delivered as the six documents an assessor asks for β€” and guaranteed to be accepted by yours.

Accepted by your assessor, guaranteedIf they will not accept our report as evidence, we join the call, change what they ask for, and retest at no cost until they do.
In your hands in 24 to 72 hoursMeasured from the moment scope is agreed. Not weeks of waiting for a consultancy booking slot, and not a queue.

Which framework are you being assessed against?

Pick every one that applies. We will show you the clauses your engagement closes and the documents your assessor receives.

Whichever you pick, every engagement delivers the same six documents. These are what an assessor asks for, and they are yours to keep.

Findings reportProof each finding was actually exploited
Methodology statementThe documented approach, as a separate document
Scope and authorisation recordWhat was tested, what was not, and who authorised it
Retest and closure recordThe re-run that proves a finding is closed
Validation and independence statementWho reviewed it, and how they are independent
Testing historyThe dated series that evidences a cadence

The two things we guarantee

Most people hesitate for one of two reasons: the report might be waved away by their assessor, or it might not arrive before the deadline that forced them to buy. Both risks are ours, not yours.

Your assessor accepts it, or we keep going

Tell us they will not accept the report and we join a call with you and them, explain the methodology, scope and validation in the terms they work in, make whatever changes they ask for, and run the engagement again. We reissue the pack and repeat until they accept it. You pay nothing more for the extra engagements or for the time we spend with your assessor.

24 to 72 hours, from scope to report

The clock starts when scope is agreed and your targets are reachable. Most engagements finish at the shorter end; a large estate, an internal network or segmentation testing uses more of the window. If we are going to miss it you hear from us before the deadline, not after it.

Retesting until findings close

A finding is not closed because you made a change. It is closed when the retest fails to reproduce it, which several standards require as evidence in its own right. Retests are included, not billed per round.

Where the guarantee stops, stated plainly

We guarantee our work is accepted as testing evidence for the control it was produced for. We do not promise you pass your audit: most outcomes turn on controls a penetration test never touches. If the gap your assessor identifies is something testing cannot close, we say so rather than retest forever.

Why this costs less and arrives sooner

Four reasons, and only one of them is price. The others are why teams who could afford a consultancy engagement still move.

The evidence stops going stale

A once-a-year engagement produces evidence that is accurate on the day it is written and drifts from that day onward, while your estate keeps changing. Testing on a continuous cadence is also what several standards ask you to evidence β€” a series of dated results, not a single report.

Annual engagement
Continuous

Days instead of a booking slot

Most of the delay in a traditional engagement is not the testing. It is waiting for a slot, agreeing scope by email, and waiting again for the write-up. Here the testing starts when scope is agreed and the pack is written as the engagement runs.

That matters most for the trigger people forget: several frameworks make a material change its own reason to test, independent of the calendar. A test you can run the week you ship is a test you will actually run.

People still decide what counts

Every finding is reproduced on a second independent pass before it reaches your report. One that reproduces is promoted, with severity set by a qualified tester against your environment. One that does not is kept as informational with the limitation stated, rather than reported as confirmed or quietly dropped.

Exploitation itself waits for a named person to authorise it. The checkpoint sits exactly where change control and compliance need it to sit, and the authorisation is recorded in the scope document.

You price the year, not the engagement

Consultancy testing is priced per engagement and scoped to a window, which is why the second test of the year rarely happens. A subscription prices the year, so testing after a release costs you nothing extra and the cadence stops being a budgeting decision.

We will not quote you someone else's number for comparison. Send us your last engagement quote and its scope and we will tell you plainly what the same coverage costs here.

Read a real report before you buy

Both of these came out of our own deliberately vulnerable test estate, unedited. They are the fastest way to judge whether the evidence would satisfy the person who reviews yours β€” and the right thing to forward to them if you want to check first.

Pricing

Testing is unlimited inside your plan window, because a cadence you have to budget for every time is a cadence that slips.

Free

$0forever

Seeing what we find before you commit anything.

  • External exposure assessment of your estate
  • Findings with severity and remediation guidance
  • No card, no sales call required
Create a free account

Pro

Talk to us

One company closing its own compliance requirement.

  • Unlimited penetration tests within your plan window
  • All six evidence documents on every engagement
  • Reports in 24 to 72 hours, guaranteed
  • Human validation before any finding is released
  • Accepted by your assessor, guaranteed
  • Retest included until findings close
Start your first test

Business

Talk to us

Larger estates, tighter cadences, and segmentation testing.

  • Everything in Pro
  • Higher concurrent testing volume
  • Internal and segmentation testing
  • Run from servers you control
  • Named contact for your assessor
Talk to us

The questions people actually ask

+Will an auditor accept a penetration test that was run by AI?

Auditors assess the sufficiency of the evidence, not the brand of tool that produced it. What they look for is a documented methodology, a scope that matches the system under assessment, findings with proof that something was actually exploited rather than merely detected, a qualified and independent reviewer, and a record of remediation and retest. Every engagement delivers those as separate documents for that reason. We also guarantee it: if your assessor will not accept our report as evidence for the control it was produced for, we join the call, change what they ask us to change, and retest at no cost until they do.

+What exactly does the acceptance guarantee cover, and where does it stop?

It covers our work being accepted as testing evidence for the control it was produced for. If your assessor will not accept it, we do three things at no additional cost: join a call with you and them and explain the methodology in their terms, make whatever changes to scope, depth or documentation they ask for, and run the engagement again and reissue the pack. That repeats until they accept it. Where it stops is stated plainly: we do not promise you pass your audit, because most audit outcomes turn on controls a penetration test never touches, and if the gap your assessor identifies is something testing cannot close, we tell you that rather than retest forever.

+Is the 24 to 72 hour delivery a real commitment?

Yes, measured from the moment scope is agreed and your targets are reachable β€” not from the moment you sign up, because scope is a conversation and we will not test something until we are sure you are authorised to have it tested. Most engagements land at the shorter end. The range exists because a larger estate, an internal network or segmentation testing takes longer to cover properly than a single external application, and we would rather quote the honest range than the best case. If we are going to miss it, you hear from us before the deadline rather than after.

+Is this a real penetration test or a vulnerability scan?

They are different activities and some standards separate them explicitly β€” PCI DSS puts scanning in Requirement 11.3 and penetration testing in 11.4, and scan output does not satisfy 11.4. A scanner reports what it matched against a signature. Our engagements go further: they authenticate, chain findings together into attack paths across the estate, and attempt exploitation to establish what an intruder could actually reach. Exploitation is the part that sits behind a human authorisation gate, because it is the point where testing stops observing and starts acting.

+Who validates the findings, and what do they actually change?

Findings are reproduced on a second independent pass before they reach your report. A finding that reproduces is promoted, with severity set by a qualified tester against your environment rather than by a generic score. A finding that does not reproduce is kept as informational with the limitation stated openly, instead of being reported as confirmed or quietly dropped. The validation and independence statement in your pack names who did that review and what they changed, which is the document an assessor asks for when they want to know a person was involved.

+How often can we test, and does it cost more each time?

Testing is unlimited inside your plan window, which is the point of pricing the year rather than the engagement. That matters for the trigger people forget: several frameworks make a material change its own reason to test, independent of the calendar, and a test you have to raise a purchase order for is a test that slips. It also matters for evidence β€” a cadence you committed to is proven by the dated series of tests, not by the latest report, which is what a SOC 2 Type II observation window and a cyber insurance renewal both actually need.

+Is it safe to run against production?

Scope is enforced in code at every tool call rather than by a setting someone can forget. A target that is not in the signed scope is refused at the boundary and the request never reaches the network. Exploitation does not begin until a named person authorises it, and that authorisation is recorded in the scope document. Post-exploitation demonstrates what is reachable without extracting your data. If you would rather not test production at all, the Business plan runs from infrastructure you control.

Close the requirement this week

Start free and see what we find on your estate before you pay anything. When you are ready, scope is agreed and the report is in your hands within 24 to 72 hours.