Title

The Tanium Server must be configured to only allow signed content to be imported. (Cat II impact)

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.

Check Content

Note: This requirement only applies to Tanium implementations in production. If implementation being evaluated is in development, this requirement is Not Applicable. Access the Tanium Server through interactive logon. Drill to Program Files >> Tanium >> Tanium Server. Open the "tanium.license" in Notepad and search for "allow_unsigned_import". If "allow unsigned_import" is followed by ":true", this is a finding.

Fix Text

Contact Tanium for a corrected license file.

Additional Identifiers

Rule ID: SV-234087r612749_rule

Vulnerability ID: V-234087

Group Title: SRG-APP-000131

Expert Comments

CCIs tied to check.

Controls tied to check. These are derived from the CCIs shown above.