Exclude short-lived cloud resources from the asset registry and reduce false test failures

What's new?

Scrut now automatically filters transient cloud resources, such as those created by auto-scaling and ephemeral orchestration lifecycles, during ingestion. These short-lived instances no longer appear in the asset registry and are excluded from asset-based continuous tests. Asset-based tests will no longer flag transient instances as failures.

Why was this needed?

Auto-scaling and other ephemeral cloud resources were previously ingested into the asset registry alongside durable infrastructure, polluting the inventory with instances that were never meant to be governed. This caused false failures on asset-based tests that expect stable, owned resources and required teams to spend time manually clearing noise assets. With transient resources filtered at ingestion, your asset registry reflects only the infrastructure your team should reasonably own and attest, giving auditors an accurate view and reducing false test failures.

How it works

• No action is required. Ingestion logic is applied automatically for supported cloud providers.

• Review your asset inventory under Compliance -> Cloud.

• Short-lived and ephemeral resources from autoscaler and orchestration lifecycles will no longer appear as governed assets.

Need help?

Your Customer Success Manager (CSM) is always ready to help if you need assistance. Explore all recent product updates → View now.