t1553-006-code-signing-policy-modification

name	T1553.006_code-signing-policy-modification
description	Adversaries may modify code signing policies to enable execution of unsigned or self-signed code.
category	configuration
version	18.1
author	cyberstrike-official
tags	["mitre-attack","enterprise","t1553.006","defense-evasion","windows","macos","sub-technique"]
technique_id	T1553.006
tactic	defense-evasion
all_tactics	["defense-evasion"]
platforms	["Windows","macOS"]
mitre_url	https://attack.mitre.org/techniques/T1553/006
tech_stack	["windows","macos"]
cwe_ids	["CWE-693"]
chains_with	["T1553","T1553.001","T1553.002","T1553.003","T1553.004","T1553.005"]
prerequisites	["T1553"]
severity_boost	{"T1553":"Chain with T1553 for deeper attack path","T1553.001":"Chain with T1553.001 for deeper attack path","T1553.002":"Chain with T1553.002 for deeper attack path"}

T1553.006 Code Signing Policy Modification

Sub-technique of: T1553

High-Level Description

Adversaries may modify code signing policies to enable execution of unsigned or self-signed code. Code signing provides a level of authenticity on a program from a developer and a guarantee that the program has not been tampered with. Security controls can include enforcement mechanisms to ensure that only valid, signed code can be run on an operating system.

Some of these security controls may be enabled by default, such as Driver Signature Enforcement (DSE) on Windows or System Integrity Protection (SIP) on macOS. Other such controls may be disabled by default but are configurable through application controls, such as only allowing signed Dynamic-Link Libraries (DLLs) to execute on a system. Since it can be useful for developers to modify default signature enforcement policies during the development and testing of applications, disabling of these features may be possible with elevated permissions.

Adversaries may modify code signing policies in a number of ways, including through use of command-line or GUI utilities, Modify Registry, rebooting the computer in a debug/recovery mode, or by altering the value of variables in kernel memory. Examples of commands that can modify the code signing policy of a system include bcdedit.exe -set TESTSIGNING ON on Windows and csrutil disable on macOS. Depending on the implementation, successful modification of a signing policy may require reboot of the compromised system. Additionally, some implementations can introduce visible artifacts for the user (ex: a watermark in the corner of the screen stating the system is in Test Mode). Adversaries may attempt to remove such artifacts.

To gain access to kernel memory to modify variables related to signature checks, such as modifying g_CiOptions to disable Driver Signature Enforcement, adversaries may conduct Exploitation for Privilege Escalation using a signed, but vulnerable driver.

Kill Chain Phase

• Defense Evasion (TA0005)

Platforms: Windows, macOS

What to Check

• Identify if Code Signing Policy Modification technique is applicable to target environment
• Check Windows systems for indicators of Code Signing Policy Modification
• Check macOS systems for indicators of Code Signing Policy Modification
• Verify mitigations are bypassed or absent (3 known mitigations)
• Assess detection coverage (1 detection strategies)