Active Directory Forest STIG Version Comparison

There are 6 differences between versions v2 r7 (Jan. 27, 2017) (the "left" version) and v3 r1 (Sept. 13, 2024) (the "right" version).

Check AD.3145_AD was added to the benchmark in the "right" version.

This check's original form is available here.

Title

Windows Server hosting Active Directory Certificate Services (AD CS) must enforce Certificate Authority (CA) certificate management approval for certificate requests.

Check Content

Certificate templates with the following extended key usages AND that allow a requestor to supply the subject name in the request must require manual approvaI. In the AD CS web server properties, select "VulnerableCertTemplate" properties. Verify that "Subject Name" and "Supply in the request" are selected. If "Subject Name" and "Supply in the request" are not selected, this is a finding.

Discussion

When users are requesting new certificates through AD CS, there must be management approval and awareness for these requests. Without this, a user or bad actor could request certificates they should not have or should not have access to.

Fix

In the AD CS web server properties, select "VulnerableCertTemplate" properties and then select "Subject Name" and "Supply in the request". Certificate templates with the following extended key usages must require manual approval in all cases: i. Smart Card Logon (1.3.6.1.4.1.311.20.2.2). ii. Any Purpose EKU (2.5.29.37.0). iii. No EKU set. i.e., this is a (subordinate) CA certificate. Certificate templates with the following extended key usages AND that allow a requestor to supply the subject name in the request must require manual approval: i. Client Authentication (1.3.6.1.5.5.7.3.2). ii. PKINIT Client Authentication (1.3.6.1.5.2.3.4). iii. Supply in request" setting: VulnerableCertTemplate Properties.