This site is the archived OWASP Foundation Wiki and is no longer accepting Account Requests.
To view the new OWASP Foundation website, please visit https://owasp.org
Difference between revisions of "OWASP Embedded Application Security"
Aaron.guzman (talk | contribs) |
(→Project Leaders) |
||
| Line 17: | Line 17: | ||
== Project Leaders == | == Project Leaders == | ||
| − | Aaron Guzman | + | |
| + | [https://owasp.org/index.php/User:Aaron.guzman Aaron Guzman] [mailto:[email protected] @] | ||
== Related Projects == | == Related Projects == | ||
Revision as of 22:43, 18 July 2016
OWASP Embedded Application Security ProjectEach year, the number of enterprise and consumer devices with embedded software are on the rise. Given the publicity with IoT and more devices becoming network connected, it is essential to create secure coding guidelines for embedded software. Embedded Application Security is not often a high priority for embedded devices such as Routers, Managed Switches, IoT devices, and even ATM Kiosks. There are many challenges in the embedded field including ODM supply chain, limited memory, a small stack, and the challenge of pushing firmware updates securely to an endpoint. The goal of this project is to identify the risks in embedded applications on a generalized list of devices, create a list of best practices, draw on the resources that OWASP already has, and bring OWASP expertise to the embedded world.
|
Mailing ListProject LeadersRelated Projects |
News and Events
In PrintWe will be releasing a user guide soon! Classifications
| |||||||
- Prevent the use of dangerous functions and APIs in efforts to protect against memory-corruption vulnerabilities inside firmware functions.
- Ensure secure compiler flags or switches are utilized upon each firmware build. (i.e For GCC -fPIE, -fstack-protector-all, -Wl,-z,noexecstack, -Wl,-z,noexecheap etc..)
- Ensure robust update mechanisms utilize cryptographically signed firmware images for updating functions.
- Do not hard code secrets such as passwords, usernames, tokens or similar variants into firmware images.
- Dispose and securely wipe sensitive information stored in buffers or temporary files during runtime after they are no longer needed (e.g. Wipe buffers from locations where personal identifiable information is stored before releasing the buffers)
- Modify Busybox and embedded frameworks alike to only libraries and functions that are being used. (e.g. Remove unused languages like perl and services such as Telnet, FTP etc)
- Validate all debugging and pre-production code have been removed prior to firmware deployment.
- Ensure all methods of communication are utilizing industry standard encryption configurations for TLS.
- Limit collection, storage, and sharing of personal identifiable information (PII) to items that are only required for operation.
- Ensure kernel and software packages on embedded images are updated to prevent from known publicly available exploits.
2016-2017 Roadmap
- Curate a list of secure coding embedded best practices
https://github.com/firmadyne/firmadyne
- Angr - [1]
- firmwalker [2]
- Binary Analysis [3]
- IDA Pro (supports ARM / MIPS)
- OpenOCD
- GDB
- binwalk
- firmware-mod-toolkit
- Capstone framework
- UART cables
- JTAG Adapters (JLINK)
- BusPirate
- BusBlaster
- CPLDs (in lieu of FPGAs)
- Oscilloscopes
- Multimeter (Ammeter, Voltmeter, etc)
- Logic Analyzers for SPI [4]
- Shikra
- JTagulator
- Radare2 [5]
