ACTIVE DIRECTORY SECURITY CHECKLIST ... - Leet Upload

ACTIVE DIRECTORY SECURITY CHECKLIST ... - Leet Upload ACTIVE DIRECTORY SECURITY CHECKLIST ... - Leet Upload

leetupload.com
from leetupload.com More from this publisher
19.07.2013 Views

Active Directory Checklist, V1R1.2 Field Security Operations 22 September 2006 Defense Information Systems Agency DS05.0130 Synch\Maint Inter-Enclave LDAP\HTTP Usage STIG ID \ V-Key DS05.0130 \ V0011760 Severity Cat II Short Name Synch\Maint Inter-Enclave LDAP\HTTP Usage IA Controls DCPP-1 MAC /Conf 1-CSP, 2-CSP, 3-CSP References AD STIG 2.3.1.3 DODI 8551.1 Long Name: A synch\maint implementation that spans enclave boundaries and uses LDAP or HTTP protocol does not use a VPN to protect the network traffic. Checks: • Interview the Application SA. • With the assistance of the SA, NSO, or network reviewer as required, review the application documentation and the site network diagram(s) to determine if the synch\maint implementation transfers directory data across enclave boundaries and uses the LDAP or HTTP protocol. - The object is to determine if application traffic is traversing enclave network boundaries and if LDAP or HTTP is used. [Retain this information for use in a subsequent check.] • If the synch\maint implementation does *not* transfer data across enclave boundaries or does *not* use LDAP or HTTP, then this check is Not Applicable. • If the synch\maint implementation transfers data using LDAP or HTTP, review the site network diagram(s) with the assistance of the SA, NSO, or network reviewer as required, to determine if a VPN is used to transport the directory data network traffic. • If a VPN solution is not used to transport directory data network traffic across enclave boundaries, then this is a Finding. Note: This check and the associated requirement are based on DoD ports and protocols restrictions stated in DoD Instruction 8551.1 and linked documents. UNCLASSIFIED 3-12

Active Directory Checklist, V1R1.2 Field Security Operations 22 September 2006 Defense Information Systems Agency DS05.0140 Synch\Maint Inter-Enclave LDAPS\HTTPS Usage STIG ID \ V-Key DS05.0140 \ V0011761 Severity Cat II Short Name Synch\Maint Inter-Enclave LDAPS\HTTPS Usage IA Controls DCPP-1 MAC /Conf 1-CSP, 2-CSP, 3-CSP References AD STIG 2.3.1.3 DODI 8551.1 Long Name: A synch\maint implementation that spans enclave boundaries and uses LDAPS or HTTPS protocol does not use a DODI 8551.1-compliant solution to protect the network traffic. Checks: • Interview the Application SA. • If the response to check DS05.0130 indicates that directory data *is* transferred across enclave boundaries, review the application documentation to determine if the synch\maint implementation uses the LDAPS or HTTPS protocol. • If directory data is *not* transferred across enclave boundaries or does *not* use LDAPS or HTTPS, then this check is Not Applicable. • If the synch\maint implementation transfers data using LDAPS or HTTPS, review the site network diagram(s) with the assistance of the SA, NSO, or network reviewer as required, to determine if a DODI 855.1-compliant network configuration is in use. - This generally means that the traffic must flow through a DMZ to comply with the PPSM requirements for LDAPS and HTTPS. • If the LDAPS or HTTPS traffic does not flow through a compliant network configuration, then this is a Finding. UNCLASSIFIED 3-13

Active Directory Checklist, V1R1.2 Field Security Operations<br />

22 September 2006 Defense Information Systems Agency<br />

DS05.0130 Synch\Maint Inter-Enclave LDAP\HTTP Usage<br />

STIG ID \ V-Key DS05.0130 \ V0011760<br />

Severity Cat II<br />

Short Name Synch\Maint Inter-Enclave LDAP\HTTP Usage<br />

IA Controls DCPP-1<br />

MAC /Conf 1-CSP, 2-CSP, 3-CSP<br />

References AD STIG 2.3.1.3<br />

DODI 8551.1<br />

Long Name: A synch\maint implementation that spans enclave boundaries and uses LDAP or<br />

HTTP protocol does not use a VPN to protect the network traffic.<br />

Checks:<br />

• Interview the Application SA.<br />

• With the assistance of the SA, NSO, or network reviewer as required, review the<br />

application documentation and the site network diagram(s) to determine if the<br />

synch\maint implementation transfers directory data across enclave boundaries<br />

and uses the LDAP or HTTP protocol.<br />

- The object is to determine if application traffic is traversing enclave network<br />

boundaries and if LDAP or HTTP is used.<br />

[Retain this information for use in a subsequent check.]<br />

• If the synch\maint implementation does *not* transfer data across enclave<br />

boundaries or does *not* use LDAP or HTTP, then this check is Not Applicable.<br />

• If the synch\maint implementation transfers data using LDAP or HTTP, review<br />

the site network diagram(s) with the assistance of the SA, NSO, or network<br />

reviewer as required, to determine if a VPN is used to transport the directory data<br />

network traffic.<br />

• If a VPN solution is not used to transport directory data network traffic across<br />

enclave boundaries, then this is a Finding.<br />

Note: This check and the associated requirement are based on DoD ports and<br />

protocols restrictions stated in DoD Instruction 8551.1 and linked documents.<br />

UNCLASSIFIED<br />

3-12

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!