Plan Your Lumin Synchronization
Tenable recommends planning your synchronization strategy to accommodate synchronization limitations and limit data duplication in Tenable.io.
Can I communicate with Tenable.io through a proxy?
To use the proxy configured for your Tenable.sc instance for communications with your Tenable.io instance, contact Tenable Support.
Can I synchronize multiple Tenable.sc instances?
You can synchronize data from one Tenable.sc to one Tenable.io instance. You cannot synchronize data from multiple Tenable.sc instances to a single Tenable.io instance.
If you purchase multiple Tenable.io instances, you can synchronize one Tenable.sc to each Tenable.io instance.
What data does synchronization include?
Tenable.sc supports synchronizing:
IPv4 addresses within dynamic assets andIPv4 addresses within static assets.Note: You cannot synchronize IPv6 addresses within static assets. If an asset contains a mix of IPv4 and IPv6 addresses, Tenable.sc synchronizes only the IPv4 addresses.
Note: You cannot synchronize non-IPv4 assets within dynamic assets. If a dynamic asset contains other asset types, Tenable.sc synchronizes only the IPv4 addresses.
Note: You cannot synchronize DNS name list assets, LDAP query assets, combination assets, watchlist assets, or import assets.
Active or agent cumulative database and scan result vulnerability data stored in IPv4 and agent repositories.
The initial synchronization includes all cumulative database data from the repository. All subsequent synchronizations include only the new or modified scan result data imported to the repository.
Note: You cannot synchronize passive scan result vulnerability data. Tenable.sc identifies vulnerability data by plugin family and excludes NNM and LCE plugin families from synchronization.
Caution: To avoid data merge issues in Tenable.io, Tenable recommends resolving all repository overlaps before synchronizing data to Tenable.io. You cannot resolve data merge issues after synchronizing a repository with Tenable.io; you must resolve overlapping repositories in Tenable.sc before synchronizing a repository for the first time. For more information, see Repository Overlap.
Do I need to synchronize both data types (repositories and assets)?
Yes. In order to accurately assess your Cyber Exposure risk with Lumin, you must synchronize one or more asset lists and one or more repositories containing vulnerability data for those assets.
Vulnerability and asset data synchronize differently to Tenable.io.
After you initiate a synchronization, Tenable.sc immediately begins transferring data to Tenable.io. After 10-15 minutes, data begins appearing in Tenable.io.
Newly transferred data does not immediately impact your Lumin metrics (for example, your CES). Tenable requires up to 48 hours to recalculate your metrics.
All data and recalculated Lumin metrics appear in Tenable.io within 48 hours.
Recalculated metrics appear in Tenable.sc after the next daily retrieval.
|Asset data (tags in Tenable.io)||
Which of my synchronized assets count toward my Tenable.io license?
Synchronized assets that count toward your Tenable.sc license also count toward your Tenable.io license. For more information about Tenable.sc asset counting, see License Requirements.
Tip: Viewing vulnerability data is temporarily not possible in Tenable.io. You can view asset and solutions data, but not vulnerability data. For more information, contact your Tenable representative.
You can view your synchronized data in both the Vulnerability Management and Lumin areas of Tenable.io.
View your synchronized data on the Assets page. For more information, see View Assets in Tenable.io Vulnerability Management.
View your synchronized data on any Lumin page. For more information, see Get Started with Lumin in the Tenable.io User Guide.
Tip: To view limited metrics Tenable.sc retrieves from Lumin in Tenable.io, see View Lumin Metrics.