Skip to content

Commit c69064b

Browse files
authored
AB#180930 Update recover-from-golden-gmsa-attack.md
1 parent 8f5fafa commit c69064b

1 file changed

Lines changed: 2 additions & 1 deletion

File tree

support/windows-server/windows-security/recover-from-golden-gmsa-attack.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: How to recover from a Golden gMSA attack
33
description: Describes how to repair compromised gMSAs after a Golden gMSA attack.
4-
ms.date: 08/25/2023
4+
ms.date: 09/06/2023
55
manager: dcscontentpm
66
audience: itpro
77
ms.topic: troubleshooting
@@ -88,6 +88,7 @@ The approach is to create a new KDS Root Key object that's unknown to the attack
8888
> - You don't have to manually repair gMSAs that were created after the Active Directory Domain Services (AD DS) database exposure ended. The attacker doesn't know the details of these accounts, and the passwords for these accounts will regenerate based on the new KDS Root Key object.
8989
> - You should consider the gMSA object in "maintenance mode" until the procedure is completed, and ignore possible errors that are reported with the accounts in the System, Security, Directory Services, and Security-Netlogon event log.
9090
> - The guide assumes that the gMSAs are child objects of the **Managed Service Accounts** container. If you have moved the accounts to custom parent containers, you need to run the steps related to the **Managed Service Accounts** container on the gMSA in these containers.
91+
> - An authoritative restore rolls back all attributes to the time of backup, including the accounts that are allowed to retrieve the gMSA credentials (`PrincipalsAllowedToRetrieveManagedPassword`).
9192
9293
In the domain holding the gMSAs that you want to repair, follow these steps:
9394

0 commit comments

Comments
 (0)