Search filters this STIG's checks locally. Separate terms must all match (use quotes for an exact phrase). A search you ran on the Search page carries over here.
Assessment Title
Rule Text
The Configuration Management (CM) repository must be properly patched and STIG compliant.
Description
Discussion Text
A Configuration Management (CM) repository is used to manage application code versions and to securely store application code.
Failure to properly apply security patches and secure the software Configuration Management system could affect the confidentiality and integrity of the application source-code.
Compromise of the Configuration Management system could lead to unauthorized changes to applications including the addition of malware, root kits, back doors, logic bombs or other malicious functions into valid application code.
This requirement is intended to be applied to application developers or organizations responsible for code management or who have and operate an application CM repository.
Failure to properly apply security patches and secure the software Configuration Management system could affect the confidentiality and integrity of the application source-code.
Compromise of the Configuration Management system could lead to unauthorized changes to applications including the addition of malware, root kits, back doors, logic bombs or other malicious functions into valid application code.
This requirement is intended to be applied to application developers or organizations responsible for code management or who have and operate an application CM repository.
New to STIG checklists? Read What is a STIG checklist? and CKL vs CKLB.