Action types
Each finding can include a human runbook, a ticket template, a PR suggestion, and a safe automated plan when the finding context supports it.
Approval policy
Tenant admins control whether automated actions are blocked, require approval, or can complete immediately for low-risk workflows.
Activity tracking
Every workflow step is linked back to the originating finding so teams can see recommendation creation, approval, status sync, and completion in one place.
54 maintained runbooks
Every workspace automatically receives BlackShield's immutable response library. Platform procedures stay current, while your custom runbooks remain separately editable.
Recommended operator flow
1. Choose the right remediation path
Start from surface status or the alert queue, drill into the exact open findings for that repository, cluster, host, or cloud account, then choose the runbook, ticket, PR, or automated plan that matches the change risk.
2. Set approval expectations up front
Use `manual only` for sensitive environments, `approval required` when automation is allowed but must be reviewed, and `auto approve` for lower-risk safe plans.
3. Synchronize status with evidence
Update the remediation action with completion, failure, and external reference data so the workflow remains useful to engineering, audit, and leadership reporting.
4. Keep ownership clear
Link a finding to a locked BlackShield runbook or a tenant-owned custom runbook. Saving action steps and AI generation always produce custom content; managed procedures are never overwritten.
What good looks like
- Every open finding has a visible owner and a recommended next action.
- Automated remediation follows the tenant policy instead of bypassing approval.
- Workflow history explains who triggered, approved, or synchronized each action.
- BlackShield runbooks appear automatically and cannot be edited or hidden by a tenant.