UAC Bypass via Windows Firewall Snap-In Hijack
Identifies attempts to bypass User Account Control (UAC) by hijacking the Microsoft Management Console (MMC) Windows Firewall snap-in. Attackers bypass UAC to stealthily execute code with elevated permissions.
Detection logic
Its licence does not clear it for publishing here
Sunturai publishes a detection's own text where the licence it arrived under has been reviewed and permits it, and Elastic License 2.0 has not. The query as its source wrote it, its canonical form and the hash that pins this revision are in the workspace record.
Detection requirements
- Platform
- IaaSIdentity ProviderLinuxmacOSOffice SuiteWindows
The rule states no platform. This is derived from the 2 ATT&CK techniques it maps to.
- Log source category
- event_index
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 |
|---|---|
| github.com/AzAgarampur/byeintegrity-uac | Only this detection cites it |
From the source
- At source
- Open at source
- Upstream identifier
- 1178ae09-5aff-460a-9f2f-455cd0ac4d8e
- Tagged by the source as
- Data Source: Elastic DefendData Source: Elastic EndgameData Source: Microsoft Defender XDRData Source: SentinelOneData Source: SysmonDomain: EndpointNoise: MediumOS: WindowsPerformance: NormalPlatform: WindowsProfile: RecommendedResources: Investigation GuideResources: OsqueryRule Type: Event Correlation (EQL)Tactic: Defense EvasionTactic: Privilege EscalationThreat: Living off the LandUse Case: Threat Detection
Licence
- Published under
- Elastic License 2.0Read the licence
- Attribution
- Required
Authorship
- Written by
- Published
- Sep 20, 2026
- Version
- 3