| The [organization] shall develop and document program-specific configuration management policies and procedures for the hardware and software for the spacecraft. {CM-1,CM-3,CM-5(6),SA-10,SA-10(3)} |  | 
                                                    
                                                        
                                                            | The [organization] shall define processes and procedures to be followed when integrity verification tools detect unauthorized changes to software, firmware, and information.{SV-IT-2}{CM-3,CM-3(1),CM-3(5),CM-5(6),CM-6,CP-2,IR-6,IR-6(2),PM-30,SC-16(1),SC-51,SI-3,SI-4(7),SI-4(24),SI-7,SI-7(7),SI-7(10)} |  | 
                                                    
                                                        
                                                            | The [organization] shall develop and document spacecraft integrity policies covering both hardware and software. {CM-5(6),SA-10(3),SI-1,SI-7(12)} |  | 
                                                    
                                                        
                                                            | The [organization] shall enable integrity verification of software and firmware components.{SV-IT-2}{CM-3(5),CM-5(6),CM-10(1),SA-8(9),SA-8(11),SA-8(21),SA-10(1),SI-3,SI-4(24),SI-7,SI-7(10),SI-7(12),SR-4(4)} | * The integrity verification mechanisms may include: 
  ** Stipulating and monitoring logical delivery of products and services, requiring downloading from approved, verification-enhanced sites; 
  ** Encrypting elements (software, software patches, etc.) and supply chain process data in transit (motion) and at rest throughout delivery; 
  ** Requiring suppliers to provide their elements “secure by default”, so that additional configuration is required to make the element insecure; 
  ** Implementing software designs using programming languages and tools that reduce the likelihood of weaknesses; 
  ** Implementing cryptographic hash verification; and
  ** Establishing performance and sub-element baseline for the system and system elements to help detect unauthorized tampering/modification during repairs/refurbishing. 
  ** Stipulating and monitoring logical delivery of products and services, requiring downloading from approved, verification-enhanced sites;
  ** Encrypting elements (software, software patches, etc.) and supply chain process data in transit (motion) and at rest throughout delivery;
  ** Requiring suppliers to provide their elements “secure by default”, so that additional configuration is required to make the element insecure;
  ** Implementing software designs using programming languages and tools that reduce the likelihood of weaknesses;
  ** Implementing cryptographic hash verification; and
  ** Establishing performance and sub-element baseline for the system and system elements to help detect unauthorized tampering/modification during repairs/refurbishing. | 
                                                    
                                                        
                                                            | The [spacecraft] shall employ the principle of least privilege, allowing only authorized accesses processes which are necessary to accomplish assigned tasks in accordance with system functions.{SV-AC-6}{AC-3,AC-6,AC-6(9),CA-9,CM-5,CM-5(5),CM-5(6),SA-8(2),SA-8(5),SA-8(6),SA-8(14),SA-8(23),SA-17(7),SC-2,SC-7(29),SC-32,SC-32(1),SI-3} |  |