OWASP Internet of Things Project

= Main =



{| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |-
 * style="border-right: 1px dotted gray;padding-right:25px;" valign="top" |

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!

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.


 * style="padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;" valign="top" |

What is the OWASP Internet of Things Project?
The OWASP Internet of Things Project provides information on:


 * IoT Attack Surface Areas
 * IoT Vulnerabilities
 * Firmware Analysis
 * ICS/SCADA Software Weaknesses
 * Community Information
 * IoT Testing Guides
 * IoT Security Guidance
 * Principles of IoT Security
 * IoT Framework Assessment
 * Developer, Consumer and Manufacturer Guidance
 * Design Principles
 * IoTGoat

Project Leaders

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

Contributors

 * Justin Klein Keane
 * Saša Zdjelar

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

 * OWASP Project Repository
 * OWASP Mobile Security
 * OWASP Web Top 10
 * OWASP Embedded Application Security
 * OWASP C-based Toolchain Hardening


 * style="padding-left:25px;width:200px;" valign="top" |

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

 * OWASP IoTGoat Project underway
 * New firmware security analysis tool, ByteSweep
 * IoT ASVS and Testing Guide set to kick off in 2019
 * Added a Slack channel
 * Added a sub-project; IoT Security Policy Project

Classifications

 * }

= IoT Top 10 = 

Internet of Things (IoT) Top 10 2018
The OWASP IoT Top 10 - 2018 is now available.
 * I1 Weak Guessable, or Hardcoded Passwords


 * I2 Insecure Network Services


 * I3 Insecure Ecosystem Interfaces


 * I4 Lack of Secure Update Mechanism


 * I5 Use of Insecure or Outdated Components


 * I6 Insufficient Privacy Protection


 * I7 Insecure Data Transfer and Storage


 * I8 Lack of Device Management


 * I9 Insecure Default Settings


 * I10 Lack of Physical Hardening

Internet of Things (IoT) Top 10 2014

 * I1 Insecure Web Interface
 * I2 Insufficient Authentication/Authorization
 * I3 Insecure Network Services
 * I4 Lack of Transport Encryption
 * I5 Privacy Concerns
 * I6 Insecure Cloud Interface
 * I7 Insecure Mobile Interface
 * I8 Insufficient Security Configurability
 * I9 Insecure Software/Firmware
 * I10 Poor Physical Security

= OWASP IoT Top 10 2018 Mapping Project = {| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |-
 * style="border-right: 1px dotted gray;padding-right:25px;" valign="top" |

IoT Top 10 2018 Mapping Project
The OWASP IoT Mapping Project is intended to provide a mapping of the OWASP IoT Top 10 2018 to industry publications and sister projects. The goal is to provide resources that enable practical uses for the OWASP IoT Top 10. As with all Top 10 lists, they should be used as a first step and expanded upon according to the applicable IoT ecosystem.

Mappings are structured with control categories, tests, or recommendations in the left column, descriptions in the middle column, and their mapping to the OWASP IoT Top 10 2018 list in the right column. Each mapping may not have a 1 to 1 relation; however, similar recommendations and/or controls are listed. For mappings that are not applicable to the IoT Top 10 2018 list, an "N/A" is provided as the mapping.

An example mapping of the IoT Top 10 2014 is provided below.



For additional mappings, please visit the following link: https://scriptingxss.gitbook.io/owasp-iot-top-10-mapping-project/


 * style="padding-left:25px;width:300px;border-right: 1px dotted gray;padding-right:25px;" valign="top" |

What is the IoT Top 10 Mapping Project?
The OWASP IoT Mapping Project is intended to provide a mapping of the OWASP IoT Top 10 2018 to industry publications and sister projects. The goal is to provide resources that enable practical uses for the OWASP IoT Top 10. As with all Top 10 lists, they should be used as a first step and expanded upon according to the applicable IoT ecosystem.

Mappings include the following:
 * OWASP IoT Top 10 2014
 * GSMA IoT Security Assessment Checklist
 * Code of Practice (UK Government)
 * ENISA Baseline Security Recommendations for IoT

and more...

GitBook
Mappings are hosted on GitBook using the following link https://scriptingxss.gitbook.io/owasp-iot-top-10-mapping-project/

Project Leaders

 * Aaron Guzman

Collaboration
The Slack Channel


 * }

= IoTGoat = 

{| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |-
 * style="border-right: 1px dotted gray;padding-right:25px;" valign="top" |

IoTGoat Project
IoT Goat is a deliberately insecure firmware based on OpenWrt. The project’s goal is to teach users about the most common vulnerabilities typically found in IoT devices. The vulnerabilities will be based on the top 10 vulnerabilities as documented by OWASP: https://www.owasp.org/index.php/OWASP_Internet_of_Things_Project. IoTGoat is expected to be released by December 2019.

To get more information on getting started or how to contribute, visit the project's Github: https://github.com/scriptingxss/IoTGoat


 * style="padding-left:25px;width:300px;border-right: 1px dotted gray;padding-right:25px;" valign="top" |

What is the IoTGoat Project?
The IoTGoat Project is a deliberately insecure firmware based on OpenWrt. The project’s goal is to teach users about the most common vulnerabilities typically found in IoT devices. The vulnerabilities will be based on the IoT Top 10.

GitHub
https://github.com/scriptingxss/IoTGoat

Project Leaders

 * Aaron Guzman
 * Fotios Chantzis
 * Paulino Calderon

Related Projects

 * WebGoat
 * Serverless Goat
 * NodeGoat
 * RailsGoat

Collaboration
The Slack Channel

IoTGoat Google Group

Quick Download

 * Project Kick-off Slides
 * Project Kick-off Meeting
 * Project Task List

News and Events

 * Coming Soon


 * }

= ByteSweep = {| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |-
 * style="border-right: 1px dotted gray;padding-right:25px;" valign="top" |

ByteSweep Project
ByteSweep is a Free Software IoT security analysis platform. This platform will allow IoT device makers, large and small, to conduct fully automated security checks before they ship firmware. A Free Software IoT Firmware Security Analysis Platform

ByteSweep Features:
 * Firmware extraction
 * File data enrichment
 * Key and password hash identification
 * Unsafe function use detection
 * 3rd party component identification
 * CVE correlation


 * style="padding-left:25px;width:300px;border-right: 1px dotted gray;padding-right:25px;" valign="top" |

What is the ByteSweep Project?
A Free Software IoT Firmware Security Analysis Platform.

GitLab
https://gitlab.com/bytesweep/bytesweep

Project Leaders

 * Matt Brown

Collaboration
The Slack Channel

Quick Download

 * https://gitlab.com/bytesweep/bytesweep/blob/master/INSTALL.md


 * }

= Firmware Security Testing Methodology =

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


 * 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) - https://github.com/scriptingxss/EmbedOS

Project Leaders

 * Aaron Guzman

Quick Download

 * TBD


 * }

= IoT Attack Surface Areas =



{| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |-
 * style="border-right: 1px dotted gray;padding-right:25px;" valign="top" |

IoT Attack Surface Areas Project
The OWASP IoT Attack Surface Areas (DRAFT) are as follows:


 * style="padding-left:25px;width:300px;border-right: 1px dotted gray;padding-right:25px;" valign="top" |

What is the IoT Attack Surface Areas Project?
The IoT Attack Surface Areas Project provides a list of attack surfaces that should be understood by manufacturers, developers, security researchers, and those looking to deploy or implement IoT technologies within their organizations.

Project Leaders

 * Daniel Miessler
 * Craig Smith

Related Projects

 * The OWASP Mobile Top 10 Project
 * The OWASP Web Top 10 Project

Collaboration
The Slack Channel

Quick Download

 * Coming Soon

News and Events

 * Coming Soon


 * }

= IoT Vulnerabilities =



{| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |-
 * style="border-right: 1px dotted gray;padding-right:25px;" valign="top" |

IoT Vulnerabilities Project

 * style="padding-left:25px;width:300px;border-right: 1px dotted gray;padding-right:25px;" valign="top" |

What is the IoT Vulnerabilities Project?
The IoT Vulnerabilities Project provides:


 * Information on the top IoT vulnerabilities
 * The attack surface associated with the vulnerability
 * A summary of the vulnerability

Project Leaders

 * Daniel Miessler
 * Craig Smith

Related Projects

 * OWASP Mobile Security
 * OWASP Web Top 10

Collaboration
The Slack Channel

Resources

 * Top 10 IoT Vulnerabilities from 2014

News and Events

 * Coming Soon


 * }

= Medical Devices =



{| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |-
 * style="border-right: 1px dotted gray;padding-right:25px;" valign="top" |

Medical Device Testing
The Medical Device Testing project is intended to provide some basic attack surface considerations that should be evaluated before shipping Medical Device equipment.


 * style="padding-left:25px;width:300px;border-right: 1px dotted gray;padding-right:25px;" valign="top" |

What is the Medical Attack Surfaces project?
The Medical Attack Surfaces project provides:


 * A simple way for testers, manufacturers, developers, and users to get an understanding of the complexity of a modern medical environment
 * Allows people to visualize the numerous attack surfaces that need to be defended within medical equipment ecosystems

Project Leaders

 * Daniel Miessler

Related Projects

 * OWASP Mobile Security
 * OWASP Web Top 10

Collaboration
The Slack Channel

Resources

 * IoT Firmware Analysis Primer
 * Online Trust Alliance - Internet of Things
 * Pre-compiled QEMU images
 * Firmware Modification Kit
 * Short Firmware Extraction Video
 * Firmware Emulation with QEMU
 * File Extraction from Network Capture

News and Events

 * Daniel Miessler presented on using Adaptive Testing Methodologies to evaluate the security of medical devices at RSA 2017.


 * }

= Firmware Analysis =



{| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |-
 * style="border-right: 1px dotted gray;padding-right:25px;" valign="top" |

Firmware Analysis Project
The Firmware Analysis Project is intended to provide security testing guidance for the IoT Attack Surface "Device Firmware":


 * style="padding-left:25px;width:300px;border-right: 1px dotted gray;padding-right:25px;" valign="top" |

What is the Firmware Analysis Project?
The Firmware Analysis Project provides:


 * Security testing guidance for vulnerabilities in the "Device Firmware" attack surface
 * Steps for extracting file systems from various firmware files
 * Guidance on searching a file systems for sensitive of interesting data
 * Information on static analysis of firmware contents
 * Information on dynamic analysis of emulated services (e.g. web admin interface)
 * Testing tool links
 * A site for pulling together existing information on firmware analysis

Project Leaders

 * Craig Smith

Related Projects

 * OWASP Mobile Security
 * OWASP Web Top 10
 * OWASP Embedded Application Security Project

Collaboration
The Slack Channel

Resources

 * IoT Firmware Analysis Primer
 * Online Trust Alliance - Internet of Things
 * Pre-compiled QEMU images
 * Firmware Modification Kit
 * Short Firmware Extraction Video
 * Firmware Emulation with QEMU
 * File Extraction from Network Capture

News and Events

 * Coming Soon


 * }

= IoT Event Logging Project=



{| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |-
 * style="border-right: 1px dotted gray;padding-right:25px;" valign="top" |

IoT Logging Events
This is a working draft of the recommended minimum IoT Device logging events. This includes many  different types of devices, including consumer IoT, enterprise IoT, and ICS/SCADA type devices.


 * style="padding-left:25px;width:300px;border-right: 1px dotted gray;padding-right: 25px;" valign="top" |

What is the IoT Security Logging Project?
The IoT Secure Logging Project provides a list of core events that should be logged in any IoT-related system. The project exists because IoT systems in general are not logging nearly enough events to constitute input for a solid detection and response program around IoT devices, and for companies that want to do this there are not many good resources for what should be logged.

Project Leaders

 * Daniel Miessler

Related Projects

 * The OWASP AppSensor Project

Collaboration
The Slack Channel

Quick Download

 * Coming Soon

News and Events

 * Coming Soon


 * }

=Project About=