| Capability |
OT Agent |
Sensor |
| Target Use Case |
For assessments, PoVs, and flexible Windows-based OT environments. |
For full deployments where traffic inspection and control are required. |
| Deployment Type |
Installed on Windows machines (HMI, workstation, jump box) |
Installed on hardware or VM, based on Tenable Core operating system. |
| ICP Dependency |
Requires pairing with ICP, but can operate independently to collect data (requires support + scripts) |
Fully dependent on ICP |
| Installation Complexity |
Lightweight, flexible; can be deployed in bulk |
Requires physical or virtual deployment + configuration |
| Data Flow to ICP |
Results pushed after scan completion |
Continuous data stream (active +passive) |
| Execution Type |
Active scanning only |
Active and passive scanning |
| Scan Management UI |
Managed from the Agents page only |
Queries triggered from the Active Query and Inventory pages. |
| Nessus Integration |
Not supported |
Nessus queries can route through Sensors. |
| Vulnerability Matching |
Uses embedded Nessus in ICP for matching. |
Uses embedded Nessus in ICP for both matching and active scanning. |
| Scan Scheduling |
Supported (one-time or recurring). |
Supported (one-time or recurring). |
| Asset Visibility |
Assets shown in inventory but not queryable from inventory. |
Assets fully queryable from inventory. |
| Credential Scope |
Uses dedicated credentials configured per Agent. |
Uses global credentials from ICP. |
| Duplicated Network Support |
Supported |
Supported |
| Respects Global Restrictions |
Not supported in version 4.3 |
Supported |
| Pairing Method |
Pairing Key (API key +certificate + ICP IP in one blob). |
Requires API key, Certificate, or IP configured manually. |
| Hardware |
None - runs on existing Windows machines. |
Dedicated hardware or VM required. |
| Passive Traffic Capture |
Not supported |
Fully supported |