SA-4(1) - Acquisition Process | Functional Properties of Controls
Require the developer of the system, system component, or system service to provide a description of the functional properties of the controls to be implemented.
Request functional properties that support evaluation without exposing sensitive internals. Useful descriptions include how command authentication, key storage/rotation, partitioning, and safe-mode gating behave across resets, SEUs, and link outages; what preconditions are enforced before hazardous actions; and what telemetry proves enforcement and failure modes, so operators can verify behavior during short contacts.
Exploit ground system and use to maliciously to interact with the spacecraft
Sample Requirements
SPARTA ID
Requirement
Rationale/Additional Guidance/Notes
SPR-432
The [organization] shall require the developer of the system, system component, or system services to provide a description of the functional properties of the controls to be implemented.{SV-SP-4}{SA-4(1)}
Understanding control behavior ensures accurate evaluation. Clear functional descriptions support validation. Transparency improves assessment quality. Governance requires documented control intent.