REFERENCE BRIEFPublic reference brief
Mission-System Access Boundary Brief
A concise public explanation of why identity, application visibility, and mission authorization are separate security decisions.
AuthorizationIdentityMission SystemsZero Trust
01
Authentication answers one question
Authentication establishes who a principal is according to an identity provider. It does not by itself establish authority over a mission object, field, query, action, workflow, or export.
02
Application entitlement remains coarse
A portal can determine whether an authenticated principal may see or launch an application. The launched application still evaluates its own policy against the requested operation and current context.
- Keep tokens and application sessions scoped to their own hosts.
- Never pass reusable credentials through URLs.
- Do not translate an identity-provider role into implicit mission authority.
- Fail closed when identity, policy, or required context is unavailable.
03
Integration consequence
A clean boundary creates more explicit interfaces, but it limits blast radius and keeps each mission application responsible for its own data, decisions, and audit trail.