Penetration Testing Methodology

What happens during a penetration test?


From defining the scope to investigating vulnerabilities, reporting findings and retesting fixes, understand exactly how we approach an assessment and what you can expect at each stage.

Our approach

Manual testing, led by consultants

Every engagement follows a documented methodology built on over a decade of hands-on penetration testing, drawing on the recognised standards and frameworks set out below.

Each engagement is scoped individually for your organisation, priced at a fixed rate before any work begins, and delivered by one assigned consultant from the initial scoping call through to the debrief.

Key approach

Manual, consultant-led testing, scoped to your environment.

Delivery

  • Tailor-made scope
  • Fixed pricing
  • One assigned consultant throughout
  • CREST accredited penetration testing
  • No outsourced testing

How we test

Five principles behind every Exploitr engagement

The frameworks further down this page define what we cover. These principles define how we work through it, whatever the service type.
01

Validated by hand

Every finding is confirmed by a consultant before it's reported. Nothing is auto-populated from a scanner, so what you receive is exploitable, not theoretical.
02

Logic before signatures

Authorisation, workflows and business logic are tested manually. These are the flaws automated tools don't reach, and often the ones with the most impact.
03

Findings in combination

Lower-severity issues are chained together to show the impact an attacker could actually achieve, rather than being reported as isolated items.
04

Attack paths, not lists

We map the route from entry point to outcome, and highlight where several paths converge on the same asset. You can follow each path in the Exploitr platform.
05

The smallest effective fix

For each attack path we identify the minimum set of changes that breaks it, so remediation effort goes where it reduces the most risk.

Testing phases

How every engagement is structured

The phases below apply across all service types. The specific test cases, frameworks, and depth of each phase are determined by the scope agreed at the outset.
01

Scoping and rules of engagement

We agree the scope, target systems or applications, testing hours, and any restrictions before any work begins. A written rules of engagement document and fixed-price proposal are produced at this stage.

The scope of a penetration test determines what is tested, how it is tested, and what is explicitly excluded. For network assessments, this covers IP ranges and services. For web applications, it covers the application surface, authenticated roles, and any restricted functionality.

A fixed-price proposal is confirmed before testing begins, and the rules of engagement document is signed by both parties. For guidance on how scoping typically works, see our articles on scoping a web application assessment and scoping a network penetration test.

02

Reconnaissance

We map the target environment before active exploitation begins. For external targets, this includes open ports, services, DNS records, and open-source intelligence. For applications, it covers routes, API endpoints, technologies in use, and session handling.

Reconnaissance is passive or semi-passive at this stage. For network testing, this involves port scanning, service enumeration, and open-source intelligence gathering. For web applications, it involves spidering the application, analysing HTTP traffic, and building a map of accessible functionality.

The output is a testing plan that ensures coverage of the full agreed scope before active exploitation begins.

03

Manual testing and exploitation

Your consultant works through the agreed scope by hand, using tools selectively, for example for parameter fuzzing or directory enumeration.

The test cases applied depend on the service, as set out in the standards and frameworks below.

Critical findings are raised with your named technical contact immediately, not held until the report.

04

Post-exploitation and privilege escalation

Where the assessment type permits, we attempt to escalate privileges and move laterally to understand the real-world impact of successful exploitation. This is standard in internal network and assumed-breach engagements.

For internal network assessments, this involves testing Active Directory trust relationships, Kerberoasting, pass-the-hash, and lateral movement techniques aligned with MITRE ATT&CK. For application testing, it covers horizontal and vertical privilege escalation, IDOR, and access control testing across all authenticated roles.

The objective is to demonstrate what a real attacker could access or achieve, not only to confirm that a vulnerability exists.

05

Reporting

A written report is delivered within two business days of testing completion, written for both technical and non-technical audiences. See how we report for what it contains.
06

Debrief and free retesting

A debrief call follows the report to walk through findings with your technical and business teams. For externally-based assessments including web application, API, and external network testing, focused retesting of remediated vulnerabilities is included at no additional charge.

The debrief covers findings in plain language, prioritisation guidance, and answers questions from your team. Once remediation is complete, we revisit the specific findings to confirm fixes are effective. This is a targeted retest of addressed vulnerabilities, included as standard.

For a full walkthrough of what the testing window looks like from your team's perspective, see our article on what to expect during a web application pentest.

Standards and frameworks

The frameworks our methodology is built on

Our testing methodology draws on established, peer-reviewed frameworks rather than an ad hoc internal checklist. Below is a summary of the primary standards we reference and how they are applied across our service types.
01

OWASP Web Security Testing Guide (WSTG)

The primary reference for web application testing coverage. Our web application and SaaS assessments follow the WSTG test cases across authentication, session management, authorisation, input validation, API security, and client-side controls.
02

OWASP API Security Top 10

API-specific risks including broken object-level authorisation (BOLA), broken authentication, excessive data exposure, and rate limiting bypass. Applied to all API and web application assessments where APIs are in scope.
03

OWASP Mobile Application Security Verification Standard (MASVS)

The reference standard for iOS and Android security testing, covering data storage, cryptography, authentication, network communication, platform interaction, and code quality. Applied to all mobile application assessments.
04

NIST SP 800-115

NIST's technical guide to information security testing and assessment. Provides the framework for our network and infrastructure testing methodology, covering planning, discovery, attack phases, and reporting structure.
05

Penetration Testing Execution Standard (PTES)

A community standard covering the full engagement lifecycle: pre-engagement, intelligence gathering, threat modelling, exploitation, post-exploitation, and reporting. Referenced across network and infrastructure assessments. See our PTES glossary entry for an overview of the standard.
06

MITRE ATT&CK

A knowledge base of adversary tactics, techniques, and procedures (TTPs) drawn from real-world observations. Used to frame exploitation and post-exploitation techniques in network and infrastructure testing, and to map findings in technical reports. See our MITRE ATT&CK glossary entry.
07

NCSC guidance

We reference NCSC guidance on penetration testing as part of how we structure engagements and communicate results. The NCSC's penetration testing guidance for organisations provides useful context for buyers and commissioning teams.
08

CREST

Exploitr is a CREST member company, accredited for penetration testing. Our methodology is aligned to CREST guidance on penetration testing, and membership means our processes, methodologies, and quality assurance have been independently assessed against their standards.
Reporting

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.
Executive summary and commentary on penetration test findings in the Exploitr platform
  • 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.
Penetration test findings tracked and reported in the Exploitr platform
  • 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.
Pentest report vulnerability detail showing CVSS scores, EPSS, affected asset, and attached evidence

Get a fixed-price quote for your next assessment

Submit your requirements and we'll reply within one business day to confirm your scope, then send a written, fixed-price proposal. All enquiries are confidential and there is no obligation to proceed.

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.