Skip to content

Windows Event ID 4765: SID History was added to an account

Written when SID History is added to an account. SID History is a legitimate migration feature, but abused it can quietly inherit privileged SIDs, so it is used for attack-side privilege escalation and persistence.

Overview

The subcategory is Audit User Account Management. It is generated when a SID is added to an account’s sIDHistory attribute. Its proper purpose is to carry over an old domain’s SID during a domain migration to preserve resource access.

How it is triggered

  • Legitimate SID History assignment by a domain migration tool (such as ADMT).
  • A technique where an attacker uses mimikatz or similar to inject a privileged group’s SID (such as Domain Admins) into a target account’s sIDHistory.

Security review points

  • SID History injection is powerful persistence and privilege escalation. Planting the Domain Admins SID into an ordinary user’s sIDHistory grants admin rights without changing group membership directly (without producing 4732, etc.). Because it is hard to detect, treat the occurrence of 4765 itself as significant.
  • Strongly suspect it if 4765 appears with no domain-migration plan, or if the added SID belongs to a privileged group.

Notes for log review

  • It normally almost never occurs. Investigate a 4765 with no legitimate context (such as a migration project) at high priority.
  • Check what the added SID refers to (whether a privileged group). Read it together with the failure version 4766.

MITRE ATT&CK mapping

TechniqueTacticWhat this event shows
T1134.005 SID-History InjectionStealth, Privilege EscalationInjecting a privileged group’s SID into sIDHistory

Mapping as of ATT&CK v19.2. To search by technique, see the ATT&CK reverse lookup.

Detection rules

SigmaHQ has 1 public detection rule that uses this event ID as a condition.

RuleTypeSeverity
Addition of SID History to Active Directory ObjectSigmaMedium

Rules are collected from SigmaHQ r2026-07-01 and from Azure-Sentinel as of 2026-10-09, limited to those whose conditions include this event ID. Sentinel rules are limited to those that query the SecurityEvent or WindowsEvent table. “Threat-specific” rules target a particular threat group or malware, and “needs setup” rules require values for your environment. Severity is the value each rule’s author assigned.

Key fields

FieldMeaning
Target Account\Account NameThe account SID History was added to
Source Account / added SIDThe inherited SID (check whether privileged)
Subject\Account NameThe subject that performed the operation

Glossary

  • SID History — an attribute that carries over a source account’s SID. Abused, it can inherit privileges without joining a group.

References