CyberKit

Event IDs

Security event 4751

A member was added to a security-disabled global group

Channel: Security. Category: Distribution Group Management.

What it records

Records that an account was added as a member of a security-disabled global (distribution) group. Generated only on domain controllers, with a separate event per member added.

Why it matters

Because distribution-group membership doesn't grant system access, this is mainly of interest for a short allowlist of sensitive lists (for example, confirming who was added to a security-alerting or executive distribution list) rather than broad security monitoring.

What triggers it

Legitimately triggered whenever someone is added to a mailing/distribution list through Exchange, Outlook, or AD tools; only worth alerting on for a small set of curated high-value lists.

Fields that carry the answer

Key fields
FieldWhat it tells you
Member > Account NameDistinguished name of the account added to the distribution group, which confirms exactly who gained membership.
Group > Group NameThe name of the distribution group, only worth investigating if it's on a curated high-value watchlist.

In practice

Member > Account Name shows CORP\newhire.jdoe being added to Group > Group Name "DL-AllStaff" through routine Outlook self-service. This event is low-priority unless the distribution list is on a monitored high-value watchlist (e.g. "DL-SecurityAlerts"), where an unexpected addition could indicate reconnaissance or social-engineering staging.

Sample record

A member was added to a security-disabled global group.

Subject:
	Security ID:		S-1-5-21-3457937927-2839227994-823803824-1110
	Account Name:		svc-exchange
	Account Domain:		CORP
	Logon ID:		0x3E4B02

Member:
	Security ID:		S-1-5-21-3457937927-2839227994-823803824-2415
	Account Name:		CN=John Doe,OU=NewHires,DC=corp,DC=local

Group:
	Security ID:		S-1-5-21-3457937927-2839227994-823803824-3020
	Group Name:		DL-AllStaff
	Group Domain:		CORP

Additional Information:
	Privileges:		-

Sources

Paste a record into Event XML or open a log in EVTX Reader.