Attack Ent T1543 002 Systemd Service

MITRE ATT&CK T1543.002: Systemd Service

When to use this skill

Use this skill when the task involves T1543.002, Systemd Service, enterprise ATT&CK, TTP mapping, detection engineering, hunting, incident-response enrichment, control validation, or authorized adversary-emulation planning. Treat it as a defensive analysis aid: keep outputs focused on understanding, detecting, mitigating, and safely validating this ATT&CK sub-technique.

Technique context

• ATT&CK domain: enterprise
• ATT&CK ID: T1543.002
• Technique name: Systemd Service
• Type: sub-technique
• ATT&CK URL: https://attack.mitre.org/techniques/T1543/002
• Tactics: persistence, privilege-escalation
• Platforms: Linux
• Required permissions: Not specified
• Effective permissions: Not specified
• Defenses bypassed: Not specified

ATT&CK description

Adversaries may create or modify systemd services to repeatedly execute malicious payloads as part of persistence. Systemd is a system and service manager commonly used for managing background daemon processes (also known as services) and other system resources.(Citation: Linux man-pages: systemd January 2014) Systemd is the default initialization (init) system on many Linux distributions replacing legacy init systems, including SysVinit and Upstart, while remaining backwards compatible.

Systemd utilizes unit configuration files with the .service file extension to encode information about a service's process. By default, system level unit files are stored in the /systemd/system directory of the root owned directories (/). User level unit files are stored in the /systemd/user directories of the user owned directories ($HOME).(Citation: lambert systemd 2022)

Inside the .service unit files, the following directives are used to execute commands:(Citation: freedesktop systemd.service)

• ExecStart, ExecStartPre, and ExecStartPost directives execute when a service is started manually by systemctl or on system start if the service is set to automatically start.
• ExecReload directive executes when a service restarts.
• ExecStop, ExecStopPre, and ExecStopPost directives execute when a service is stopped.

Adversaries have created new service files, altered the commands a .service file’s directive executes, and modified the user directive a .service file executes as, which could result in privilege escalation. Adversaries may also place symbolic links in these directories, enabling systemd to find these payloads regardless of where they reside on the filesystem.(Citation: Anomali Rocke March 2019)(Citation: airwalk backdoor unix systems)(Citation: Rapid7 Service Persistence 22JUNE2016)

The .service file’s User directive can be used to run service as a specific user, which could result in privilege escalation based on specific user/group permissions.

Systemd services can be created via systemd generators, which support the dynamic generation of unit files. Systemd generators are small executables that run during boot or configuration reloads to dynamically create or modify systemd unit files by converting non-native configurations into services, symlinks, or drop-ins (i.e., Boot or Logon Initialization Scripts).(Citation: Elastic Security Labs Linux Persistence 2024)(Citation: Pepe Berba Systemd 2022)

Agent workflow

1. Clarify scope: identify the system, asset class, log sources, cloud or endpoint platform, and whether the user wants triage, detection, coverage assessment, or safe emulation planning.
2. Load bundled resources as needed: use references/technique-profile.json for structured metadata, references/detection-and-mitigation.md for triage and telemetry guidance, references/known-threat-context.md for ATT&CK relationship context, and templates/ for repeatable outputs.
3. Map observations to ATT&CK: compare the user's evidence to the ATT&CK description, tactics, platforms, and known procedure patterns before asserting a match.
4. Produce defensive outputs: prioritize hypotheses, telemetry requirements, detection logic ideas, validation steps, containment guidance, and mitigations.
5. Preserve uncertainty: distinguish confirmed evidence, plausible indicators, assumptions, and gaps. Recommend what to collect next.
6. Stay safe: do not provide malware, credential theft, persistence, evasion, destructive automation, or unauthorized exploitation instructions. For adversary emulation, keep steps bounded to approved lab or control-validation contexts and omit operational abuse details.

Bundled resources

• references/technique-profile.json: machine-readable ATT&CK metadata for this technique.
• references/detection-and-mitigation.md: detection notes, telemetry checklist, triage questions, mitigation candidates, and false-positive considerations.
• references/known-threat-context.md: ATT&CK relationship context with attribution cautions.
• templates/detection-brief.md: detection engineering brief template.
• templates/hunt-plan.md: threat hunt plan template.
• templates/incident-response-note.md: incident response note template.
• templates/coverage-assessment.md: ATT&CK coverage assessment template.
• scripts/render_brief.py: local helper that renders a Markdown defensive brief from technique-profile.json.
• assets/output-schema.json: JSON schema for structured technique analysis outputs.

To generate a quick brief, run python scripts/render_brief.py --output brief.md from inside this skill directory, or adapt the templates directly.

Detection guidance

No ATT&CK detection guidance was present in the source STIX object.

Useful telemetry and data sources

• Not specified in the STIX object.

Mitigations to consider

• Limit Software Installation
• Privileged Account Management
• Restrict File and Directory Permissions
• User Account Management

Known threat context

Use these examples only as contextual leads, not as proof that an observed event is this technique:

• 2022 Ukraine Electric Power Attack (campaign)
• Exaramel for Linux (malware)
• Fysbis (malware)
• Gomir (malware)
• Hildegard (malware)
• Pupy (tool)
• RIFLESPINE (malware)
• Rocke (intrusion-set)
• RotaJakiro (malware)
• Scattered Spider (intrusion-set)
• Shai-Hulud (malware)
• SysUpdate (malware)
• TeamTNT (intrusion-set)

Recommended output pattern

When responding with this skill, structure the answer as:

• Assessment: whether the evidence supports this ATT&CK mapping and why.
• Evidence: specific indicators, logs, behaviors, and assumptions.
• Detection: telemetry sources, analytic logic, and tuning considerations.
• Response: containment, eradication, recovery, and validation actions.
• Coverage gaps: missing logs, sensors, controls, or environmental details.
• References: include the ATT&CK URL and any user-provided evidence references.

ATT&CK contributors

• Tony Lambert, Red Canary
• Emad Al-Mousa, Saudi Aramco
• Tim (Wadhwa-)Brown
• Ruben Groenewoud (@RFGroenewoud)