Scheduled Scans on Your Cadence

Cron-driven recurring scans with scan-to-scan diffing, SLA tracking, and project-scoped schedules for continuous attack surface coverage.

Manage All Schedules in One Place

See next run times, last results, and active status for every scheduled scan.

metrictower.com/scheduled-scans
Scheduled Scans
Automatically run scans on a recurring schedule.
+ New Schedule
Name Target Frequency Next Run Last Run Status
Weekly Prod Scan
24 modules
acme-corp.com Weekly in 3 days 4 days ago Active
Nightly Staging
24 modules
staging.acme-corp.com Daily in 14 hours 10 hours ago Active
Monthly Full Audit
24 modules
10.0.0.0/24 Monthly in 18 days 12 days ago Active
API Endpoint Check
24 modules
api.acme-corp.com Custom in 2 days 5 days ago Paused

Scan on Autopilot

Configure once, monitor continuously. Every scheduled scan uses the same 57-module pipeline as on-demand scans.

Flexible Scheduling

Daily, weekly, monthly, or any custom cron expression. Scans run at the time you set, every time.

Scan Comparison

Diff any two scan runs side by side. See new findings, fixed issues, and unchanged vulnerabilities at a glance.

Module Templates

Save your module selection as a reusable template. Apply the same configuration to every scheduled run without re-selecting each time.

Pause and Resume

Pause a schedule during change freezes or maintenance windows, then resume with one click. No data is lost.

How It Works

Step 1

Create a schedule

Pick a target, select modules (or load a template), and choose a frequency -- daily, weekly, monthly, or custom cron. Name it so you can find it later.

Step 2

Scans run automatically

At the scheduled time, MetricTower launches the full scan pipeline. Sandboxed workers start, modules execute in dependency order, results are stored.

Step 3

Compare results

After each run, compare with previous scans. See which findings are new (regressions), which were fixed, and which remain unchanged -- tracked automatically within each project.

Step 4

Get notified

Receive email notifications when scans complete. Critical findings trigger alerts via Slack, Teams, Discord, PagerDuty, or webhooks -- whichever channels your team uses.

More Than a Cron Job

Scheduled scans are full-featured pipeline runs with comparison, deduplication, and SLA tracking built in.

Project-Scoped Scheduling

Organize schedules by project. Findings are deduplicated within each project -- the system tracks whether a vulnerability is new, repeated, regressed, or resolved across every run. False positives carry forward automatically so you only review each issue once.

Scan Diff and Trend Tracking

Compare any two scan runs to see exactly what changed. New findings are flagged as regressions. Fixed issues are confirmed. Unchanged findings stay in their current workflow state. Over time, build a clear picture of your security posture trend.

Custom Cron Expressions

Beyond daily, weekly, and monthly presets, you can use any standard cron expression. Scan every Tuesday and Thursday at 2 AM, or the first Monday of each month. Full five-field cron syntax with your local timezone.

Notification Integrations

Completed scans trigger notifications through Slack, Microsoft Teams, Discord, PagerDuty, OpsGenie, Datadog, or generic webhooks. Critical findings can trigger immediate alerts. Everything is configurable per-integration.

Security Monitor Bundle

Pre-configured daily health check using 5 lightweight scanners: HTTP headers, email security, sensitive files, DNS service detection, and JavaScript secrets. Runs at 3 AM, checks up to 10 targets per team. Results appear as regular scan findings with full deduplication and alerting. Zero infrastructure overhead.

Continuous Vulnerability Monitoring on Autopilot

Set up recurring scans that run daily, weekly, or on any custom cron schedule. Compare results across runs to track new findings, fixed issues, and regressions. Scan comparison, deduplication, and SLA tracking built in.