Security hardening

Map assets and trust boundaries before selecting controls. Enforce authorization where actions execute and data leaves the system.

Threat model first

1. Identify protected assets, users, tenants, privileged operations, and permitted data destinations.
2. Trace untrusted input through requests, files, dependencies, tool results, retrieval, memory, and model output.
3. Name the enforcement owner for each boundary: application, storage, tool server, operating system, or network.
4. Use STRIDE to identify spoofing, tampering, repudiation, disclosure, denial of service, and privilege escalation.
5. Write abuse cases beside allowed behavior. Record assumptions and controls that the current system cannot enforce.

Resolve changes to auth flows, sensitive data, integrations, or elevated roles against the approved scope. Existing authorization is sufficient within that scope.

Boundary controls