Why use scheduling
Recurring security tasks benefit from automation:- Continuous monitoring: Automatically scan for new vulnerabilities in your infrastructure on a daily or weekly basis
- Regular compliance checks: Run security audits and compliance assessments at consistent intervals
- Proactive detection: Catch security issues early by running reconnaissance tasks on schedule
- Reduced manual overhead: Free your team from repetitive tasks while maintaining consistent security coverage
- How scheduling works
- Execute the task: Run the specified agent with its configured prompt and context at the scheduled time
- Use fresh data: Each scheduled run operates with current environment variables and latest tool versions
- Persist results: Save all artifacts, findings, and reports to your files for review and comparison
- Maintain context: Leverage memory from previous runs to improve detection and reduce false positives
- Send notifications: Alert your team when critical findings are discovered or when runs complete
Common scheduling patterns
| Schedule Type | Example Use Case |
|---|---|
| Daily | Monitor production infrastructure for new exposed services or vulnerabilities |
| Weekly | Run comprehensive security assessments on staging environments before releases |
| Monthly | Perform in-depth penetration tests and compliance audits |
| On-demand with intervals | Trigger scans after deployments, then repeat every few hours during rollout |
| Continuous | Run lightweight reconnaissance continuously with configurable delays between runs |