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"
Craig Smith (talk | contribs) |
Craig Smith (talk | contribs) |
||
Line 814: | Line 814: | ||
* Curate informational resources | * Curate informational resources | ||
* Present research | * Present research | ||
+ | == == | ||
+ | [https://otalliance.org Online Trust Alliance] | ||
+ | |||
+ | Informal industry working group supported by over 100 organizations. | ||
+ | |||
+ | Their goals include: | ||
+ | * Lead - Leadership and a commitment to stewardship are keys to consumer trust and differentiation. | ||
+ | * Innovate - Innovation and the long-term vitality of the internet and online services are essential for society and our economy. | ||
+ | * Collaboration - OTA and our members facilitate multi-stakeholder efforts across the ecosystem, developing best practices promoting innovation, brand protection and enhancing confidence of online services. | ||
= IoT Conferences = | = IoT Conferences = |
Revision as of 20:54, 3 September 2015
- Main
- IoT Attack Surface Areas
- Top IoT Vulnerabilities
- Top 10 IoT Vulnerabilities (2014)
- IoT Testing Guides
- IoT Security Guidance
- Talks
- Curated IoT Reading
- Community
- IoT Conferences
OWASP Internet of Things (IoT) ProjectOxford 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. LicensingThe 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.
|
What is the OWASP Internet of Things Project?The OWASP Internet of Things Project provides:
Project Leaders
Related Projects |
Email ListQuick DownloadIoT Attack Surface Mapping DEFCON 23 News and Events
Classifications
|
The OWASP IoT Attack Surface Areas (DRAFT) are as follows:
Attack Surface | Vulnerability |
---|---|
Ecosystem Access Control |
|
Device Memory |
|
Device Physical Interfaces |
|
Device Web Interface |
|
Device Firmware |
|
Device Network Services |
|
Administrative Interface |
|
Local Data Storage |
|
Cloud Web Interface |
|
Third-party Backend APIs |
|
Update Mechanism |
|
Mobile Application |
|
Vendor Backend APIs |
|
Ecosystem Communication |
|
Network Traffic |
|
The top IoT vulnerabilities (DRAFT) are as follow:
Vulnerability | Attack Surface | Summary |
---|---|---|
Username Enumeration |
|
|
Weak Passwords |
|
|
Account Lockout |
|
|
Unencrypted Services |
|
|
Two-factor Authentication |
|
|
Poorly Implemented Encryption |
|
|
Update Sent Without Encryption |
|
|
Update Location Writable |
|
|
Denial of Service |
|
|
Removal of Storage Media |
|
|
No Manual Update Mechanism |
|
|
Missing Update Mechanism |
|
|
Firmware Version Display and/or Last Update Date |
|
|
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
- I1 Insecure Web Interface
- I2 Insufficient Authentication/Authorization
- I3 Insecure Network Services
- I4 Lack of Transport Encryption
- I5 Privacy Concerns
- I6 Insecure Cloud Interface
- I7 Insecure Mobile Interface
- I8 Insufficient Security Configurability
- I9 Insecure Software/Firmware
- I10 Poor Physical Security
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.
Category | IoT Security Consideration |
---|---|
I1: Insecure Web Interface |
|
I2: Insufficient Authentication/Authorization |
|
I3: Insecure Network Services |
|
I4: Lack of Transport Encryption |
|
I5: Privacy Concerns |
|
I6: Insecure Cloud Interface |
|
I7: Insecure Mobile Interface |
|
I8: Insufficient Security Configurability |
|
I9: Insecure Software/Firmware |
|
I10: Poor Physical Security |
|
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
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.
Category | IoT Security Consideration |
---|---|
I1: Insecure Web Interface |
|
I2: Insufficient Authentication/Authorization |
|
I3: Insecure Network Services |
|
I4: Lack of Transport Encryption |
|
I5: Privacy Concerns |
|
I6: Insecure Cloud Interface |
|
I7: Insecure Mobile Interface |
|
I8: Insufficient Security Configurability |
|
I9: Insecure Software/Firmware |
|
I10: Poor Physical Security |
|
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.
Category | IoT Security Consideration |
---|---|
I1: Insecure Web Interface |
|
I2: Insufficient Authentication/Authorization |
|
I3: Insecure Network Services |
|
I4: Lack of Transport Encryption |
|
I5: Privacy Concerns |
|
I6: Insecure Cloud Interface |
|
I7: Insecure Mobile Interface |
|
I8: Insufficient Security Configurability |
|
I9: Insecure Software/Firmware |
|
I10: Poor Physical Security |
|
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.
Category | IoT Security Consideration |
---|---|
I1: Insecure Web Interface |
|
I2: Insufficient Authentication/Authorization |
|
I3: Insecure Network Services |
|
I4: Lack of Transport Encryption |
|
I5: Privacy Concerns |
|
I6: Insecure Cloud Interface |
|
I7: Insecure Mobile Interface |
|
I8: Insufficient Security Configurability |
|
I9: Insecure Software/Firmware |
|
I10: Poor Physical Security |
|
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. ]
RSA Conference San Francisco
Securing the Internet of Things: Mapping IoT Attack Surface Areas with the OWASP IoT Top 10 Project
Daniel Miessler, Practice Principal
April 21, 2015
---
Defcon 23
IoT Attack Surface Mapping
Daniel Miessler
August 6-9, 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
A service that lets you create powerful connections with one simple statement.
Channels are the basic building blocks of IFTTT. Channels include:
- Triggers - The this part of a Recipe
- Actions - The that part of a Recipe
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
Informal industry working group supported by over 100 organizations.
Their goals include:
- Lead - Leadership and a commitment to stewardship are keys to consumer trust and differentiation.
- Innovate - Innovation and the long-term vitality of the internet and online services are essential for society and our economy.
- Collaboration - OTA and our members facilitate multi-stakeholder efforts across the ecosystem, developing best practices promoting innovation, brand protection and enhancing confidence of online services.