- Home
- Techniques
- Enterprise
- Create or Modify System Process
Create or Modify System Process
Sub-techniques (4)
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. [1] On macOS, launchd processes known as Launch Daemon and Launch Agent are run to finish system initialization and load user specific parameters.[2]
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. [3].
Mitigations
| Mitigation | Description |
|---|---|
| Audit |
Use auditing tools capable of detecting privilege and service abuse opportunities on systems within an enterprise and correct them. |
| Limit Software Installation |
Restrict software installation to trusted repositories only and be cautious of orphaned software packages. |
| 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. |
| 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. |
Detection
Monitor for changes to system processes that do not correlate with known software, patch cycles, etc., including by comparing results against a trusted system baseline. New, benign system processes may be created during installation of new software. Data and events should not be viewed in isolation, but as part of a chain of behavior that could lead to other activities, such as network connections made for Command and Control, learning details about the environment through Discovery, and Lateral Movement.
Command-line invocation of tools capable of modifying services may be unusual, depending on how systems are typically used in a particular environment. Look for abnormal process call trees from known services and for execution of other commands that could relate to Discovery or other adversary techniques.
Monitor for changes to files associated with system-level processes.