Cybernion
← Insights

Security

Penetration Testing Methodology Explained

30 Aug 2026 · Updated 30 Aug 2026

A good penetration test follows a recognised, structured methodology rather than being ad hoc. The main ones are NIST SP 800-115 (four phases), the Penetration Testing Execution Standard (seven phases), the OWASP guides for web, API and mobile, and OSSTMM. They share a common structure: plan, discover, exploit, report. Asking which methodology a provider follows, and whether they hold accreditation such as CREST, is how a buyer judges quality.

The difference between a good penetration test and a box-ticking one is often the methodology behind it. A structured method means the test is thorough and repeatable; its absence means trusting one tester’s habits. The recognised methodologies, and what each covers, follow.

What is a penetration testing methodology?

A penetration testing methodology is a structured, repeatable process that a tester follows so that an engagement is systematic, consistent and defensible. Without one, a test depends entirely on the individual tester’s habits and memory, which makes coverage unpredictable. With one, the engagement follows a defined path that can be reviewed and relied on.

Several recognised methodologies exist, and a credible provider will follow one or more of them: NIST SP 800-115, the Penetration Testing Execution Standard (PTES), the OWASP testing guides for web, API and mobile applications, and OSSTMM. They differ in detail and emphasis, but they share a common structure, planning and reconnaissance, then discovery of weaknesses, then exploitation, then reporting. That shared structure is why a test that follows any of them will cover the essential ground. It also matters for compliance: PCI DSS explicitly requires a documented penetration testing methodology based on an industry accepted approach such as NIST SP 800-115, OWASP, PTES or OSSTMM.

What are the phases of the NIST penetration testing methodology?

NIST SP 800-115, the US technical guide to security testing, defines a four-stage penetration testing methodology: planning, discovery, attack and reporting. It is the most commonly cited baseline methodology, and other approaches map onto it.

Planning comes first, and NIST is explicit that no actual testing occurs in this phase, it is where rules are identified, management approval is documented, and goals are set. Discovery has two parts: information gathering and scanning to identify hosts and services, and vulnerability analysis that compares what is found against vulnerability databases. The attack phase is the core, and NIST breaks it into steps, gaining access, escalating privileges, browsing the system, and installing additional tools, with a loop back to discovery whenever new information opens up further targets. Reporting is not only the final step: NIST stresses that reporting occurs simultaneously with the other phases, with logs kept throughout and a final report that describes the vulnerabilities, presents a risk rating and gives remediation guidance. The four phases are simple, but they capture how a real attack unfolds.

What are the seven PTES phases?

The Penetration Testing Execution Standard, PTES, defines the process in seven phases, and it is more granular than the NIST four. The phases are pre-engagement interactions, intelligence gathering, threat modeling, vulnerability analysis, exploitation, post exploitation, and reporting.

The value of the PTES structure is that it makes explicit some things the NIST model folds together. Pre-engagement interactions cover scoping and rules of engagement, the commercial and legal groundwork that a good test depends on. Threat modeling, a distinct PTES phase, pushes the tester to think about who would attack the target and how, before diving into exploitation. Post exploitation is also called out separately, which matters because demonstrating business impact, what an attacker could actually reach and do after getting in, is often where the real value of a test lies. PTES then ends with reporting. For a buyer, PTES is a useful reference because its phase names describe exactly what a thorough engagement should include, from scoping through to impact and reporting.

What are the OWASP guides, OSSTMM and CREST?

Beyond the general methodologies, some standards focus on specific targets or on accrediting providers. The OWASP guides are the reference for application testing: the Web Security Testing Guide covers web application testing across areas such as authentication, authorisation, session management, input validation and business logic; the OWASP API Security Top 10 covers API risks; and the OWASP mobile application security standard and testing guide cover mobile apps. A web or API test should follow the relevant OWASP guide.

OSSTMM, the Open Source Security Testing Methodology Manual from ISECOM, is another recognised methodology, focused on measurable operational security across several channels. And CREST is not a methodology but an accreditation body: it is an international not-for-profit that accredits both penetration testing companies and individual testers against rigorous standards, including in Australasia. A CREST accredited provider has passed an audit of its processes, and its testers hold recognised certifications, which gives a buyer independent assurance of quality. When judging a provider, the combination of a recognised methodology and accreditation such as CREST is a strong signal of a credible, consistent test.

Why the methodology matters when choosing a provider

The methodology is one of the clearest ways to tell a serious penetration test from a superficial one before buying. A provider that follows NIST SP 800-115, PTES or the relevant OWASP guide will cover the right areas systematically and produce a report an organisation can act on and defend to an auditor or client. A provider that cannot name its methodology is a warning sign.

Two practical questions separate a serious provider from the rest. The first is which methodology the provider follows, and whether it fits the target, for example the OWASP Web Security Testing Guide for a web application. The second is what accreditation the firm and its testers hold, with CREST the common benchmark. For regulated work the methodology is not optional: PCI DSS requires a documented, industry accepted methodology, and an IRAP or ISO 27001 context will expect a credible, repeatable approach too. Asking these questions up front is the simplest way to ensure the test is thorough. For an organisation commissioning a penetration test that wants it done to a recognised methodology, Cybernion offers penetration testing.

Frequently asked questions

What is a penetration testing methodology?

A penetration testing methodology is a structured, repeatable process a tester follows so an engagement is thorough, consistent and defensible rather than ad hoc. Recognised methodologies include NIST SP 800-115, the Penetration Testing Execution Standard (PTES), the OWASP testing guides for web, API and mobile, and OSSTMM. They share a common structure, planning and reconnaissance, then discovery, then exploitation, then reporting, and following one is a sign of a credible test.

What are the phases of the NIST penetration testing methodology?

NIST SP 800-115 defines a four-stage methodology, planning, discovery, attack and reporting. Planning sets rules and goals with no testing. Discovery gathers information and analyses vulnerabilities. The attack phase gains access, escalates privileges, browses the system and installs tools, looping back to discovery as new information appears. Reporting runs throughout and produces the final report with findings, risk ratings and remediation guidance.

What are the seven PTES phases?

The Penetration Testing Execution Standard defines seven phases, pre-engagement interactions, intelligence gathering, threat modeling, vulnerability analysis, exploitation, post exploitation, and reporting. They cover the full engagement from scoping and rules of engagement, through reconnaissance and identifying weaknesses, to exploiting them, assessing business impact, and reporting the results. PTES is a widely used community standard for structuring a penetration test.

What is CREST accreditation?

CREST is an international not-for-profit that accredits both penetration testing companies and individual professionals against rigorous standards. A CREST accredited provider has passed an audit of its processes and its testers hold recognised certifications, which gives a buyer assurance of quality and consistency. CREST operates internationally, including in Australasia, and its accreditation is a common way to judge whether a penetration testing provider is credible.

Why does the penetration testing methodology matter?

The methodology matters because it determines whether a test is thorough and repeatable or shallow and inconsistent. A provider that follows a recognised methodology such as NIST SP 800-115, PTES or the OWASP guides will cover the right areas systematically and produce a defensible report, and frameworks like PCI DSS actually require a documented, industry-accepted methodology. When choosing a provider, ask which methodology they follow and whether they hold accreditation such as CREST.


Written by Gaurav Vikash, an ASD endorsed IRAP assessor and senior cyber security leader with 18 years of experience across Australia, the UK and Asia, including CISO and senior security leadership roles. He holds CISSP, CISA, CISM and CRISC and is an ISO 27001 Lead Auditor and ISO 42001 Lead Implementer, and speaks regularly at industry conferences.

Talk to us.

Sources:

  1. NIST SP 800-115, Technical Guide to Information Security Testing and Assessment, National Institute of Standards and Technology, September 2008
  2. The Penetration Testing Execution Standard, PTES, 2026
  3. Web Security Testing Guide, OWASP, 2026
  4. CREST, CREST International, 2026

Last updated: 30 August, 2026

Talk to us about your engagement

A scoped proposal within one business day.