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"
(Added links to some of the news and events) |
|||
| Line 132: | Line 132: | ||
| '''Device Memory''' | | '''Device Memory''' | ||
| | | | ||
| − | * Cleartext usernames | + | * Sensitive data |
| − | * Cleartext passwords | + | ** Cleartext usernames |
| − | * Third-party credentials | + | ** Cleartext passwords |
| − | * Encryption keys | + | ** Third-party credentials |
| + | ** Encryption keys | ||
|- | |- | ||
| '''Device Physical Interfaces''' | | '''Device Physical Interfaces''' | ||
| Line 151: | Line 152: | ||
| '''Device Web Interface''' | | '''Device Web Interface''' | ||
| | | | ||
| − | * SQL injection | + | * Standard set of web vulnerabilities: |
| − | * Cross-site scripting | + | ** SQL injection |
| − | * Cross-site Request Forgery | + | ** Cross-site scripting |
| − | * Username enumeration | + | ** Cross-site Request Forgery |
| − | * Weak passwords | + | ** Username enumeration |
| − | * Account lockout | + | * Credential management vulnerabilities: |
| − | * Known default credentials | + | ** Username enumeration |
| + | ** Weak passwords | ||
| + | ** Account lockout | ||
| + | ** Known default credentials | ||
| + | ** Insecure password recovery mechanism | ||
|- | |- | ||
| '''Device Firmware''' | | '''Device Firmware''' | ||
| | | | ||
| − | * | + | * Sensitive data exposure: |
| − | * | + | ** Backdoor accounts |
| − | * | + | ** Hardcoded credentials |
| − | * Encryption keys | + | ** Encryption keys |
| − | * Encryption (Symmetric, Asymmetric) | + | ** Encryption (Symmetric, Asymmetric) |
| + | ** Sensitive information | ||
| + | ** Sensitive URL disclosure | ||
* Firmware version display and/or last update date | * Firmware version display and/or last update date | ||
| − | |||
* Vulnerable services (web, ssh, tftp, etc.) | * Vulnerable services (web, ssh, tftp, etc.) | ||
* Security related function API exposure | * Security related function API exposure | ||
| Line 190: | Line 196: | ||
* Lack of payload verification | * Lack of payload verification | ||
* Lack of message integrity check | * Lack of message integrity check | ||
| + | * Credential management vulnerabilities: | ||
| + | ** Username enumeration | ||
| + | ** Weak passwords | ||
| + | ** Account lockout | ||
| + | ** Known default credentials | ||
| + | ** Insecure password recovery mechanism | ||
|- | |- | ||
| '''Administrative Interface''' | | '''Administrative Interface''' | ||
| | | | ||
| − | * SQL injection | + | * Standard web vulnerabilities: |
| − | * Cross-site scripting | + | ** SQL injection |
| − | * Cross-site Request Forgery | + | ** Cross-site scripting |
| − | * Username enumeration | + | ** Cross-site Request Forgery |
| − | * Weak passwords | + | ** Username enumeration |
| − | * Account lockout | + | * Credential management vulnerabilities: |
| − | * Known default credentials | + | ** Username enumeration |
| + | ** Weak passwords | ||
| + | ** Account lockout | ||
| + | ** Known default credentials | ||
| + | ** Insecure password recovery mechanism | ||
* Security/encryption options | * Security/encryption options | ||
* Logging options | * Logging options | ||
| Line 214: | Line 230: | ||
| '''Cloud Web Interface''' | | '''Cloud Web Interface''' | ||
| | | | ||
| − | * SQL injection | + | |
| − | * Cross-site scripting | + | * Standard set of web vulnerabilities: |
| − | * Cross-site Request Forgery | + | ** SQL injection |
| − | * Username enumeration | + | ** Cross-site scripting |
| − | * Weak passwords | + | ** Cross-site Request Forgery |
| − | * Account lockout | + | * Credential management vulnerabilities: |
| − | * Known default credentials | + | ** Username enumeration |
| + | ** Weak passwords | ||
| + | ** Account lockout | ||
| + | ** Known default credentials | ||
| + | ** Insecure password recovery mechanism | ||
* Transport encryption | * Transport encryption | ||
| − | |||
* Two-factor authentication | * Two-factor authentication | ||
|- | |- | ||
| Line 277: | Line 296: | ||
* Short range | * Short range | ||
* Non-standard | * Non-standard | ||
| − | * Wireless (WiFi, Z-wave, Zigbee, Bluetooth) | + | * Wireless (WiFi, Z-wave, XBee, Zigbee, Bluetooth, LoRA) |
* Protocol fuzzing | * Protocol fuzzing | ||
|- | |- | ||
Revision as of 20:57, 18 January 2017
- Main
- IoT Attack Surface Areas
- IoT Vulnerabilities
- Firmware Analysis
- IoT Event Logging Project
- ICS/SCADA
- IoT Security Policy Project
- Community
- Project About
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 information on:
Project Leaders
Contributors
Related Projects |
CollaborationQuick DownloadIoT Attack Surface Mapping DEFCON 23 News and Events
Classifications
| |||||||
IoT Attack Surface Areas ProjectThe OWASP IoT Attack Surface Areas (DRAFT) are as follows:
|
What is the IoT Attack Surface Areas Project?The IoT Attack Surface Areas Project provides a list of attack surfaces that should be understood by manufacturers, developers, security researchers, and those looking to deploy or implement IoT technologies within their organizations. Project Leaders
Related ProjectsCollaborationQuick Download
News and Events
|
IoT Vulnerabilities Project
|
What is the IoT Vulnerabilities Project?The IoT Vulnerabilities Project provides:
Project Leaders
Related ProjectsCollaborationResourcesNews and Events
|
Firmware Analysis ProjectThe Firmware Analysis Project is intended to provide security testing guidance for the IoT Attack Surface "Device Firmware":
|
What is the Firmware Analysis Project?The Firmware Analysis Project provides:
Project Leaders
Related ProjectsCollaborationResources
News and Events
|
IoT Logging EventsThis is a working draft of the recommended minimum IoT Device logging events. This includes many different types of devices, including consumer IoT, enterprise IoT, and ICS/SCADA type devices.
|
What is the IoT Security Logging Project?The IoT Secure Logging Project provides a list of core events that should be logged in any IoT-related system. The project exists because IoT systems in general are not logging nearly enough events to constitute input for a solid detection and response program around IoT devices, and for companies that want to do this there are not many good resources for what should be logged. Project Leaders
Related ProjectsCollaborationQuick Download
News and Events
|
ICS/SCADA ProjectThe OWASP ICS/SCADA Top 10 software weaknesses are as follows:
|
What is the ICS/SCADA Project?The ICS/SCADA Project provides:
Project Leaders
Related ProjectsCollaborationQuick Download
News and Events
|
IoT Security Policy ProjectThe OWASP IoT Security Policy Project provides:
|
What is the IoT Security Policies Project?The IoT Security Policy Project provides: Project Leaders
Related ProjectsCollaborationQuick Download
News and Events
|
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 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
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 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.
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.
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.
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.
Talks
RSA Conference San Francisco
Securing the Internet of Things: Mapping IoT Attack Surface Areas with the OWASP IoT Top 10 Project
Daniel Miessler, Practice Principal
April 21, 2015
---
Defcon 23
IoT Attack Surface Mapping
Daniel Miessler
August 6-9, 2015
Podcasts
IoT Conferences
Conference Call for Papers
| PROJECT INFO What does this OWASP project offer you? |
RELEASE(S) INFO What releases are available for this project? | |||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
| |||||||||||||||||||||||||||||||||||||
