|
|
| (One intermediate revision by one other user not shown) |
| Line 1: |
Line 1: |
| − | =Main=
| + | #REDIRECT [[OWASP_Internet_of_Things_Project]] |
| − | | |
| − | <div style="width:100%;height:160px;border:0,margin:0;overflow: hidden;">[[File:OWASP_Project_Header.jpg|link=]]</div>
| |
| − | | |
| − |
| |
| − | == '''NOTE''': This project is part of [https://www.owasp.org/index.php/OWASP_Internet_of_Things_Project The OWASP IoT Project], which is located [https://www.owasp.org/index.php/OWASP_Internet_of_Things_Project#tab=Main here]. ==
| |
| − | | |
| − | {| 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.
| |
| − | | |
| − | == ==
| |
| − | {{Social Media Links}}
| |
| − | | |
| − | | 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 I''N'' category, list the top few considerations that should be observed in that context
| |
| − | | |
| − | == Project Leaders ==
| |
| − | | |
| − | * Daniel Miessler
| |
| − | * Craig Smith
| |
| − | * Jason Haddix
| |
| − | | |
| − | == Related Projects ==
| |
| − | | |
| − | * [https://www.owasp.org/index.php/OWASP_Mobile_Security_Project The OWASP Mobile Top 10 Project]
| |
| − | * [https://www.owasp.org/index.php/Category:OWASP_Top_Ten_Project The OWASP Web Top 10 Project]
| |
| − | | |
| − | | valign="top" style="padding-left:25px;width:200px;" |
| |
| − | | |
| − | == Email List ==
| |
| − | [https://lists.owasp.org/mailman/listinfo/owasp_internet_of_things_top_ten_project Subcribe here]
| |
| − | | |
| − | == Quick Download ==
| |
| − | [https://www.owasp.org/images/3/36/IoTTestingMethodology.pdf IoT Attack Surface Mapping DEFCON 23]
| |
| − | | |
| − | [https://www.owasp.org/images/2/2d/Iot_testing_methodology.JPG IoT Testing Guidance Handout]
| |
| − | | |
| − | [https://www.owasp.org/images/7/71/Internet_of_Things_Top_Ten_2014-OWASP.pdf OWASP IoT Top Ten PDF]
| |
| − | | |
| − | [https://www.owasp.org/images/8/8e/Infographic-v1.jpg OWASP IoT Top Ten Infographic]
| |
| − | | |
| − | [https://www.owasp.org/images/0/01/Internet_of_Things_Top_Ten_2014-OWASP-ppt.pptx OWASP IoT Top Ten PPT]
| |
| − | | |
| − | [https://www.owasp.org/images/5/51/RSAC2015-OWASP-IoT-Miessler.pdf 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==
| |
| − | | |
| − | {| width="200" cellpadding="2"
| |
| − | |-
| |
| − | | align="center" valign="top" width="50%" rowspan="2"| [[File:Owasp-incubator-trans-85.png|link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Incubator_Projects]]
| |
| − | | align="center" valign="top" width="50%"| [[File:Owasp-builders-small.png|link=]]
| |
| − | |-
| |
| − | | align="center" valign="top" width="50%"| [[File:Owasp-defenders-small.png|link=]]
| |
| − | |-
| |
| − | | colspan="2" align="center" | [[File:Cc-button-y-sa-small.png|link=http://creativecommons.org/licenses/by-sa/3.0/]]
| |
| − | |-
| |
| − | | colspan="2" align="center" | [[File:Project_Type_Files_DOC.jpg|link=]]
| |
| − | |}
| |
| − | | |
| − | |}
| |
| − | | |
| − | = OWASP Internet of Things Top 10 for 2014 =
| |
| − | | |
| − | <div style="width:100%;height:160px;border:0,margin:0;overflow: hidden;">[[File:OWASP_Project_Header.jpg|link=]]</div>
| |
| − | | |
| − | | |
| − | The OWASP Internet of Things Top 10 - 2014 is as follows:
| |
| − | | |
| − | * [[Top_10_2014-I1 Insecure Web Interface | I1 Insecure Web Interface]]
| |
| − | * [[Top_10_2014-I2 Insufficient Authentication/Authorization | I2 Insufficient Authentication/Authorization]]
| |
| − | * [[Top_10_2014-I3 Insecure Network Services | I3 Insecure Network Services]]
| |
| − | * [[Top_10_2014-I4 Lack of Transport Encryption | I4 Lack of Transport Encryption]]
| |
| − | * [[Top_10_2014-I5 Privacy Concerns | I5 Privacy Concerns]]
| |
| − | * [[Top_10_2014-I6 Insecure Cloud Interface | I6 Insecure Cloud Interface]]
| |
| − | * [[Top_10_2014-I7 Insecure Mobile Interface | I7 Insecure Mobile Interface]]
| |
| − | * [[Top_10_2014-I8 Insufficient Security Configurability | I8 Insufficient Security Configurability]]
| |
| − | * [[Top_10_2014-I9 Insecure Software/Firmware | I9 Insecure Software/Firmware]]
| |
| − | * [[Top_10_2014-I10 Poor Physical Security | 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!
| |
| − | | |
| − | | |
| − | | |
| − | == Project Sponsors ==
| |
| − | | |
| − | * [http://www8.hp.com/us/en/software-solutions/fortify-on-demand-application-security/ HP Fortify on Demand]
| |
| − | * Contribute and add your name here!
| |
| − | | |
| − | <!-- ==== Project Identification ====
| |
| − | {{Template:OWASP OWASP_Top10 Project}} -->
| |
| − | | |
| − | = Community =
| |
| − | | |
| − | [https://www.iamthecavalry.org/ 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
| |
| − | == ==
| |
| − | [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
| |
| − | == ==
| |
| − | [https://otalliance.org Online Trust Alliance]
| |
| − | | |
| − | Formed as an informal industry working group in 2005, today OTA is an Internal Revenue Service (IRS) approved 501c3 charitable organization with the mission to enhance online trust and empower users, while promoting innovation and the vitality of the internet. OTA is global organization supported by over 100 organizations headquartered in Bellevue, Washington with offices in Washington DC.
| |
| − | | |
| − | Addressing the mounting concerns, in January 2015 the Online Trust Alliance, established the [https://otalliance.org/initiatives/internet-things IoT Trustworthy Working Group (ITWG)], a multi-stakeholder initiative. The group recognizes “security and privacy by design” must be a priority from the onset of product development and be addressed holistically. The framework focuses on privacy, security sustainability. The sustainability pillar is critical as it looks at the life-cycle issues related to long- term supportability and transfers of ownership of devices and the data collected.
| |
| − | == ==
| |
| − | [https://allseenalliance.org/framework AllSeen Alliance]
| |
| − | | |
| − | The AllSeen Alliance is a Linux Foundation collaborative project. They're a cross-industry consortium dedicated to enabling the interoperability of billions of devices, services and apps that comprise the Internet of Things. The Alliance supports the AllJoyn Framework, an open source software framework that makes it easy for devices and apps to discover and communicate with each other. Developers can write applications for interoperability regardless of transport layer, manufacturer, and without the need for Internet access. The software has been and will continue to be openly available for developers to download, and runs on popular platforms such as Linux and Linux-based Android, iOS, and Windows, including many other lightweight real-time operating systems.
| |
| − | == ==
| |
| − | [http://www.iiconsortium.org/ The Industrial Internet Consortium (IIC)]
| |
| − | | |
| − | The Industrial Internet Consortium is the open membership, international not-for-profit consortium that is setting the architectural framework and direction for the Industrial Internet. Founded by AT&T, Cisco, GE, IBM and Intel in March 2014, the consortium’s mission is to coordinate vast ecosystem initiatives to connect and integrate objects with people, processes and data using common architectures, interoperability and open standards.
| |
| − | == ==
| |
| − | [http://securingsmartcities.org/ Securing Smart Cities]
| |
| − | | |
| − | Securing Smart Cities is a not-for-profit global initiative that aims to solve the existing and future cybersecurity problems of smart cities through collaboration between companies, governments, media outlets, other not-for-profit initiatives and individuals across the world.
| |
| − | = Manufacturers =
| |
| − | | |
| − | == Manufacturer IoT Security Guidance ==
| |
| − | | |
| − | (DRAFT)
| |
| − | | |
| − | [[File:Internet_of_Things_Top_10_2014.png]]
| |
| − | | |
| − | 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.
| |
| − | | |
| − | {| 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. ]
| |
| − | | |
| − | = 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.
| |
| − | | |
| − | {| border="1" class="wikitable" style="text-align:left;"
| |
| − | ! Category
| |
| − | ! IoT Security Consideration
| |
| − | ! Recommendations
| |
| − | |- style="vertical-align:top;"
| |
| − | | '''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
| |
| − | |
| |
| − | When building a web interface consider implementing lessons learned from web application security. Employ a [https://www.owasp.org/index.php/OWASP_Periodic_Table_of_Vulnerabilities#Generic_Application_Frameworks framework] that utilizes security controls to ensure that vulnerabilities are mitigated in code. Be sure to plan for eventual upgrades or security fixes to the framework as well. If you use optional plugins to the framework be sure to review them for security.
| |
| − | | |
| − | Deploy and protect the web interface in the same way you would any web application. Utilize encrypted transport protocols if possible, being sure to validate certificates. Limit access in whatever ways possible. Assume users will not change configuration so deploy in a secure manner with strong credentials already in place.
| |
| − | |- style="vertical-align:top;"
| |
| − | | '''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
| |
| − | |
| |
| − | Refer to the [https://www.owasp.org/index.php/Authentication_Cheat_Sheet OWASP Authentication Cheat Sheet]
| |
| − | |- style="vertical-align:top;"
| |
| − | | '''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
| |
| − | |
| |
| − | Try to utilize tested, proven, networking stacks and interfaces that handle exceptions gracefully. Be sure that any test or maintenance interfaces are disabled or properly protected. Avoid exposing unauthenticated protocols (such as TFTP) or unencrypted channels (such as telnet) if possible. Consider the attack surface that device network services present. Turn off unnecessary services and deploy measures to protect required services, detect malicious activity, and react to an attack with measures such as lock-outs or temporary firewall rules.
| |
| − | |- style="vertical-align:top;"
| |
| − | | '''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
| |
| − | |
| |
| − | Utilize encrypted protocols wherever possible to protect all data in transit. Where protocol encryption is not possible consider encrypting data before transfer.
| |
| − | |- style="vertical-align:top;"
| |
| − | | '''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
| |
| − | |
| |
| − | Data can present unintended privacy concerns when aggregated. As a rule collect the minimal amount of data possible. Consult with data scientists, legal and compliance teams to determine risk of data collection and storage. Consider implications of consent and the fact that IoT devices may not present an interface for collecting consent and may passively collect data about people other than owners and operators. IoT may collect information about individuals who cannot provide consent (such as minors) and data collection should be modified accordingly.
| |
| − | |- style="vertical-align:top;"
| |
| − | | '''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
| |
| − | |
| |
| − | Cloud security presents unique security considerations, as well as countermeasures. Be sure to consult your cloud provider about options for security mechanisms. Consult the OWASP [https://www.owasp.org/index.php/Category:OWASP_Cloud_%E2%80%90_10_Project Cloud Top 10 Security Risks] documents.
| |
| − | |- style="vertical-align:top;"
| |
| − | | '''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
| |
| − | |
| |
| − | Mobile interfaces to IoT ecosystems require targeted security. Consult the [https://www.owasp.org/index.php/OWASP_Mobile_Security_Project OWASP Mobile Project] for further guidance.
| |
| − | |- style="vertical-align:top;"
| |
| − | | '''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
| |
| − | |
| |
| − | Security can be a value proposition. Design should take into consideration a sliding scale of security requirements. Architect projects with secure defaults and allow consumers to select options to be enabled or disabled. IoT design should be forward compatible with respect to security - as cipher suites increase and new security technologies become widely available IoT design should be able to adopt these new technologies.
| |
| − | | |
| − | Remember the security lifecycle of protect, detect, and react. Design systems to allow for the detection of malicious activity as well as self defending capabilities and a reaction plan should a compromise be detected. Design all stages of the lifecycle to be evolutionary so improvements can be added to a system or device future releases, updates, or patches.
| |
| − | |- style="vertical-align:top;"
| |
| − | | '''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
| |
| − | |
| |
| − | Many IoT deployments are either brownfield (i.e. applied over existing infrastructure) and/or have an extremely long deployment cycle. To maintain the security of devices over time it is critical to plan for patches and updates.
| |
| − | | |
| − | Confidentiality, Integrity, and Availability (CIA) are primary concerns when providing binaries and updates to edge devices. Encrypt updates before distribution, providing decryption keys along with download instructions to authorized devices. Updates should have cryptographic signatures using public key cryptography that can be verified by devices. A cryptographic signature allows for distribution of updates over untrusted channels, such as Content Delivery Network (CDN), peer-to-peer, or machine to machine (M2M).
| |
| − | | |
| − | Devices should always validate cryptographic certificates and discard updates that are not properly delivered or signed. If unencrypted updates are utilized be sure that a cryptographic hash of the update is provided over an encrypted channel so the device can detect tampering.
| |
| − | | |
| − | Provide a mechanism for issuing, updating and revoking cryptographic keys as well. Key management and lifecycle should be taken into consideration prior to deployment. This includes the SSL trust store, or root trust, on a device, which may have to be modified over the lifespan of the device.
| |
| − | |- style="vertical-align:top;"
| |
| − | | '''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
| |
| − | |
| |
| − | Plan on having IoT edge devices fall into malicious hands. Utilize whatever physical security protections are available. Disable any testing or debugging interfaces, utilize Hardware Security Modules (HSM's), cryptographic co-processors, and Trusted Platform Modules (TPM's) wherever possible.
| |
| − | | |
| − | Consider the implications of a compromised device. Do not share credentials, application or cryptographic keys across multiple devices to limit the scope of damage due to a physical compromise.
| |
| − | | |
| − | Plan for the transfer of ownership of devices and ensure that data is not transferable along with the ownership.
| |
| − | |}
| |
| − | | |
| − | ===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
| |
| − | * Recognize the value in autonomous IoT systems to perform security operations that are onerous or impossible to a user. Consider cryptographic authentication mechanisms, public key cryptography, and transitive trust schemes.
| |
| − | | |
| − | [ 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.
| |
| − | | |
| − | {| border="1" class="wikitable" style="text-align: left"
| |
| − | ! Category
| |
| − | ! IoT Security Consideration
| |
| − | |-
| |
| − | | '''I1: Insecure Web Interface'''
| |
| − | |
| |
| − | * Assess any web interface to determine if weak passwords are allowed
| |
| − | * Assess the account lockout mechanism
| |
| − | * Assess the web interface for XSS, SQLi and CSRF vulnerabilities and other web application vulnerabilities
| |
| − | * Assess the use of HTTPS to protect transmitted information
| |
| − | * Assess the ability to change the username and password
| |
| − | * Determine if web application firewalls are used to protect web interfaces
| |
| − | |-
| |
| − | | '''I2: Insufficient Authentication/Authorization'''
| |
| − | |
| |
| − | * Assess the solution for the use of strong passwords where authentication is needed
| |
| − | * Assess the solution for multi-user environments and ensure it includes functionality for role separation
| |
| − | * Assess the solution for Implementation two-factor authentication where possible
| |
| − | * Assess password recovery mechanisms
| |
| − | * Assess the solution for the option to require strong passwords
| |
| − | * Assess the solution for the option to force password expiration after a specific period
| |
| − | * Assess the solution for the option to change the default username and password
| |
| − | |-
| |
| − | | '''I3: Insecure Network Services'''
| |
| − | |
| |
| − | * Assess the solution to ensure network services don't respond poorly to buffer overflow, fuzzing or denial of service attacks
| |
| − | * Assess the solution to ensure test ports are are not present
| |
| − | |-
| |
| − | | '''I4: Lack of Transport Encryption'''
| |
| − | |
| |
| − | * Assess the solution to determine the use of encrypted communication between devices and between devices and the internet
| |
| − | * Assess the solution to determine if accepted encryption practices are used and if proprietary protocols are avoided
| |
| − | * Assess the solution to determine if a firewall option available is available
| |
| − | |-
| |
| − | | '''I5: Privacy Concerns'''
| |
| − | |
| |
| − | * Assess the solution to determine the amount of personal information collected
| |
| − | * Assess the solution to determine if collected personal data is properly protected using encryption at rest and in transit
| |
| − | * Assess the solution to determine if Ensuring data is de-identified or anonymized
| |
| − | * Assess the solution to ensure end-users are given a choice for data collected beyond what is needed for proper operation of the device
| |
| − | |-
| |
| − | | '''I6: Insecure Cloud Interface'''
| |
| − | |
| |
| − | * Assess the cloud interfaces for security vulnerabilities (e.g. API interfaces and cloud-based web interfaces)
| |
| − | * Assess the cloud-based web interface to ensure it disallows weak passwords
| |
| − | * Assess the cloud-based web interface to ensure it includes an account lockout mechanism
| |
| − | * Assess the cloud-based web interface to determine if two-factor authentication is used
| |
| − | * Assess any cloud interfaces for XSS, SQLi and CSRF vulnerabilities and other vulnerabilities
| |
| − | * Assess all cloud interfaces to ensure transport encryption is used
| |
| − | * Assess the cloud interfaces to determine if the option to require strong passwords is available
| |
| − | * Assess the cloud interfaces to determine if the option to force password expiration after a specific period is available
| |
| − | * Assess the cloud interfaces to determine if the option to change the default username and password is available
| |
| − | |-
| |
| − | | '''I7: Insecure Mobile Interface'''
| |
| − | |
| |
| − | * Assess the mobile interface to ensure it disallows weak passwords
| |
| − | * Assess the mobile interface to ensure it includes an account lockout mechanism
| |
| − | * Assess the mobile interface to determine if it Implements two-factor authentication (e.g Apple's Touch ID)
| |
| − | * Assess the mobile interface to determine if it uses transport encryption
| |
| − | * Assess the mobile interface to determine if the option to require strong passwords is available
| |
| − | * Assess the mobile interface to determine if the option to force password expiration after a specific period is available
| |
| − | * Assess the mobile interface to determine if the option to change the default username and password is available
| |
| − | * Assess the mobile interface to determine the amount of personal information collected
| |
| − | |-
| |
| − | | '''I8: Insufficient Security Configurability'''
| |
| − | |
| |
| − | * Assess the solution to determine if password security options (e.g. Enabling 20 character passwords or enabling two-factor authentication) are available
| |
| − | * Assess the solution to determine if encryption options (e.g. Enabling AES-256 where AES-128 is the default setting) are available
| |
| − | * Assess the solution to determine if logging for security events is available
| |
| − | * Assess the solution to determine if alerts and notifications to the user for security events are available
| |
| − | |-
| |
| − | | '''I9: Insecure Software/Firmware'''
| |
| − | |
| |
| − | * Assess the device to ensure it includes update capability and can be updated quickly when vulnerabilities are discovered
| |
| − | * Assess the device to ensure it uses encrypted update files and that the files are transmitted using encryption
| |
| − | * Assess the device to ensure is uses signed files and then validates that file before installation
| |
| − | | |
| − | |-
| |
| − | | '''I10: Poor Physical Security'''
| |
| − | |
| |
| − | * Assess the device to ensure it utilizes a minimal number of physical external ports (e.g. USB ports) on the device
| |
| − | * Assess the device to determine if it can be accessed via unintended methods such as through an unnecessary USB port
| |
| − | * Assess the device to determine if it allows for disabling of unused physical ports such as USB
| |
| − | * Assess the device to determine if it includes the ability 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
| |
| − | | |
| − | = 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.
| |
| − | | |
| − | {| 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. ]
| |
| − | | |
| − | = Project Details =
| |
| − | | |
| − | <div style="width:100%;height:160px;border:0,margin:0;overflow: hidden;">[[File:OWASP_Project_Header.jpg|link=]]</div>
| |
| − | | |
| − | | |
| − | {{:Projects/OWASP_Internet_of_Things_Top_Ten_Project}}
| |
| − | | |
| − | | |
| − | __NOTOC__ <headertabs />
| |
| − | | |
| − | [[Category:OWASP_Project]] [[Category:OWASP_Document]] [[Category:OWASP_Download]] [[Category:OWASP_Release_Quality_Document]]
| |
