Cased
Title

Scan Your Infrastructure on Your Schedule

Control when Cased scans your infrastructure for drift—every 6 hours by default, or set your own schedule

Author
Rika Sun Rika Sun
Published
Scan Your Infrastructure on Your Schedule

We’ve added configurable infrastructure scanning. Set your scan frequency to match your workflow, or trigger scans manually when you need them.

Drift Happens When You’re Not Looking

Someone tweaks a security group in the console at 3pm. A teammate updates tags on an S3 bucket. A resource drifts away from what’s declared in your Terraform.

Before, you’d only catch it when you manually updated your infrastructure settings. Now, scans run automatically.

Your Schedule

Configure how often Cased checks your infrastructure:

  • Every 6 hours (default): Catch drift within half a workday
  • Every 12 hours: Balance freshness with scan frequency
  • Daily: Once-a-day checks for stable environments
  • Never: Disable automatic scanning, scan only when you want

Infrastructure scan scheduling

Click “Scan now” when you need immediate drift detection after a deploy or change.

How It Works

Pick your schedule from the dropdown. Cased handles the rest.

Every 30 minutes, we check which environments are due for a scan. When your interval is up, we pull your Terraform or Pulumi state and check for drift. You’ll see the results in your infrastructure view.

Set Your Cadence

Head to your infrastructure environments at app.cased.com and set your scan schedule. The default of 6 hours catches drift fast without over-scanning.