Open Source Security Testing Methodology Manual (OSSTMM) (PDF)
A scientific, metrics-driven approach to security testing.
How we work
A clear, predictable process from the first call to the retest, with no surprises for your team.
Process
We learn your environment, goals, deadlines and compliance needs.
A statement of work with scope, schedule, rules of engagement and pricing.
Hands-on testing within agreed windows. Critical issues are reported to you immediately.
Every finding is exploited by hand, safely, to prove real impact and remove false positives.
An audit-ready report and a walkthrough with your team.
We retest remediated findings within 45 days and confirm they are closed.
Standards
Our methodology draws on established frameworks and the compliance standards our clients answer to, combined with hands-on experience from more than two decades of testing.
A scientific, metrics-driven approach to security testing.
The go-to framework for web application assessments.
The U.S. government’s technical guide to security testing and assessment.
A practical, phase-driven standard that mirrors how real engagements are conducted.
The payment card industry’s security standard, including requirement 11.4 for regular penetration testing and segmentation testing.
Your report
Our commitments
We avoid exploits that could destroy data or take systems offline, and we follow the rules of engagement we agree on.
We can sign a confidentiality agreement before scoping, and your findings are shared only with the people you designate.
A single point of contact, regular updates and immediate notice of anything critical.
The first step is a short scoping call.