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"

From OWASP
Jump to: navigation, search
(.)
 
(2 intermediate revisions by the same user not shown)
Line 146: Line 146:
 
|}
 
|}
  
−
= Seek & Understand =
+
= IoT Top 10 =
−
 
 
−
== IoT Top 10 ==
 
 
<div style="width:100%;height:160px;border:0,margin:0;overflow: hidden;">[[File:OWASP_Project_Header.jpg|link=]]</div>
 
<div style="width:100%;height:160px;border:0,margin:0;overflow: hidden;">[[File:OWASP_Project_Header.jpg|link=]]</div>
  
Line 184: Line 182:
 
* [[Top 10 2014-I10 Poor Physical Security|I10 Poor Physical Security]]
 
* [[Top 10 2014-I10 Poor Physical Security|I10 Poor Physical Security]]
  
−
== OWASP IoT Top 10 2018 Mapping Project ==
+
= OWASP IoT Top 10 2018 Mapping Project =
 
{| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |-
 
{| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |-
 
| style="border-right: 1px dotted gray;padding-right:25px;" valign="top" |
 
| style="border-right: 1px dotted gray;padding-right:25px;" valign="top" |
Line 313: 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,122: Line 1,184:
 
== News and Events ==
 
== News and Events ==
 
* Coming Soon
 
* Coming Soon
−
 
−
|}
 
−
 
−
= 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 TBD.
 
−
 
−
{{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 ==
 
−
* TBD
 
  
 
|}
 
|}

Latest revision as of 07:02, 1 November 2019

OWASP Project Header.jpg

OWASP Internet of Things (IoT) Project

Oxford 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!
OWASP 2018 IoT Top10 Final.jpg

Philosophy

The 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.

Methodology

The 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:

  1. Team Formation: finding people who would be willing to contribute to the 2018 update, both as SMEs and as project leaders to perform various tasks within the duration of the project.
  2. Project Review: analysis of the 2014 project to determine what’s changed in the industry since that release, and how the list should be updated given those changes.
  3. Data Collection: collection and review of multiple vulnerability sources (both public and private), with special emphasis on which issues caused the most actual impact and damage.
  4. Sister Project Review: a review of dozens of other IoT Security projects to ensure that we’d not missed something major and that we were comfortable with both the content and prioritization of our release. Examples included: CSA IoT Controls Matrix, CTIA, Stanford’s Secure Internet of Things Project, NISTIR 8200, ENISA IoT Baseline Report, Code of Practice for Consumer IoT Security, and others.
  5. Community Draft Feedback: release of the draft to the community for review, including multiple Twitter calls for comments, the use of a public feedback form, and a number of public talks where feedback was gathered. The feedback was then reviewed by the team along with initial Data Collection, as well as Sister Project Review, to create the list contents and prioritization.
  6. Release: release of the project to the public in December 2018.

The Future of the OWASP IoT Top 10

The team has a number of activities planned to continue improving on the project going forward.

Some of the items being discussed include:

  • Continuing to improve the list on a two-year cadence, incorporating feedback from the community and from additional project contributors to ensure we are staying current with issues facing the industry.
  • Mapping the list items to other OWASP projects, such as the ASVS, and perhaps to other projects outside OWASP as well.
  • Expanding the project into other aspects of IoT—including embedded security, ICS/ SCADA,etc.
  • Adding use and abuse cases, with multiple examples, to solidify each concept discussed.
  • Considering the addition of reference architectures, so we can not only tell people what to avoid, but how to do what they need to do securely.

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

Licensing

The 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.


Share this:  E-mail this story Bookmark with Facebook Share on Digg.com Share on delicious Share on reddit.com Share on stumbleupon.com Share on LinkedIn.com Share on twitter.com Seed on Newsvine

What is the OWASP Internet of Things Project?

The OWASP Internet of Things Project provides information on:

Project Leaders

  • Daniel Miessler
  • Craig Smith
  • Vishruta Rudresh
  • Aaron Guzman

Contributors

IoT Top 2018 Contributors

  • Vijayamurugan Pushpanathan
  • Alexander Lafrenz
  • Masahiro Murashima
  • Charlie Worrell
  • José A. Rivas (jarv)
  • Pablo Endres
  • Ade Yoseman
  • Cédric Levy-Bencheotn
  • Jason Andress
  • Amélie Didion - Designer

Related Projects

Collaboration

The OWASP Slack Channel

Hint: If you're new to Slack, join OWASP's slack channel first, then join #iot-security within OWASP's channel.

Quick Download

OWASP IoT Top Ten 2018

IoT Attack Surface Mapping DEFCON 23

IoT Testing Guidance Handout

OWASP IoT Top Ten 2014 PDF

OWASP IoT Project Overview

News and Events

Classifications

Owasp-incubator-trans-85.png Owasp-builders-small.png
Owasp-defenders-small.png
Cc-button-y-sa-small.png
Project Type Files DOC.jpg

Retrieved from "https://wiki.owasp.org/index.php?title=OWASP_Internet_of_Things_Project&oldid=255839"