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"
Aaron.guzman (talk | contribs) (Tag: Visual edit) |
Aaron.guzman (talk | contribs) (→Classifications) (Tag: Visual edit) |
||
| Line 111: | Line 111: | ||
<div style="width:100%;height:160px;border:0,margin:0;overflow: hidden;">[[File:OWASP_Project_Header.jpg|link=]]</div> | <div style="width:100%;height:160px;border:0,margin:0;overflow: hidden;">[[File:OWASP_Project_Header.jpg|link=]]</div> | ||
| − | == Top 10 | + | == Internet of Things (IoT) Top 10 2018 == |
The OWASP IoT Project is currently reviewing the Top Ten list for 2018. The official launch date is December 2018. Provide your insight and expertise by joining the #iot-security channel meetups on Slack. | The OWASP IoT Project is currently reviewing the Top Ten list for 2018. The official launch date is December 2018. Provide your insight and expertise by joining the #iot-security channel meetups on Slack. | ||
| + | * I1 Weak Guessable, or Hardcoded Passwords | ||
| + | Use of easily bruteforced, publicly available, or unchangeable credentials, including backdoors in firmware or client software that grants unauthorized access to deployed systems. | ||
| + | * I2 Insecure Network Services | ||
| + | Unneeded or insecure network services running on the device itself, especially those exposed to the internet, that compromise the confidentiality, integrity/authenticity, or availability of information or allow unauthorized remote control. | ||
| + | * I3 Insecure Ecosystem Interfaces | ||
| + | Insecure web, backend API, cloud, or mobile interfaces in the ecosystem outside of the device that allows compromise of the device or its related components. Common issues include a lack of authentication/authorization, lacking or weak encryption, and a lack of input and output filtering. | ||
| + | * I4 Lack of Secure Update Mechanism | ||
| + | Lack of ability to securely update the device or ecosystem. This includes lack of firmware validation on device, lack of secure delivery (un-encrypted in transit), lack of anti-rollback mechanisms, lack of notifications of security changes due to updates. | ||
| + | * I5 Use of Insecure or Outdated Components | ||
| + | Use of deprecated and insecure software components/libraries that could allow the device to be compromised. Including insecure customization of operating systems, and the use of third-party software or hardware components from a compromised supply chain. | ||
| + | * I6 Insufficient Privacy Protection | ||
| + | User's personal information stored on the device or in the ecosystem that is used insecurely, improperly, or without permission. | ||
| + | * I7 Insecure Data Transfer and Storage | ||
| + | Lack of encryption or access control of sensitive data anywhere within the ecosystem, including at rest, in transit, or during processing. | ||
| + | * I8 Lack of Device Management | ||
| + | Lack of security support on existing devices deployed in production, including asset management, update management, and secure decommissioning. | ||
| + | * I9 Insecure Default Settings | ||
| + | Devices or systems that are shipped with insecure default settings or lack the capability to make the system more secure. | ||
| + | * I10 Lack of Physical Hardening | ||
| + | Lack of physical hardening measures, allowing potential attackers to gain sensitive information that can help in a future remote attack or take local control of the device. | ||
| − | == Top 10 | + | == Internet of Things (IoT) Top 10 2014 == |
* [[Top 10 2014-I1 Insecure Web Interface|I1 Insecure Web Interface]] | * [[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-I2 Insufficient Authentication/Authorization|I2 Insufficient Authentication/Authorization]] | ||
Revision as of 18:53, 19 December 2018
- Main
- IoT Top 10
- IoT Attack Surface Areas
- IoT Vulnerabilities
- Medical Devices
- Firmware Analysis
- IoT Event Logging Project
- ICS/SCADA
- Community
- Project About
Get Involved!The OWASP IoT Project is currently reviewing the Top Ten list for 2018. Provide your insight and expertise by joining the #iot-security channel meetups on Slack. 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 |
CollaborationHint: If you're new to Slack, join OWASP's slack channel first, then join #iot-security within OWASP's channel. Quick DownloadOWASP IoT 2018 Planning Session IoT Attack Surface Mapping DEFCON 23 News and Events
Classifications
| |||||||
Internet of Things (IoT) Top 10 2018
The OWASP IoT Project is currently reviewing the Top Ten list for 2018. The official launch date is December 2018. Provide your insight and expertise by joining the #iot-security channel meetups on Slack.
- I1 Weak Guessable, or Hardcoded Passwords
Use of easily bruteforced, publicly available, or unchangeable credentials, including backdoors in firmware or client software that grants unauthorized access to deployed systems.
- I2 Insecure Network Services
Unneeded or insecure network services running on the device itself, especially those exposed to the internet, that compromise the confidentiality, integrity/authenticity, or availability of information or allow unauthorized remote control.
- I3 Insecure Ecosystem Interfaces
Insecure web, backend API, cloud, or mobile interfaces in the ecosystem outside of the device that allows compromise of the device or its related components. Common issues include a lack of authentication/authorization, lacking or weak encryption, and a lack of input and output filtering.
- I4 Lack of Secure Update Mechanism
Lack of ability to securely update the device or ecosystem. This includes lack of firmware validation on device, lack of secure delivery (un-encrypted in transit), lack of anti-rollback mechanisms, lack of notifications of security changes due to updates.
- I5 Use of Insecure or Outdated Components
Use of deprecated and insecure software components/libraries that could allow the device to be compromised. Including insecure customization of operating systems, and the use of third-party software or hardware components from a compromised supply chain.
- I6 Insufficient Privacy Protection
User's personal information stored on the device or in the ecosystem that is used insecurely, improperly, or without permission.
- I7 Insecure Data Transfer and Storage
Lack of encryption or access control of sensitive data anywhere within the ecosystem, including at rest, in transit, or during processing.
- I8 Lack of Device Management
Lack of security support on existing devices deployed in production, including asset management, update management, and secure decommissioning.
- I9 Insecure Default Settings
Devices or systems that are shipped with insecure default settings or lack the capability to make the system more secure.
- I10 Lack of Physical Hardening
Lack of physical hardening measures, allowing potential attackers to gain sensitive information that can help in a future remote attack or take local control of the device.
Internet of Things (IoT) Top 10 2014
- 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
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
|
Medical Device TestingThe Medical Device Testing project is intended to provide some basic attack surface considerations that should be evaluated before shipping Medical Device equipment.
|
What is the Medical Attack Surfaces project?The Medical Attack Surfaces project provides:
Project Leaders
Related ProjectsCollaborationResources
News 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
|
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
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? | |||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
| |||||||||||||||||||||||||||||||||||||
