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. |

| Subject: | RE: AD Child Domains |
|---|---|
| Date: | Thu, 24 Apr 2008 06:34:38 -0700 |
Raoul: this should be negotiated at the political level before scrambling to find a technical solution. There is nothing particularly "strict" about PCI's password guidelines. It's clear that PCI is enough of a driver in your organization to have sparked this discussion (which is good), however PCI is focused primarily on protecting cardholder data. The PCI DSS as written today is not a draconian Security Standard. My best advice before you complicate your AD environment would be to make sure that standard password enforcement is absolutely out of the question. Given the huge increase in client-side attacks over the last 18 months, it is in your organization's best interest to get these users out of the dark ages. You're not forcing the use of SecureID tokens here - this is standard 21st Century common sense. This sounds like an education and socialization question; not a technical one. My 2 cents. Sheldon Malm Director Security Research & Development nCircle Network Security Check out the VERT daily post http://blog.ncircle.com/vert -----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
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | RE: Setting up mail server(s) ?, hdm |
|---|---|
| Next by Date: | Re: Re: HTTP tunneling to bypass proxy filter, uglyhunK |
| Previous by Thread: | AD Child Domains, Raoul Armfield |
| Next by Thread: | RE: AD Child Domains, Rhett Grant |
| Indexes: | [Date] [Thread] [Top] [All Lists] |