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 Internet of Things Project"
Aaron.guzman (talk | contribs) (Tag: Visual edit) |
Aaron.guzman (talk | contribs) |
||
| (5 intermediate revisions by the same user not shown) | |||
| Line 10: | Line 10: | ||
''The OWASP Internet of Things Project is designed to help manufacturers, developers, and consumers better understand the security issues associated with the Internet of Things, and to enable users in any context to make better security decisions when building, deploying, or assessing IoT technologies''. | ''The OWASP Internet of Things Project is designed to help manufacturers, developers, and consumers better understand the security issues associated with the Internet of Things, and to enable users in any context to make better security decisions when building, deploying, or assessing IoT technologies''. | ||
| − | The project looks to define a structure for various IoT sub-projects | + | The project looks to define a structure for various IoT sub-projects separated into the following categories - Seek & Understand, Validate & Test, and Governance. |
==Updated!== | ==Updated!== | ||
| Line 311: | Line 311: | ||
== Quick Download == | == Quick Download == | ||
* https://gitlab.com/bytesweep/bytesweep/blob/master/INSTALL.md | * https://gitlab.com/bytesweep/bytesweep/blob/master/INSTALL.md | ||
| + | |||
| + | |} | ||
| + | |||
| + | = Firmware Security Testing Methodology = | ||
| + | [[File:OWASP_Project_Header.jpg|link=]] | ||
| + | |||
| + | {| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |- | ||
| + | | style="border-right: 1px dotted gray;padding-right:25px;" valign="top" | | ||
| + | |||
| + | == Firmware Security Testing Methodology == | ||
| + | |||
| + | The Firmware Security Testing Methodology (FSTM) is composed of nine stages tailored to enable security researchers, software developers, consultants, hobbyists, and Information Security professionals with conducting firmware security assessments. | ||
| + | |||
| + | {| class="wikitable" | ||
| + | |'''Stage''' | ||
| + | |'''Description''' | ||
| + | |- | ||
| + | |1. Information gathering and reconnaissance | ||
| + | |Acquire all relative technical and documentation details pertaining to the target device’s firmware | ||
| + | |- | ||
| + | |2. Obtaining firmware | ||
| + | |Attain firmware using one or more of the proposed methods listed | ||
| + | |- | ||
| + | |3. Analyzing firmware | ||
| + | |Examine the target firmware’s characteristics | ||
| + | |- | ||
| + | |4. Extracting the filesystem | ||
| + | |Carve filesystem contents from the target firmware | ||
| + | |- | ||
| + | |5. Analyzing filesystem contents | ||
| + | |Statically analyze extracted filesystem configuration files and binaries for vulnerabilities | ||
| + | |- | ||
| + | |6. Emulating firmware | ||
| + | |Emulate firmware files and components | ||
| + | |- | ||
| + | |7. Dynamic analysis | ||
| + | |Perform dynamic security testing against firmware and application interfaces | ||
| + | |- | ||
| + | |8. Runtime analysis | ||
| + | |Analyze compiled binaries during device runtime | ||
| + | |- | ||
| + | |9. Binary Exploitation | ||
| + | |Exploit identified vulnerabilities discovered in previous stages to attain root and/or code execution | ||
| + | |}The full methodology release can be downloaded via the following https://github.com/scriptingxss/owasp-fstm/releases/download/v1.0/Firmware_Security_Testing_Methodology_Version1.pdf. | ||
| + | |||
| + | {{Social Media Links}} | ||
| + | |||
| + | | style="padding-left:25px;width:300px;border-right: 1px dotted gray;padding-right:25px;" valign="top" | | ||
| + | |||
| + | == What is the Firmware Security Testing Methodology == | ||
| + | |||
| + | The Firmware Security Testing Methodology Project provides: | ||
| + | |||
| + | *Attack walkthroughs | ||
| + | *Tool usage examples | ||
| + | *Screenshots | ||
| + | *Companion virtual machine preloaded with tools (EmbedOS) - <nowiki>https://github.com/scriptingxss/EmbedOS</nowiki> | ||
| + | |||
| + | == Project Leaders == | ||
| + | |||
| + | * Aaron Guzman | ||
| + | |||
| + | == Quick Download == | ||
| + | * https://github.com/scriptingxss/owasp-fstm/releases | ||
|} | |} | ||
| Line 1,079: | Line 1,143: | ||
* [https://github.com/scriptingxss/IoTGoat OWASP IoTGoat] | * [https://github.com/scriptingxss/IoTGoat OWASP IoTGoat] | ||
|- | |- | ||
| − | |} | + | | |
| − | + | |}{{Social Media Links}} | |
| − | |||
| − | {{Social Media Links}} | ||
| style="padding-left:25px;width:300px;border-right: 1px dotted gray;padding-right:25px;" valign="top" | | | style="padding-left:25px;width:300px;border-right: 1px dotted gray;padding-right:25px;" valign="top" | | ||
| Line 1,230: | Line 1,292: | ||
|} | |} | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
=Project About= | =Project About= | ||
Latest revision as of 07:02, 1 November 2019
OWASP Internet of Things (IoT) ProjectOxford defines the Internet of Things as: “A proposed development of the Internet in which everyday objects have network connectivity, allowing them to send and receive data.” The OWASP Internet of Things Project is designed to help manufacturers, developers, and consumers better understand the security issues associated with the Internet of Things, and to enable users in any context to make better security decisions when building, deploying, or assessing IoT technologies. The project looks to define a structure for various IoT sub-projects separated into the following categories - Seek & Understand, Validate & Test, and Governance. Updated!The OWASP IoT Project for 2018 has been released!PhilosophyThe OWASP Internet of Things Project was started in 2014 as a way help Developers, Manufacturers, Enterprises, and Consumers to make better decisions regarding the creation and use of IoT systems. This continues today with the 2018 release of the OWASP IoT Top 10, which represents the top ten things to avoid when building, deploying, or managing IoT systems. The primary theme for the 2018 OWASP Internet of Things Top 10 is simplicity. Rather than having separate lists for risks vs. threats vs. vulnerabilities—or for developers vs. enterprises vs. consumers—the project team elected to have a single, unified list that captures the top things to avoid when dealing with IoT Security. The team recognized that there are now dozens of organizations releasing elaborate guidance on IoT Security—all of which are designed for slightly different audiences and industry verticals. We thought the most useful resource we could create is a single list that addresses the highest priority issues for manufacturers, enterprises, and consumers at the same time. The result is the 2018 OWASP IoT Top 10. MethodologyThe project team is a collection of volunteer professionals from within the security industry, with experience spanning multiple areas of expertise, including: manufacturers, consulting, security testers, developers, and many more. The project was conducted in the following phases:
The Future of the OWASP IoT Top 10The team has a number of activities planned to continue improving on the project going forward. Some of the items being discussed include:
Participation in the OWASP IoT Project is open to the community. We take input from all participants — whether you’re a developer, a manufacturer, a penetration tester, or someone just trying to implement IoT securely. You can find the team meeting every other Friday in the the #iot-security room of the OWASP Slack Channel. The OWASP IoT Security Team, 2018 LicensingThe OWASP Internet of Things Project is free to use. It is licensed under the http://creativecommons.org/licenses/by-sa/3.0/ Creative Commons Attribution-ShareAlike 3.0 license], so you can copy, distribute and transmit the work, and you can adapt it, and use it commercially, but all provided that you attribute the work and if you alter, transform, or build upon this work, you may distribute the resulting work only under the same or similar license to this one.
|
What is the OWASP Internet of Things Project?The OWASP Internet of Things Project provides information on:
Project Leaders
Contributors
IoT Top 2018 Contributors
Related Projects |
CollaborationHint: If you're new to Slack, join OWASP's slack channel first, then join #iot-security within OWASP's channel. Quick DownloadIoT Attack Surface Mapping DEFCON 23 News and Events
Classifications
| |||||||
