Provide Digitally Signed Certificates for Releases

In order to increase the security around the SonarQube application and its plugins, it is recommended to provide digitally signed certificates in order to validate it has not been tampered with and that it has been provided from a trusted vendor.

This is a recommendation provided by DISA STIG’s, namely the Application Security and Development STIG. DISA provides a standard in securing applications that can be used across public and private entities.

These digitally signed certificates should be provided with each release, readily accessible to validate against the product.

Below is the identified STIG vulnerability associated to this.

Application Security and Development Security Technical Implementation Guide :: Release: 10 Benchmark Date: 25 Oct 2019

Vul ID : V-69509 Rule ID : SV-84131r1_rule STIG ID : APSC-DV-001430
Severity : CAT II Classification : Unclass

Rule Title : 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.

Discussion : 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 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.

Check Text : Review the application documentation and interview the application administrator to determine the process and commands used for patching the application.

Access application configuration settings.

Review commands and procedures used to patch the application and ensure a capability exists to prevent unsigned patches from being applied.

If the application is not capable of preventing installation of patches and packages that are not signed, or if the vendor does not provide a cryptographic hash value that can be manually checked prior to installation, this is a finding.

Fix Text : 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.

References

CCI : CCI-001749: The information system prevents the installation of organization-defined software components without verification the software component has been digitally signed using a certificate that is recognized and approved by the organization.
NIST SP 800-53 Revision 4 :: CM-5 (3)

Greetings,

Append .asc to any download link you find for SonarQube editions or plugins and you’ll find a signature!

Example: sonarqube-datacenter-8.2.0.32929.zip.asc

Thank you for providing this information. I think it would be highly beneficial to having this information more readily available on the download page.

Is there any plans to also implement the use of hashes along with the signature?