Skip to main content

Module context

Module context 

Source
Expand description

The subject security context — a subject’s verified clearance, the subject.ctx side of the per-op dominance check subject.ctx ⊒ object.label.

A subject context is the SecurityLabel a verified principal is cleared up to. Where the object label is content-bound (in a manifest), the subject context rides the verified claims/envelope (design §3, §11 data structures: subject ctx in the verified claims/envelope).

§Where it lives on the wire

The subject context is derived, not self-asserted. Two inputs feed it, both already verified by the time the monitor runs:

  1. The principal’s clearance (level + compartments) — assigned by policy / enrollment and carried in the verified crate::auth::Claims (the JWT is signed by the issuing node, so the clearance is authority-asserted, not subject-asserted). The wire field is added by the SubjectContextClaims seam below; the actual Claims/common.capnp field add is gated on S8/#574 (hybrid envelope) — see BLOCKERS.
  2. The principal’s assurance (#548) — derived from the verified key material, never claimed. See SecurityContext::derive_assurance.

§Fail-closed

A subject with no derivable clearance has no context (None), and the monitor denies — there is no Default clearance. Assurance defaults to Assurance::Unverified (the floor) precisely so an un-attested key dominates nothing above the floor.

Structs§

SecurityContext
A verified subject’s security context = the clearance label the monitor compares against object labels.

Enums§

VerifiedKeyMaterial
How a principal’s key material was verified, used to derive (never trust) an Assurance. Produced by the envelope/claims verification layer — this type is the seam between “what crypto verified” and “what the lattice sees”.

Traits§

SubjectContextClaims
Seam for carrying a subject clearance on the verified claims/envelope.