Before anything technical happens, we align on what's in scope, what's off-limits, who the contacts are, and what success looks like. You receive an NDA and a Rules of Engagement (RoE) document to sign before any work begins. This phase defines the engagement — and protects both parties.
We map your attack surface the way a real attacker would — passively first, then actively. OSINT collection, subdomain enumeration, employee profiling, technology fingerprinting, and public exposure analysis give us a picture of your real-world footprint before a single packet is sent to your systems.
The core of the engagement. We manually test each attack vector identified during recon, using controlled techniques to confirm exploitability, chain vulnerabilities where possible, and establish the real business impact. We don't just report scanner output — every finding is manually validated and understood.
We write reports that people actually read. Every engagement produces two documents: an executive summary for leadership and a full technical report for your engineering team. No copy-paste scanner output, no 80-page PDFs full of noise. Findings are prioritised by real-world risk and paired with specific, actionable remediation steps.
The work isn't done when the report is delivered. We're available to answer your developers' questions during the remediation window, and once you're ready, we re-test every finding at no additional charge. You receive a remediation close-out report confirming what's been fixed and what — if anything — needs further attention.
"Penetration testing is a privilege — we're granted access to systems that organisations rely on. We take that seriously. Our job is to find problems, not create them, and to leave every environment exactly as we found it."
— Betasec, Rules of Engagement standardOur scoping process is straightforward. Tell us what you need, and we'll handle the rest.
Request a Scope →