victim - account which privileges we’d relay (e.g. DA)
desired service - service account to which we’d relay victim’s auth
infected account, either fake (newly created specifically for the attack) or owned by an attacker
Desired service account should have an msDS-AllowedToActOnBehalfOfOtherIdentity attribute featuring a infected account’s SPN. (You should be able to create fake machine account (if you do NOT already own one!) and modify target service’s attributes (if it DOESN’T feature your owned account already!)) (not default)
The victim should be not in “Protected Users” group. (default)
The victim should not have an “Account is sensitive and cannot be delegated” attribute set. (default)
Infected account should have an TRUSTED_TO_AUTH_FOR_DELEGATION flag featured in it’s userAccountControl attribute
Infected account (that is set inside of msDS-AllowedToActOnBehalfOfOtherIdentity of a target service) should have an SPN (machine accounts BY DEFAULT have GenericWrite to themselves, so if you compromise a machineaccount you can write an SPN to it) (user accounts BY DEFAULT DO NOT have GenericWrite to themselves, so if you compromise a useraccount you can NOT write an SPN to it, it should already have an SPN) (default)
If relay to LDAP, LDAP singing should be OFF (default)