CyberStack

MITRE ATT&CK / Techniques / T1543

Create or Modify System Process

ID
T1543
Tactics
TA0003 Persistence, TA0004 Privilege Escalation
Platforms
Containers, Linux, macOS, Windows
Data sources
Service Creation, Process Creation, Windows Registry Key Modification, File Modification, Command Execution, Container Creation
Source
attack.mitre.org
MITRE last modified
12 Sep 2026

Adversaries may create or modify system-level processes to repeatedly execute malicious payloads as part of persistence. When operating systems boot up, they can start processes that perform background system functions. On Windows and Linux, these system processes are referred to as services.[3] On macOS, launchd processes known as Launch Daemon and Launch Agent are run to finish system initialization and load user specific parameters.[4]

Adversaries may install new services, daemons, or agents that can be configured to execute at startup or a repeatable interval in order to establish persistence. Similarly, adversaries may modify existing services, daemons, or agents to achieve the same effect.

Services, daemons, or agents may be created with administrator privileges but executed under root/SYSTEM privileges. Adversaries may leverage this functionality to create or modify system processes in order to escalate privileges.[5]

Sub-techniques (5)

Detection

Mitigations (9)

M1018 User Account Management

Limit privileges of user accounts and groups so that only authorized administrators can interact with system-level process changes and service configurations.

M1022 Restrict File and Directory Permissions

Restrict read/write access to system-level process files to only select privileged users who have a legitimate need to manage system services.

M1026 Privileged Account Management

Manage the creation, modification, use, and permissions associated to privileged accounts, including SYSTEM and root.

M1028 Operating System Configuration

Ensure that Driver Signature Enforcement is enabled to restrict unsigned drivers from being installed.

M1033 Limit Software Installation

Restrict software installation to trusted repositories only and be cautious of orphaned software packages.

M1040 Behavior Prevention on Endpoint

On Windows 10, enable Attack Surface Reduction (ASR) rules to prevent an application from writing a signed vulnerable driver to the system.[1] On Windows 10 and 11, enable Microsoft Vulnerable Driver Blocklist to assist in hardening against third party-developed drivers.[2]

M1045 Code Signing

Enforce registration and execution of only legitimately signed service drivers where possible.

M1047 Audit

Use auditing tools capable of detecting privilege and service abuse opportunities on systems within an enterprise and correct them.

M1054 Software Configuration

Where possible, consider enforcing the use of container services in rootless mode to limit the possibility of privilege escalation or malicious effects on the host running the container.

Software (9)

References

  1. Malicious Driver Reporting Center
  2. Microsoft driver block rules
  3. TechNet Services
  4. AppleDocs Launch Agent Daemons
  5. OSX Malware Detection