Ethical Hacking

Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package.
Computer Forensics Training at InfoSec Institute

Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors.




Network Security Security-Basics
[Top] [All Lists]

RE: AD Child Domains

Subject: RE: AD Child Domains
Date: Wed, 23 Apr 2008 20:08:39 -0400
-----Original Message-----
From: listbounce@securityfocus.com
[mailto:listbounce@securityfocus.com] On Behalf Of Raoul Armfield
Sent: Wednesday, April 23, 2008 2:43 PM
To: security-basics@securityfocus.com
Subject: AD Child Domains

We are in the process of making a modification to our AD structure.
For
PCI compliance we need to segregate a portion of our users to a
separate
domain.  This set of users do not need/want (and are very vocal about
it) to follow the stricter password policy that PCI mandates.

I understand that when you create a child domain it by default creates
a
two-way transitive trust between the two domains.  Is it possible to
limit this trust relationship to a one-way trust relationship?  If this
is possible it seems to me that it may be preferable to creating a new
forest just for a couple of hundred users.

Of course it is entirely possible that I am not thinking this through
completely and am missing some important factors to consider.  Your
thoughts would be greatly appreciated.

Raoul

There is no way (that I know of) to selectively configure the transitive
trust established between a parent/child domain.  I am not fully
understanding what you are trying to accomplish other than using a separate
password policy which a child domain will allow.  Only use a separate forest
to meet a security need.  And again I would be evaluating if it could be
done with a DACL.  It becomes much more complicated and time consuming to
manage two forests then to manage a parent/child Domain.

<Prev in Thread] Current Thread [Next in Thread>