​
Scheduling

Scheduled audits run on a cron schedule, provisioning a fresh sandbox and executing the configured audit each interval. Use them for continuous coverage between manual engagements.

​
Why schedule audits

  • Continuous coverage — catch regressions within hours, not at the next quarterly review
  • Compliance — produce continuous evidence for SOC 2 / ISO 27001 / PCI controls
  • Drift detection — see when a new subdomain appears or a new vulnerability surfaces (new-subdomain alerts included)
  • Release gating — schedule a shallow audit shortly after each release window

​
Creating a scheduled audit

  1. Open an app and go to Schedule
  2. Create a new schedule:
    • Audit type — shallow or deep
    • Cron expression — when to run
    • Targets — defaults to the app’s domain
  3. Save — the schedule is active immediately
Schedules can be paused, edited, or deleted without affecting past audit history.

​
Cron syntax

Standard 5-field cron:
Common patterns

​
Choosing a cadence

Shallow audits are designed for frequent runs. Deep audits consume significantly more credits — schedule them weekly or less often unless you specifically need higher frequency.

​
Notifications

When a scheduled audit completes, you’re notified by email and Slack (if connected) with the score, finding counts, and a link to the report. If a scheduled run is skipped because the app is out of credits, you’ll get a dedicated “skipped” notification.

​
Next steps

Slack Integration

Route notifications to a channel.

Shallow Audits

The mode built for frequent runs.