Home / Glossary / Vulnerability scan
Glossary, read 12 Nov 2026
Vulnerability scan in a SOC 2 examination, defined with a sourced example
The definition of Vulnerability scan
SOC 2 reviewers look for scans that run on a schedule and for proof that someone reads them. Control RA-5 in NIST SP 800-53 asks you to monitor and scan at a defined frequency and when new vulnerabilities are reported, then analyze the results and remediate. A scan report with 400 open items and no tickets is worse evidence than a shorter report with owners and dates.
Teams get two things wrong. They accept the severity the scanner assigns. NIST SP 800-115 says assessors should determine the appropriate risk level for each vulnerability and not simply accept scanner ratings. They also scan only the cloud account and skip laptops, containers and third-party libraries that hold the same data.
The auditor's sample is usually one or two scan runs from inside the observation window, plus the tickets for a few high-severity findings. Keep run dates, scope lists and the closure trail in one place. Expect the auditor to ask how you decided which findings to fix first, so write the severity rule down before the window opens, not after the first finding arrives.
A sourced example
NIST SP 800-115 gives an example of why scanner ratings need a human: a scanner might label an FTP server a moderate risk because it transmits passwords in cleartext, but if the server is an anonymous public server that uses no passwords, the actual risk might be considerably lower. The assessor sets the final risk level. NIST SP 800-115, read 12 Nov 2026.
Related terms
Sources
- NIST SP 800-115, read 12 Nov 2026
- NIST CSRC glossary, vulnerability scanning, read 12 Nov 2026
- NIST SP 800-53 Rev. 5 control catalog (OSCAL), read 12 Nov 2026
Last reviewed 12 Nov 2026.