PTES
The Penetration Testing Execution Standard (PTES) modelled for the organisation buying or auditing a penetration test: define and authorise the scope in writing, agree the goals and how risk will be scored, obtain permission to test and any third-party and legal consent, set the rules of engagement (including for disruptive testing and social engineering), keep clear lines of communication and incident handling, make sure intelligence gathering, threat modelling, vulnerability analysis and exploitation stay within what was authorised and are recorded, protect and then destroy the engagement data, document and reverse every change, and require reporting that ties findings to business risk with credentials and sensitive content protected.
PTES is a compliance framework from International (community standard) with 5 domains and 18 controls that map to 129 other frameworks. The largest domains are Conduct of the test: what the commissioning organisation must ensure is governed – PTES (5 controls), Pre-engagement: scope, authorisation and rules of engagement – PTES (4 controls), Communication and incident handling during the test – PTES (3 controls). Every control below carries what it requires and what an assessor expects to see.
Get the official standard. This page is a source-grounded companion to the published text, not a replacement for it.
Visit pentest-standard.orgFramework summaries on this platform are interpretations grounded in the published source, for educational and compliance planning purposes. They do not reproduce or replace the official standards. Refer to the authoritative source for the definitive text. Framework names and trademarks belong to their respective organisations.
Framework Domains (5)
Communication and incident handling during the test – PTES
| Code | Title |
|---|---|
| ptes::PTES-2.1 | Establish lines of communication and an emergency contact list |
| ptes::PTES-2.2 | Agree incident handling and the interaction with the organisation's response team |
| ptes::PTES-2.3 | Encrypt sensitive communications and the final report in transit |
Conduct of the test: what the commissioning organisation must ensure is governed – PTES
| Code | Title |
|---|---|
| ptes::PTES-3.1 | Keep intelligence gathering within scope and the rules of engagement |
| ptes::PTES-3.2 | Require a consistent, repeatable threat model tied to the organisation's assets |
| ptes::PTES-3.3 | Scope vulnerability analysis to the agreed depth and breadth |
| ptes::PTES-3.4 | Ensure exploitation and confirmation stay authorised, planned and least-disruptive |
| ptes::PTES-3.5 | Benchmark detection and response only as agreed, and record what was detected |
Evidence, data protection and post-test cleanup – PTES
| Code | Title |
|---|---|
| ptes::PTES-4.1 | Protect and, where required, avoid holding the organisation's sensitive data |
| ptes::PTES-4.2 | Encrypt, control and destroy engagement data and evidence |
| ptes::PTES-4.3 | Document every change and require a controlled cleanup and restoration |
Pre-engagement: scope, authorisation and rules of engagement – PTES
| Code | Title |
|---|---|
| ptes::PTES-1.1 | Define and record the scope in writing before testing |
| ptes::PTES-1.2 | Record the goals and the metrics used to grade risk |
| ptes::PTES-1.3 | Obtain written permission to test and address legal and third-party consent |
| ptes::PTES-1.4 | Agree the rules of engagement: how, when and where testing occurs |
Reporting – PTES
| Code | Title |
|---|---|
| ptes::PTES-5.1 | Require an executive summary that ties findings to business risk |
| ptes::PTES-5.2 | Require a technical report with evidence, impact and remediation |
| ptes::PTES-5.3 | Protect credentials and sensitive content in the report |
Your Compliance Coverage
If you comply with PTES, you already cover:
NIST SP 800-53 Rev 5
30%
14 controls mapped
Compare →ISO 27002:2022
26%
12 controls mapped
Compare →NIST SP 800-115 (Technical Guide to Information Security Testing and Assessment)
23%
11 controls mapped
Compare →+ 126 more: PCI DSS 4.0 (11%), NIST SP 800-124 Revision 2 - Guidelines for Managing the Security of Mobile Devices (9%)
See all 129 mapped frameworks ↓Maps to 129 other frameworks
Coverage is not the same as your position
This page shows what PTES overlaps with in general. Where your organisation actually stands, against the standard you are going for and the certifications you already hold, is a different question. Same graph and the same recorded refutations, scoped to you rather than to a pair.
The Compliance Position Diagnostic, $5,000 fixed, ten business daysWhat is PTES and who does it apply to?
PTES is a compliance framework from International (community standard) with 5 domains and 18 controls. The Penetration Testing Execution Standard (PTES) modelled for the organisation buying or auditing a penetration test: define and authorise the scope in writing, agree the goals and how risk will be scored, obtain permission to test and any third-party and legal consent, set the rules of engagement (including for disruptive testing and social engineering), keep clear lines of communication and incident handling, make sure intelligence gathering, threat modelling, vulnerability analysis and exploitation stay within what was authorised and are recorded, protect and then destroy the engagement data, document and reverse every change, and require reporting that ties findings to business risk with credentials and sensitive content protected. It is used by organisations to establish and maintain compliance with industry standards and regulatory requirements.
What does PTES actually require?
PTES has 18 controls organised across 5 domains. The largest domains are Conduct of the test: what the commissioning organisation must ensure is governed – PTES (5 controls), Pre-engagement: scope, authorisation and rules of engagement – PTES (4 controls), Communication and incident handling during the test – PTES (3 controls). Each control defines specific requirements that organisations must implement to achieve compliance.
If I already comply with another framework, how much of PTES do I already cover?
PTES maps to 129 other compliance frameworks. The top mapping partners are NIST SP 800-53 Rev 5 (30% coverage), ISO 27002:2022 (26% coverage), NIST SP 800-115 (Technical Guide to Information Security Testing and Assessment) (23% coverage). Use our comparison tool to explore control-level mappings between frameworks.
How do I implement PTES?
Start your PTES compliance journey by running a self-assessment on our platform to identify your current compliance posture. Our AI advisory can answer specific questions about PTES requirements, and cross-framework mapping helps you leverage existing controls from other frameworks you may already comply with. Create a free account to access all 18 controls and track your progress.
Start Your Compliance Journey
Create a free account to run self-assessments, get AI advisory, and track your compliance progress across 1,120 frameworks.
Get Started Free →Free forever, no credit card required