|Finding ID||Version||Rule ID||IA Controls||Severity|
|Non-DoD-approved PKIs have not been evaluated to ensure they have security controls and identity vetting procedures in place that are sufficient for DoD systems to rely on the identity asserted in the certificate. PKIs lacking sufficient security controls and identity vetting procedures risk being compromised and issuing certificates that enable adversaries to impersonate legitimate users.|
|Apache Server 2.4 Windows Server Security Technical Implementation Guide||2022-12-14|
|Check Text ( C-15564r277559_chk )|
| Review the "ssl.conf" file. |
Look for the "SSLCACertificateFile" directive.
Review the path of the "SSLCACertificateFile" directive.
Review the contents of <'path of cert'>\ca-bundle.crt.
Examine the contents of this file to determine if the trusted CAs are DoD approved.
If the trusted CA that is used to authenticate users to the website does not lead to an approved DoD CA, this is a finding.
NOTE: There are non-DoD roots that must be on the server for it to function. Some applications, such as antivirus programs, require root CAs to function. DoD-approved certificate can include the External Certificate Authorities (ECA), if approved by the AO. The PKE InstallRoot 3.06 System Administrator Guide (SAG), dated 08 Jul 2008, contains a complete list of DoD, ECA, and IECA CAs.
|Fix Text (F-15562r277560_fix)|
|Configure the web server's trust store to trust only DoD-approved PKIs (e.g., DoD PKI, DoD ECA, and DoD-approved external partners).|