1200KM / sigma-rule
Azure Domain Federation Settings Modified — Sigma Rule
Sigma rule 352a54e1-74ba-4929-9d47-8193d67aba1e. Azure Domain Federation Settings Modified — Sigma Rule. Identifies when an user or application modified the federation settings on the domain.
Rule metadata and linked tags
Author: Austin Songer. Source status: test; severity: medium. Source dates: 2021-09-06 / 2022-06-08.
{
"product": "azure",
"service": "auditlogs"
}Pinned original Sigma rule · Detection Rule License 1.1
Source SHA-256: ce64728e94d9dba47fb581a873750d73fe087c2a1917991b893cccabe1d181ae
Detection logic
Original source YAML. Source-tag agreement is not proof of complete semantic coverage. This rule has not been compiled for a SIEM backend or validated against live telemetry here.
title: Azure Domain Federation Settings Modified
id: 352a54e1-74ba-4929-9d47-8193d67aba1e
status: test
description: Identifies when an user or application modified the federation settings on the domain.
references:
- https://learn.microsoft.com/en-us/azure/active-directory/hybrid/how-to-connect-monitor-federation-changes
author: Austin Songer
date: 2021-09-06
modified: 2022-06-08
tags:
- attack.privilege-escalation
- attack.persistence
- attack.initial-access
- attack.stealth
- attack.t1078
logsource:
product: azure
service: auditlogs
detection:
selection:
ActivityDisplayName: Set federation settings on domain
condition: selection
falsepositives:
- Federation Settings being modified or deleted may be performed by a system administrator.
- Verify whether the user identity, user agent, and/or hostname should be making changes in your environment.
- Federation Settings modified from unfamiliar users should be investigated. If known behavior is causing false positives, it can be exempted from the rule.
level: medium
False positives
- Federation Settings being modified or deleted may be performed by a system administrator.
- Verify whether the user identity, user agent, and/or hostname should be making changes in your environment.
- Federation Settings modified from unfamiliar users should be investigated. If known behavior is causing false positives, it can be exempted from the rule.
Source references
Connected ecosystem references
Exact source-tagged techniques
Telemetry review
Read the original logsource above, then inspect the linked detection workspaces for technique-level sensor context. No per-rule telemetry equivalence is inferred.
Pinned research references. No browser attack runner, live simulation result or validated detector is asserted. Source mappings and validation limits are preserved. ATT&CK / Atomic provenance · Detection provenance.