PTES
What is PTES?
PTESA community-built penetration testing methodology organizing engagements into seven phases from pre-engagement scoping through reporting and remediation guidance.
The Penetration Testing Execution Standard (PTES) is a community-maintained methodology, hosted at pentest-standard.org, that defines how a professional penetration test should be scoped, executed, and reported. It organizes work into seven phases: Pre-engagement Interactions, Intelligence Gathering, Threat Modeling, Vulnerability Analysis, Exploitation, Post-Exploitation, and Reporting. A deliberate design choice is that the core standard stays tool-agnostic; practical "how" detail — specific commands, payloads, and tooling — lives in a companion PTES Technical Guidelines document rather than the standard itself.
PTES's lasting contribution is the discipline it imposes at the two ends of an engagement. Pre-engagement forces a written scope, explicit rules of engagement, and signed authorization, which is what separates a legal test from unauthorized access. Post-Exploitation forces testers to measure business impact — the value of reachable data, pivot paths, and persistence — instead of stopping at a shell. Because the standard has seen little revision in recent years, mature teams pair it with more frequently updated references: NIST SP 800-115 for process, OWASP WSTG for web-app test cases, OSSTMM for measurement, and MITRE ATT&CK to describe post-exploitation TTPs. Exploitation and post-exploitation iterate — a new foothold feeds back into further exploitation — which is why the model is a loop, not a straight line.
flowchart TD A["Pre-engagement: scope, rules of engagement, authorization"] --> B["Intelligence Gathering"] B --> C["Threat Modeling"] C --> D["Vulnerability Analysis"] D --> E["Exploitation"] E --> F["Post-Exploitation: pivot, persistence, business impact"] F -->|new foothold| E F --> G["Reporting: findings, risk, remediation"]
● Examples
- 01
A consultancy maps every pentest engagement letter back to PTES pre-engagement requirements.
- 02
A red team uses PTES post-exploitation guidance to score impact realistically for the board.
● Frequently asked questions
What is PTES?
A community-built penetration testing methodology organizing engagements into seven phases from pre-engagement scoping through reporting and remediation guidance. It belongs to the Compliance & Frameworks category of cybersecurity.
What does PTES mean?
A community-built penetration testing methodology organizing engagements into seven phases from pre-engagement scoping through reporting and remediation guidance.
How do you defend against PTES?
Defences for PTES typically combine technical controls and operational practices, as detailed in the full definition above.
What are other names for PTES?
Common alternative names include: Penetration Testing Execution Standard.