A bare-metal SaaS company already paying for Datadog asked us before its first SOC 2 audit: Can Datadog be our vulnerability scanner of record, or do we need Nessus too? Datadog can be the scanner of record for every server and container with the Datadog Agent installed. Firewalls, switches, hypervisors and server management controllers (BMCs) need a different method, so an on-prem SOC 2 program typically pairs one agent-based tool for hosts (Datadog or Wazuh) with a periodic network scan (Nessus or similar) for everything else.
At a glance
- SOC 2 criterion: CC7.1 asks for detection of new vulnerabilities; its point of focus calls for periodic scans, scans after significant changes and timely remediation.
- Datadog Cloud Security Vulnerabilities: Agent-based on-prem; covers hosts, host images and containers running the Datadog Agent.
- Wazuh vulnerability detection: Open source, agent-based; the same agent also feeds SIEM and file integrity monitoring.
- Nessus: Network scanner with credentialed checks for servers, firewalls, switches, VMware and storage APIs.
- The gap agents leave: Network gear, hypervisors such as ESXi, BMCs (iDRAC, iLO), storage arrays and UPS cards.
- Common setup: One agent for hosts plus a scheduled network scan of everything else in scope.
What Does SOC 2 Require From a Vulnerability Scanner?
SOC 2 requires a vulnerability scanning process that covers every in-scope asset and produces dated evidence, and it leaves the choice of tool to the company. Criterion CC7.1 reads: To meet its objectives, the entity uses detection and monitoring procedures to identify (1) changes to configurations that result in the introduction of new vulnerabilities, and (2) susceptibilities to newly discovered vulnerabilities. Its point of focus Conducts Vulnerability Scans calls for scans on a periodic basis and after significant changes are made to the environment, and for timely remediation of identified deficiencies.
An auditor tests five things against the scanner of record:
| SOC 2 scanner requirement | What the auditor checks |
| Coverage | Every in-scope asset in the inventory appears in scan results, including network devices and hypervisors |
| Depth | Authenticated or agent-based checks on servers, beyond an external port scan |
| Frequency | Scans at the cadence the policy states, plus after significant changes |
| Dated reports | Scan output with timestamps across the observation period |
| Remediation tracking | Tickets for findings, closed within the policy's SLAs, or a documented risk acceptance |
The SOC 2 vulnerability scanning guide for on-prem servers covers the tiered scan cadence and remediation SLAs.
Datadog vs Wazuh vs Nessus for SOC 2: Side-by-Side Comparison
Datadog, Wazuh and Nessus each meet CC7.1 for the assets they can see, and each sees a different set. Datadog and Wazuh read package inventory from an agent on each host; Nessus scans over the network.
| Datadog Cloud Security Vulnerabilities | Wazuh vulnerability detection | Nessus (Tenable) | |
| How it finds vulnerabilities | Datadog Agent on each host reports OS packages; matched to CVEs | Wazuh agent (Syscollector) reports installed packages; server matches to CVEs | Network scan, with credentialed checks over SSH, Windows, SNMP or vendor APIs |
| On-prem Linux and Windows servers | Yes, with the Agent | Yes, with the agent | Yes, credentialed scan |
| Containers and images | Yes | Host packages only; container image scanning is outside its documented scope | Limited to what the scan reaches |
| Firewalls, switches, routers | No vulnerability detection (Network Device Monitoring covers metrics and config changes) | No vulnerability detection (agentless monitoring covers config and commands over SSH) | Yes, credentialed checks on Cisco, Palo Alto, F5, Fortinet and others |
| VMware ESXi or vCenter | No; ESXi is absent from the Agent's supported platforms | No; ESXi is absent from the agent's supported platforms | Yes, VMware ESX SOAP API and vCenter credentials |
| BMCs (iDRAC, iLO), UPS and PDU cards | No | No | Unauthenticated network checks on reachable IPs |
| Also does | Monitoring, SIEM, cloud posture | SIEM, file integrity monitoring, configuration assessment | Configuration compliance audits |
| Remediation tickets | Jira ticket creation | Alerts; tickets through a custom integration | Exports; tickets through Tenable platform or manual |
| Licence model | Commercial SaaS | Open source, self-hosted | Commercial |
What Datadog Cloud Security Vulnerabilities Covers On-Prem
Datadog Cloud Security Vulnerabilities scans hosts, host images and container images through the Datadog Agent, which Datadog documents as supported on-prem. Its agentless scanning covers AWS, Azure and GCP only, so a bare-metal environment relies on the Agent (version 7.46 or later, with host SBOM collection enabled).
The gap is every device without an Agent. Datadog Network Device Monitoring collects SNMP metrics and tracks configuration changes on routers, switches and firewalls, and its documentation describes no CVE detection for those devices. The Datadog Cloud Security Management guide covers setup, severity scoring and evidence exports.
What Wazuh Vulnerability Detection Covers
Wazuh vulnerability detection covers every endpoint with the Wazuh agent. The agent's Syscollector module sends the package inventory to the Wazuh server, which flags a package when its version falls within the affected range of a CVE and re-evaluates every agent when CVE content updates.
Two Wazuh details are relevant on-prem:
- Offline feed. Wazuh can use a locally hosted copy of its vulnerability repository, which suits networks with restricted outbound access.
- Agentless monitoring is a separate feature. Wazuh connects over SSH to routers, firewalls and switches to monitor configuration and command output. That supports CC7.1 change detection, and the documentation treats it as monitoring, separate from vulnerability detection.
Wazuh has no licence fee and the highest operating effort, since the team operates the Wazuh server, indexer and dashboard. The SOC 2 logging and SIEM guide for bare metal covers the SIEM side of the same deployment.
What Nessus Covers That Agent-Based Scanners Miss
Nessus covers any device it can reach over the network, so it fills the gap agent-based scanners leave on-prem. Tenable documents credentialed checks for targets beyond standard Windows, macOS and Linux, such as network appliances and management APIs.
Credentialed coverage relevant to a bare-metal SOC 2 scope:
- SSH-based appliances: Cisco hardware, Palo Alto firewalls, F5 BIG-IP and Fortinet
- Management APIs: VMware vCenter, VMware ESX SOAP API, NetApp API, Nutanix Prism and Palo Alto PAN-OS over HTTPS
- Servers: Linux over SSH and Windows over SMB
Devices with no supported credential type, such as most BMCs and UPS network cards, still get unauthenticated checks of their listening services. Nessus scans can be scheduled, and dated reports export to PDF, HTML or CSV for the auditor.
Which On-Prem Assets Do Agent-Based Scanners Miss for SOC 2?
Agent-based scanners miss every in-scope device built on vendor firmware with no agent package. In a typical bare-metal scope:
- Edge and internal firewalls
- Core and top-of-rack switches, and routers
- Hypervisor hosts such as VMware ESXi (Linux-based hypervisors such as Proxmox or KVM hosts can run a Linux agent)
- Server BMCs: Dell iDRAC, HPE iLO, Supermicro IPMI
- Storage arrays and their controllers
- UPS and PDU management cards, and out-of-band console servers
These devices hold some of the highest-impact vulnerabilities in a data center. A BMC gives full control of a server below the operating system, and a firewall CVE can expose the whole network.
Watch out
Any in-scope device left out of scanning can become an audit exception.
SOC 2 auditors reconcile the in-scope asset inventory against scan results. A switch or BMC missing from a Datadog-only or Wazuh-only report, with no firmware review or risk acceptance, is a gap in CC7.1 evidence.
Recommended SOC 2 Scanner-of-Record Setup: One Agent for Hosts Plus a Periodic Network Scan
Split the on-prem scanner of record by what each tool can see:
- Hosts and containers: one agent. If the Datadog Agent is already on every server, enable Cloud Security Vulnerabilities and name it as the host scanner. If Wazuh is already the SIEM, use its vulnerability detection. Running both on the same hosts doubles triage work for the same CVEs.
- Agentless devices: a network scan. Run a credentialed Nessus scan, or equivalent, of firewalls, switches, hypervisors, BMCs and storage on the policy's cadence, often quarterly, plus after firmware changes.
- Devices that accept no scanner credentials: a firmware review. Record firmware versions each quarter, check vendor advisories, and document a risk acceptance for anything unsupported.
- One remediation queue. Send findings from both tools into the same ticket system with the same severity SLAs, so the auditor samples one process.
- Name both tools in the policy. State in the vulnerability management policy and the system description which tool covers which asset class.
For the bare-metal company that asked the question, the answer was to keep Datadog for its Linux fleet and add a quarterly credentialed network scan of its firewalls, switches and BMCs. External scans and penetration testing are separate controls; the SOC 2 penetration testing guide for on-prem covers them.
Which GRC Platforms Pull Findings From Datadog, Wazuh and Nessus?
Vanta and Drata pull findings from some of these tools, which cuts manual evidence uploads. The table reflects each vendor's help documentation as of 2026-10-17.
| Scanner | Vanta | Drata |
| Datadog Cloud Security | Yes: imports host and container CVE findings when Cloud Security is enabled | Monitoring and logging connection; absent from Drata's vulnerability connection list |
| Wazuh | Absent from Vanta's vulnerability scanner list | Absent from Drata's vulnerability connection list |
| Tenable | Yes: Tenable integration, for a cloud.tenable.com account | Yes: Tenable Vulnerability Management only |
| Nessus Professional (standalone) | Not listed in Vanta's vulnerability scanner help articles | No; Drata names Tenable Vulnerability Management as its only Tenable integration |
Where a tool has no integration, upload dated scan reports, schedules and remediation tickets instead. The guide to SOC 2 evidence collection on-prem covers that workflow. A GRC platform tracks the evidence, and the security team decides what gets scanned and how fast findings close.
How to Document a SOC 2 Scanner of Record for the Auditor
Document the scanner of record as a mapping from asset class to tool, frequency and owner, and give the auditor these items at planning:
- Asset-to-scanner map: each in-scope asset class with its tool and method
- Coverage reconciliation: inventory compared against agent lists and scan targets, gaps explained
- Scan schedule: exports or screenshots of each tool's configured schedule
- Dated results: reports or exports across the observation period
- Remediation evidence: tickets with open and close dates against the SLA
- Risk acceptances: signed decisions for anything that cannot be fixed or scanned
Datadog, Wazuh or Nessus: Pick the SOC 2 Scanner That Covers the Whole Inventory
The best SOC 2 vulnerability scanner setup for an on-prem company covers the whole asset inventory with the least duplicate work. Proven coverage beats a longer tool list. The SOC 2 for bare metal and on-prem infrastructure page lists the other controls that change when a company operates its own hardware.
Related Guides
- SOC 2 Vulnerability Risk Acceptance: What to Do When There Is No Vendor Fix
- SOC 2 Automatic Patching: Do Unattended Security Updates Need a Change Ticket?
Pick a scanner of record once
Truvo maps your tools to SOC 2 coverage on-prem and fills the gaps agents can't see.
Frequently Asked Questions
Is Datadog enough for SOC 2 vulnerability scanning?
Datadog Cloud Security Vulnerabilities is enough for servers and containers running the Datadog Agent. It does not detect vulnerabilities on firewalls, switches, ESXi hosts or BMCs, so on-prem companies add a periodic network scan such as Nessus, or a documented firmware review and risk acceptance.
Can Wazuh be used for SOC 2 vulnerability scanning?
Yes, for every host running the Wazuh agent. Its vulnerability detection module matches the agent's package inventory against the Wazuh CTI feed or an offline copy. Network devices and hypervisors need a separate network scan or firmware review.
Do we need Nessus for SOC 2?
Nessus is optional, since SOC 2 leaves the tool choice to the company. On-prem companies still need a way to check network devices, hypervisors and BMCs, and a credentialed network scanner such as Nessus is a common choice. Companies with only cloud or agent-capable hosts can often meet CC7.1 with an agent-based tool.
How often should we run vulnerability scans for SOC 2?
SOC 2 requires scans on a periodic basis and after significant changes, and leaves the interval to the company. A common cadence is continuous or weekly agent-based detection on production hosts, quarterly network scans of infrastructure devices, and a scan after major changes.
Does Vanta or Drata integrate with Datadog, Wazuh or Nessus?
Vanta imports CVE findings from Datadog Cloud Security and connects to Tenable cloud accounts. Drata connects to Tenable Vulnerability Management only; Datadog, Wazuh and standalone Nessus are absent from its vulnerability connection list.
Sources
- AICPA, 2017 Trust Services Criteria (With Revised Points of Focus, 2022)
- Datadog, Cloud Security Vulnerabilities
- Datadog, Cloud Security setup on Linux with the Agent
- Datadog, Network Device Monitoring
- Wazuh, Vulnerability detection
- Wazuh, How vulnerability detection works
- Wazuh, Agentless monitoring
- Tenable, Nessus credentialed checks on network devices and APIs
- Tenable, Nessus credential types
- Tenable, Nessus vulnerability scans and compliance audits
- Tenable, Nessus scan schedule settings
- Tenable, Nessus scan reports
- Vanta, Integrating Vanta and Datadog
- Vanta, Vulnerability scanner integrations (checked 2026-10-17)
- Vanta, Connecting Vanta and Tenable Vulnerability Management (FedRAMP)
- Drata, Supported vulnerability connections (checked 2026-10-17)
- Drata, Tenable Vulnerability Management connection
- Drata, Datadog connection
Ready to Start Your Compliance Journey?
Get a clear, actionable roadmap with our readiness assessment.
Contact Us
Sample SOC 2 Control List
Input your email to download the list.
About the Author
Former security architect for Bank of Canada and Payments Canada. 20+ years building compliance programs for critical infrastructure.