Adversaries may gain access to and use third-party software suites installed within an enterprise network, such as administration, monitoring, and deployment systems, to move laterally through the network. Third-party applications and software deployment systems may be in use in the network environment for administration purposes (e.g., SCCM, HBSS, Altiris, etc.).
Access to a third-party network-wide or enterprise-wide software system may enable an adversary to have remote code execution on all systems that are connected to such a system. The access may be used to laterally move to other systems, gather information, or cause a specific effect, such as wiping the hard drives on all endpoints.
The permissions required for this action vary by system configuration; local credentials may be sufficient with direct access to the third-party system, or specific domain credentials may be required. However, the system may require an administrative account to log in or to perform it's intended purpose.
APT32 compromised McAfee ePO to move laterally by distributing malware as a software deployment task.
During C0018, the threat actors used PDQ Deploy to move AvosLocker and tools across the network.
Sandworm Team has used the commercially available tool RemoteExec for agentless remote code execution.
Silence has used RAdmin, a remote software tool used to remotely control workstations and ATMs.
Threat Group-1314 actors used a victim's endpoint management platform, Altiris, for lateral movement.
It is believed that a patch management system for an anti-virus product commonly installed among targeted companies was used to distribute the Wiper malware.
|M1015||Active Directory Configuration||
Ensure proper system and access isolation for critical network systems through use of group policy.
Ensure proper system and access isolation for critical network systems through use of multi-factor authentication.
Ensure proper system isolation for critical network systems through use of firewalls.
Verify that account credentials that may be used to access deployment systems are unique and not used throughout the enterprise network.
|M1026||Privileged Account Management||
Grant access to application deployment systems only to a limited number of authorized administrators.
|M1029||Remote Data Storage||
If the application deployment system can be configured to deploy only signed binaries, then ensure that the trusted signing certificates are not co-located with the application deployment system and are instead located on a system that cannot be accessed remotely or to which remote access is tightly controlled.
Patch deployment systems regularly to prevent potential remote access through Exploitation for Privilege Escalation.
|M1018||User Account Management||
Ensure that any accounts used by third-party providers to access these systems are traceable to the third-party and are not used throughout the network or used by other third-party providers in the same environment. Ensure there are regular reviews of accounts provisioned to these systems to verify continued business need, and ensure there is governance to trace de-provisioning of access that is no longer required. Ensure proper system and access isolation for critical network systems through use of account privilege separation.
Have a strict approval policy for use of deployment systems.
|ID||Data Source||Data Component||Detects|
|DS0015||Application Log||Application Log Content||
Often these third-party applications will have logs of their own that can be collected and correlated with other data from the environment. Ensure that third-party application logs are on-boarded to the enterprise logging system and the logs are regularly reviewed. Audit software deployment logs and look for suspicious or unauthorized activity. A system not typically used to push software to clients that suddenly is used for such a task outside of a known admin function may be suspicious. Monitor account login activity on these applications to detect suspicious/abnormal usage.Perform application deployment at regular times so that irregular deployment activity stands out.
Monitor for newly executed processes that does not correlate to known good software. Analyze the process execution trees, historical activities from the third-party application (such as what types of files are usually pushed), and the resulting activities or events from the file/binary/script pushed to systems.