1. Why the directory is a priority target
The central directory holds the list of users, groups and permissions, and it is often the system on which workstations, email and many applications depend. Anyone who gains control of the directory can create access, change permissions and erase their own traces. For this reason, controls on this service must be treated as an absolute priority, even in a small company.
Hardening the directory does not mean applying dozens of settings at once. It means choosing a few high-impact controls, applying them in a verifiable way and maintaining them over time. This guide sets out which ones, in what order and how to tell that the work has succeeded.
2. Prerequisites before you act
Several conditions must be in place before you change any setting. A wrong change to this service can block access for the whole organisation, so the work must be prepared carefully.
- An up-to-date inventory of who administers the directory
- A copy of the current configuration, stored securely
- A change window agreed with those who use the connected systems
- A contact who can decide on exceptions
3. Administrative groups and privileged accounts
The first intervention concerns the groups with administrative powers over the directory. These groups must be few, known and reviewed regularly. Every membership must be justified, and service accounts should not appear among the administrators without an explicit, documented reason.
Create a separate administrative identity for whoever manages the directory, and limit use of that identity to the operations that require it. Administrators should not browse the web or read email with the same account. Any external supplier must have temporary, logged access. A practical check is to ask how many people can create new accounts or change permissions in a single step. The answer should be short, and every name on that list should have a written reason.
4. Password and authentication policies
Password rules should be written to discourage predictable choices and to block reuse of credentials that are already compromised. The strongest current guidance favours long passwords, checked against lists of exposed credentials, and second-factor authentication for administrative access. Mandatory, very frequent expiry dates, on the other hand, often make people's choices worse and should be reconsidered.
Lockout after failed attempts must be configured with care: an overly strict lockout can become a tool in an attacker's hands, who uses it to lock users out. Ask your consultant how to balance the two needs in your environment.
5. Protecting controllers and logs
The servers hosting the directory, known as controllers, are the core of the service. They must be protected like the most critical systems, with restricted network access and logs that cannot be altered by those who administer them day to day.
- Limit which workstations and networks can connect to the directory controllers.
- Apply security updates within defined timeframes, with prior verification on the connected systems.
- Enable logging of changes to users, groups and permissions, and keep the logs in a separate location.
- Review the logs at regular intervals and define who receives alerts about unusual changes.
- Disable obsolete authentication protocols, after verifying which applications still use them.
- Define a tested recovery procedure for the directory, with verified backup copies.
6. Common mistakes to avoid
The first mistake is leaving administrative groups with members who have never been reviewed, often added for a project that ended long ago. The second is disabling an old protocol without knowing which applications use it, causing unexpected outages. The third is having directory backups that have never been restored: you discover they do not work exactly when you need them.
The fourth mistake is assuming the directory alone protects everything. Connected applications, workstations and service credentials remain points of access and must be considered together with the directory.
7. How to verify the directory is more secure
Check progress with concrete evidence. Verify that administrative groups contain only approved people, that recent changes are logged and that a recovery test completes successfully in a separate environment. For each setting changed, note the date, the reason and the test results on the connected applications.
This record demonstrates the work carried out and is also useful when a supplier or auditor asks about the configuration. A useful indicator is the time taken to respond to a request to recover a locked account. If the process is slow or unclear, simplify it without weakening the controls, otherwise people will look for shortcuts.
8. How to start
This week, list the groups with administrative powers over the directory and the people who belong to them. Remove, with approval, memberships that no longer have a reason. Then check whether a recent copy of the configuration exists and when the recovery was last tested. With these two checks you have already reduced the main risk without changing anything critical. Also record who carried out the check and the date, so the work remains readable even after a change of personnel.
Frequently Asked Questions
Can I harden the directory without stopping work?
Yes, if you proceed in small, verifiable steps. Changes that affect authentication or password policies must be announced, tested first in a test environment and applied in an agreed window. Changes to administrative groups, on the other hand, can often be made straight away, because they do not affect people's daily work.
Is a well-configured directory enough to be secure?
No. Configuration is necessary but not sufficient. You also need an identity management process, protection for privileged accounts, monitoring of changes and the ability to respond to an incident. The directory is the central point, not the only defence.
Who should have administrative control of the directory?
A few people, chosen by role and approved by their manager. Ideally, whoever manages it uses a separate identity and does not use it for day-to-day work. An external supplier, if there is one, should have temporary and logged access, not permanent access.
How can I tell whether the directory has already been compromised?
It is not simple to establish with certainty. Indicators to check are unjustified changes to administrative groups, accounts created outside the process, unusual access at odd hours and undocumented policy changes. If you notice anything of this kind, involve your security consultant immediately and do not alter the traces before they have been preserved.
When can an obsolete protocol be disabled?
There is no general rule. What matters is which application still uses it and why. An obsolete protocol should be disabled only after testing and verifying which applications depend on it. The decommissioning plan must be written and communicated, with an alternative ready.