Skip to content

[Rule Tuning] Microsoft 365 Global Administrator Role Assigned #5288

@terrancedejesus

Description

@terrancedejesus

Summary

Microsoft 365 Global Administrator Role Assigned rule has an exclusion that causes FNs due it being a multi-value field and thus picking up multiple user types.

Example from testing:

o365.audit.Target.Type: [2, 2, 2, 5, 3]

Thus if we exclude 5 as we do in the query, it causes the rule to not fire.

event.dataset:o365.audit
    and event.code:"AzureActiveDirectory"
    and event.action:"Add member to role."
    and event.outcome: "success"
    and o365.audit.ModifiedProperties.Role_DisplayName.NewValue: (
        "Global Administrator" or "Company Administrator"
    )
    and o365.audit.AzureActiveDirectoryEventType: 1
    and o365.audit.RecordType: 8
    and not o365.audit.Target.Type: (4 or 5 or 6)

Thus we need to remove and not o365.audit.Target.Type: (4 or 5 or 6).

Image

NOTE: Rather than attempting to account for the variations / combinations of the target user types, it is best to remove this exclusion entirely.

Metadata

Metadata

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions