Security is part of the path
Bower's protection model is built into collection, selection, persistence and delivery. These are product invariants, not optional dashboard settings.
- Default deny. Unknown event types do not pass policy evaluation.
- Protect before storing. Redaction happens before persistence, and failure is handled as a security failure.
- Trust signed content. Packs must be signed by a trusted key.
- Keep acknowledgement state. Events are not removed before acknowledgement.
- Prove arrival. Only a destination query finding the exact event counts as delivery proof.
Understand the boundaries
Read the threat model for the data flows and assumptions, the identity and role model for management access, and producer scopes for intake permissions.
The ISM alignment document maps controls and evidence. It is not certification or a statement that a particular deployment is compliant. Cited ASVS and ISM IDs come only from the verified lists.
Privacy controls
The Privacy & Secret Protection Engine explains detectors, actions and metadata. Use managed profiles and the guided privacy editor to review changes.