実行フロー
1) Explore
[Determine Entry Point] The adversary must first identify a system that they wish to target and search for an entry point they can use to install the malicious software. This could be a system which they have prior knowledge of, giving them insight into the software and environment.
技法
- Use a JTAGulator to identify exposed JTAG and UART interfaces in smaller embedded systems.
- Identify exposed USB connectors that could be used to load software.
2) Explore
[Discover Vulnerability in Supply Chain] The adversary maps out the supply chain for the targeted system. They look for ooportunities to gain physical access to the system after it has left the manufacturer, but before it is deployed to the victim.
技法
- Procure a system and observe the steps it takes in the shipment process.
- Identify possible warehouses that systems are stored after manufacturing.
3) Experiment
[Test Malicious Software] Before performing the attack in the wild, an adversary will test the attack on a system they have procured to ensure that the desired outcome will be achieved.
技法
- Design malicious software that will give an adversary a backdoor into the system once it is deployed to the victim.
- Obtain already designed malicious software that just need to be placed into the system.
4) Exploit
[Implant Software in the Supply Chain] Using the vulnerability in the supply chain of the system discovered in the explore phase, the adversary implants the malicious software into the system. This results in the adversary gaining unintended access to systems once they reach the victim and can lead to a variety of follow up attacks.
前提条件
Physical access to the system after it has left the manufacturer but before it is deployed at the victim location.
必要なスキル
Advanced knowledge of the design of the system and it's operating system components and subcomponents.
Malicious software creation.
緩和策
Deploy strong code integrity policies to allow only authorized apps to run.
Use endpoint detection and response solutions that can automaticalkly detect and remediate suspicious activities.
Maintain a highly secure build and update infrastructure by immediately applying security patches for OS and software, implementing mandatory integrity controls to ensure only trusted tools run, and requiring multi-factor authentication for admins.
Require SSL for update channels and implement certificate transparency based verification.
Sign everything, including configuration files, XML files and packages.
Develop an incident response process, disclose supply chain incidents and notify customers with accurate and timely information.
参考文献
REF-439
Supply Chain Attack Framework and Attack Patterns
John F. Miller.
http://www.mitre.org/sites/default/files/publications/supply-chain-attack-framework-14-0228.pdf REF-716
Supply chain attacks
Daniel Simpson, Dani Halfin, Andrews Mariano Gorzelany, Beth Woodbury.
https://docs.microsoft.com/en-us/windows/security/threat-protection/intelligence/supply-chain-malware
登録情報
| 名前 |
組織 |
日付 |
リリース日 |
| CAPEC Content Team |
The MITRE Corporation |
2014-06-23 +00:00 |
|
変更履歴
| 名前 |
組織 |
日付 |
コメント |
| CAPEC Content Team |
The MITRE Corporation |
2015-11-09 +00:00 |
Updated Typical_Likelihood_of_Exploit |
| CAPEC Content Team |
The MITRE Corporation |
2020-07-30 +00:00 |
Updated Related_Attack_Patterns |
| CAPEC Content Team |
The MITRE Corporation |
2022-02-22 +00:00 |
Updated Execution_Flow, Mitigations, References |
| CAPEC Content Team |
The MITRE Corporation |
2022-09-29 +00:00 |
Updated Taxonomy_Mappings |