Applies to BloodHound Enterprise and CE Privilege Zones has two tabs: Tiers (Zones) and Labels. Zones allow the logical separation of objects into three unique hierarchical groups according to the structure of your environment. Labels are a flexible tool to categorically bucket different objects. Together, these tools enable further risk mitigation in your environments by highlighting the violations and misconfigurations to your customized network model. Zones and Labels each offer two views: Summary and Detail. Use the view selector (drop-down) in the UI to toggle between them.
  • Summary shows the zone/label name, selector count, object count, and, for Zones, their hierarchy (the top zone is most critical).
  • Detail lists every selector and the objects that each selector pulls into the chosen zone or label.
Summary View: Privilege Zones summary view Detail View: Privilege Zones detail view

​
Zones

​
Creating a Privilege Zone

  1. Navigate to “Privilege Zones” in the left menu
Navigate to Priv Zones
  1. Click “Create Tier”
Create a tier
  1. Enter all relevant information about the zone
Configure new zone
  1. Click “Define Selector” to save your new Privilege Zone and continue on to define the objects to include in the zone

​
Labels

​
Creating a Label

  1. Select “Create Label”
  2. Add a name and an optional description
  3. Click “Define Selector” to save the label
Configure a new label

​
Selectors

Zone Selectors provide a logical method of ensuring objects appear in the appropriate zone using either a Cypher query or by searching for an object ID. If an object has been added to multiple Zones, the most critical zone in your defined hierarchy will take precedence. Label Selectors are a flexible method of tagging objects in the environments. Objects can have multiple labels, and those labels are searchable and filterable using Cypher in the Explore page. The process and screens for creating and editing label selectors is the same as creating or editing zone selectors. Any changes made to a selector will take effect on the next analysis. Defining a selector using Cypher Example of Cypher selector Defining a selector using Object ID Example of an Object ID selector

​
Defining a Selector

If you start defining a selector via the zone creation process, skip to step 2.
  1. From the Zone or Labels tab, select “Create Selector”
  2. Provide a name
  3. Optionally add a description to explain to others on your team, including yourself, the purpose of the Selector
  4. Choose a selector type: Cypher or object ID
  5. If using Cypher:
    1. Enter the Cypher query into the “Cypher Search” box
    2. To see the sample results, click “Update Sample Results” above the Cypher query box. The first 200 sample results will populate the list to the right
    3. Optionally, click “View in Explore” to pivot to the explore page and view the full Cypher query results
  6. If using object ID
    1. Type in the blank to search for an object
    2. Select that object to add to the list
  7. Adding the following object types will automatically include (→) more objects according to the definition below
    1. OU/Container → All objects contained in the OU/container
    2. Group → All objects with membership in the Group
    3. AZResourceGroup/AZSubscription → All objects contained in the RG/Sub
    4. AZGroup → All objects with membership in the group
    5. AZRole → All objects with role assignments (or eligibility)
  8. Click “Save” to finalize the creation of the selector
Selectors can be enabled or disabled by editing the selector.

​
Deleting a Selector

Example of an Object ID selector
  1. Navigate to the detail view of the zone or label
  2. Click on the zone or label containing the desired selector
  3. Click on the desired selector
  4. Click “Edit” which will open the selector management page
  5. Click on “Delete Selector” below the middle column of the page
  6. Confirm your changes by typing “Delete this selector” and clicking “confirm”
Delete a selector modal
  1. A toast message will appear in the top right corner of the screen confirming the selector was deleted
Selector successfully deleted toast message

​
Disable/Enable a Selector

  1. From the detail view click on a selector
  2. Click “Edit” to enter edit mode
  3. Under the “Defining Selector” column on the left, click the Enabled/Disabled to toggle the selector
Selector enable/disable toggle

​
Predefined Selectors

BloodHound provides a set of selectors by default that places known critical objects into Tier 0 according to SpecterOps best practices. Some of these selectors can be disabled while others cannot.
SelectorDisable-ableTypeReason
Account OperatorsTRUEDC groupThe Account Operators group has GenericAll in the default security descriptor on the AD object classes: User, Group, and Computer. That means all objects of these types will be under full control of Account Operators unless they are protected with AdminSDHolder. Not all Tier Zero objects will be protected with AdminSDHolder typically, as not all Tier Zero objects will be included in Protected Accounts and Groups. This means Account Operators members have a path to compromise Tier Zero most often.



It is possible to delete all GenericAll ACEs for Account Operators on Tier Zero objects. To protect future Tier Zero objects, one would have to either remove the Account Operators ACE from the default security descriptors or implement a process of removing the ACEs as Tier Zero objects are being created. However, we recommend not using the group and classifying it as Tier Zero instead.
AdministratorFALSEAD userThe built-in Administrator account has admin access to DCs by default and is therefore Tier Zero.
AdministratorsFALSEDC groupThe Administrators group has full control over most of AD’s essential objects and are inarguably part of Tier Zero.
AdminSDHolderFALSEAD containerThe permissions configured on AdminSDHolder is a template that will be applied on Protected Groups and Users with SDProp, by default every hour. Control over AdminSDHolder means you have control over the Protected Groups (and their members) and Users, which include Tier Zero groups such as Domain Admins. The AdminSDHolder container is therefore a Tier Zero object.
AIA CA (AD object)TRUEAD objectThe AIA CA objects may represent offline enterprise CAs or cross CAs. In such cases, deleting the AIA CA object would cause certificates, potentially of Tier Zero principals, to lose trust. We therefore recommend to treat AIACAs as Tier Zero.
Application AdministratorTRUEEntra ID roleThe Application Administrator role can control tenant-resident apps. This includes creating new credentials for apps, which can be used to authenticate the tenant as the app’s service principal and abuse the service principal privileges. The role is therefore considered Tier Zero if the tenant contains any Tier Zero service principals.
Azure tenant objectFALSEEntra ID roleAn attacker with control of the Tenant Root Object has control of all identities, applications, roles, and devices that reside in that tenant. Further, control of the Tenant Root Object enables an attacker to gain control of all Azure Resource Manager subscriptions that trust the tenant. This object is therefore considered Tier Zero.
AZUREADSSOACC objectTRUEEntra ID roleMicrosoft automatically creates the AZUREADSSOACC account when enabling Seamless SSO. When configured for Seamless SSO, this object can modify any synced object within an Azure environment, granting significant control over the organization.
Backup OperatorsFALSEDC groupThe Backup Operators group has the SeBackupPrivilege and SeRestorePrivilege rights on the domain controllers by default. These privileges allow members to access all files on the domain controllers, regardless of their permission, through backup and restore operations. Additionally, Backup Operators have full remote access to the registry of domain controllers. To compromise the domain, members of Backup Operators can dump the registry hives of a domain controller remotely, extract the domain controller account credentials, and perform a DCSync attack. Alternative ways to compromise the domain exist as well. The group is considered Tier Zero because of these known abuse techniques.
Cert PublishersTRUEAD groupThe Cert Publishers group has full control permissions on root CA and AIA CA objects. This enables an attacker to add or remove certificates for these objects, which are trusted throughout the AD forest. As certificate authentication requires the certificate to chain up to a trusted root CA, an attacker could prevent successful authentication for AD accounts and disrupt Tier Zero operations. The group is therefore Tier Zero.

In some environments, the group also has full control over the NTAuth store. In that scenario, the group can take over the forest by adding a forged root certificate, making it trusted for NTAuth.
Certificate templateTRUEAD objectControl over a certificate template enables the ADCS ESC4 attack and Tier Zero takeover if the template is published to a CA trusted in the NTAuth store and that chains up to a trusted root CA. There are default templates that meet this requirement; others remain unpublished. A template cannot be used if it is not published, making control over an unpublished object less concerning. However, if it is ever published, it becomes a risk. We, therefore, recommend treating all certificate templates as Tier Zero objects, whether published or not.
Cryptographic OperatorsTRUEDC groupThe Cryptographic Operators group has the local privilege on domain controllers to perform cryptographic operations but no privilege to log in.

There are no known ways to abuse the membership of the group to compromise Tier Zero. The local privilege the group has on the domain controllers is considered security dependencies, and the group is therefore considered Tier Zero.
Distributed COM UsersTRUEDC groupThe Distributed COM Users group has local privileges on domain controllers to launch, activate, and use Distributed COM objects but no privilege to log in.

There are no known ways to abuse the membership of the group to compromise Tier Zero. The local privileges the group has on the DCs are considered security dependency, and the group is therefore considered Tier Zero.
DNS AdminsTRUEAD groupDnsAdmins controls DNS which enables an attacker to trick a privileged victim to authenticate against an attacker-controlled host as it was another host. This enables a Kerberos relay attack. Also, control over DNS enables disruption of Tier Zero since Kerberos depends on DNS by default.

The group could previously use a feature in the Microsoft DNS management protocol to make the DNS service load any DLL and thereby obtain a session as SYSTEM on the DNS server. This vulnerability was patched in Dec 2021.
Domain AdminsFALSEAD groupThe Domain Admins group has full control over most of AD’s essential objects and are inarguably part of Tier Zero.
Domain ControllersFALSEAD groupThe Domain Controllers group has the GetChangesAll privilege on the domain. This is not enough to perform DCSync, where the GetChanges privilege is also required.

There are no known ways to abuse membership in this group to compromise Tier Zero. However, the GetChangesAll privilege is considered a security dependency that should only be held by Tier Zero principals. Additionally, control over the group allows one to impact the operability of Tier Zero by removing domain controllers from the group, which breaks AD replication. The group is therefore considered Tier Zero.
Domain root objectFALSEAD objectAn attacker with control over the domain root object can compromise the domain in multiple ways, for example by a DCSync attack (see reference). The domain root object is therefore Tier Zero.
Enterprise AdminsFALSEAD groupThe Enterprise Admins group has full control over most of AD’s essential objects and are inarguably part of Tier Zero.
Enterprise CA (AD object)TRUEAD objectControl over an enterprise CA object enables an attacker to publish certificate templates. If any templates that allow ADCS domain escalation exist but are unpublished, then control over the enterprise CA object could enable a takeover of Tier Zero. An attacker could potentially also disrupt or takeover Tier Zero by deleting the certificate of the enterprise CA or changing the DNShostName of the enterprise CA to an attacker-controlled host. Enterprise CA objects are therefore Tier Zero.

If the enterprise CA certificate is removed from the NTAuth store, certificates from this CA cannot be used for domain authentication, thus preventing a Tier Zero takeover.
Enterprise CA ComputersTRUEAD computerEnterprise CAs can by default issue certificates that enable authentication as anyone, thereby allowing takeover of Tier Zero. An attacker with admin rights on an enterprise CA can obtain a certificate as any user in different ways. One option is to dump the private key of the CA and craft a ‘golden certificate’ as a target user. This attack can be prevented by protecting the private key with hardware. Alternatively, the attacker can publish any template, modify pending certificate requests, and issue denied requests, which typically also enable a takeover of Tier Zero. Enterprise CA computer objects are therefore Tier Zero.

If the enterprise CA certificate is removed from the NTAuth store, then certificates from this CA cannot be used for domain authentication, thus preventing a Tier Zero takeover.
Enterprise Domain ControllersFALSEDC objectThere are no known ways to abuse membership in this group to compromise Tier Zero. However, the GetChangesAll privilege is considered a security dependency that should only be held by Tier Zero principals. Additionally, control over the group allows one to impact the operability of Tier Zero by removing domain controllers from the group, which breaks AD replication. The group is therefore considered Tier Zero.
Enterprise Key AdminsFALSEAD groupThe Enterprise Key Admins group has write access to the msds-KeyCredentialLink attribute on all users (not protected by AdminSDHolder) and on all computers in the AD forest. This enables the group to compromise all these principals through Shadow Credentials attacks. The group is therefore considered Tier Zero.
Exchange Trusted SubsystemTRUEAD groupThe Exchange Trusted Subsystem group has takeover permissions on all users with the default ACL inheritance enabled from the domain, regardless of the permission model Exchange is configured to. The compromising permission is write access to the AltSecurityIdentities attribute, which allows an attacker to add an explicit mapping for the user for domain authentication. Typically, some Tier Zero users inherit permissions from the domain. The group is therefore Tier Zero.



The group can only be treated as non-Tier Zero if all Tier Zero users are protected from this compromising permission.
Exchange Windows PermissionsTRUEAD groupThe Exchange Windows Permissions group has takeover permissions on all users (WriteDACL and reset password) and all groups (edit membership) with the default ACL inheritance enabled from the domain, if Exchange is configured with the default shared permission model or the RBAC split model. Typically, some Tier Zero users and groups inherit permissions from the domain. The group is therefore Tier Zero.

If Exchange is configured in the AD split model, then this group has no compromising permissions and can be treated as non-Tier Zero.
Global AdministratorFALSEEntra ID roleThe Global Administrator role is the highest privilege role in Entra ID and inarguably part of Tier Zero. It can do almost anything, and grant permission to do the things it cannot do.
Intune AdministratorTRUEEntra ID roleThe Intune Administrator role has permission to execute scripts locally on Entra-managed devices. The role has therefore a potential attack path to Tier Zero through Entra-managed devices used by Tier Zero principals. Furthermore, the Intune Administrator role can manage Conditional Access, which can be abused to lower the security of Tier Zero or prevent the operability of Tier Zero. The role is therefore considered Tier Zero.
Key AdminsFALSEAD groupThe Key Admins group has write access to the msds-KeyCredentialLink attribute on all users (not protected by AdminSDHolder) and on all computers in the AD domain. This enables the group to compromise all these principals through Shadow Credentials attacks. The group is therefore considered Tier Zero.
Knowledge AdministratorTRUEEntra ID roleThe Knowledge Administrator role can control non-role-assignable groups. If any non-role-assignable group has compromising permissions over a Tier Zero asset (e.g. Contributor on a domain controller Azure VM), then the Knowledge Administrator role can add arbitrary principals to the given group and compromise Tier Zero. If no non-role-assignable group has compromising permissions over a Tier Zero asset, then there is no attack path to Tier Zero from the Knowledge Administrator role. It therefore depends on the usage of non-role-assignable groups whether the role should be considered Tier Zero.
KRBTGT objectsTRUEAD userThe krbtgt’s credentials allow one to create golden ticket and compromise the domain. Therefore, if you obtain the credentials of this account, then you can authenticate as any Tier Zero user. However, there is currently no known privilege on the object to obtain the Kerberos keys or to compromise the account in any other way. When you reset the password of krbtgt, AD will ignore your password input and use a random string instead. So, the reset password privilege does not work for a compromise. An attacker could use the reset password privilege to harm Tier Zero, as a double password reset causes all Kerberos TGTs in the domain to become invalid. So, since control over the account can harm Tier Zero, and there is no reason for delegating control to non-Tier Zero, the krbtgt is Tier Zero.
NTAuth storeTRUEAD objectThe NTAuth store is a security dependency for Tier Zero. A certificate that impersonates any user in AD must chain up to a trusted root CA and be issued by a CA trusted by the NTAuth store. With control over a root CA and the NTAuth store, an attacker can make an attacker-controlled root CA certificate meet these requirements and issue certificates as anyone, taking over Tier Zero. Control over the NTAuth store alone may be sufficient to disrupt Tier Zero operations, as the attacker can delete CA certificates that Tier Zero principals or systems rely on for authentication. The NTAuth store is therefore Tier Zero.
Partner Tier2 SupportFALSEEntra ID roleThe Partner Tier2 Support role can reset the password for any principal, including principals with the Global Administrator role. The role is therefore considered Tier Zero.
Performance Log UsersTRUEDC groupThe Performance Log Users group has local privileges on domain controllers to launch, activate, and use Distributed COM objects but no privilege to log in.

There are no known ways to abuse the membership of the group to compromise Tier Zero. The local privileges the group has on the DCs are considered security dependency, and the group is therefore considered Tier Zero.
Print OperatorsTRUEDC groupThe Print Operators group has the local privilege on the domain controllers to load device drivers and can log on locally on domain controllers by default.

It is feasible to remove the logon privilege from the group on the domain controllers, such that the group has no known abusable path to Tier Zero. However, the local privilege to load device drivers is considered a security dependency for the domain controllers, and the group is therefore considered Tier Zero.
Privileged Authentication AdministratorFALSEEntra ID roleThe Privileged Authentication Administrator role can set or reset any authentication method (including passwords) for any principal, including principals with the Global Administrator role. The role is therefore considered Tier Zero.
Privileged Role AdministratorFALSEEntra ID roleThe Privileged Role Administrator role can grant any other admin role to any principal at the tenant level. The role is therefore considered Tier Zero.
Read-Only Domain ControllersTRUEAD computerAn attacker with control over a RODC computer object can compromise Tier Zero principals. The attacker can modify the msDS-RevealOnDemandGroup and msDS-NeverRevealGroup attributes of the RODC computer object such that the RODC can retrieve the credentials of a targeted Tier Zero principal. The attacker can obtain admin access to the OS of the RODC through the managedBy attribute, from where they can obtain the credentials of the RODC krbtgt account. With that, the attacker can create a RODC golden ticket for the target principal. This ticket can be converted to a real golden ticket as the target has been added to the msDS-RevealOnDemandGroup attribute and is not protected by the msDS-NeverRevealGroup attribute. Therefore, the RODC computer object is Tier Zero.
Root CA objectTRUEAD objectA root CA is a security dependency for Tier Zero. A certificate that impersonates any user in AD must chain up to a trusted root CA and be issued by a CA trusted by the NTAuth store. With control over a root CA and the NTAuth store, an attacker can make an attacker-controlled root CA certificate meet these requirements and issue certificates as anyone, taking over Tier Zero. Control over a root CA alone may be sufficient to disrupt Tier Zero operations, as the attacker can delete root CA certificates that Tier Zero principals or systems rely on for authentication. Root CA objects are therefore Tier Zero.
Schema AdminsFALSEAD groupThe Schema Admins group has full control over the AD schema. This allows the group members to create or modify ACEs for future AD objects. An attacker could grant full control to a compromised principal on any object type and wait for the next Tier Zero asset to be created, to then have a path to Tier Zero. This attack could be remediated by removing any unwanted ACEs on objects before they are promoted to Tier Zero, but we recommend considering the group as Tier Zero instead.
Security AdministratorTRUEEntra ID roleThe Security Administrator role has access to Live Response API (if not disabled) with permission to execute scripts locally on Entra-managed devices. The role has therefore a potential attack path to Tier Zero through Entra-managed devices used by Tier Zero principals. Furthermore, the Security Administrator role can manage Conditional Access, which can be abused to lower the security of Tier Zero or prevent the operability of Tier Zero. The role is therefore considered Tier Zero.
Server OperatorsTRUEDC groupThe Server Operators group has local privileges on the domain controllers and perform administrative operations as creating backups of all files. The group can log on locally on domain controllers by default.

It is feasible to remove the logon privilege from the group on the domain controllers, such that the group has no known abusable path to Tier Zero. However, the local privileges are considered security dependencies for the domain controllers, and the groups are therefore considered Tier Zero.