Standard attack pattern
Draft
CAPEC-524: Rogue Integration Procedures
An attacker alters or establishes rogue processes in an integration facility in order to insert maliciously altered components into the system. The attacker would then supply the malicious components. This would allow for malicious disruption or additional compromise when the system is deployed.
Last updated
High
Typical severity
Per MITRE
Low
Likelihood of attack
Per MITRE
0
Related weaknesses
CWEs this targets
Standard
Abstraction
MITRE classification
Overview
CAPEC-524 (Rogue Integration Procedures) is a standard-level attack pattern catalogued by MITRE in the Common Attack Pattern Enumeration and Classification (CAPEC). It describes a recurring method attackers use to exploit software weaknesses.
What the attacker needs
Prerequisites
- Physical access to an integration facility that prepares the system before it is deployed at the victim location.
Skills required
- High skill: Advanced knowledge of the design of the system.
- High skill: Hardware creation and manufacture of replacement components.
How to mitigate it
Defenses that reduce the risk of CAPEC-524.
- 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.
- Maintain strong physical system access controls and monitor networks and physical facilities for insider threats.