Compliance
3 min read
SOC 2 penetration test vs vulnerability scan
A vulnerability scan helps identify potential weaknesses across the systems it can inspect. A penetration test investigates selected attack paths within an agreed scope. For SOC 2, the useful question is how those activities support your controls and evidence. Confirm the scope, timing and expectations for your examination before commissioning either.
Vulnerability scans and penetration tests compared
Question | Vulnerability scan | Penetration test |
|---|---|---|
Main purpose | Identify potential weaknesses using automated checks. | Investigate whether selected weaknesses can be used in an attack. |
Typical output | Findings that need validation, prioritisation and remediation. | Tested scenarios, supporting evidence, impact and recommended fixes. |
Coverage limits | Depends on the assets, access and checks configured. | Depends on agreed scope, access, time and testing methods. |
Follow-through | Review findings and verify relevant changes. | Assign remediation owners and agree what needs retesting. |
Both activities need interpretation. A result with no findings does not establish that the system has no weaknesses. NIST SP 800-115 explains how scanning and penetration testing fit into a broader assessment process.
What SOC 2 says about security testing
The AICPA Trust Services Criteria are used to evaluate controls against an organisation's objectives and risks. Their points of focus guide evaluation; they are not a uniform checklist for every business.
A point of focus under CC4.1 includes penetration testing among possible ongoing or separate evaluations. CC7.1 addresses identifying vulnerabilities, with a point of focus covering periodic infrastructure and software scans and scans after significant changes. The criteria do not set one annual penetration test schedule for every organisation.
Your risk assessment, documented controls and commitments determine the work you need to demonstrate. Discuss the proposed testing and evidence with the independent CPA firm conducting your SOC 2 examination. Customer contracts or another applicable standard can add requirements.
Agree the testing scope before you book
Bring these questions to the planning conversation:
Which applications, APIs, networks and cloud environments are in scope?
What access will the tester receive, and which activities need explicit authorisation?
What testing do your policies and customer commitments already promise?
What report, remediation records and retest evidence will you retain?
A useful statement of work records exclusions as well as included systems. Agree the operating constraints, reporting arrangements and handling of sensitive findings before testing starts.
For applications, include the relevant user roles and workflows. The OWASP Web Security Testing Guide explains why automated tools and manual techniques have different coverage, and why a balanced testing approach matters.
Choose a schedule your team can maintain
Record the reasons for your testing frequency and what triggers a review, such as a significant change to an application or its infrastructure. Account for contractual obligations and any other applicable standards. Keep the schedule, asset inventory and responsibility for follow-up together so the policy is practical to operate.
Testing produces work to manage. Give findings an owner, track remediation decisions and retain the evidence of checks or retesting. A report alone does not show what happened afterwards.
Common questions
Can a vulnerability scan replace a penetration test?
They answer different questions. Compare the proposed work with the purpose, scope and commitments behind your testing control. A scan result alone does not establish that a separately promised penetration test was performed.
Does SOC 2 always require an annual penetration test?
There is no single annual schedule in the Trust Services Criteria for every organisation. Determine the relevant controls and testing frequency from your risks and commitments, and discuss the examination evidence with your CPA firm.
Can our compliance platform handle the testing?
Check the actual service scope. Establish who performs the testing, which systems and methods it covers, and what reporting and retesting are included. Confirm how the work and evidence fit your readiness plan.
Plan the work around your assessment
Our compliance readiness service helps coordinate gaps, controls and evidence. Our penetration testing and VAPT service covers testing agreed for your environment. The independent CPA firm's SOC 2 examination and report are separate from this preparation work.
Start with a free security review to discuss your requirements, current controls and priorities.
Want this looked at for real?
Get a free security review and we will show you where you actually stand.