ASD ISM 1931 Ensure SID filtering for domain and forest trusts
What it says
SID Filtering is enabled for domain and forest trusts.
Quoted as published. Everything else on this page is written by Control Stack.
In plain English
Keep SID filtering enabled on every external domain trust and forest trust, so sign-ins arriving over the trust cannot carry SIDs from outside the trusted domain or forest.
SID Filtering must be enabled on domain and forest trusts. A trust lets accounts in another domain or forest use your resources. SID filtering makes your domain controllers drop any security identifier (SID) in a sign-in that does not belong to the trusted domain or forest, such as one planted in an account's sIDHistory attribute. Domain trusts here are external trusts, which link to one domain in another forest. Domains inside one forest are not filtered from each other, because the forest is the security boundary.
Free. Save your status, tasks and notes.
Why it matters
Without filtering, an administrator or intruder in the trusted domain or forest can add one of your privileged group SIDs to an account's sIDHistory and be treated as a member of that group on your systems. Filtering strips such SIDs at the trust.
How to implement
List every trust in each of your domains.
Run Get-ADTrust -Filter * in each domain, recording the partner, direction and type of each trust, and mark the external and forest trusts.
Check and enable filtering on your side of each trust.
From the trusting domain, run netdom trust with /quarantine for an external trust, which should report SID filtering enabled, and with /enablesidhistory for a forest trust, which should report SID history disabled. Where either is not, finish any migration relying on sIDHistory, then set /quarantine:yes or /enablesidhistory:no under change control.
Finish migrations instead of relaxing filtering.
Filtering is usually turned off so migrated users keep old access through sIDHistory. Re-permission resources to the users' new accounts and groups, remove sIDHistory as ISM-1936 requires, then turn filtering back on.
Control your side of a trust with another organisation.
Your domain controllers apply filtering to sign-ins arriving from the trusted side, so your setting protects your resources. Ask the other organisation to keep filtering on for its side too.
Keep it running
Recheck filtering whenever a trust is created, reset or changed, and after any migration project. Domain controllers log trust changes as security events 4706 (new trust) and 4716 (trust modified), which can trigger the check.
Evidence and audit
- Check 1 of 2What an auditor asks for
Ask for
Every trust listed directly from each domain's domain controllers, and netdom output for each external and forest trust, run from the trusting side.
Look at
Whether each external trust reports SID filtering enabled and each forest trust reports SID history disabled.
Good evidence
Every external trust shows SID filtering (quarantine) enabled and every forest trust shows SID history disabled, with no trust left relaxed for a migration or a partner's request.
- Check 2 of 2What an auditor asks for
Ask for
Security events 4706 and 4716 from the domain controllers since the last check, with the matching change records.
Look at
Each trust created or modified, and whether filtering was checked afterwards.
Good evidence
The log covers the whole period, every trust created or changed has a matching change record, and each shows filtering enabled when checked afterwards.
Mappings
Closest match in ISO/IEC 27001: A.8.9, Configuration management, which this control partially meets.
ISO/IEC 27001: 1 mapping
This control partially meets A.8.9.
ISM-1931 requires SID Filtering to be enabled on domain and forest trusts to prevent abuse of SIDHistory/foreign SIDs across trust boundaries. Annex A 8.9 mandates organisations to establish secure configurations across systems and networks, which includes configuring Active Directory trusts securely. ISM-1931 specifies a technical configuration requirement within the broader configuration management expectations of Annex A 8.9.
Mappings show how controls relate across frameworks. They do not imply full equivalence or certification.




