SI-14(1) - Non-persistence | Refresh from Trusted Sources
Obtain software and data employed during system component and service refreshes from the following trusted sources: [Assignment: organization-defined trusted sources].
Refreshing from trusted sources safeguards the non-persistence approach by ensuring that any ephemeral states, operating system images, or mission data come exclusively from validated origins. Typically, the spacecraft would request updated software or configuration files from known, cryptographically verified ground stations or partner satellites. Digital signatures or secure hashing algorithms confirm that these updates match approved references (often known as “golden images”) the mission authority maintains. If any unexpected discrepancy is found—a corrupted download or unknown certificate—the spacecraft rejects the refresh. This mechanism enables quick and safe rollouts of security patches, new mission parameters, or adjusted flight software, all while preserving a strict chain of trust. Over time, such trusted refresh cycles support agile yet secure system evolution, helping the spacecraft adapt to emergent threats or mission changes.