$loading...
Interactive flowchart of penetration testing methodology based on OWASP, PTES, and OSSTMM frameworks. Each phase links to the Payload Playground tools you need.
Gather intelligence about the target. Map the attack surface using passive and active information gathering techniques before making direct contact.
Actively probe the target to discover open ports, services, misconfigurations, and exposed endpoints. Build a detailed map of the attack surface.
Analyze discovered services and endpoints for known vulnerabilities, misconfigurations, and logic flaws. Prioritize findings by severity and exploitability.
Prove the vulnerability is real by exploiting it in a controlled manner. Generate targeted payloads and demonstrate impact without causing damage.
After initial access, escalate privileges, maintain persistence, and pivot to other systems. Encode payloads to evade detection.
Document every finding with evidence, severity scores, and remediation advice. A clear report turns technical findings into actionable business decisions.
Rushing to exploitation is the most common mistake. Thorough reconnaissance and scanning often reveal low-hanging fruit that would be missed otherwise. Each phase builds on the previous one — skipping steps means missing vulnerabilities.
Take screenshots, save request/response pairs, and log timestamps during testing. Reconstructing findings from memory after the engagement leads to incomplete reports and missed details. Use the HTTP Parser to save raw requests as you work.
Clients take findings more seriously when they include standardized severity ratings. Use the CVSS Calculator to score each finding consistently. A CVSS 9.8 critical hits differently than saying "this is bad."
Individually, an IDOR, a missing CSRF token, and an open redirect might each be medium severity. Chained together, they can become account takeover. Always look for ways to combine findings for maximum demonstrated impact.