Summary

Developers should implement and enable trusted execution if it is available on the device's System-on-Chip (SoC) or CPU.

Description

Enabling and implementing trusted execution, especially when available on the device's System-on-Chip (SoC) or CPU, is important for several security reasons. Trusted execution environments provide a secure and isolated space within a device's hardware to run sensitive operations, protecting them from potential threats including malware, rootkits, and privilege escalation attempts.

References

• CWE-693. Protection mechanism failure
• CWE-1192. System-on-Chip (SoC) using components without unique identifiers
• CWE-1233. Improper hardware lock protection for security sensitive controls
• OWASP10-A5. Security misconfiguration
• AGILE-3. Deliver working software frequently
• MITRE-M1038. Execution prevention
• PDPO-9A_66G. Powers exercisable in relation to premises and electronic devices
• CMMC-CM_L2-3_4_9. User-installed software
• CMMC-SI_L1-3_14_5. System & file scanning
• FEDRAMP-AC-6_8. Least privilege - Privilege levels for code execution
• FEDRAMP-CM-7_5. Least functionality - Authorized software, whitelisting
• ISO27002-8_19. Installation of software on operational systems
• IEC62443-UC-2_4. Mobile code
• NISTSSDF-PW_6_1. Configure the compilation, interpreter, and build processes to improve executable security
• CAPEC-681. Exploitation of Improperly Controlled Hardware Security Identifiers
• ISO27001-8_19. Installation of software on operational systems