The application must have the capability to prevent the installation of patches, service packs, or application components without verification the software component has been digitally signed using a certificate that is recognized and approved by the organization.
An XCCDF Rule
Description
Changes to any software components can have significant effects on the overall security of the application. Verifying software components have been digitally signed using a certificate that is recognized and approved by the organization ensures the software has not been tampered with and that it has been provided by a trusted vendor. Accordingly, patches, service packs, or application components must be signed with a certificate recognized and approved by the organization. Verifying the authenticity of the software prior to installation validates the integrity of the patch or upgrade received from a vendor. This ensures the software has not been tampered with and that it has been provided by a trusted vendor. Self-signed certificates are disallowed by this requirement. The application should not have to verify the software again. This requirement does not mandate DOD certificates for this purpose; however, the certificate used to verify the software must be from an approved certificate authority (CA). If this capability is not present, the vendor must provide a cryptographic hash value that can be verified by a system administrator prior to installation.
- ID
- SV-222513r1015691_rule
- Version
- APSC-DV-001430
- Severity
- Medium
- References
- Updated
Remediation Templates
A Manual Procedure
Design and configure the application to have the capability to prevent unsigned patches and packages from being installed.
Provide a cryptographic hash value that can be verified by a system administrator prior to installation.