AC-3(8) - Access Enforcement | Revocation of Access Authorizations

Enforce the revocation of access authorizations resulting from changes to the security attributes of subjects and objects based on [Assignment: organization-defined rules governing the timing of revocations of access authorizations].


ID: AC-3(8)
Enhancement of : AC-3

Space Segment Guidance

Revoking access authorizations in a space setting typically involves a ground command that updates platform-level permissions. For instance, if a hosted payload relinquishes its lease or a coalition partner's data privileges change, the mission operator needs a mechanism to reflect this promptly onboard. Although the actual data handling—such as cryptographic key updates—often resides with the ground station, the spacecraft can still enforce protective measures. For example, if payload "X" loses read privileges to bus telemetry, subsequent requests from "X" would be blocked at a firmware-level or OS-level gate. Swift propagation of revocation changes is crucial because mission windows might be brief, and an undiscovered stale authorization could allow a formerly trusted entity to send commands or read sensitive data. Hence, space architectures often combine ground-based policy changes with an onboard verification routine that either denies requests from revoked entities or flags them in telemetry logs for immediate operator review.