This site has been deprecated in favor of https://attack.mitre.org and will remain in place until 11/1/22.
Project File Infection
To visit this technique’s new page please go to and update your links to https://attack.mitre.org/techniques/T0873
| Project File Infection | |
|---|---|
| Technique | |
| ID | T0873 |
| Tactic | Persistence |
| Data Sources | File: File Modification |
| Asset | Engineering Workstation, Human-Machine Interface |
Description
Adversaries may attempt to infect project files with malicious code. These project files may consist of objects, program organization units, variables such as tags, documentation, and other configurations needed for PLC programs to function.1 Using built in functions of the engineering software, adversaries may be able to download an infected program to a PLC in the operating environment enabling further execution and persistence techniques.2
Adversaries may export their own code into project files with conditions to execute at specific intervals.3 Malicious programs allow adversaries control of all aspects of the process enabled by the PLC. Once the project file is downloaded to a PLC the workstation device may be disconnected with the infected project file still executing.2
Procedure Examples
- Stuxnet copies itself into Step 7 projects in such a way that it automatically executes when the Step 7 project is loaded.3
Mitigations
- Code Signing - Allow for code signing of any project files stored at rest to prevent unauthorized tampering. Ensure the signing keys are not easily accessible on the same system.
- Encrypt Sensitive Information - When at rest, project files should be encrypted to prevent unauthorized changes.4
- Restrict File and Directory Permissions - Ensure permissions restrict project file access to only engineer and technician user groups and accounts.
- Audit - Review the integrity of project files to verify they have not been modified by adversary behavior. Verify a cryptographic hash for the file with a known trusted version, or look for other indicators of modification (e.g., timestamps).
References
- a b Nicolas Falliere, Liam O Murchu, Eric Chien. (2011, February). W32.Stuxnet Dossier (Version 1.4). Retrieved September 22, 2017.
- ^ National Institute of Standards and Technology. (2013, April). Security and Privacy Controls for Federal Information Systems and Organizations. Retrieved September 17, 2020.
| ||||||||||||||||||||||||||||||||
