Skip to content
Tutorials Center
My learning

Topics

Lesson 8 of 38 Β· Scoping, Rules and Methodology

Penetration Testing Methodologies and Standards

Tour the main penetration testing methodologies and frameworks: PTES, NIST SP 800-115, OWASP WSTG, OSSTMM and MITRE ATT&CK, and learn how to build your own repeatable process.

A methodology is a repeatable process that makes sure you test the same things the same way every time, and that nothing important is skipped when you are tired or excited by a juicy finding. Several public frameworks exist. None of them is a magic script. They are structured checklists and vocabularies that experienced testers adapt. This lesson surveys the most common ones, shows where they overlap, and helps you build your own simple process.

Why use a methodology

  • Coverage. A list prevents you from forgetting boring but important checks.
  • Repeatability. Two testers on the same system should produce comparable results.
  • Communication. Clients recognize named standards and can map findings to their compliance needs.
  • Training. Juniors learn the shape of the work by following the stages.

The main frameworks

PTES (Penetration Testing Execution Standard)

A community standard that divides an engagement into seven phases: pre-engagement interactions, intelligence gathering, threat modeling, vulnerability analysis, exploitation, post-exploitation and reporting. It is good at describing the whole lifecycle, including the business conversations at both ends.

NIST SP 800-115

The US National Institute of Standards and Technology's Technical Guide to Information Security Testing and Assessment. It describes four phases (planning, discovery, attack, reporting), and also covers techniques such as log review and file integrity checking. It is widely accepted in government and regulated industries.

OWASP Web Security Testing Guide (WSTG)

A detailed, practical catalog of web application and API tests, organized into categories such as information gathering, configuration, identity, authentication, authorization, session management, input validation, error handling, cryptography, business logic, client-side and API testing. It is paired with the OWASP Top 10, a short awareness list of the most critical web risks, and the ASVS, a verification standard with security requirements.

OSSTMM

The Open Source Security Testing Methodology Manual from ISECOM. It is scientific in tone and measures "operational security" in channels such as human, physical, wireless and data networks.

MITRE ATT&CK

Not a testing methodology but a knowledge base of real attacker behavior, organized into tactics (goals such as Initial Access, Persistence, Privilege Escalation, Lateral Movement) and techniques (specific ways to reach them). Testers use it to describe what they did in shared language, and defenders use it to check which techniques they can detect.

Others you will hear about

  • CREST and CHECK guidance (UK) for accredited testers.
  • PCI DSS requirements that name when and how payment environments are tested.
  • Cyber Kill Chain from Lockheed Martin, a seven-stage model of an attack.

Pick the right tool

PTES / NIST Whole engagement lifecycle.
OWASP WSTG Detailed web and API tests.
MITRE ATT&CK Shared names for attacker behavior.
OSSTMM Measuring operational security.

Most testers combine two or three.

1 / 2

A simple process you can adopt

Whatever the framework, the working loop looks similar:

flowchart LR
    P["Plan and scope"] --> R["Recon"]
    R --> S["Scan and enumerate"]
    S --> V["Analyze vulnerabilities"]
    V --> X["Exploit (carefully)"]
    X --> O["Post-exploitation: assess impact"]
    O --> W["Report"]
    W --> T["Retest"]

A merged view of PTES and NIST phases. Chapters 3 to 8 of this course follow it.

For each phase, keep a short written checklist. For example, for scanning: all in-scope hosts discovered, all TCP ports checked, key UDP ports checked, services identified, versions recorded, scan limits logged.

Mapping a finding to frameworks

Good reports tag each finding so that readers can find the standard behind it. Typical tags are an OWASP Top 10 category for web issues, a CWE number (Common Weakness Enumeration) for the weakness class, a CVE identifier for a specific known vulnerability, and an ATT&CK technique ID for behavior. For example, a login form that accepts unlimited password guesses maps to an "authentication failures" category, CWE-307, and the ATT&CK technique for brute force.

Stand-in: a methodology checklist tracker

The first example models the phases as a checklist and reports coverage. It is useful as a personal template.

Python Track coverage of a methodology

Press Run (or Ctrl + Enter) to see the result here.

Program input Β· what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

The second example tags findings with framework references from a small lookup table. The mapping is illustrative; real mappings need a careful read of each framework.

Python Tag findings with CWE and ATT&CK

Press Run (or Ctrl + Enter) to see the result here.

Program input Β· what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Choosing a framework for an engagement

  • Whole network or infrastructure test: PTES or NIST phases, plus ATT&CK for describing techniques.
  • Web application test: OWASP WSTG as the checklist, ASVS if requirements are the goal.
  • Regulated environment: follow whichever standard the regulation names.
  • Detection testing or red team: ATT&CK to plan and score what the defenders caught.

Revisit your process after each job. Add the check you forgot, remove steps that never matter, and keep the checklist short enough to be used.

Check your understanding

Quick check Β· 4 questions

of 4 answered You scored / 4 Β· perfect!

  1. 1. Which resource is a catalog of detailed tests for web applications?

    The WSTG lists web and API tests by category such as authentication, authorization and input validation.
  2. 2. What is MITRE ATT&CK mainly used for?

    It is a knowledge base of adversary behavior, useful for planning tests and checking detection coverage.
  3. 3. Why use a written methodology?

    Checklists reduce omissions and make results comparable, but they do not replace judgment.
  4. 4. What does a CWE number identify?

    CWE is a taxonomy of weakness types. A CVE identifies one specific known vulnerability.

Summary

  • Methodologies give coverage, repeatability, shared language and a way to train newcomers.
  • PTES and NIST SP 800-115 cover the whole lifecycle; OWASP WSTG details web testing; OSSTMM measures operational security; ATT&CK describes attacker behavior.
  • Map findings to OWASP categories, CWE, CVE and ATT&CK IDs in reports.
  • Combine frameworks to fit the engagement and refine your checklist after each job.

Next: Note-Taking and Evidence