This detection focuses on identifying the filesystem-level arrival of these tools, specifically monitoring for executables, installers, and scripts identified via a managed lookup table of known remote access utilities. Because these tools are often utilized by legitimate administrators, the detection requires careful tuning via exception lists to avoid noise. The presence of these files is a high-fidelity indicator that requires immediate investigation to determine if the deployment was authorized by internal IT or performed by an unauthorized third party.

Attack Chain

1. Initial access is gained through phishing, exploitation of a public-facing application, or compromised credentials.
2. The attacker performs initial reconnaissance to identify system architecture and installed security software.
3. The attacker downloads or drops the remote access utility installer (e.g., .exe, .msi, or .pkg) to a temporary directory.
4. The installer is executed to register the remote access service, creating persistent registry keys or startup entries.
5. The remote access agent initiates an outbound connection to the vendor's command-and-control infrastructure.
6. The attacker uses the persistent remote access session to conduct lateral movement and harvest credentials.
7. Final objectives, such as data exfiltration or ransomware deployment, are executed via the established remote session.

Impact

Successful deployment of unauthorized remote access software grants an attacker persistent, interactive control over the affected system. This facilitates long-term presence, bypass of network segmentation, and the ability to exfiltrate sensitive data or deploy further payloads, often resulting in widespread environment compromise and significant operational disruption.

Recommendation

1. Deploy file-creation monitoring (Sysmon Event ID 11 or equivalent EDR telemetry) focusing on paths associated with user-writeable directories.
2. Maintain a centralized, organizational list of authorized remote access utilities to act as an allowlist against the remote_access_software lookup.
3. Audit the current remote_access_software_usage_exceptions list to ensure all legitimate administrative tools are properly excluded.
4. Use the provided Splunk analytic to monitor for unauthorized arrivals of new binaries from the identified remote utility categories.