Tenable One Open Connector FAQ

The following is not supported in Tenable FedRAMP Moderate environments. For more information, see the Tenable FedRAMP Product Offering.

The following are frequently asked questions regarding Tenable One Open Connector.

What happens to existing data if a user re-uploads a file that is missing a previously mapped, non-mandatory column?

Each upload acts as a new full sync. If a previously mapped and non-mandatory field is missing in the new file, Tenable Exposure Management removes the associated data from the platform.

What happens if a user changes the uniqueness criteria in the second upload?

The new uniqueness criteria apply only to the new upload. The platform treats the upload as a new dataset and does not retroactively update previously ingested records.

What happens if an asset appears in the first file but is missing from later uploads?

The asset remains in Tenable Exposure Management for the duration set in the retention policy. Each time the asset is included again in a new file, the retention countdown resets.

How does Asset Retention work in Tenable One Open Connector?

Tenable Exposure Management automatically removes assets once they exceed the Asset Retention period defined in the connector settings. The default retention period is 460 days, but you can customize this value to suit your requirements.

Source File State	Expected Retention Behavior
If your source file includes a last-seen column and you map it to the Asset Last Observed At attribute, the system uses the specific date value provided in the file.	The asset remains in Tenable Exposure Management as long as the last_seen date, plus the configured retention days, is greater than the current date. If the retention period expires without a data update, Tenable Exposure Management removes the asset.
If your source file does notinclude a last-seen field, or if you do not map a timestamp, the system uses the the time of the file upload as the Asset Last Observed At value.	The asset is retained for the duration of the configured retention period, starting from the upload date. If the asset is included in subsequent uploads, Tenable Exposure Management removes the asset once the period expires. If the asset is not included in subsequent uploads, Tenable Exposure Management immediately removes it. For example, if the retention period is set to 30 days, and the asset Last Observed At value is January 1, the asset is scheduled for deletion on January 31, unless it appears in a new file upload before that date.

Source File State

Expected Retention Behavior

If your source file includes a last-seen column and you map it to the Asset Last Observed At attribute, the system uses the specific date value provided in the file.

The asset remains in Tenable Exposure Management as long as the last_seen date, plus the configured retention days, is greater than the current date. If the retention period expires without a data update, Tenable Exposure Management removes the asset.

If your source file does notinclude a last-seen field, or if you do not map a timestamp, the system uses the the time of the file upload as the Asset Last Observed At value.

The asset is retained for the duration of the configured retention period, starting from the upload date.

If the asset is included in subsequent uploads, Tenable Exposure Management removes the asset once the period expires.

If the asset is not included in subsequent uploads, Tenable Exposure Management immediately removes it.

For example, if the retention period is set to 30 days, and the asset Last Observed At value is January 1, the asset is scheduled for deletion on January 31, unless it appears in a new file upload before that date.