Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →cyberstrikeus/T1553.006_code-signing-policy-modification
Adversaries may modify code signing policies to enable execution of unsigned or self-signed code.
Passed 20 of 21 test cases with the skill, and 17 of 21 without it.
and 6 more in the full report
4 fixed17 passed either way0 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 3 test cases the skill fixed. Same model, same prompt, with and without the skill.
Can you list all 3 official MITRE ATT&CK mitigation IDs and titles for preventing or restricting Code Signing Policy Modification (T1553.006)?
| Checked | Without skill | With skill |
|---|---|---|
| Lists M1026 Privileged Account Management. | Passed | Passed |
| Lists M1046 Boot Integrity. | Missed | Passed |
| Lists M1024 Restrict Registry Permissions. | Missed | Passed |
The instructions your model reads when the skill loads.
Sub-technique of: T1553
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.
Platforms: Windows, macOS
The following tests are from Atomic Red Team and provide actionable ways to test this technique:
Allows adversaries to subvert trust controls by modifying the code signing policy, enabling the execution of unsigned drivers.
Supported Platforms: windows Elevation Required: Yes
test cases passed, vs 17 / 21 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.