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.0350 Synch\Maint Certificate Validity Checking STIG ID \ V-Key DS05.0350 \ V0011772 Severity Cat III Short Name Synch\Maint Certificate Validity Checking IA Controls IAAC-1 MAC /Conf 1-CS, 2-CS, 3-CS References AD STIG 2.3.3.8 Long Name: A synch\maint product that utilizes PKI certificates does not perform certificate validation that includes CRL or OCSP checking. Checks: • Interview the Application SA. • Review the application documentation or configuration settings to determine if the synch\maint implementation utilizes PKI certificates. • If PKI certificates are *not* used, then this check is Not Applicable. • If PKI certificates *are* used, review the application documentation or configuration settings to determine if the product performs certificate validation that includes CRL or OCSP checking. - Note that certificates could be used in multiple parts of the implementation such as client authentication of the server *and* server authentication of the client. All uses should be examined. • If the synch\maint implementation utilizes PKI certificates and the product does not perform certificate validation that includes CRL or OCSP checking, then this is a Finding. Note: At this time it is understood that SimpleSync, MIIS, and IIFP do *not* perform CRL or OCSP checking. UNCLASSIFIED 3-24

Active Directory Checklist, V1R1.2 Field Security Operations 22 September 2006 Defense Information Systems Agency DS05.0370 Synch\Maint Mutual Authentication STIG ID \ V-Key DS05.0370 \ V0011773 Severity Cat III Short Name Synch\Maint Mutual Authentication IA Controls ECTM-1. ECTM-2 MAC /Conf 1-CSP, 2-CSP, 3-CSP References AD STIG 2.3.3.8 Long Name: A synch\maint implementation does not perform authentication of the synch\maint client and target directory server (mutual authentication). Checks: • Interview the Application SA. • Review the application documentation or configuration settings to determine if the synch\maint implementation performs authentication of the synch\maint client *and* the target directory server. - For client authentication this could include the use of an ID\password for the client to access the server. - For the server authentication this could include the use of LDAPS or HTTPS in which the client validates the server’s PKI certificate. • If the synch\maint implementation does not perform mutual authentication, then this is a Finding. UNCLASSIFIED 3-25

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

22 September 2006 Defense Information Systems Agency<br />

DS05.0370 Synch\Maint Mutual Authentication<br />

STIG ID \ V-Key DS05.0370 \ V0011773<br />

Severity Cat III<br />

Short Name Synch\Maint Mutual Authentication<br />

IA Controls ECTM-1. ECTM-2<br />

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

References AD STIG 2.3.3.8<br />

Long Name: A synch\maint implementation does not perform authentication of the<br />

synch\maint client and target directory server (mutual authentication).<br />

Checks:<br />

• Interview the Application SA.<br />

• Review the application documentation or configuration settings to determine if<br />

the synch\maint implementation performs authentication of the synch\maint client<br />

*and* the target directory server.<br />

- For client authentication this could include the use of an ID\password for the<br />

client to access the server.<br />

- For the server authentication this could include the use of LDAPS or HTTPS in<br />

which the client validates the server’s PKI certificate.<br />

• If the synch\maint implementation does not perform mutual authentication, then<br />

this is a Finding.<br />

UNCLASSIFIED<br />

3-25

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

Saved successfully!

Ooh no, something went wrong!