Threat Directory > AD domain with unsecure RBCD delegation on domain controllers

AD domain with unsecure RBCD delegation on domain controllers

Cayosoft Threat Definition CTD-000089

Protect Your Active Directory

Tune into Guardians of the Directory Podcast.

Guardians of the Directory

Like This Article?​

Subscribe to our LinkedIn Newsletter to receive more educational content

Risk Summary

Unsecure Resource-Based Constrained Delegation (RBCD) permissions on domain controllers allow attackers with certain delegated rights to impersonate almost any user in the domain. This includes the ability to access sensitive systems and data without needing direct privileged account credentials.
  • Severity: Critical
  • Platform: Active Directory
  • Category: Infrastructure
  • MITRE ATT&CK Tactics: Credential Access
  • MITRE D3FEND Tactics: Application Configuration Hardening

Description

A threat actor could exploit this vulnerability by identifying non-privileged users outside of Domain Admins, Enterprise Admins, or Built-in Admins groups who have write access to RBCD settings on domain controllers.
With write access, attackers can configure a resource to impersonate any user (except those explicitly excluded in delegation settings).
This enables them to access services and systems under the guise of high-value accounts, bypassing normal authentication restrictions.

Cayosoft Guardian Protector™

Real-World Scenario

In a large enterprise, a helpdesk technician account is mistakenly granted write permissions to RBCD settings on a domain controller.
An attacker compromises the technician’s account and uses these rights to configure a controlled machine to impersonate a domain admin. The attacker then remotely connects to critical servers, extracts password hashes, and moves laterally without triggering standard privileged account alerts.
Cayosoft Guardian could have detected the unsecure delegation settings early, preventing the escalation.

Stop Privilege Escalation—Then Undo It with Cayosoft Guardian

Real-time alerts across AD & Entra ID with one-click rollback.

How to Detect (Cayosoft Guardian)

1.) Sign in to Cayosoft Guardian Threat Detection Dashboard.

2.) Search for CTD-000089 or AD domain with unsecure RBCD delegation on domain controllers.

3.) Open any alert and Click for details (from Raise Threat Alert action).

4.) Review the evidence to see which accounts or groups have write permissions to RBCD settings on domain controllers.

Remediation Steps

Using the remediation advice in Cayosoft Guardian, follow these steps to remove the vulnerability:

To change permissions using Active Directory Users and Computers:

  1. ) Press View > Advanced features.
  2. ) Locate the domain controller object.
  3. ) Right-click on it, and select Properties.
  4. ) Select the Security tab.
  5. ) Remove unwanted users or groups.
  6. ) Click OK to save the permission settings.

How to Prevent It

  • Limit delegation rights strictly to trusted administrative accounts.
  • Periodically audit RBCD permissions across all domain controllers.
  • Use Cayosoft Guardian to continuously monitor delegation settings and receive real-time alerts for misconfigurations.

FAQ

RBCD is a Kerberos feature that allows a service or resource to act on behalf of a user when accessing another resource. It is designed for scenarios like front-end servers impersonating users to back-end services.

Domain controllers are the highest-value assets in Active Directory. If attackers gain the ability to set RBCD permissions on them, they can configure their own systems to impersonate privileged accounts, effectively bypassing authentication and MFA.

If a non-privileged account has write access to RBCD settings on domain controllers, attackers can abuse it to impersonate domain admins or service accounts, granting themselves unrestricted access to critical systems.

References

  • Microsoft Documentation – RBCD
  • ANSSI Advisory – vuln_delegation_a2d2

Final Thought

Unsecure RBCD on domain controllers is essentially a backdoor into impersonating admins. Closing this gap is critical to prevent stealthy privilege escalation attacks that bypass password and MFA protections.Bottom of Form