Persist dry-run response plans
This commit is contained in:
parent
812cf0c836
commit
1a5b6f1d8d
11 changed files with 133 additions and 5 deletions
|
|
@ -108,6 +108,12 @@ Sentinel should remain conservative:
|
|||
Future response features should produce dry-run plans first, log all changes,
|
||||
and avoid shell-string execution where structured APIs exist.
|
||||
|
||||
Current CLI response planning already leaves a local audit trail: generated
|
||||
dry-run plans are saved under `response-plans/`, and
|
||||
`response-audit.log` records who/what generated the plan and where it was
|
||||
stored. This is a review/handoff record only; it does not prove containment
|
||||
commands were executed.
|
||||
|
||||
## Abuse Considerations
|
||||
|
||||
Some security tools can become dual-use. Enodia should avoid:
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue