Rule version TCAT-AS-001430 · STIG v3 · 2026-08-26
Use of self-signed certificates creates a lack of integrity and invalidates the certificate based authentication trust model. Certificates used by production systems must be issued/signed by a trusted Root CA and cannot be self-signed. For systems that communicate with industry partners, the DoW ECA program supports the issuance of DoW-approved certificates to industry partners. For information on the DoW ECA program, refer to the DoW PKI office. Links to their site are available on https://public.cyber.mil.
For the systemd Ubuntu OS, check the tomcat.service file to read the content of the JAVA_OPTS environment variable setting.
sudo cat /etc/systemd/system/tomcat.service |grep -i truststore
EXAMPLE output: set JAVA_OPTS="-Djavax.net.ssl.trustStore=/path/to/truststore" "-Djavax.net.ssl.trustStorePassword=************"
If the variable is not set, use the default location command below. If the variable is set, use the alternate location command below and include the path and truststore file.
-Default location: keytool -list -cacerts -v | grep -i issuer
-Alternate location: keytool -list -keystore <location of trust store file> -v |grep -i issuer
If there are no CA certificates issued by a Certificate Authority (CA) that is part of the DoW PKI/PKE, this is a finding.
Obtain and install the DoW PKI CA certificate bundles by accessing the DoW PKI office website at https://cyber.mil/pki-pke.
Download the certificate bundles and then use certificate management utilities such as keytool or openssl to import the DoW CA certificates into the trust store.