Operations, schedules and playbooks
Schedule repeatable testing, start from templates, reuse playbooks and skills, and use Operations to review what AI engineers hold back.
On this page
Schedules
Schedule runs repeatable tasks for you: an instruction, a target and when it runs (daily, or on an interval). Each run opens a session you can review.
Start from a template or write your own:
| Template | Purpose |
|---|---|
| Daily CVE watch | Check your stack against newly published vulnerabilities. |
| Daily bug watch | Look for newly introduced issues. |
| New-asset monitor | Notice assets that appear. |
| Secrets watch | Look for exposed secrets. |
| Weekly web audit | Recurring web application testing. |
| Weekly API audit | Recurring API testing. |
| Weekly fix verification | Retest fixed findings. |
The schedule view shows upcoming runs, the latest outcome and each task’s run history. Choose which engineer a schedule runs as.
Playbooks and skills
Playbook is your library of reusable procedures. A playbook describes how to run a kind of engagement step by step; a skill packages one capability Nebula can use. Create, edit and share them with your organization; access is governed by the playbooks:* and skills:* member scopes.
From the terminal, the CLI runs the same kind of multi-step engagement with its nebula agent; breachline run takes an objective non-interactively.
Operations
Operations holds the safety controls and review queues for your AI engineers:
- Autonomy settings for unattended work.
- Held inbound messages and held outbound sends waiting for review.
- Egress holds on outbound network activity.
- Quarantine for items that were flagged.