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
Line 302: Line 302:
 
** Ensuring strong passwords are required by users
 
** Ensuring strong passwords are required by users
 
** Implementing account lockout after 3 - 5 failed login attempts
 
** Implementing account lockout after 3 - 5 failed login attempts
 +
 +
= IoT Security Guidance =
 +
 +
== '''Manufacturer IoT Security Guidance''' ==
 +
 +
(DRAFT)
 +
 +
 +
The goal of this section 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.
 +
 +
{| 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
 +
|-
 +
| '''I2: Insufficient Authentication/Authorization'''
 +
|
 +
* Ensure that any access requiring authentication requires strong passwords
 +
* Ensure that user roles can be properly segregated in multi-user environments
 +
* Implement two-factor authentication where possible
 +
* Ensure password recovery mechanisms are secure
 +
* Ensure that users have the option to require strong passwords
 +
* 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
 +
|-
 +
| '''I3: Insecure Network Services'''
 +
|
 +
* Ensure all devices operate with a minimal number of network ports active
 +
* Ensure all devices do not make network ports and/or services available to the internet via UPnP for example
 +
* Review all required network services for vulnerabilities such as buffer overflows or denial of service
 +
|-
 +
| '''I4: Lack of Transport Encryption'''
 +
|
 +
* Ensure all communication between system components is encrypted as well as encrypting traffic between the system or device and the internet
 +
* Use recommended and accepted encryption practices and avoid proprietary protocols
 +
* Ensure SSL/TLS implementations are up to date and properly configured
 +
* Consider making a firewall option available for the product
 +
|-
 +
| '''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
 +
* Ensure only authorized individuals have access to collected personal information
 +
* Ensure only less sensitive data is collected
 +
* Ensuring data is de-identified or anonymized
 +
* Ensuring a data retention policy is in place
 +
* Ensuring end-users are given a choice for data collected beyond what is needed for proper operation of the device
 +
|-
 +
| '''I6: Insecure Cloud Interface'''
 +
|
 +
* Ensure all cloud interfaces are reviewed for security vulnerabilities (e.g. API interfaces and cloud-based web interfaces)
 +
* Ensure that any cloud-based web interface disallows weak passwords
 +
* Ensure that any cloud-based web interface has an account lockout mechanism
 +
* Implement two-factor authentication for cloud-based web interfaces
 +
* Ensure that all cloud interfaces use transport encryption
 +
* Ensure that any cloud-based web interface has been tested for XSS, SQLi and CSRF vulnerabilities
 +
* Ensure that users have the option to require strong passwords
 +
* 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
 +
|-
 +
| '''I7: Insecure Mobile Interface'''
 +
|
 +
* Ensure that any mobile application disallows weak passwords
 +
* Ensure that any mobile application has an account lockout mechanism
 +
* Implement two-factor authentication for mobile applications (e.g Apple's Touch ID)
 +
* Ensure that any mobile application uses transport encryption
 +
* Ensure that users have the option to require strong passwords
 +
* 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 section 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
 +
* 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
 +
* Ensuring data is de-identified or anonymized
 +
* Ensuring end-users are given a choice for data collected beyond what is needed for proper operation of the device
 +
|-
 +
| '''I6: Insecure Cloud Interface'''
 +
|
 +
* Ensure all cloud interfaces are reviewed for security vulnerabilities (e.g. API interfaces and cloud-based web interfaces)
 +
* Ensure that any cloud-based web interface coding is written to disallows weak passwords
 +
* Ensure that any cloud-based web interface coding is written to include an account lockout mechanism
 +
* Implement two-factor authentication for cloud-based web interfaces
 +
* Ensure that any cloud interface coding has been tested for XSS, SQLi and CSRF vulnerabilities
 +
* Ensure that all cloud interfaces use transport encryption
 +
* Ensure that cloud interfaces are written to include the option to require strong passwords
 +
* Ensure that cloud interfaces are written to include the option to force password expiration after a specific period
 +
* Ensure that cloud interfaces are written to include the option to change the default username and password
 +
|-
 +
| '''I7: Insecure Mobile Interface'''
 +
|
 +
* Ensure that any mobile application coding is written to disallows weak passwords
 +
* Ensure that any mobile application coding is written to include an account lockout mechanism
 +
* Implement two-factor authentication for mobile applications (e.g Apple's Touch ID)
 +
* Ensure that any mobile application uses transport encryption
 +
* Ensure that mobile interfaces are written to include the option to require strong passwords
 +
* Ensure that mobile interfaces are written to include the option to force password expiration after a specific period
 +
* Ensure that mobile interfaces are written to include the option to change the default username and password
 +
* Ensure that mobile interfaces only collect the minimum amount of personal information needed
 +
|-
 +
| '''I8: Insufficient Security Configurability'''
 +
|
 +
* Ensure applications are written to include password security options (e.g. Enabling 20 character passwords or enabling two-factor authentication)
 +
* Ensure applications are written to include encryption options (e.g. Enabling AES-256 where AES-128 is the default setting)
 +
* Ensure all applications are written to produce logs for security events
 +
* Ensure all applications are written to produce alerts and notifications to the user for security events
 +
|-
 +
| '''I9: Insecure Software/Firmware'''
 +
|
 +
* Ensure all applications are written to include update capability and can be updated quickly when vulnerabilities are discovered
 +
* Ensure all applications are written to process encrypted update files and that the files are transmitted using encryption
 +
* Ensure all applications are written to process signed files and then validate that file before installation
 +
 +
|-
 +
| '''I10: Poor Physical Security'''
 +
|
 +
* Ensure applications are written to utilize a minimal number of physical external ports (e.g. USB ports) on the device
 +
* Ensure all applications can not be accessed via unintended methods such as through an unnecessary USB port
 +
* Ensure all applications are written to allow for disabling of unused physical ports such as USB
 +
* Consider writing applications to limit administrative capabilities to a local interface only
 +
|}
 +
 +
===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. ]
 +
 +
 +
== '''Consumer IoT Security Guidance''' ==
 +
 +
(DRAFT)
 +
 +
The goal of this section 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.
 +
 +
{| 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
 +
* 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.
 +
* Deny data collection if it appears to be beyond what is needed for proper operation of the device (If provided the choice)
 +
|-
 +
| '''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. ]
  
  

Revision as of 20:39, 17 August 2015

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 such as Attack Surface Areas, Testing Guides and Top Vulnerabilities.

Iot-project.png

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:

  • IoT Attack Surface Areas
  • IoT Testing Guides
  • Top IoT Vulnerabilities

Project Leaders

  • Daniel Miessler
  • Craig Smith

Related Projects

Email List

Subscribe to the Top Ten list

Quick Download

IoT Attack Surface Mapping DEFCON 23

IoT Testing Guidance Handout

OWASP IoT Top Ten PDF

OWASP IoT Top Ten Infographic

OWASP IoT Top Ten PPT

OWASP IoT Top Ten-RSA 2015

News and Events

  • Daniel Miessler gave his IoT talk at DEFCON 23
  • Migrating the IoT Top Ten to be under the IoT Project

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