Code Signing

Enforce binary and application integrity with digital signature verification to prevent untrusted code from executing.

ID: M1045
Version: 1.1
Created: 11 June 2019
Last Modified: 20 May 2020

Techniques Addressed by Mitigation

Domain ID Name Use
Enterprise T1059 Command and Scripting Interpreter

Where possible, only permit execution of signed scripts.

.001 PowerShell

Set PowerShell execution policy to execute only signed scripts.

.002 AppleScript

Require that all AppleScript be signed by a trusted developer ID before being executed - this will prevent random AppleScript code from executing.[3] This subjects AppleScript code to the same scrutiny as other .app files passing through Gatekeeper.

Enterprise T1554 Compromise Client Software Binary

Ensure all application component binaries are signed by the correct application developers.

Enterprise T1546 .006 Event Triggered Execution: LC_LOAD_DYLIB Addition

Enforce that all binaries be signed by the correct Apple Developer IDs.

.013 Event Triggered Execution: PowerShell Profile

Enforce execution of only signed PowerShell scripts. Sign profiles to avoid them from being modified.

Enterprise T1525 Implant Container Image

Several cloud service providers support content trust models that require container images be signed by trusted sources.[1][2]

Enterprise T1036 Masquerading

Require signed binaries.

.001 Invalid Code Signature

Require signed binaries.

.005 Match Legitimate Name or Location

Require signed binaries.

Enterprise T1505 Server Software Component

Ensure all application component binaries are signed by the correct application developers.

.002 Transport Agent

Ensure all application component binaries are signed by the correct application developers.

.001 SQL Stored Procedures

Ensure all application component binaries are signed by the correct application developers.

References