Methodology and Your Practice Lab · Planning and setup
L4. A Repeatable Method: PTES, WSTG and ATT&CK
Follow a repeatable testing methodology and map your work to PTES phases, OWASP WSTG test IDs and MITRE ATT&CK tactics.
Lesson 4 of 21 · About 25 minutes including the lab
By the end of this lesson you can
- List the seven PTES phases and the four NIST SP 800-115 phases.
- Use OWASP WSTG test IDs to plan and record web application checks.
- Map a finding to a MITRE ATT&CK tactic and technique.
- Explain why a methodology beats a list of tools.
Video transcript
Two testers, the same app. Why do they find different things? A methodology is a repeatable sequence of phases, so every test covers the same ground. PTES, the WSTG and MITRE ATT&CK each help with a different part. PTES runs from pre engagement and intelligence gathering through exploitation and reporting. The OWASP Web Security Testing Guide lists test cases for each area of a web app. MITRE ATT&CK names attacker techniques, so the report and the defenders speak the same language. Coverage becomes repeatable and easy to explain to the client. Gaps appear, and two tests of the same app are hard to compare. Pick the phases before you start. Map each test to a WSTG case. Name each technique with its MITRE ATT&CK ID. A method makes your results repeatable. Test yourself in the knowledge check.
Course outlineLesson 4 of 21
Lesson notes
Beginners often learn tools first. Professionals learn a method first, then pick tools for each step. A method makes your work repeatable, lets a client compare tests over time, and stops you from skipping steps when you find something exciting early.
The Penetration Testing Execution Standard (PTES) describes seven phases: pre-engagement interactions, intelligence gathering, threat modeling, vulnerability analysis, exploitation, post-exploitation and reporting. NIST SP 800-115 groups the same work into four phases: planning, discovery, attack and reporting. This course follows that order.
The OWASP Web Security Testing Guide (WSTG) is a detailed checklist for web applications. Each test has an ID, such as WSTG-INFO-02 (fingerprint the web server), WSTG-ATHZ-04 (insecure direct object references) or WSTG-INPV-05 (SQL injection). Recording the IDs you ran shows a reviewer exactly what was covered, and what was not.
MITRE ATT&CK is a knowledge base of real adversary behavior, organized as tactics (the goal, such as Reconnaissance TA0043 or Privilege Escalation TA0004) and techniques (how, such as T1046 Network Service Discovery or T1110 Brute Force). Testers use it to describe their activity in the same language defenders use for detection, which makes it easier for the blue team to check whether they saw you.
The OWASP Top 10 is an awareness document about the most critical web application risk categories. It is useful for prioritizing and explaining, but it is not a testing standard. Use the WSTG for what to test and the OWASP Application Security Verification Standard (ASVS) for what “secure” should look like.
Commands and expected output
How this course maps to the frameworks
Course module PTES phase WSTG category ATT&CK tactic
------------------------------ ---------------------------------- -------------------- --------------------------
Foundations Pre-engagement interactions - -
Recon, scanning, enumeration Intelligence gathering WSTG-INFO, WSTG-CONF TA0043 Reconnaissance, TA0007 Discovery
Web vulnerabilities Threat modeling, vuln analysis WSTG-ATHZ, WSTG-INPV TA0001 Initial Access (T1190)
Auth, passwords, privesc Exploitation, post-exploitation WSTG-ATHN, WSTG-SESS TA0006 Credential Access, TA0004 Privilege Escalation
Reporting and retest Reporting - -This is a reference table, not a command to run. Keep a copy in your notes template so each finding gets a PTES phase, the WSTG test ID you used and the closest ATT&CK technique.
Hands-on labs
Practice only on these legal targets: your own local lab or machines a platform assigns to you. Never use these techniques on systems you do not have written permission to test.
Your local lab
Build your testing checklistOpen the WSTG and copy the test IDs from the Information Gathering (WSTG-INFO) section into your notes template, with a status column: not started, in progress, done, not applicable.
Practice task
Take the finding “a viewer could edit the schedule” from the video scenario. Write down its PTES phase, the matching WSTG test ID and the OWASP Top 10:2025 category it belongs to.
Key takeaways
- PTES: pre-engagement, intelligence gathering, threat modeling, vulnerability analysis, exploitation, post-exploitation, reporting.
- WSTG test IDs make web testing coverage explicit and reviewable.
- ATT&CK tactics are goals; techniques are how. Use them to talk to defenders.
- The OWASP Top 10 is for awareness and prioritization, not a test plan.
Framework mapping
1. Which PTES phase comes immediately after intelligence gathering?
2. What does recording WSTG test IDs in your notes give the client?
3. In MITRE ATT&CK, what is “Privilege Escalation (TA0004)”?
4. Why is the OWASP Top 10 not enough as a test plan?