UCF STIG Viewer Logo
Changes are coming to https://stigviewer.com. Take our survey to help us understand your usage and how we can better serve you in the future.
Take Survey

Directory data (outside the root DSE) of a non-public directory must be configured to prevent anonymous access.


Overview

Finding ID Version Rule ID IA Controls Severity
V-14798 DS00.3130_2008_R2 SV-39012r2_rule ECAN-1 ECCD-1 ECCD-2 High
Description
To the extent that anonymous access to directory data (outside the root DSE) is permitted, read access control of the data is effectively disabled. If other means of controlling access (such as, network restrictions) are compromised, there may be nothing else to protect the confidentiality of sensitive directory data.
STIG Date
Windows Server 2008 R2 Domain Controller Security Technical Implementation Guide 2015-09-02

Details

Check Text ( C-46919r1_chk )
Verify anonymous access is not allowed to the AD domain naming context.

Open a command prompt (not elevated).
Run "ldp.exe".
From the Connection menu, select Bind.
Select Simple bind for the Bind type.
Clear the User, Password, and Domain fields, Click OK.

Confirmation of anonymous access will be displayed at the end:
res = ldap_simple_bind_s
Authenticated as: 'NT AUTHORITY\ANONYMOUS LOGON'

From the Browse menu, select Search.
In the Search dialog, enter the DN of the domain naming context (generally something like "dc=disaost,dc=mil") in the Base DN field.
Clear the Attributes field and select Run.

Error messages should display related to binds and user not authenticated.

If attribute data is displayed, anonymous access is enabled to the domain naming context and this is a finding.
Fix Text (F-45051r1_fix)
Configure directory data (outside the root DSE) of a non-public directory to prevent anonymous access.

For AD, there are multiple configuration items that could enable anonymous access.

Changing the access permissions on the domain naming context object (from the secure defaults) could enable anonymous access. If the check procedures indicate this is the cause, the process that was used to change the permissions should be reversed. This could have been through the Windows Support Tools ADSI Edit console (adsiedit.msc).

The dsHeuristics option is used. This is addressed in check V-8555 in the AD Forest STIG.