Executive Summary
Server Software Component (T1505) is a MITRE ATT&CK technique associated with Persistence. Adversaries may abuse legitimate extensible development features of servers to establish persistent access to systems.
Why Attackers Use It
Attackers use Server Software Component because it provides a reliable way to advance their objective within the Persistence tactic, often with a favorable balance of impact versus detectability on Windows, Linux, macOS, Network Devices, ESXi environments. Defenders should assess this behavior in the context of the affected platform and adjacent activity rather than treating it as a standalone indicator.
MITRE Description
Adversaries may abuse legitimate extensible development features of servers to establish persistent access to systems. Enterprise server applications may include features that allow developers to write and install software or scripts to extend the functionality of the main application. Adversaries may install malicious components to extend and abuse server applications.(Citation: volexity_0day_sophos_FW)
Attack Flow
- Attacker gains the prerequisite access or context described below.
- Attacker executes Server Software Component to achieve its tactical objective (Persistence).
- Resulting access/data/effect is leveraged to advance the broader attack chain (see Related Techniques).
Prerequisites
- Platform(s): Windows, Linux, macOS, Network Devices, ESXi
- ATT&CK does not define one universal permission requirement for this technique. Establish the required access from the observed implementation and affected platform.
Common Tools
- Tool attribution is implementation-specific. Use ATT&CK procedure examples and local telemetry to identify the binaries, services, scripts, accounts, or cloud resources involved.
Commands
No universal command represents Server Software Component. Capture the exact command line, arguments, parent process, account, host, and execution time from the investigated environment; do not operationalize unverified examples.
Network Traffic
- Network observability is implementation-dependent. Review DNS, proxy, firewall, flow, authentication, and packet telemetry around the activity window, then correlate remote endpoints and protocol behavior with host evidence.
Windows Events
| Event ID | Log Channel | What It Indicates |
|---|
| Environment-specific | Relevant Windows channel(s) | Correlate authentication, process, object-access, and configuration events with the observed execution context. |
Sysmon Events
| Sysmon Event ID | Name | Why It's Relevant Here |
|---|
| Environment-specific | Validate configured telemetry | Use process, network, file, registry, DNS, or image-load telemetry only when relevant and enabled. |
Detection Opportunities
No MITRE detection guidance published for this technique.
Relevant ATT&CK Data Sources: N/A
Sigma Rules
A universal Sigma rule would create unreliable results because this technique has no single guaranteed observable. Build detection logic from a documented behavior and supported data source, scope it to the affected platform, and validate it against benign administrative activity before deployment.
Splunk Queries
Start with the data sources named in the detection section. Scope searches by asset, identity, and time window; correlate the primary behavior with preceding access and subsequent actions. A portable query is intentionally not provided where the technique lacks a universal schema or observable.
Investigation Workflow
- Confirm that the observed behavior is consistent with Server Software Component and rule out expected administrative or application activity.
- Establish the first-seen time, initiating identity, source system, target system, and affected resources.
- Collect relevant host, identity, network, cloud, and application telemetry for the surrounding time window.
- Correlate parent and child activity, remote connections, file or configuration changes, and related ATT&CK techniques.
- Determine scope by searching for the same observable across peer assets and identities.
- Preserve volatile evidence and record confidence, assumptions, and telemetry gaps before containment.
Containment
- Isolate affected host(s)/account(s) identified during investigation.
- Revoke or rotate any credentials/tokens potentially exposed.
- Apply the mitigations listed below where not already enforced.
- Validate no related techniques (see Related Techniques) were chained against the same asset.
Mitigation
- M1045 -- Code Signing: Code Signing is a security process that ensures the authenticity and integrity of software by digitally signing executables, scripts, and other code artifacts.
- M1047 -- Audit: Auditing is the process of recording activity and systematically reviewing and analyzing the activity and system configurations.
- M1024 -- Restrict Registry Permissions: Restricting registry permissions involves configuring access control settings for sensitive registry keys and hives to ensure that only authorized users or processes can make modifications.
- M1042 -- Disable or Remove Feature or Program: Disable or remove unnecessary and potentially vulnerable software, features, or services to reduce the attack surface and prevent abuse by adversaries.
- M1046 -- Boot Integrity: Boot Integrity ensures that a system starts securely by verifying the integrity of its boot process, operating system, and associated components.
- M1018 -- User Account Management: User Account Management involves implementing and enforcing policies for the lifecycle of user accounts, including creation, modification, and deactivation.
- M1026 -- Privileged Account Management: Privileged Account Management focuses on implementing policies, controls, and tools to securely manage privileged accounts (e.g., SYSTEM, root, or administrative accounts).
Related Techniques
- T1505.001
- T1505.002
- T1505.003
- T1505.004
- T1505.005
- T1505.006