Home / Glossary / Penetration test
Glossary, read 12 Nov 2026
Penetration test in a SOC 2 examination, defined with a sourced example
The definition of Penetration test
Auditors usually ask for the most recent penetration test report and proof that the findings were tracked to closure. The report should name the tester, the date, the scope and the severity of each finding. A test of the marketing site while the product runs elsewhere will not satisfy a reviewer who reads the system description.
The usual error is calling a vulnerability scan a penetration test. NIST treats them as different techniques: a scan identifies known weaknesses on hosts, while a test attempts to exploit them. Another is scoping out production. NIST SP 800-115 says penetration testing poses a high risk because it uses real exploits against production systems, and that, because of its high cost and potential impact, testing on an annual basis may be sufficient.
NIST SP 800-53 control CA-8 simply says to conduct penetration testing at a defined frequency on defined systems. What the auditor checks is that you defined that frequency, ran the test within it, and fixed the high findings with dated tickets. Keep the tester's report, the retest result and the ticket links together, because the auditor will ask for all three in one request.
A sourced example
NIST SP 800-115 section 5.2.1 describes the first phase this way: "In the planning phase, rules are identified, management approval is finalized and documented, and testing goals are set." It adds that no actual testing occurs in that phase. For a SOC 2 file, the signed rules of engagement from this phase are the first piece of evidence. NIST SP 800-115, read 12 Nov 2026.
Related terms
Sources
- NIST SP 800-115, read 12 Nov 2026
- NIST CSRC glossary, penetration testing, read 12 Nov 2026
- NIST SP 800-53 Rev. 5 control catalog (OSCAL), read 12 Nov 2026
Last reviewed 12 Nov 2026.