Phase 2: Component Deployment
Component deployment is the second phase of your Tenable One adoption. This phase focuses on connecting your key environments so Tenable Exposure Management can begin ingesting asset and vulnerability data from all your data sources.
Depending on the deployment resources at your disposal, you may choose to focus on achieving these outcomes sequentially or concurrently. You may also proceed to the next phase after just one or two outcomes are completed, and plan to return later to focus on another application.
Expected Outcomes
In this phase, you configure data sources to feed into Tenable Exposure Management. This includes connecting Tenable applications (components) and third-party connectors.
The expected outcomes include the following, depending on what applications your organization allocated licenses to:
-
Tenable Vulnerability Management scans are configured, and assets and findings are syncing.
-
Legacy Tenable Cloud Security is configured, with environments syncing their workloads.
-
Tenable Security Center is configured and syncing asset and vulnerability data.
-
Tenable Web App Scanning scans are configured, with web app data syncing.
-
Tenable Patch Management is configured and syncing asset, risk context and patch data.
-
Tenable Attack Surface Management domains are configured, with records syncing.
-
Tenable AI Exposure is integrated and syncing enterprise AI LLMs (for example, Copilot or ChatGPT).
-
Tenable OT Security is integrated and syncing OT asset data.
-
Tenable Identity Exposure is integrated and syncing identity data.
-
Tenable Third-Party Data Connectors are configured, with asset and risk data syncing.
Tip: For more information on how to deploy each Tenable component, see the Tenable One Platform Deployment Guide.
Why This Is Important
This phase is critical for populating Tenable Exposure Management with comprehensive data from across your attack surface. This data ingestion is the foundation for all exposure analysis, attack path visualization, and reporting.
Verification
You can verify the success of this phase by confirming the following within at minimum 24 hours of component enablement:
Note: Keep in mind that Tenable Exposure Management updates data using a specific cadence. For more information, see Data Timing.
-
Assets appear in the Tenable Exposure Management views. For more information, see Assets.
-
No errors are reported for third-party data connectors. For more information, see Connector Data Status.
-
An initial exposure score and letter grade are generated. For more information, see Exposure View.
-
Attack paths are beginning to populate. For more information, see Attack Path.
What to do next: