Scheduling

Automate recurring security scans for continuous protection.

Creating a Schedule

  1. Go to Projects → Your Project → Schedules
  2. Click Create Schedule
  3. Select target and scan profile
  4. Choose frequency and time
  5. Configure notifications
  6. Save and activate

Frequency Options

Daily

Run every day at a specified time. Ideal for staging environments and rapid development.

Weekly

Run once per week. Good balance for most production applications.

Monthly

Run once per month. Suitable for stable, infrequently changing applications.

Custom (Cron)

Full cron expression support for complex schedules.

0 2 * * 1-5 (2 AM on weekdays)

Schedule Configuration

{
  "name": "Weekly Production Scan",
  "target": "https://example.com",
  "profile": "standard",
  "schedule": {
    "frequency": "weekly",
    "day": "sunday",
    "time": "02:00",
    "timezone": "America/New_York"
  },
  "notifications": {
    "on_complete": true,
    "on_critical": true,
    "channels": ["slack", "email"]
  },
  "enabled": true
}

Best Practices

  • Schedule scans during low-traffic periods
  • Use Deep profile for weekly/monthly scans
  • Use Quick profile for daily CI/CD scans
  • Enable notifications for critical findings
  • Review scan results regularly, even automated ones
  • Adjust schedules based on deployment frequency

Managing Schedules

Via API:

# List schedules
curl https://api.hackerbot.io/v1/schedules \
  -H "Authorization: Bearer hb_live_xxxx"

# Pause a schedule
curl -X PATCH https://api.hackerbot.io/v1/schedules/sched_abc123 \
  -H "Authorization: Bearer hb_live_xxxx" \
  -d '{"enabled": false}'

# Delete a schedule
curl -X DELETE https://api.hackerbot.io/v1/schedules/sched_abc123 \
  -H "Authorization: Bearer hb_live_xxxx"
Exclusions Team Management