This site has been deprecated in favor of https://attack.mitre.org and will remain in place until 11/1/22.
Execution through API
|Execution through API|
|Data Sources||Module: Module Load, Network Traffic: Network Traffic Content|
Adversaries may attempt to leverage Application Program Interfaces (APIs) used for communication between control software and the hardware. Specific functionality is often coded into APIs which can be called by software to engage specific functions on a device or other software.
- Stuxnet utilizes the PLC communication and management API to Modify Controller Tasking and Modify Program.1
- Triton leverages a reconstructed TriStation protocol within its framework to trigger APIs related to program download, program allocation, and program changes.2
- Authorization Enforcement - All APIs used to perform execution, especially those hosted on embedded controllers (e.g., PLCs), should provide adequate authorization enforcement of user access. Minimize user's access to only required API calls.3
- Human User Authentication - All APIs on remote systems or local processes should require the authentication of users before executing any code or system changes.
- Access Management - Access Management technologies can be used to enforce authorization policies and decisions, especially when existing field devices do not provide capabilities to support user identification and authentication.4 These technologies typically utilize an in-line network device or gateway system to prevent access to unauthenticated users, while also integrating with an authentication service to first verify user credentials.
- Execution Prevention - Minimize the exposure of API calls that allow the execution of code.