New identity security posture assessments: Unsecure SID-History attributes and Microsoft LAPS Usage


We are happy to announce two new Azure ATP identity security posture assessments for unsecure SID-History attributes and Microsoft LAPS usage.


What is the SID-History attribute?

SID History is an attribute that supports migration scenarios. Every user account has an associated Security Identifier (SID) which is used to track the security principal and the access the account has when connecting to resources. SID History enables access for another account to effectively be cloned to another and is extremely useful to ensure users retain access when moved (migrated) from one domain to another. 


What risk does unsecure SID History attribute pose?

Organizations that fail to secure their account attributes leave the door unlocked for malicious actors.

Malicious actors, much like thieves, often look for the easiest and quietest way into any environment. Accounts configured with an unsecure SID History attribute are windows of opportunities for attackers and can expose risks.

For example, a non-sensitive account in a domain can contain the Enterprise Admin SID in its SID History from another domain in the Active Directory forest, thus “elevating” access for the user account to effective Admin in all domains in the forest. Also, if you have a forest trust without SID Filtering enabled (also called Quarantine), it’s possible to inject a SID from another forest and it will be added to the user token when authenticated and used for elevated access.

How do I use this security assessment?

  1. Use the report table to discover which of your accounts have an unsecure SID History attribute. 


  • Take appropriate action to remove SID History attribute from the accounts using PowerShell using the following command:
    1. Identify the SID in the SIDHistory attribute on the account.

Get-ADUser -Identity <account> -Properties SIDHistory | Select-Object -ExpandProperty SIDHistory

2. Remove the SIDHistory attribute using the SID identified earlier.

Set-ADUser -Identity <account> -Remove @{SIDHistory='S-1-5-21-...'}



What is Microsoft LAPS?

Microsoft LAPS (Local Administrator Password Solution) provide a solution to the issue of using a common local account with an identical password on every computer in a domain. LAPS resolve this issue by setting a different, rotated random password for the common local administrator account on every computer in the domain.


Why should I use Microsoft LAPS?

LAPS simplify password management while helping customers implement additional recommended defenses against cyberattacks. In particular, the solution mitigates the risk of lateral escalation that results when customers use the same administrative local account and password combination on their computers. LAPS store the password for each computer’s local administrator account in Active directory, secured in a confidential attribute in the computer’s corresponding AD object. The computer can update its own password data in Active directory, and domain administrators can grant read access to authorized users or groups, such as workstation helpdesk administrators.


How do I use this security assessment?

  1. Use the report table to discover which of your domains have some (or all) compatible windows devices that are not protected by LAPS, or that have not had their LAPS managed password changed in the last 60 days.
  2. For domains that are partially protected, select the relevant row to view the list of devices not protected by LAPS in that domain. 


  1. Take appropriate action on those devices by downloading, installing, and configuring or troubleshooting Microsoft LAPS using the documentation provided in the LAPS download.



You can find these new assessments under the Identity Security Posture in the Cloud App Security portal (Azure ATP integration must be enabled).


We would love to get your insights!

0 Replies