Updated 2026-11-13
Before Automating Defense: Check Approval and Applied Results #
Verify the need for action, its permitted scope and the state afterward.
The original case introduced an approval step between notification and response. This public account focuses on operational checks rather than individual commands.
Separate detection from the response decision #
A detected signal does not justify the same response for every subject. Check the need, the target and the possible effect on legitimate use.
Make the approval specific #
Record who authorized what, with a consistent target and scope. Approval and successful application require separate confirmation.
Verify results and recovery arrangements #
Check the state after execution and prepare a way to review or reverse an action when needed. Set the automation scope according to the environment and requirements.
The lessons from the original case have been reorganized for this public article. See the BASTION introduction for current features and deployment conditions.