OWASP Internet of Things Top Ten Project

=Main=



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

OWASP Internet of Things Top 10
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 (IoT) Top 10 is a project 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 defines the top ten security surface areas presented by IoT systems, and provides information on threat agents, attack vectors, vulnerabilities, and impacts associated with each. In addition, the project aims to provide practical security recommendations for builders, breakers, and users of IoT systems.

Licensing
The OWASP Internet of Things Top 10 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.


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

What is the OWASP Internet of Things Top 10?
The OWASP Internet of Things Top 10 provides:


 * A list of the 10 Most Significant IoT Security Surface Areas
 * A list of basic recommendations for manufacturers, developers, and consumers

For each attack surface areas, the following sections are included:


 * A description of the attack surface
 * Threat agents
 * Attack vectors
 * Security weaknesses
 * Technical impacts
 * Business impacts
 * Example vulnerabilities
 * Example attacks
 * Guidance on how to avoid the issue
 * References to OWASP and other related resources

For each role in Manufacturers, Developers, and Consumer, the following recommendations are included:


 * For each IN category, list the top few considerations that should be observed in that context

Project Leaders

 * Daniel Miessler
 * Craig Smith
 * Jason Haddix

Related Projects

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


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

Email List
Subcribe here

Quick Download
OWASP Internet of Things Top Ten 2014 PDF

OWASP Internet of Things Top Ten 2014 Infographic

OWASP Internet of Things Top Ten 2014 PPT

OWASP IoT Top Ten RSA 2015 Presentation

News and Events

 * [April 2015] Added the IoT Top 10 talk from RSA
 * [April 2015] Added an IoT Top 10 Infographic
 * IoT day is April 9th!
 * [February 2015] Added a PDF containing a walk through of the project and the Top Ten.

Classifications

 * }

= OWASP Internet of Things Top 10 for 2014 =



The OWASP Internet of Things Top 10 - 2014 is as follows:


 * 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

Introduction
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 (IoT) Top 10 is a project designed to help vendors who are interested in making common appliances and gadgets network/Internet accessible. The project walks through the top ten security problems that are seen with IoT devices, and how to prevent them.

Examples of IoT Devices: Cars, lighting systems, refrigerators, telephones, SCADA systems, traffic control systems, home security systems, TVs, DVRs, etc…

Feedback
Please let us know how your organization is using the Internet of Things Top 10. Include your name, organization's name, and brief description of how you use the list. Thanks for supporting OWASP!

We hope you find the information in the OWASP Internet of Things Top Ten useful. Please contribute back to the project by sending your comments, questions, and suggestions to Daniel.Miessler@owasp.org, Craig.Smith@owasp.org, or Jason.Haddix@owasp.org, Thanks!

Project Sponsors

 * HP Fortify on Demand
 * Contribute and add your name here!

= Talks =

RSA Conference San Francisco Securing the Internet of Things: Mapping IoT Attack Surface Areas with the OWASP IoT Top 10 Project Daniel Miessler, Practice Principal April 21, 2015 --- Defcon 2015 IoT Security Daniel Miessler August 6-9, 2015

= In the News =
 * "McKinsey: The IoT is Worth $11.1T a Year" CMS Wire. CMS Wire 05 July 2015
 * "Why Caterpillar is letting its geek flag fly" Crain's. Crain's 04 July 2015
 * "The cable box might solve the Internet of Thing's biggest problem" msn.com. msn.com 04 July 2015
 * "The Internet Versus The Great California Drought" Forbes. Forbes 01 July 2015

= IoT Conferences - July 2015=


 * Softweb Solutions Internet of Things Workshop Partnered with Microsoft Downers Grove, US July 09
 * Knotty Objects | MIT Media Lab Summit | MIT Media Lab Boston, US July 15 - 16
 * Internet of Things Chicago Chicago, US July 17
 * APPNATION Internet of Things (IoT) Summit Santa Clara US July 20 - 21
 * Black Hat USA 2015 - Offensive IoT Exploitation Las Vegas, US August 01 - 06
 * IoT - Internet of Things Las Vegas US August 06 - 09

= Community =

I Am The Cavalry

A global grassroots organization that is focused on issues where computer security intersects public safety and human life.

Their areas of focus include:
 * Medical devices
 * Automobiles
 * Home Electronics
 * Public Infrastructure

If This Then That (IFTTT)

A service that lets you create powerful connections with one simple statement.

Channels are the basic building blocks of IFTTT. Channels include:
 * Triggers - The this part of a Recipe
 * Actions - The that part of a Recipe

BuildItSecure.ly

A project focused on helping small business connect with security researchers to aid in securing their IoT-based products before going market.

Their goals include:
 * Focus effort towards small business
 * Build partnerships
 * Coordinate efforts
 * Curate informational resources
 * Present research

= Manufacturers =

Manufacturer IoT Security Guidance
(DRAFT)



The goal of this page is help manufacturers build more secure products in the Internet of Things space. The guidance below is at a basic level, giving builders of products a basic set of guidelines to consider from their perspective. This is not a comprehensive list of considerations, and should not be treated as such, but ensuring that these fundamentals are covered will greatly improve the security of any IoT product.

General Recommendations
Consider the following recommendation for all Internet of Things products:
 * Avoid the potential for persistent vulnerabilities in devices that have no update capability by ensuring that all devices and systems are built with the ability to be updated when vulnerabilities are discovered
 * Rebranded devices used as part of a system should be properly configured so that unnecessary or unintended services do not remain active after the rebranding

[ NOTE: Given the fact that each deployment and every environment is different, it is important to weigh the pros and cons of implementing the advice above before taking each step. ]

= Developers =

Developer IoT Security Guidance
(DRAFT)

The goal of this page is help developers build more secure applications in the Internet of Things space. The guidance below is at a basic level, giving developers of applications a basic set of guidelines to consider from their perspective. This is not a comprehensive list of considerations, and should not be treated as such, but ensuring that these fundamentals are covered will greatly improve the security of any IoT product.

General Recommendations
Consider the following recommendations for all user interfaces (local device, cloud-based and mobile):
 * Avoid potential Account Harvesting issues by:
 * Ensuring valid user accounts can't be identified by interface error messages
 * Ensuring strong passwords are required by users
 * Implementing account lockout after 3 - 5 failed login attempts

[ NOTE: Given the fact that each deployment and every environment is different, it is important to weigh the pros and cons of implementing the advice above before taking each step. ]

= Testers =

Tester IoT Security Guidance
(DRAFT)

The goal of this page is to help testers assess IoT devices and applications in the Internet of Things space. The guidance below is at a basic level, giving testers of devices and applications a basic set of guidelines to consider from their perspective. This is not a comprehensive list of considerations, and should not be treated as such, but ensuring that these fundamentals are covered will greatly improve the security of any IoT product.

General Recommendations
Consider the following recommendations for all user interfaces (local device, cloud-based and mobile):
 * Avoid potential Account Harvesting issues by:
 * Ensuring valid user accounts can't be identified by interface error messages
 * Ensuring strong passwords are required by users
 * Implementing account lockout after 3 - 5 failed login attempts

= Consumers =

Consumer IoT Security Guidance
(DRAFT)

The goal of this page is help consumers purchase secure products in the Internet of Things space. The guidance below is at a basic level, giving consumers a basic set of guidelines to consider from their perspective. This is not a comprehensive list of considerations, and should not be treated as such, but ensuring that these fundamentals are covered will greatly aid the consumer in purchasing a secure IoT product.

General Recommendations
If you are looking to purchase a device or system, consider the following recommendations:
 * Include security in feature considerations when evaluating a product
 * Place Internet of Things devices on a separate network if possible using a firewall

[ NOTE: Given the fact that each deployment and every environment is different, it is important to weigh the pros and cons of implementing the advice above before taking each step. ]

= Project Details =

