+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.