AC-3(2) - Access Enforcement | Dual Authorization

Enforce dual authorization for [Assignment: organization-defined privileged commands and/or other organization-defined actions].


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

Space Segment Guidance

When spacecraft missions require dual authorization to reduce the risk of single-person misuse, the ground segment typically handles the two-operator aspect. However, incorporating indicators of dual concurrence within the command stream can be crucial for on-orbit verification. For instance, multiple cryptographic signatures, or a specific "arm–execute" handshake, can be enforced to ensure no single console operator can unilaterally activate mission-critical functions like propulsion changes or cryptographic key rotation. Even if the flight software does not confirm dual operator presence, it can validate that all commands carry the expected signatures or security tokens. Space programs can also maintain an onboard audit log reflecting dual-authorization events, providing evidence that two authorized parties concurred post-facto. Any high-stakes command requiring unanimous ground approval might only be accepted upon detecting these dual credentials if the vehicle's design includes limited autonomy. Autonomy preserves mission integrity and safeguards against internal threat actors or compromised ground stations. Ultimately, dual authorization fosters a "checks-and-balances" mentality for all critical uplinks—especially given that a single flawed or malicious command could jeopardize an irreplaceable national asset in orbit.