Skip to content
This repository was archived by the owner on Feb 12, 2025. It is now read-only.
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 6 additions & 1 deletion ATPDocs/ensure-privileged-accounts-with-sensitive-flag.md
Original file line number Diff line number Diff line change
Expand Up @@ -14,7 +14,7 @@ ms.date: 10/05/2024

# Security Assessment: Ensure that all privileged accounts have the configuration flag "this account is sensitive and cannot be delegated"

This recommendation lists all privileged accounts that lack the "account is sensitive and cannot be delegated" flag. Privileged accounts are accounts that are being members of a privileged group such as Domain admins, Schema admins, Read only domain controllers and so on. 
This recommendation lists all privileged accounts that lack the "account is sensitive and cannot be delegated" flag. Privileged accounts are accounts that are being members of a privileged group such as Domain admins, Schema admins, writable domain controllers, Read only domain controllers and so on. 

## Organization risk

Expand All @@ -30,6 +30,11 @@ If the sensitive flag is disabled, attackers could exploit Kerberos delegation t

![Screenshot showing admin in AD.](media/ensure-privileged-accounts-with-sensitive-flag/administrator-properties.png)

With Powershell, you can set the flag using one of:
Set-ADUser -Identity <user> -AccountNotDelegated $true
Set-ADComputer -Identity <computer> -AccountNotDelegated $true
Set-ADServiceAccount -Identity <(g|d)MSA> -AccountNotDelegated $true

## Next steps

[Learn more about Microsoft Secure Score](/microsoft-365/security/defender/microsoft-secure-score)
Expand Down