Windows Defender Disabled Via SystemSettingsAdminFlows.EXE

SIGMA detection rule by Chirag Damani (KPMG India), Swachchhanda Shrawan Poudel (Nextron Systems) · NOASSERTION

Detects the usage of SystemSettingsAdminFlows.exe to disable Windows Defender. SystemSettingsAdminFlows.exe is a legitimate Windows component used for administrative configuration tasks. However, attackers may abuse it to disable Windows Defender as part of their attack chain, especially in the context of ransomware or other malware campaigns.

title: Windows Defender Disabled Via SystemSettingsAdminFlows.EXE
id: da92713f-ca2d-4fab-8320-098013d3f43a
status: experimental
description: |
    Detects the usage of SystemSettingsAdminFlows.exe to disable Windows Defender.
    SystemSettingsAdminFlows.exe is a legitimate Windows component used for administrative configuration tasks.
    However, attackers may abuse it to disable Windows Defender as part of their attack chain, especially in the context of ransomware or other malware campaigns.
references:
    - https://thedfirreport.com/2026/02/23/apache-activemq-exploit-leads-to-lockbit-ransomware/
    - https://www.huntress.com/blog/lolbin-to-inc-ransomware
tags:
    - attack.defense-impairment
    - attack.t1685
author: Chirag Damani (KPMG India), Swachchhanda Shrawan Poudel (Nextron Systems)
date: 2026-07-01
logsource:
    category: process_creation
    product: windows
detection:
    selection_ssaf_img:
        - Image|endswith: '\SystemSettingsAdminFlows.exe'
        - OriginalFileName: 'SystemSettingsAdminFlows.EXE'
    selection_ssaf_cli:
        CommandLine|contains: 'defender'
    selection_cli_enable_opt:
        CommandLine|contains:
            - 'RTP '
            - 'RealTimeProtection '
            - 'DisableEnhancedNotifications '
    selection_cli_enable_value:
        CommandLine|contains: '1'
    selection_cli_disable_opt:
        CommandLine|contains:
            - 'SubmitSamplesConsent '
            - 'SpyNetReporting '
            - 'DisableCDPUserAuthPolicy '
    selection_cli_disable_value:
        CommandLine|contains: '0'
    # In Enterprise environments, if defender was disabled via GUI, it would be expected to see the following parent-child process relationship:
    # Thus, uncomment the below filter to exclude such cases because of high false positives:
    # filter_main_gui_options:
    #     ParentImage|endswith:
    #         - '\SystemSettings.exe'
    #         - '\Explorer.exe'
    condition: all of selection_ssaf_* and (all of selection_cli_enable_* or all of selection_cli_disable_*)
falsepositives:
    - Legitimate turn off of Windows Defender by the technical users or administrators for troubleshooting or other purposes.
level: high
regression_tests_path: regression_data/rules/windows/process_creation/proc_creation_win_lolbin_systemsettingsadminflows_defender_disable/info.yml

[[ currentRule.title && currentRule.title.length > 60 ? currentRule.title.slice(0, 60) + '…' : currentRule.title ]]

255f013d-ab28-4b66-accc-c32c1509b359

Propose edits, view related rules, and engage with the community through comments.

Executable code, not a declarative rule

This submission is arbitrary [[ currentRule.format ? currentRule.format.toUpperCase() : '' ]] code, not a declarative detection rule — review it as you would any script before running it, and note that it cannot be safely aggregated or auto-executed alongside YARA/Sigma/Suricata/CRS rules.

Rejected pattern present

[[ reason ]]

What does this mean?

Format & documentation suggestions

Not a security issue — this rule is valid and was accepted as-is. These are optional fields/conventions its own format recommends, mainly affecting its quality score and how well it documents itself for other reviewers.

[[ reason ]]

What do these messages mean?

[[ currentRule.title && currentRule.title.length > 60 ? currentRule.title.slice(0, 60) + '…' : currentRule.title ]]

[[ currentRule.title ]]

Community Discussion