International (community standard)

PTES

50 controls. 138 other frameworks in our corpus share controls with it. Here is all of it, and how much of it you are already doing.

Page built . This page is derived from the framework corpus, which changes when the corpus is extended rather than daily.

50 controls 138 frameworks share controls with it International (community standard) verified against its source document

Every control below is one this framework asks for. The right hand column counts how many other frameworks in our corpus carry the same control, which is the difference between doing this work once and doing it again for the next standard.

There is no implementation kit for this framework yet. The control list and the overlap above are free and complete.

What you already have

Frameworks whose controls overlap this one, most first. If you run any of them, the count is roughly what you have already evidenced.

Every control

CodeControlAlso in
PTES-EX-1Exploitation Planning0
PTES-EX-2Countermeasure Evasion and Anti Forensics0
PTES-EX-3Customized Exploitation0
PTES-INT-1Passive Intelligence Gathering0
PTES-INT-2Active Information Gathering0
PTES-INT-3Human Intelligence and Footprinting0
PTES-POST-1Post Exploitation Pivoting0
PTES-POST-2Persistence Mechanisms0
PTES-POST-3Data Exfiltration and Impact Demonstration0
PTES-POST-4Cleanup0
PTES-PRE-1Engagement Scope Definition0
PTES-PRE-2Rules of Engagement0
PTES-PRE-3Goals and Success Criteria0
PTES-REP-1Executive Summary0
PTES-REP-2Technical Findings0
PTES-REP-3Remediation Roadmap and Retesting0
PTES-TM-1Business Asset Analysis0
PTES-TM-2Threat Agents and Capabilities0
PTES-TM-3Threat Capability Mapping0
PTES-VA-1Vulnerability Analysis Approach0
PTES-VA-2Active and Passive Testing0
PTES-VA-3Research and Identification0
PTESPHASE-1Pre-Engagement Interactions and Scoping102
PTESPHASE-2Intelligence Gathering (OSINT)77
PTESPHASE-3Threat Modeling62
PTESPHASE-4Vulnerability Analysis37
PTESPHASE-5Exploitation0
PTESPHASE-6Post Exploitation0
PTESPHASE-7Reporting and Cleanup0
PTES-1.1Define and record the scope in writing before testing4
PTES-1.2Record the goals and the metrics used to grade risk2
PTES-1.3Obtain written permission to test and address legal and third-party consent2
PTES-1.4Agree the rules of engagement: how, when and where testing occurs2
PTES-2.1Establish lines of communication and an emergency contact list1
PTES-2.2Agree incident handling and the interaction with the organisation's response team2
PTES-2.3Encrypt sensitive communications and the final report in transit2
PTES-3.1Keep intelligence gathering within scope and the rules of engagement2
PTES-3.2Require a consistent, repeatable threat model tied to the organisation's assets2
PTES-3.3Scope vulnerability analysis to the agreed depth and breadth3
PTES-3.4Ensure exploitation and confirmation stay authorised, planned and least-disruptive2
PTES-3.5Benchmark detection and response only as agreed, and record what was detected2
PTES-4.1Protect and, where required, avoid holding the organisation's sensitive data1
PTES-4.2Encrypt, control and destroy engagement data and evidence3
PTES-4.3Document every change and require a controlled cleanup and restoration2
PTES-5.1Require an executive summary that ties findings to business risk2
PTES-5.2Require a technical report with evidence, impact and remediation2
PTES-5.3Protect credentials and sensitive content in the report1
SCOPE-NOTEWhat this framework covers and does not cover0
STANDARDThe Penetration Testing Execution Standard and its seven sections0
STATUSVersion, licence and status; the superseded batch nodes0

Tell me when PTES files something new

One email when a public company newly discloses something this framework governs, naming the company and what our corpus says it puts in scope. Nothing else, and one click to stop.

What this page is

A control-level reference for PTES, drawn from our framework corpus. Control codes and titles are references to the standard, not reproductions of it. The overlap counts and the auditor artefacts are our own work and are the part you will not find elsewhere.

Measure this against what you already run · All frameworks · Today's edition