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.

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==

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

−

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

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

−

==Volunteers==

+

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.

−

The OWASP Internet of Things Top Ten Project is developed by a worldwide team of volunteers. The primary contributors to date have been:

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!

−

|headertab=Acknowledgements

+

−

|usenext=2013NextLink

+

−

|next=A2-{{Top_10_2010:ByTheNumbers

+

−

|2

+

−

|year=2013

+

−

|language=en}}

+

−

|useprev=2013PrevLink

+

−

|prev={{Top_10:LanguageFile|text=top10|year=2013|language=en}}

+

−

|year=2013

+

−

|language=en

+

−

}}

+

−

='''___________Road Map and Getting Involved___________'''=

+

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 or Craig.Smith@owasp.org Thanks!

* [http://www.forbes.com/sites/joemckendrick/2015/03/25/is-the-internet-of-things-heralding-the-next-great-economic-shift/ "Why the Internet of Things Heralds the Next Great Economic Disruption"] ''Forbes.'' Forbes 25 March 2015

−

|next=A2-{{Top_10_2010:ByTheNumbers

+

* [http://www.fastcompany.com/3044046/tech-forecast/welcome-to-privacy-hell-otherwise-known-as-the-internet-of-things "Welcome to Privacy Hell, Also Known As the Internet of Things"] ''FastCompany.'' FastCompany 23 March 2015

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

+

== ==

+

[https://ifttt.com/ If This Then That (IFTTT)]

+

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

−

='''A3-Cross-Site Scripting (XSS)'''=

+

Channels are the basic building blocks of IFTTT. Channels include:

+

* Triggers - The ''this'' part of a Recipe

+

* Actions - The ''that'' part of a Recipe

+

== ==

+

[http://builditsecure.ly 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

−

='''A4-Insecure Direct Object References'''=

+

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

−

='''A5-Security Misconfiguration'''=

+

{| border="1" class="wikitable" style="text-align: left"

+

! Category

+

! IoT Security Consideration

+

|-

+

| '''I1: Insecure Web Interface'''

+

|

+

* Ensure that any web interface in the product disallows weak passwords

+

* Ensure that any web interface in the product has an account lockout mechanism

+

* Ensure that any web interface in the product has been tested for XSS, SQLi and CSRF vulnerabilities

+

* Ensure that any web interface has the ability to use HTTPS to protect transmitted information

+

* Include web application firewalls to protect any web interfaces

+

* Ensure that any web interface allows the owner to change the default username and password

* Ensure encryption options are made available (e.g. Enabling AES-256 where AES-128 is the default setting)

+

* Ensure secure logging is available for security events

+

* Ensure alerts and notifications are available to the user for security events

+

|-

+

| '''I9: Insecure Software/Firmware'''

+

|

+

* Ensure all system devices have update capability and can be updated quickly when vulnerabilities are discovered

+

* Ensure update files are encrypted and that the files are also transmitted using encryption

+

* Ensure that update files are signed and then validated by the device before installing

+

* Ensure update servers are secure

+

* Ensure the product has the ability to implement scheduled updates

+

|-

+

| '''I10: Poor Physical Security'''

+

|

+

* Ensure the device is produced with a minimal number of physical external ports (e.g. USB ports)

+

* Ensure the firmware of Operating System can not be accessed via unintended methods such as through an unnecessary USB port

+

* Ensure the product is tamper resistant

+

* Ensure the product has the ability to limit administrative capabilities in some fashion, possibly by only connecting locally for admin functions

+

* Ensure the product has the ability to disable external ports such as USB

+

|}

+

===General Recommendations===

−

='''A6-Sensitive Data Exposure'''=

+

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 =

−

='''A7-Missing Function Level Access Control'''=

+

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

+

{| border="1" class="wikitable" style="text-align: left"

+

! Category

+

! IoT Security Consideration

+

|-

+

| '''I1: Insecure Web Interface'''

+

|

+

* Ensure that any web interface coding is written to prevent the use of weak passwords

+

* Ensure that any web interface coding is written to include an account lockout mechanism

+

* Ensure that any web interface coding has been tested for XSS, SQLi and CSRF vulnerabilities

+

* Ensure that any web interface has the ability to use HTTPS to protect transmitted information

+

* Ensure that any web interface coding is written to allow the owner to change the username and password

+

* Consider the use of web application firewalls to protect any web interfaces

+

|-

+

| '''I2: Insufficient Authentication/Authorization'''

+

|

+

* Ensure that applications are written to require strong passwords where authentication is needed

+

* Ensure the application takes into account multi-user environments and includes functionality for role separation

+

* Implement two-factor authentication where possible

+

* Ensure password recovery mechanisms are written to function in a secure manner

+

* Ensure that applications are written to include the option to require strong passwords

+

* Ensure that applications are written to include the option to force password expiration after a specific period

+

* Ensure that applications are written to include the option to change the default username and password

+

|-

+

| '''I3: Insecure Network Services'''

+

|

+

* Ensure applications that use network services don't respond poorly to buffer overflow, fuzzing or denial of service attacks

+

* Ensure applications test ports are taken out of service before going to production

+

|-

+

| '''I4: Lack of Transport Encryption'''

+

|

+

* Ensure all applications are written to make use of encrypted communication between devices and between devices and the internet

[ 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. ]

−

='''A9-Using Components with Known Vulnerabilities'''=

+

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

−

='''A10-Unvalidated Redirects and Forwards'''=

+

{| border="1" class="wikitable" style="text-align: left"

+

! Category

+

! IoT Security Consideration

+

|-

+

| '''I1: Insecure Web Interface'''

+

|

+

* If your system has the option to use HTTPS, ensure it is enabled

+

* If your system has a two factor authentication option, ensure that it is enabled

+

* If your system has web application firewall option, ensure that it is enabled

+

* If your system has a local or cloud-based web application, ensure that you change the default password to a strong one and if possible change the default username as well

+

* If the system has account lockout functionality, ensure that it is enabled

Latest revision as of 10:57, 26 March 2015

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.

Share this:

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

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.

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 or Craig.Smith@owasp.org Thanks!

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

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.

Category

IoT Security Consideration

I1: Insecure Web Interface

Ensure that any web interface in the product disallows weak passwords

Ensure that any web interface in the product has an account lockout mechanism

Ensure that any web interface in the product has been tested for XSS, SQLi and CSRF vulnerabilities

Ensure that any web interface has the ability to use HTTPS to protect transmitted information

Include web application firewalls to protect any web interfaces

Ensure that any web interface allows the owner to change the default username and password

Ensure that users have the option to force password expiration after a specific period

Ensure that users have the option to change the default username and password

I8: Insufficient Security Configurability

Ensure password security options are made available (e.g. Enabling 20 character passwords or enabling two-factor authentication)

Ensure encryption options are made available (e.g. Enabling AES-256 where AES-128 is the default setting)

Ensure secure logging is available for security events

Ensure alerts and notifications are available to the user for security events

I9: Insecure Software/Firmware

Ensure all system devices have update capability and can be updated quickly when vulnerabilities are discovered

Ensure update files are encrypted and that the files are also transmitted using encryption

Ensure that update files are signed and then validated by the device before installing

Ensure update servers are secure

Ensure the product has the ability to implement scheduled updates

I10: Poor Physical Security

Ensure the device is produced with a minimal number of physical external ports (e.g. USB ports)

Ensure the firmware of Operating System can not be accessed via unintended methods such as through an unnecessary USB port

Ensure the product is tamper resistant

Ensure the product has the ability to limit administrative capabilities in some fashion, possibly by only connecting locally for admin functions

Ensure the product has the ability to disable external ports such as USB

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

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.

Category

IoT Security Consideration

I1: Insecure Web Interface

Ensure that any web interface coding is written to prevent the use of weak passwords

Ensure that any web interface coding is written to include an account lockout mechanism

Ensure that any web interface coding has been tested for XSS, SQLi and CSRF vulnerabilities

Ensure that any web interface has the ability to use HTTPS to protect transmitted information

Ensure that any web interface coding is written to allow the owner to change the username and password

Consider the use of web application firewalls to protect any web interfaces

I2: Insufficient Authentication/Authorization

Ensure that applications are written to require strong passwords where authentication is needed

Ensure the application takes into account multi-user environments and includes functionality for role separation

Implement two-factor authentication where possible

Ensure password recovery mechanisms are written to function in a secure manner

Ensure that applications are written to include the option to require strong passwords

Ensure that applications are written to include the option to force password expiration after a specific period

Ensure that applications are written to include the option to change the default username and password

I3: Insecure Network Services

Ensure applications that use network services don't respond poorly to buffer overflow, fuzzing or denial of service attacks

Ensure applications test ports are taken out of service before going to production

I4: Lack of Transport Encryption

Ensure all applications are written to make use of encrypted communication between devices and between devices and the internet

Use recommended and accepted encryption practices and avoid proprietary protocols

Consider making a firewall option available for the application

I5: Privacy Concerns

Ensure only the minimal amount of personal information is collected from consumers

Ensure all collected personal data is properly protected using encryption at rest and in transit

[ 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. ]

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.

Category

IoT Security Consideration

I1: Insecure Web Interface

If your system has the option to use HTTPS, ensure it is enabled

If your system has a two factor authentication option, ensure that it is enabled

If your system has web application firewall option, ensure that it is enabled

If your system has a local or cloud-based web application, ensure that you change the default password to a strong one and if possible change the default username as well

If the system has account lockout functionality, ensure that it is enabled

Consider employing network segmentation technologies such as firewalls to isolate IoT systems from critical IT systems

I2: Insufficient Authentication/Authorization

If your system has a local or cloud-based web application, ensure that you change the default password to a strong one and if possible change the default username as well

If the system has account lockout functionality, ensure that it is enabled

If the system has the option to require strong passwords, ensure that is enabled

If the system has the option to require new passwords after 90 days for example, ensure that is enabled

If your system has a two factor authentication option, ensure that it is enabled

If your system has the option to set user privileges, consider setting user privileges to the minimal needed for operation

Consider employing network segmentation technologies such as firewalls to isolate IoT systems from critical IT systems

I3: Insecure Network Services

If your system has a firewall option available, enable it and ensure that it can only be accessed from your client systems

Consider employing network segmentation technologies such as firewalls to isolate IoT systems from critical IT systems

I4: Lack of Transport Encryption

If your system has the option to use HTTPS, ensure it is enabled

I5: Privacy Concerns

Do not enter sensitive information into the system that is not absolutely required, e.g. address, DOB, CC, etc.

I6: Insecure Cloud Interface

If your system has the option to use HTTPS, ensure it is enabled

If your system has a two factor authentication option, ensure that it is enabled

If your system has web application firewall option, ensure that it is enabled

If your system has a local or cloud-based web application, ensure that you change the default password to a strong one and if possible change the default username as well

If the system has account lockout functionality, ensure that it is enabled

If the system has the option to require strong passwords, ensure that is enabled

If the system has the option to require new passwords after 90 days for example, ensure that is enabled

I7: Insecure Mobile Interface

If the mobile application has the option to require a PIN or password, consider using it for extra security (on client and server)

If the mobile application has the option to use two factory authentication such as Apple's Touch ID, ensure it is enabled

If the system has account lockout functionality, ensure that it is enabled

If the system has the option to require strong passwords, ensure that is enabled

If the system has the option to require new passwords after 90 days for example, ensure that is enabled

Do not enter sensitive information into the mobile application that is not absolutely required, e.g. address, DOB, CC, etc.

I8: Insufficient Security Configurability

If your system has the option, enable any logging functionality for security-related events

If your system has the option, enable any alert and notification functionality for security-related events

If your system has security options for passwords, ensure they are enabled for strong passwords

If your system has security options for encryption, ensure they are set for an accepted standard such as AES-256

I9: Insecure Software/Firmware

If your system has the option to verify updates, ensure it is enabled

If your system has the option to download updates securely, ensure it is enabled

If your system has the ability to schedule updates on a regular cadence, consider enabling it

I10: Poor Physical Security

If your system has the ability to limit administrative capabilities possible by connecting locally, consider enabling that feature

Disable any unused physical ports through the administrative interface

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 INFOWhat does this OWASP project offer you?

RELEASE(S) INFOWhat releases are available for this project?

what

is this project?

Name: OWASP Internet of Things Top Ten Project (home page)

Purpose: 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.