Knowledge noteGrowing
Trust Boundaries
A trust boundary marks where data, identity, or authority changes and therefore where explicit verification must happen.
A trust boundary marks where data, identity, or authority changes and therefore where explicit verification must happen.
A browser can propose an action; it cannot grant itself permission. The server verifies identity and intent, and the database independently enforces which rows that identity may access.
Useful boundaries include browser to server, server to database, application to provider, and repository content to public output. Designing secure public boundaries applies this map to forms, analytics, feeds, and indexes.
Keep the rule close to the protected resource and reuse it everywhere. A hidden button is presentation, not authorization.