AAA protocols perform the access decision work, while directory services catalogue identities and resources that AAA systems can query. In practice, AAA answers who can access what and under which conditions, while LDAP-based directories store the user and device data that supports those decisions. The two are complementary, but they serve different roles in enterprise access control.
How AAA and directory services split the job
AAA protocols and directory services are often used together, but they are not the same layer. AAA protocols handle the live access transaction, including authentication, authorisation, and accounting. Directory services hold the identity records, group membership, device attributes, and policy inputs that the AAA system consults when it needs to make a decision.
That distinction matters operationally because the protocol is the enforcement point, while the directory is the source of truth. If the directory is unavailable or stale, AAA may still be running, but its decisions can be incomplete, out of date, or forced into fallback behaviour that changes the security posture.
A useful mental model is that AAA asks, "Should this session be allowed now?" while the directory answers, "What do we know about this user, device, or resource?" The directory may also store attributes that support group-based or role-based policy, but it does not itself enforce the network access decision.
Where LDAP fits, and where it does not
LDAP-based directories are commonly associated with this pattern because they expose a standard way to query identity data. In network access control, that data can include usernames, device objects, group membership, and organisational attributes that feed policy. NHIMG’s AAA Security Guide explains this split across AAA, RADIUS, TACACS+, and directory-backed policy lookups.
LDAP is not the access decision engine. It does not decide whether a device should be placed on the corporate VLAN, sent to quarantine, or granted administrative access. Instead, it supplies the records and relationships that a RADIUS server, policy engine, or network access server can evaluate against an access rule.
This is why teams sometimes misdiagnose an access issue. If an operator edits the directory and expects access to change immediately, the actual enforcement point may still be caching attributes, waiting on replication, or applying a different source of policy. In practice, the network path, AAA server, and directory must all be checked when access behaves unexpectedly.
Why the separation matters in network access control
In NAC, the protocol side and the directory side solve different problems. The AAA side handles the interactive exchange at connection time, while the directory side helps describe who or what is connecting and what that subject is entitled to do. That is why a NAC deployment may query directory groups for a user, certificates for a device, and posture data from another control, all before making a final access choice.
That separation becomes especially important when the subject is a device rather than a person. Network access policies often need device identity, ownership, and trust state as well as user identity. Network Access Control (NAC) Guide covers how 802.1X, EAP-TLS, RADIUS hardening, device profiling, and dynamic VLAN assignment combine in that workflow.
It also explains why directory data alone is not enough. A directory can tell you that an account exists, but it cannot observe whether the endpoint is healthy, whether the certificate is current, or whether the session should be shifted into a restricted network segment. AAA plus policy enforcement fills that gap.
Risk and Threat Considerations
When organisations blur the boundary between AAA and directory services, they can create avoidable access risk. A stale group entry, a replicated directory delay, or an overbroad policy lookup can grant access that no longer matches the intended control. The same confusion can also hide failures, because teams may blame the directory when the real issue is AAA policy, or blame AAA when the underlying identity record is wrong.
Failure mechanism: Access decisions become inconsistent when the enforcement layer and the identity source drift apart, or when fallback paths and cached attributes continue to authorise sessions after the directory state has changed.
Impact: Users or devices may retain access after they should have lost it, while legitimate sessions may be denied or misrouted, increasing exposure, support load, and the chance of misconfiguration becoming a security incident.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
CIS Controls v8, NIST SP 800-53 Rev 5 and OWASP ASVS set the governance and control requirements practitioners need to meet.
| Framework | Control / Reference | Relevance |
|---|---|---|
| CIS Controls v8 | CIS-6 — Access Control Management | AAA and directory-backed access depend on centralized access control and revocation. |
| Recommendation — Centralize access decisions and revocation so AAA policy reflects current directory state. | ||
| NIST SP 800-53 Rev 5 | IA-2 — Identification and Authentication (Organizational Users) | AAA protocols perform live authentication for user access decisions in enterprise networks. |
| IA-9 — Identification and Authentication (Service and Application Accounts) | Network access control often includes device and non-user identities queried through AAA and directories. | |
| AC-2 — Account Management | Directory services hold account and group records that support access governance decisions. | |
| Recommendation — Use IA-2 to authenticate users before authorizing network access. Apply IA-9 when machine or service identities are part of network access decisions. Manage account lifecycle and group membership so directory data stays authoritative. | ||
| OWASP ASVS | V8 — Authorization | The AAA versus directory split is fundamentally about authorization decisions and supporting identity data. |
| Recommendation — Separate authorization checks from identity storage and enforce decisions server-side. | ||
Practitioner Guidance
What to verify: Confirm which system is authoritative for each decision type, whether authentication, authorisation, accounting, or attribute lookup, and verify that the AAA server is querying the intended directory source rather than a stale replica or cached policy store.
Decision rule: If an access issue affects who is allowed in, start with AAA policy and decision logs; if it affects who the subject is, start with the directory record, group membership, or device object. When both appear normal, check replication timing, attribute caching, and network path dependencies before changing policy.
Practitioner takeaway: Treat the directory as identity data plumbing and AAA as the decision layer. The control fails in practice when teams expect one to substitute for the other instead of validating both parts of the access chain.
Related resources from NHI Mgmt Group
- Why do combined network and application permissions improve access control for internal services?
- What is the difference between network-level access control and identity-based access control for internal services?
- How should security teams balance on-premises directory services with cloud access control in a hybrid environment?
- How should security teams control network access when Active Directory is not enough on its own?
Deepen Your Knowledge
Free weekly newsletter
Subscribe to the NHI & AI Identity Journal
The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.
Bonus 33% off our NHI Course when you subscribe.
Reviewed and updated by the NHIMG editorial team on October 30, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org