Penetration Testing
A simulated cyberattack conducted to identify vulnerabilities in systems, networks, or applications before they can be exploited by malicious actors.
On this page
What is Penetration Testing?
Penetration testing (pen testing) involves authorized security professionals attempting to exploit vulnerabilities using techniques similar to real attackers. Types include external testing (targeting internet-facing systems), internal testing (simulating insider access), web application testing, API testing, and social engineering testing. Results identify exploitable vulnerabilities, misconfigurations, and control weaknesses. Regular penetration testing is required by standards including PCI DSS and recommended by frameworks like NIST and ISO 27001.
Application to Vendor Screening
For vendors with access to your systems or handling sensitive data, penetration testing is an important security assurance mechanism. Organizations should review vendor pen test results, require vendors to remediate identified vulnerabilities, and potentially include vendor systems in their own testing scope.
Practical Examples
- Reviewing a vendor's annual penetration test report and remediation evidence
- Requiring a vendor to conduct penetration testing before go-live
- Including vendor API endpoints in your organization's penetration testing scope
Frequently Asked Questions
How often should vendors conduct penetration testing?
At least annually for vendors handling sensitive data or providing critical services. Additional testing should follow significant changes to systems or applications. PCI DSS requires annual testing and after significant changes.
What is the difference between penetration testing and vulnerability scanning?
Vulnerability scanning is automated detection of known weaknesses. Penetration testing involves skilled professionals attempting to actively exploit vulnerabilities, testing defenses, and chaining findings to demonstrate real-world attack impact.