Scheduled Discovery

Coming Soon

Scheduled discovery scans are currently under development. This documentation is prepared for the upcoming release.

Automate infrastructure scans on a recurring schedule using cron expressions. Scheduled discovery eliminates manual rescans and ensures continuous monitoring of your cloud infrastructure.

Creating a Schedule

Set up automated discovery scans in 5 steps:

1Choose existing session template or create new scan configuration

2Set cron expression (daily, weekly, or custom schedule)

3Select resource types to scan

4Enable or disable schedule

5Review configuration and save

Cron Expression Examples

Common schedule patterns:

Expression	Description	Best For
`0 2 * * *`	Daily at 2:00 AM	Daily drift detection
`0 /6 * *`	Every 6 hours	Critical production environments
`0 0 * * 0`	Weekly on Sunday at midnight	Weekly compliance audits
`0 0 1 * *`	Monthly on the 1st at midnight	Monthly cost reporting
`0 9 * * 1-5`	Weekdays at 9:00 AM	Business hours monitoring

Managing Schedules

Once created, you can:

View All Schedules

See all configured schedules across your organization

Enable/Disable

Temporarily pause schedules without deleting configuration

Edit Configuration

Update cron expression, resource types, or regions

View Run History

Check last run time and next scheduled run

Delete Schedule

Remove automated scans when no longer needed

Use Cases

Use Case	Schedule	Benefit
Daily Drift Detection	Daily at 2 AM	Catch unauthorized changes within 24 hours
Weekly Compliance Audits	Sunday midnight	Regular compliance reporting for security teams
Monthly Cost Reporting	1st of month	Track infrastructure costs month-over-month
Continuous Production Monitoring	Every 6 hours	Real-time awareness of critical infrastructure

Example: Daily Production Scan

Scenario

You want to automatically scan your production AWS account every morning to detect drift and ensure compliance.

Schedule Configuration

Schedule Name:       daily-prod-scan
Description:         Automated production infrastructure scan
Provider:            AWS
Integration:         AWS Production (123456789012)
Regions:             us-east-1, us-west-2
Resource Types:      VPC, EC2, RDS, S3, Security Groups
Cron Expression:     0 2 * * *
Timezone:            UTC
Status:              Enabled
Last Run:            2026-01-16 02:00:00 UTC
Next Run:            2026-01-17 02:00:00 UTC

What Happens

02:00 UTC Daily: Scan automatically starts
02:00-02:05: Resources discovered across both regions
02:05: New session created with timestamp
02:05: Optional drift detection against previous day's scan
Dashboard Updated: Latest scan results visible in UI

Notifications

When scan completes, you can configure notifications via:

Email
Slack
Webhook

Best Practices

Scheduling Tips

• Avoid peak hours - Schedule during off-peak times (nights/weekends) to minimize API rate limiting

• Stagger multi-account scans - If scanning multiple accounts, offset schedules by 30-60 minutes

• Monitor API limits - Frequent scans may hit AWS/GCP/Azure API rate limits

• Review session retention - Set appropriate retention policy to avoid accumulating too many sessions

• Test first - Run manual scans before enabling schedule to verify configuration