Spoof Security Alerting
Adversaries may spoof security alerting from tools, presenting false evidence to impair defenders' awareness of malicious activity. Messages produced by defensive tools contain information about potential security events as well as the functioning status of security software and the system. Rather than or in addition to Indicator Blocking, an adversary can spoof positive affirmations that security tools are continuing to function even after legitimate security tools have been disabled. An adversary can also present a 'healthy' system status even after infection. For example, adversaries may show a fake Windows Security GUI and tray icon with a 'healthy' system status after Windows Defender and other system tools have been disabled. This technique was observed in Black Basta ransomware campaigns using custom EDR evasion tools tied to FIN7.
let SecurityTrayProcesses = dynamic([
"SecurityHealthSystray.exe", "SecurityHealthHost.exe",
"MSASCuiL.exe", "NisSrv.exe"
]);
let DefenderServiceNames = dynamic([
"WinDefend", "SecurityHealthService",
"wscsvc", "Sense", "WdNisSvc"
]);
union
(
DeviceProcessEvents
| where Timestamp > ago(24h)
| where FileName in~ (SecurityTrayProcesses)
| where not(FolderPath startswith "C:\\Windows\\System32" or FolderPath startswith "C:\\Program Files\\Windows Defender" or FolderPath startswith "C:\\ProgramData\\Microsoft\\Windows Defender")
| project Timestamp, DeviceName, AccountName, FileName, FolderPath,
ProcessCommandLine, InitiatingProcessFileName,
SHA256, DetectionType="FakeSecurityProcess_WrongPath"
),
(
DeviceProcessEvents
| where Timestamp > ago(24h)
| where ProcessCommandLine has_any ("SecurityHealth", "Windows Defender", "WindowsSecurity")
| where FileName !in~ (SecurityTrayProcesses)
| where FileName !in~ ("MsMpEng.exe", "svchost.exe", "services.exe")
| project Timestamp, DeviceName, AccountName, FileName, FolderPath,
ProcessCommandLine, InitiatingProcessFileName,
SHA256, DetectionType="SpoofedSecurityUI"
),
(
DeviceProcessEvents
| where Timestamp > ago(24h)
| where ProcessCommandLine has_any ("sc stop WinDefend", "sc stop SecurityHealthService", "sc stop wscsvc", "Set-MpPreference -DisableRealtimeMonitoring", "sc config WinDefend start= disabled")
| project Timestamp, DeviceName, AccountName, FileName,
ProcessCommandLine, InitiatingProcessFileName,
InitiatingProcessCommandLine,
DetectionType="DefenderServiceDisabled"
)
| sort by Timestamp desc Data Sources
Required Tables
False Positives
- Third-party security tools (Norton, McAfee, Bitdefender) that may reference 'Windows Security' or 'SecurityHealth' strings in their own process command lines for integration purposes
- System administrators legitimately stopping Windows Defender services during installation of an alternative AV product as part of a documented migration
- Portable security scanning tools run from USB or temporary directories that contain 'Defender' or 'Security' in their file names
- Windows Update or feature updates that temporarily restart SecurityHealthService from a staging directory before moving files to their final location
References (5)
- https://attack.mitre.org/techniques/T1562/011/
- https://www.sentinelone.com/labs/black-basta-ransomware-attacks-deploy-custom-edr-evasion-tools-tied-to-fin7-threat-actor/
- https://www.microsoft.com/en-us/security/blog/2022/05/09/ransomware-as-a-service-understanding-the-cybercrime-gig-economy-and-how-to-protect-yourself/
- https://learn.microsoft.com/en-us/defender-endpoint/prevent-changes-to-security-settings-with-tamper-protection
- https://www.crowdstrike.com/blog/carbon-spider-embraces-big-game-hunting/
Unlock Pro Content
Get the full detection package for T1562.011 including response playbook, investigation guide, and atomic red team tests.