Data retention

runZero allows the data retention periods to be configured at the organization level. The organization settings page provides three ways to control how runZero manages your asset and scan data. Data expiration is processed as a nightly batch job based on the current settings for each organization in your account.

By default, data is retained for one year in the runZero Platform. This retention can be increased to three years. The runZero Community edition is limited to 30 days of retention.

Stale asset expiration

This setting can be used to remove assets that have not been seen in the specified number of days. This correlates with the last_seen:>Xdays search query, where X is defined as the number of days since this asset was last found to be responsive. This setting applies to both online and offline assets. This feature is useful if your organization has a maximum data retention policy for cloud services.

Offline asset expiration

This setting can be used to remove offline assets that have not been seen in the specified number of days. This correlates with the last_seen:>Xdays AND alive:false search query, where X is defined as the number of days since this asset was last found to be responsive. This setting is useful when short DHCP leases or guest wireless networks result in many offline assets appearing in the inventory. The default setting for new organizations is 90 days, but this can be set to zero to disable automatic asset removal.

Scan data expiration

This setting controls how long runZero will retain the raw data and metadata for Scan and Import tasks. If your organization has a maximum data retention policy for cloud services, this setting can be used to force the removal of any data older than a given number of days. The default setting of 365 preserves one year of historical scan data.

Event records

Account-level event records (found under Alerts -> Events) are always retained for one year. If you need to keep copies of these for longer than one year, these records can be exported and archived through the UX and API.

Updated