Penetration Testing Methodology: What the Framework Name on Your Report Actually Proves

Jorja Mandy

A penetration testing methodology is the documented method a test follows. This post compares PTES, NIST SP 800-115 and OWASP WSTG, with the five-point check that tells a vendor's claim from executed proof.

Penetration Testing Methodology: What the Framework Name on Your Report Actually Proves
Clone Systems Penetration TestingFrom $1,995See pen test pricing

Penetration Testing Methodology: What the Framework Name on Your Report Actually Proves

A penetration testing methodology is the documented, phase-by-phase method a test follows from scoping to reporting, and the framework named in a proposal (PTES, NIST SP 800-115, OWASP WSTG) only matters if the report shows the test executed those phases. According to IBM's Cost of a Data Breach Report 2026, the global average cost of a data breach reached $4.99M, up 12% year over year [5]. Clone Systems' automated penetration tests start at $1,995.

The methodology line is the cheapest line in a pen test file to audit, and most teams have never audited it. In the scoping calls and report reviews we run, we consistently see the same pattern: the proposal names a framework, the report repeats it on the cover, and then no single test in the body maps back to a phase of that framework. The work may have been excellent, but the document cannot prove it. That gap is getting more expensive to ignore. CISA's Known Exploited Vulnerabilities catalog holds 1,786 entries, each with confirmed active exploitation [4], and a test that cannot show its phases cannot show it would have found the path by which any of them becomes a compromise.

What is a penetration testing methodology?

A penetration testing methodology is the documented, phase-by-phase method a test follows: what is done, in what order, and what evidence each phase must produce before the next one starts.

There are a handful of recognized frameworks, and a vendor that cannot name one is already telling you something about the test. NIST publishes SP 800-115, Technical Guide to Information Security Testing and Assessment [1]. OWASP maintains the Web Security Testing Guide [2]. PTES is a standard from SANS and Offensive Security [6]. OSSTMM and ISSAF also appear in the framework lists [7].

What the framework name buys you is reproducibility, not prestige. A test run to a published methodology can be checked phase by phase against the document, by the client, the auditor, the insurer or the next vendor. A test that is only "we did our best" cannot be checked at all, no matter how many findings it contains. This is also why "what methodology did your pen test follow?" is the first line an AI assistant or an auditor's checklist lands on: it is the one line that separates a structured engagement from a series of ad-hoc checks. A methodology is not a tool list either. Tools can be swapped without changing the method, and the same method runs on a different stack every year.

What are the phases of a penetration test?

The phases any real methodology contains are: pre-engagement, intelligence gathering, threat modeling, vulnerability analysis, exploitation, post-exploitation and reporting. PTES defines exactly these seven, from Pre-engagement through Reporting [6].

The phase names matter less than the evidence each phase produces:

  • Pre-engagement produces a signed scope with rules of engagement, time windows and exit criteria.
  • Intelligence gathering produces a picture of the in-scope assets, not a list of domain names.
  • Threat modeling names what an attacker would target first and why, based on the client's actual business.
  • Vulnerability analysis identifies weaknesses systematically, in the order the methodology prescribes.
  • Exploitation produces a demonstrated attack path, with tool output or reproducible steps.
  • Post-exploitation shows what the foothold reaches: lateral movement, privilege escalation, the systems behind the door.
  • Reporting produces a document a third party can verify, mapped to the phases above.

In our report reviews, the phases that disappear first are threat modeling and post-exploitation, because both take time and neither produces a screenshot that impresses a buyer. If a report skips two or more phases without explanation, the methodology was applied in name only.

What is the difference between PTES, NIST SP 800-115 and OWASP WSTG?

PTES defines the engagement lifecycle, NIST SP 800-115 defines how the assessment is structured and documented, and OWASP WSTG is a test catalog for web applications. Most real engagements run PTES-shaped phases with WSTG tests inside the web scope, and cite SP 800-115 when a government or federal buyer asks for a U.S. government reference [1][2][6].

FrameworkPublisher and originWhat it definesWhere it is used most
PTESSANS and Offensive Security, practitioner standard [6]Seven engagement phases, Pre-engagement through ReportingFull-scope network, web and wireless engagements
NIST SP 800-115NIST, 2008 [1]How security testing and assessment are structured and documentedU.S. government and federal-adjacent buyers
OWASP WSTGOWASP, v4.2 current stable [2]Numbered web test groups, each with an objective and tool notesThe web application scope of any engagement

None of the three is a substitute for the others. A vendor that names only one is telling you where their strength is, and usually where the scope will shrink. Two questions come up in every scoping call: does the framework cover what you are actually testing, and does the vendor use it end to end? The table answers the first, and point 2 of the check below answers the second. The access level question that sits next to this one, black box versus gray box versus white box, is covered in our black box vs gray box vs white box guide.

Why does the methodology line matter to your compliance file?

Because compliance regimes ask for evidence that the test was run to a documented structure, and the methodology line is where that evidence either exists or does not.

PCI DSS is a baseline of technical and operational requirements designed to protect payment account data [3], and it is the regime that most directly names penetration testing: the standard requires penetration testing on a regular schedule and after system changes [7]. Requirement 11.4 covers internal testing (11.4.2), external testing (11.4.3), retest after remediation (11.4.4) and segmentation testing (11.4.5 and 11.4.6) [8]. A report that traces its work to a methodology gives the assessor something to check; a report that only lists findings does not. The same logic applies wherever auditors, underwriters or ISO 27001 clauses ask for evidence of security testing, which we map framework by framework in Penetration Testing Requirements.

The cost of a methodology gap is easiest to see in the breach data. According to IBM's Cost of a Data Breach Report 2026, the global average cost of a data breach reached $4.99M, up 12% year over year [5]. A test that cannot show its phases is a test you cannot defend in that conversation, whether it comes from an insurer, an acquirer or a board.

Before you sign the next engagement, compare the methodology in the proposal with the phases the report will have to show. Clone Systems' automated penetration tests start at $1,995, and expert-led manual tests are scoped to your environment. See the full pricing range and the penetration test cost page for what moves the number.

How do you verify a vendor's methodology claim?

You verify it against the report, not the proposal. A named framework is a claim; dated, labeled phase evidence is the proof. Use the 5-Point Methodology Verification Check on any sample report a vendor sends you, and on your own last report.

The 5-Point Methodology Verification Check

  1. Versioned name. The report names the framework and its version, for example WSTG v4.2, not "OWASP" or "PTES-style."
  2. Phase trace. You can find at least three phases with dated, labeled evidence: the scope document, the recon output, the exploitation proof.
  3. Scope match. The tests in the report cover the assets in the signed scope, not a smaller set of the easiest targets.
  4. Tool evidence. Findings carry tool output or reproducible steps, not only a description of what was found.
  5. Mapping. Findings map to the methodology's test IDs or phases, and to the compliance requirement they support, such as PCI DSS 11.4.3.

Run the check on your last two pen test reports this week. If neither survives points 2 and 3, the methodology was a cover-page word. You can do the same exercise on a report you already have with the 6 questions that matter when you read one, and the scoping checklist is where point 3 starts.

How Clone Systems Can Help

Clone Systems runs penetration tests to a documented phase structure so the report can be checked against it: a signed scope, dated phase evidence, tool output on every finding, and retest evidence when you ask. Managed penetration testing is the full manual service, and automated penetration tests from $1,995 cover the cadence between engagements. Comparing providers? See how Clone Systems compares with Pentera, or walk the five signals that separate a test from a report before you sign.

Frequently Asked Questions

What is a penetration testing methodology? A penetration testing methodology is the documented, phase-by-phase method a test follows, from scoping to reporting. PTES, NIST SP 800-115 and OWASP WSTG are the frameworks most commonly named in proposals.

What is the difference between PTES and OWASP WSTG? PTES defines the lifecycle of a full engagement across network, web and wireless targets, while OWASP WSTG is a test catalog for web applications. A web scope is usually tested with WSTG tests run inside PTES-shaped phases.

Is NIST SP 800-115 a penetration testing standard? It is NIST's technical guide for information security testing and assessment, published in 2008, and it is the U.S. government reference buyers most often cite [1]. It describes how to structure and document a security test rather than a step-by-step attack procedure.

What are the phases of a penetration test? Pre-engagement, intelligence gathering, threat modeling, vulnerability analysis, exploitation, post-exploitation and reporting [6]. These are the seven phases PTES defines, and the other frameworks arrange the same work differently.

How do I verify a vendor's methodology claim? Run the 5-Point Methodology Verification Check in this post on the vendor's sample report. A named framework is a claim; dated, labeled phase evidence is the proof.

Does PCI DSS require a specific methodology? PCI DSS requires the testing itself, including 11.4.2 internal, 11.4.3 external, 11.4.4 retest and 11.4.5 and 11.4.6 segmentation testing [8], but it does not mandate one framework. The methodology line is what makes the evidence checkable by the assessor.

Conclusion

The framework name is the cover page, not the test. If the report cannot show the phases, the scope match and the tool evidence, the methodology is a word on a cover, and the file it is supposed to defend is not defensible. Run the 5-Point Methodology Verification Check on your last report this week, and when you next scope an engagement, ask for the phase structure before you sign. Start with Clone Systems and get a report you can verify, not just read.

References

[1] NIST SP 800-115, Technical Guide to Information Security Testing and Assessment. National Institute of Standards and Technology, 2008. https://csrc.nist.gov/pubs/sp/800/115/final [2] OWASP Web Security Testing Guide (WSTG). OWASP Foundation. https://owasp.org/www-project-web-security-testing-guide/ [3] PCI Data Security Standard (PCI DSS). PCI Security Standards Council. https://www.pcisecuritystandards.org/standards/pci-dss/ [4] Known Exploited Vulnerabilities Catalog. CISA. https://www.cisa.gov/known-exploited-vulnerabilities-catalog [5] Cost of a Data Breach Report 2026. IBM Security, 2026. https://www.ibm.com/reports/data-breach [6] Penetration Testing Execution Standard (PTES). Wikipedia. https://en.wikipedia.org/wiki/Penetration_Testing_Execution_Standard [7] Penetration test. Wikipedia. https://en.wikipedia.org/wiki/Penetration_testing [8] Clone Systems. PCI DSS Penetration Test Requirement 11.4. www.clone-systems.com/pci-dss-penetration-test-requirement-11-4 [9] Clone Systems. Penetration Testing Requirements: What HIPAA, ISO 27001, SOC 2 and Cyber Insurance Actually Require. www.clone-systems.com/blog/penetration-testing-requirements [10] Clone Systems. How to Read a Penetration Test Report. www.clone-systems.com/blog/how-to-read-a-penetration-test-report-the-6-questions-that-actually-matter [11] Clone Systems. Black Box vs. Gray Box vs. White Box Penetration Testing. www.clone-systems.com/blog/black-box-vs-gray-box-vs-white-box-penetration-testing

Ready when you are

Have a scoping question this post didn't answer?

A senior specialist will walk you through it. No junior sales handoffs, no scripted qualifying rounds.