This site has been deprecated in favor of and will remain in place until 11/1/22.

Supply Chain Compromise

From attackics
Revision as of 11:15, 13 April 2021 by Oalexander (talk | contribs)
Jump to navigation Jump to search

To visit this technique’s new page please go to and update your links to

Supply Chain Compromise
ID T0862
Tactic Initial Access
Data Sources Web proxy, File monitoring, Detonation chamber, Digital signatures
Asset Data Historian, Control Server, Data Historian, Field Controller/RTU/PLC/IED, Human-Machine Interface, Input/Output Server, Safety Instrumented System/Protection Relay


Adversaries may perform supply chain compromise to gain control systems environment access by means of infected products, software, and workflows. Supply chain compromise is the manipulation of products, such as devices or software, or their delivery mechanisms before receipt by the end consumer. Adversary compromise of these products and mechanisms is done for the goal of data or system compromise, once infected products are introduced to the target environment.

Supply chain compromise can occur at all stages of the supply chain, from manipulation of development tools and environments to manipulation of developed products and tools distribution mechanisms. This may involve the compromise and replacement of legitimate software and patches, such as on third party or vendor websites. Targeting of supply chain compromise can be done in attempts to infiltrate the environments of a specific audience. In control systems environments with assets in both the IT and OT networks, it is possible a supply chain compromise affecting the IT environment could enable further access to the OT environment.

Counterfeit devices may be introduced to the global supply chain posing safety and cyber risks to asset owners and operators. These devices may not meet the safety, engineering and manufacturing requirements of regulatory bodies but may feature tagging indicating conformance with industry standards. Due to the lack of adherence to standards and overall lesser quality, the counterfeit products may pose a serious safety and operational risk.1

Yokogawa identified instances in which their customers received counterfeit differential pressure transmitters using the Yokogawa logo. The counterfeit transmitters were nearly indistinguishable with a semblance of functionality and interface that mimics the genuine product.1

F-Secure Labs analyzed the approach the adversary used to compromise victim systems with Havex.2 The adversary planted trojanized software installers available on legitimate ICS/SCADA vendor websites. After being downloaded, this software infected the host computer with a Remote Access Trojan (RAT).

Procedure Examples

  • Dragonfly 2.0 trojanized legitimate software to deliver malware disguised as standard windows applications.3
  • Dragonfly trojanized legitimate ICS equipment providers software packages available for download on their websites.4
  • XENOTIME targeted several ICS vendors and manufacturers.5
  • The Backdoor.Oldrea RAT is distributed through trojanized installers planted on compromised vendor sites.6


  • Code Signing - When available utilize hardware and software root-of-trust to verify the authenticity of a system. This may be achieved through cryptographic means, such as digital signatures or hashes, of critical software and firmware throughout the supply chain.
  • Update Software - A patch management process should be implemented to check unused dependencies, unmaintained and/or previously vulnerable dependencies, unnecessary features, components, files, and documentation.
  • Audit - Perform audits or scans of systems, permissions, insecure software, insecure configurations, etc. to identify potential weaknesses. Perform periodic integrity checks of the device to validate the correctness of the firmware, software, programs, and configurations. Integrity checks, which typically include cryptographic hashes or digital signatures, should be compared to those obtained at known valid states, especially after events like device reboots, program downloads, or program restarts.
  • Vulnerability Scanning - Implement continuous monitoring of vulnerability sources. Also, use automatic and manual code review tools.7
  • Supply Chain Management - A supply chain management program should include methods the assess the trustworthiness and technical maturity of a supplier, along with technical methods (e.g., code-signing, bill of materials) needed to validate the integrity of newly obtained devices and components. Develop procurement language that emphasizes the expectations for suppliers regarding the artifacts, audit records, and technical capabilities needed to validate the integrity of the device’s supply chain.8