How we test
Five principles behind every Exploitr engagement
Validated by hand
Logic before signatures
Findings in combination
Attack paths, not lists
The smallest effective fix
Testing phases
How every engagement is structured
Reporting
Standards and frameworks
The frameworks our methodology is built on
OWASP Web Security Testing Guide (WSTG)
OWASP API Security Top 10
OWASP Mobile Application Security Verification Standard (MASVS)
NIST SP 800-115
Penetration Testing Execution Standard (PTES)
MITRE ATT&CK
NCSC guidance
CREST
Reports built for technical teams and business stakeholders
Every engagement produces a written report delivered within two business days of testing completion, written for the technical teams responsible for remediation and the business stakeholders who sign off on remediation priorities. Our article on how to write a penetration test report sets out what a well-structured report should contain.
Findings are tracked live in the Exploitr platform throughout testing, so your team can see what is being found without waiting for the report.
- Executive summary: A concise overview of the engagement, key findings, and overall risk exposure, written for non-technical stakeholders including board members, senior management, and compliance auditors.
- Scope and methodology section: A documented description of the testing approach, the scope agreed during the engagement, the standards and frameworks applied, and any items that were excluded from testing.
- Rules of engagement, exclusions, and limitations: A summary of the agreed rules of engagement, including testing windows, excluded functionality, and any other restrictions. This section also notes any limitations that may have affected the testing, such as time constraints or unavailable systems.

- Technical findings: Each vulnerability documented with a CVSS-aligned severity rating, reproduction steps, proof-of-concept evidence, affected component, and remediation guidance.
- Prioritisation guidance: Findings are prioritised based on the risk they present to your organisation, with recommendations for the minimum set of changes that break attack paths and reduce risk.
- Examples of good practice: Where relevant, we provide examples of good practice to help your team understand how to implement a fix and avoid similar issues in the future.

- CVSS, EPSS, and risk scoring: Each vulnerability is scored with CVSS v3.1 (and/or CVSS v4.0) and EPSS scores, where applicable, alongside our own Exploitr risk rating that considers the context of your environment and the potential impact of exploitation.
- Evidence and attachments: Proof-of-concept screenshots, logs, and other evidence are attached to each finding to support your technical teams in reproducing and remediating the issue.
- Affected assets and attack paths: Where relevant, findings are linked to the affected asset and any attack paths that lead to it, so your team can understand the wider impact of a vulnerability and prioritise remediation accordingly.

Get a fixed-price quote for your next assessment
Common questions
Penetration testing methodology: frequently asked questions
Our methodology draws on the OWASP WSTG and OWASP API Security Top 10 for application testing, NIST SP 800-115 and PTES for network and infrastructure testing, OWASP MASVS for mobile applications, and MITRE ATT&CK for technique selection and findings mapping, alongside NCSC guidance for UK organisations.
See the frameworks our methodology is built on for how each one is applied.
All testing is manually led. Automated tools are used selectively, for example for large-scale parameter fuzzing or directory enumeration, but every finding is reviewed and validated by the consultant. Business logic flaws, authorisation vulnerabilities, and chained attack paths are identified with the human analysis that automated tools cannot replicate.
You will not receive a repackaged vulnerability scan.
The core principles stay the same across every service: manual, intelligence-driven testing by an in-house consultant, with a fixed price confirmed before work begins. What changes is the framework and test cases applied, set out in the standards section, and the depth agreed at scoping. See the services overview for each service.
These terms describe how much information is shared with the tester before the engagement begins.
Black-box (or closed book) testing simulates an external attacker with no prior knowledge of your environment. Grey-box testing provides the tester with partial information, typically credentials or access as an authenticated user. This is the most common approach for web application and API assessments. White-box (aka. transparent or open book) testing gives the tester full access to source code, architecture documentation, and credentials.
For more detail on each, see our glossary entries for black-box testing, grey-box testing and white-box testing.
Scoping starts after your enquiry, usually with a short questionnaire or a call. We ask about the systems or applications that are to be tested, their complexity, any compliance context, and your objectives. From that we produce a fixed-price written proposal that confirms the targets that are in scope, the methodology and approach that will be applied, the deliverables that you will receive, and the wider rules of engagement like any testing windows or exclusions.
For more detail on how scoping typically works in practice, see our articles on scoping a web application assessment and scoping a network penetration test.
Critical findings are escalated to your named technical contact the same day they are discovered, and are not held until the report is delivered. This gives your team the option to begin remediation before the testing window closes, and we can retest the finding there and then.
You can also view any findings in real time throughout the engagement via the Exploitr platform.
We do not use AI tools to perform penetration testing. Our methodology is based on manual, intelligence-driven testing by experienced consultants.
While AI can assist in certain tasks, it cannot replace the nuanced analysis and decision-making required to identify complex vulnerabilities and business logic flaws. See our AI policy for more information.
