CM-4(2) - Impact Analyses | Verification of Controls
After system changes, verify that the impacted controls are implemented correctly, operating as intended, and producing the desired outcome with regard to meeting the security and privacy requirements for the system.
Maintaining a separate, instrumented test environment, often a “flat sat” or digital twin is crucial for verifying system changes in conditions that approximate orbit. Engineers can replicate thermal extremes, communication latencies, and partial faults before uploading new software. This realistic setup uncovers potential incompatibilities or vulnerabilities far more effectively than theoretical checks. Because of the high stakes, rigorous pre-integration in such an environment ensures reliability and safeguards mission-critical functionality, allowing operators to catch fatal flaws early and refine patches without risking the actual spacecraft.
The [organization] shall analyze changes to the spacecraft to determine potential security impacts prior to change implementation.{CM-4,CM-3,CM-3(2),CM-3(7),CM-4(2),SA-10}
The [organization] shall confirm that the operational spacecrafts correspond to the baseline configuration. {CM-2,CM-3,CM-3(7),CM-4(2),CM-6,SA-10}
The [organization] shall develop, document, and maintain under configuration control, a current baseline configuration of the spacecrafts.{CM-2,CM-3(7),CM-4(2),CM-6,SA-8(30),SA-10}
The [organization] shall retain at least two previous versions of all spacecraft associated software on the ground with the capability to restore previous version on the spacecraft.{CM-2(3),CM-3(7),CM-4(2),SA-10,SA-10(4)}