STIGhubSTIGhub
STIGsSearchCompareAbout

STIGhub

A free tool to search and browse the entire DISA STIG library. Saves up to 75% in security compliance research time.

Navigation

  • Browse STIGs
  • Search
  • Compare Versions

Resources

  • About
  • VPAT
  • DISA STIG Library
Powered by Pylon
© 2026 Beacon Cloud Solutions, Inc. All rights reserved.
← Back to Apache Server 2.4 Windows Server Security Technical Implementation Guide

V-214328

CAT II (Medium)

The Apache web server must only accept client DOD-approved and RFC 5280-compliant certificates.

Rule ID

SV-214328r1192941_rule

STIG

Apache Server 2.4 Windows Server Security Technical Implementation Guide

Version

V3R4

CCIs

CCI-000185, CCI-002470

Discussion

A certificate's certification path is the path from the end entity certificate to a trusted root certification authority (CA). Certification path validation is necessary for a relying party to make an informed decision regarding acceptance of an end entity certificate. Certification path validation includes checks such as certificate issuer trust, time validity, and revocation status for each certificate in the certification path. Revocation status information for CA and subject certificates in a certification path is commonly provided via certificate revocation lists (CRLs) or online certificate status protocol (OCSP) responses. 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. Satisfies: SRG-APP-000175-WSR-000095, SRG-APP-000427-WSR-000186

Check Content

Review the <'INSTALLED PATH'>\conf\extra\httpd-ssl.conf file to determine if the "SSLVerifyDepth" and "SSLCACertificateFile" directives exist.

SSLVerifyDepth 1 

If "SSLVerifyDepth" is set to "0", this is a finding.

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 certificates can include the External Certificate Authorities (ECA), if approved by the authorizing official (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

Configure the web server's trust store to trust only DOD-approved PKIs (e.g., DOD PKI, DOD ECA, and DOD-approved external partners).

Edit the <'INSTALLED PATH'>\conf\extra\httpd-ssl.conf file.
 
Find the line "SSLVerifyDepth" and ensure it is set properly:
 
SSLVerifyDepth 1

Restart the Apache service.
 
"SSLVerifyDepth" is set based on the number of CAs that are required in the certificate chain to check before the client certificate is accepted as valid. A setting of "0" would allow self-signed CAs to validate client certificates, which is not desirable in this context.

Additional Information:
https://httpd.apache.org/docs/current/mod/mod_ssl.html