Tipos de ação
Each finding can include a human runbook, a ticket template, a PR suggestion, and a safe automated plan when the finding context supports it.
Política de aprovação
Tenant admins control whether automated actions are blocked, require approval, or can complete immediately for low-risk workflows.
Rastreamento de atividades
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 runbooks mantidos
Every workspace automatically receives BlackShield's immutable response library. Platform procedures stay current, while your custom runbooks remain separately editable.
Fluxo de operador recomendado
1. Escolha o caminho de correção correto
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. Defina antecipadamente as expectativas de aprovação
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. Sincronize o status com as evidências
Update the remediation action with completion, failure, and external reference data so the workflow remains useful to engineering, audit, and leadership reporting.
4. Mantenha a propriedade clara
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.
Que bom parece
- Cada descoberta aberta tem um proprietário visível e uma próxima ação recomendada.
- A correção automatizada segue a política do locatário em vez de ignorar a aprovação.
- O histórico do fluxo de trabalho explica quem acionou, aprovou ou sincronizou cada ação.
- Os runbooks do BlackShield aparecem automaticamente e não podem ser editados ou ocultados por um locatário.