Skip to content

Windows Event ID 4675: SIDs were filtered

Written when SIDs are filtered (excluded) for an Active Directory trust. It shows the operation of the mechanism that prevents privileges from being illicitly carried across a trust.

Overview

The subcategory is Audit Logon. It is generated when SID filtering takes effect for a specific AD trust (a relationship in which one domain/forest accepts authentication from another). SID filtering removes, from an access token brought in from the trusting side, any SID that does not belong to the trusted domain, preventing privilege escalation that abuses SID History.

How it is triggered

  • When a SID subject to filtering is excluded during authentication across a trust.
  • It occurs in environments that have domain/forest trusts with SID filtering enabled.

Security review points

  • A record that SID filtering took effect can indicate that a privilege SID (especially a privileged group’s SID) that should not be carried across the trust was being brought in. It can relate to an attempt at cross-trust privilege escalation abusing SID History.
  • Check which trust and which SID was excluded, and review whether the trust configuration (filtering enabled/disabled) is appropriate.

Notes for log review

  • It only carries meaning in environments with trusts. Without forest/domain trusts it basically does not appear.
  • A one-off is often configuration-induced. If it concentrates on a specific trust or SID, investigate with related logs, keeping the possibility of an attack in view.

MITRE ATT&CK mapping

TechniqueTacticWhat this event shows
T1134.005 SID-History InjectionStealth, Privilege EscalationRecords privileged SIDs brought across a trust and removed by filtering

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

Detection rules

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

RuleTypeSeverity
EatonForeseer - Unauthorized LoginsSentinel (needs setup)High

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 whose SIDs were filtered
Trust InformationThe trust direction, attributes, type, and the trusted domain’s SID
Filtered SIDsThe excluded SIDs

Glossary

  • SID History — an attribute that carries an old SID over during account migration. Abused, it can inject privileged SIDs across a trust, which is why SID filtering blocks it.

References