For Security & Risk Professionals

Primary Analyst Photo	Document Information	Rate this Document
	August 11, 2009 Active Directory Q&A: Demand Rises Directory Consolidation Saves On Administrative Costs, Eases Provisioning by Andras Cser with Robert Whiteley, Margaret Ryan	Average: 10  (1 rating)

This is an excerpt

Executive Summary

For the past 10 years, Active Directory (AD) has remained the backbone of identity infrastructures. Organizations continue to struggle with consolidating AD domains across the enterprise and centralizing ownership for them. Business partners' information is usually stored separately from employee data, usually in a different AD domain. Those organizations that were able to address the security concerns of putting AD in the DMZ usually created a separate AD domain in the DMZ with trust relationships carefully managed. Although auditing and providing domain-specific and minimal privileges for system administrators remains problematic with AD (often requiring third-party tools), most companies do not see any near-term alternatives to using AD for managing Windows users, groups, and computers.

TABLE OF CONTENTS

• 1. Who owns AD and lightweight directory access protocol (LDAP) in the organization?
• 2. How do you handle mergers and acquisitions (M&A) with AD and LDAP?
• 3. How do you store business-to-business (B2B) users' information in AD?
• 4. How do you put AD in the DMZ?
• 5. How do you enforce password policies in AD?
• 6. How do you track changes in AD?
• 7. How do you manage sensitive access to AD?
• 8. What are the typical models for AD topology design?
• 9. What are some of the alternatives to AD?
• 10. What are some of the issues around AD and LDAP infrastructure?

This is an excerpt

Buy Risk-Free

Price: US $499

Our Service Guarantee: If you are not completely satisfied with this document, notify Forrester within 24 hours of purchase for a full refund.

Already a Forrester Client?
Log in to read this document.