Penetration Testing.

Penetration testing ("pentesting") is a goal-driven security assessment in which qualified testers attempt to breach an organization's defenses using the same tools and techniques as real attackers. Engagements have a defined scope, rules of engagement, and written authorization, and can target networks, web and mobile applications, cloud workloads, APIs, physical sites, or people via social engineering.

Methodologies. Mature pentests follow published standards rather than ad-hoc poking: the PTES (Penetration Testing Execution Standard) defines seven phases from pre-engagement to reporting; NIST SP 800-115 is the U.S. technical guide; the OWASP Web Security Testing Guide (WSTG) and OSSTMM cover web and operational testing. Testers are often certified through OSCP, GPEN, or CREST.

Depth vs. scanning. Unlike an automated vulnerability scan, a pentest proves exploitability by chaining findings to demonstrate business impact. A classic chain uses an exposed edge device — for example the Log4Shell flaw (CVE-2021-44228) or a vulnerable VPN/firewall appliance — for initial access, then Kerberoasting or credential reuse for lateral movement toward domain admin. On the web side, an IDOR chained with stored XSS can escalate to full admin takeover.

Output and limits. A pentest is a point-in-time snapshot; a report ranks findings by severity with reproduction steps and remediation, validating existing controls and supporting PCI DSS, HIPAA, SOC 2, and ISO 27001 compliance. It complements, but does not replace, continuous scanning and red-team exercises.

flowchart TD
  A[Scoping & Rules of Engagement] --> B[Reconnaissance / OSINT]
  B --> C[Scanning & Enumeration]
  C --> D[Exploitation: prove access]
  D --> E[Post-Exploitation: privesc & lateral movement]
  E --> F{Objective reached?}
  F -->|No| C
  F -->|Yes| G[Reporting & Remediation guidance]