Application URI Configuration Changes
Detects when a configuration change is made to an applications URI. URIs for domain names that no longer exist (dangling URIs), not using HTTPS, wildcards at the end of the domain, URIs that are no unique to that…
Description
Detects when a configuration change is made to an applications URI. URIs for domain names that no longer exist (dangling URIs), not using HTTPS, wildcards at the end of the domain, URIs that are no unique to that app, or URIs that point to domains you do not control should be investigated.
Detection logic
Detection requirements
- Platform
- ContainersIaaSIdentity ProviderOffice SuiteSaaS
The rule states no platform. This is derived from the 2 ATT&CK techniques it maps to.
- Log source product
- azure
- Log source service
- auditlogs
Known benign triggers
- When and administrator is making legitimate URI configuration changes to an application. This should be a planned event.
MITRE ATT&CK mappings
0 exclusive techniques.This is coverage no other published rule has; it is not this rule's total technique count.
References
| Reference | Cited by |
|---|---|
| learn.microsoft.com/en-us/entra/architecture/security-operations-applications#application-configuration-changes | 13from 2 sources |
From the source
- At source
- Open at source
- Upstream identifier
- 0055ad1f-be85-4798-83cf-a6da17c993b3
- Tagged by the source as
- attack.credential-accessattack.initial-accessattack.persistenceattack.privilege-escalationattack.stealth
Licence
- Published under
- Detection Rule License 1.1Read the licence
- Attribution
- Required
Authorship
- Published
- Aug 26, 2026
- Version
- 1