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 up to one year in the runZero Platform. This can be increased to up to three years. The runZero Community edition is limited to 30 days of retention.

Stale asset expiration

Stale asset expiration allows you to make sure that out-of-date information gets purged from runZero. Assets which have not been seen in the specified number of days are automatically deleted. The automatic deletion task runs once per day.

The stale asset expiration limit applies to both online and offline assets. For example, if an asset was online when last scanned, but hasn’t been scanned (or imported via a connector) in the specified number of days, then the information is stale and the asset will be deleted. It’s like running an asset search query of last_seen:>Xdays (where X is replaced by a number), and deleting the resulting assets.

You can disable stale asset expiration by setting the number of days to zero.

Offline asset expiration

Offline asset expiration allows you to clear out information about assets that no longer exist on the network. Assets which are offline and have not been seen in the specified number of days are automatically deleted daily. Online assets are not touched. The automatic deletion task runs once per day.

This feature is particularly useful for guest wireless networks, or networks with short DHCP leases. It’s like running an asset search query of last_seen:>Xdays AND alive:false (where X is replaced by a number), and deleting the resulting assets.

You can disable offline asset expiration by setting the number of days to zero.

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.