This guide provides everything you need to understand, scope, and execute this type of testing-with practical guidance you can act on immediately.
PTES: Penetration Testing Execution Standard
PTES provides a comprehensive framework for conducting penetration tests, covering seven phases: pre-engagement interactions, intelligence gathering, threat modelling, vulnerability analysis, exploitation, post-exploitation, and reporting. It's the most commonly referenced methodology in general pentesting and provides detailed technical guidelines for each phase.
OWASP Testing Guide
The OWASP Testing Guide is the standard reference for web application pentesting. It provides detailed test cases organised by category-information gathering, configuration testing, identity management, authentication, authorisation, session management, input validation, error handling, cryptography, business logic, and client-side testing. For web application and API pentesting, OWASP is the methodology auditors most commonly expect.
NIST SP 800-115
NIST Special Publication 800-115 provides guidelines for information security testing and assessment. It's the methodology most commonly referenced in government and healthcare contexts, and it aligns with HIPAA and FedRAMP requirements. NIST SP 800-115 covers planning, discovery, attack execution, and reporting.
Which Methodology to Follow
For web applications and APIs: OWASP Testing Guide. For general infrastructure and network testing: PTES. For healthcare and government: NIST SP 800-115. For cloud environments: CSA Cloud Penetration Testing Playbook alongside the relevant application/infrastructure methodology. Most professional pentest providers combine elements from multiple frameworks based on the engagement scope.
Documenting for Compliance
Your pentest report should reference the methodology followed. Auditors don't mandate a specific methodology in most frameworks, but they do expect a documented, recognised approach. Penetrify documents the testing methodology in every report, referencing OWASP, PTES, and NIST as applicable to the engagement scope.
The Bottom Line
Methodology isn't about choosing the 'right' framework-it's about following a structured, documented approach that ensures comprehensive coverage and satisfies your auditor. The best providers adapt multiple methodologies to your specific environment.