Tipi di azioni
Each finding can include a human runbook, a ticket template, a PR suggestion, and a safe automated plan when the finding context supports it.
Politica di approvazione
Tenant admins control whether automated actions are blocked, require approval, or can complete immediately for low-risk workflows.
Monitoraggio delle attività
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 runbook mantenuti
Every workspace automatically receives BlackShield's immutable response library. Platform procedures stay current, while your custom runbooks remain separately editable.
Flusso operatore consigliato
1. Scegli il giusto percorso di riparazione
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. Stabilire in anticipo le aspettative di approvazione
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. Sincronizzare lo stato con le prove
Update the remediation action with completion, failure, and external reference data so the workflow remains useful to engineering, audit, and leadership reporting.
4. Mantieni chiara la proprietà
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.
Che bell'aspetto
- Ogni ricerca aperta ha un proprietario visibile e un'azione successiva consigliata.
- La correzione automatizzata segue la politica del tenant invece di ignorare l'approvazione.
- La cronologia del flusso di lavoro spiega chi ha attivato, approvato o sincronizzato ciascuna azione.
- I runbook BlackShield vengono visualizzati automaticamente e non possono essere modificati o nascosti da un tenant.