Turning On Rolling Histories from Administrator
The second sandbox option is "Time-to-live" (TTL). This option does not limit the number of scans that can be held within a sandbox, but the sandbox itself will automatically be deleted after 90 days, along with any scans in that sandbox. After 90 days, the sandboxes and scans are automatically moved to the 'soft deleted list' and are purged from the deleted list. As with Rolling History, underlying scan data - flaw info and mitigations are still kept.
Note: Once a TTL sandbox has been deleted, the sandbox name can be reused.
If a client requests to be switched from Rolling History to TTL, engage with the CSM to ensure the client is fully aware that this is a global change and will affect every Applications' Sandboxes for the entire client org. It is not possible to mix Rolling History and TTL between Applications. It is a global change for the Organization.
To update a client org from Rolling History to TTL: When viewing the Admin page of the client's org, navigate to >Features > General Platform >Cap number of scans per sandbox.
Additional Note: When switching a client from Rolling History to TTL, if there are any scans that have been deleted in fewer than 7 days, it may be possible to restore the scan to the sandbox by retrieving it from the deleted list - this is not always possible and the client should be discouraged. However, if unable to restore a scan from the deleted list, an Engineering ticket can be created with the 'Zoo' Engineering Team name.
.png){kind=logo}
