Difference between revisions of "OWASP Internet of Things Project"

Latest revision as of 07:02, 1 November 2019

Main
IoT Top 10
OWASP IoT Top 10 2018 Mapping Project
IoTGoat
ByteSweep
Firmware Security Testing Methodology
IoT Attack Surface Areas
IoT Vulnerabilities
Medical Devices
Firmware Analysis
IoT Event Logging Project
Project About

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 separated into the following categories - Seek & Understand, Validate & Test, and Governance.

Updated!

The OWASP IoT Project for 2018 has been released!

Philosophy

The OWASP Internet of Things Project was started in 2014 as a way help Developers, Manufacturers, Enterprises, and Consumers to make better decisions regarding the creation and use of IoT systems.

This continues today with the 2018 release of the OWASP IoT Top 10, which represents the top ten things to avoid when building, deploying, or managing IoT systems. The primary theme for the 2018 OWASP Internet of Things Top 10 is simplicity. Rather than having separate lists for risks vs. threats vs. vulnerabilities—or for developers vs. enterprises vs. consumers—the project team elected to have a single, unified list that captures the top things to avoid when dealing with IoT Security.

The team recognized that there are now dozens of organizations releasing elaborate guidance on IoT Security—all of which are designed for slightly different audiences and industry verticals. We thought the most useful resource we could create is a single list that addresses the highest priority issues for manufacturers, enterprises, and consumers at the same time.

The result is the 2018 OWASP IoT Top 10.

Methodology

The project team is a collection of volunteer professionals from within the security industry, with experience spanning multiple areas of expertise, including: manufacturers, consulting, security testers, developers, and many more.

The project was conducted in the following phases:

Team Formation: finding people who would be willing to contribute to the 2018 update, both as SMEs and as project leaders to perform various tasks within the duration of the project.
Project Review: analysis of the 2014 project to determine what’s changed in the industry since that release, and how the list should be updated given those changes.
Data Collection: collection and review of multiple vulnerability sources (both public and private), with special emphasis on which issues caused the most actual impact and damage.
Sister Project Review: a review of dozens of other IoT Security projects to ensure that we’d not missed something major and that we were comfortable with both the content and prioritization of our release. Examples included: CSA IoT Controls Matrix, CTIA, Stanford’s Secure Internet of Things Project, NISTIR 8200, ENISA IoT Baseline Report, Code of Practice for Consumer IoT Security, and others.
Community Draft Feedback: release of the draft to the community for review, including multiple Twitter calls for comments, the use of a public feedback form, and a number of public talks where feedback was gathered. The feedback was then reviewed by the team along with initial Data Collection, as well as Sister Project Review, to create the list contents and prioritization.
Release: release of the project to the public in December 2018.

The Future of the OWASP IoT Top 10

The team has a number of activities planned to continue improving on the project going forward.

Some of the items being discussed include:

Continuing to improve the list on a two-year cadence, incorporating feedback from the community and from additional project contributors to ensure we are staying current with issues facing the industry.
Mapping the list items to other OWASP projects, such as the ASVS, and perhaps to other projects outside OWASP as well.
Expanding the project into other aspects of IoT—including embedded security, ICS/ SCADA,etc.
Adding use and abuse cases, with multiple examples, to solidify each concept discussed.
Considering the addition of reference architectures, so we can not only tell people what to avoid, but how to do what they need to do securely.

Participation in the OWASP IoT Project is open to the community. We take input from all participants — whether you’re a developer, a manufacturer, a penetration tester, or someone just trying to implement IoT securely. You can find the team meeting every other Friday in the the #iot-security room of the OWASP Slack Channel.

The OWASP IoT Security Team, 2018

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:

What is the OWASP Internet of Things Project?

The OWASP Internet of Things Project provides information on:

IoT Attack Surface Areas
IoT Vulnerabilities
Firmware Analysis
ICS/SCADA Software Weaknesses
Community Information
IoT Testing Guides
IoT Security Guidance
Principles of IoT Security
IoT Framework Assessment
Developer, Consumer and Manufacturer Guidance
Design Principles
IoTGoat

Project Leaders

Daniel Miessler
Craig Smith
Vishruta Rudresh
Aaron Guzman

Contributors

Justin Klein Keane
Saša Zdjelar

IoT Top 2018 Contributors

Vijayamurugan Pushpanathan
Alexander Lafrenz
Masahiro Murashima
Charlie Worrell
José A. Rivas (jarv)
Pablo Endres
Ade Yoseman
Cédric Levy-Bencheotn
Jason Andress
Amélie Didion - Designer

Related Projects

Collaboration

The OWASP Slack Channel

Hint: If you're new to Slack, join OWASP's slack channel first, then join #iot-security within OWASP's channel.

Quick Download

OWASP IoT Top Ten 2018

IoT Attack Surface Mapping DEFCON 23

IoT Testing Guidance Handout

OWASP IoT Top Ten 2014 PDF

OWASP IoT Project Overview

News and Events

OWASP IoTGoat Project underway
New firmware security analysis tool, ByteSweep
IoT ASVS and Testing Guide set to kick off in 2019
Added a Slack channel
Added a sub-project; IoT Security Policy Project

Classifications

Internet of Things (IoT) Top 10 2018

The OWASP IoT Top 10 - 2018 is now available.

I1 Weak Guessable, or Hardcoded Passwords

I2 Insecure Network Services

I3 Insecure Ecosystem Interfaces

I4 Lack of Secure Update Mechanism

I5 Use of Insecure or Outdated Components

I6 Insufficient Privacy Protection

I7 Insecure Data Transfer and Storage

I8 Lack of Device Management

I9 Insecure Default Settings

I10 Lack of Physical Hardening

Internet of Things (IoT) Top 10 2014

IoT Top 10 2018 Mapping Project

The OWASP IoT Mapping Project is intended to provide a mapping of the OWASP IoT Top 10 2018 to industry publications and sister projects. The goal is to provide resources that enable practical uses for the OWASP IoT Top 10 . As with all Top 10 lists, they should be used as a first step and expanded upon according to the applicable IoT ecosystem.

Mappings are structured with control categories, tests, or recommendations in the left column, descriptions in the middle column, and their mapping to the OWASP IoT Top 10 2018 list in the right column. Each mapping may not have a 1 to 1 relation; however, similar recommendations and/or controls are listed. For mappings that are not applicable to the IoT Top 10 2018 list, an "N/A" is provided as the mapping.

An example mapping of the IoT Top 10 2014 is provided below.

For additional mappings, please visit the following link: https://scriptingxss.gitbook.io/owasp-iot-top-10-mapping-project/

Share this:

What is the IoT Top 10 Mapping Project?

The OWASP IoT Mapping Project is intended to provide a mapping of the OWASP IoT Top 10 2018 to industry publications and sister projects. The goal is to provide resources that enable practical uses for the OWASP IoT Top 10 . As with all Top 10 lists, they should be used as a first step and expanded upon according to the applicable IoT ecosystem.

Mappings include the following:

and more...

GitBook

Mappings are hosted on GitBook using the following link https://scriptingxss.gitbook.io/owasp-iot-top-10-mapping-project/

Project Leaders

Aaron Guzman

Collaboration

The Slack Channel

IoTGoat Project

IoT Goat is a deliberately insecure firmware based on OpenWrt. The project’s goal is to teach users about the most common vulnerabilities typically found in IoT devices. The vulnerabilities will be based on the top 10 vulnerabilities as documented by OWASP: https://www.owasp.org/index.php/OWASP_Internet_of_Things_Project. IoTGoat is expected to be released by December 2019.

To get more information on getting started or how to contribute, visit the project's Github: https://github.com/scriptingxss/IoTGoat

Share this:

What is the IoTGoat Project?

The IoTGoat Project is a deliberately insecure firmware based on OpenWrt. The project’s goal is to teach users about the most common vulnerabilities typically found in IoT devices. The vulnerabilities will be based on the IoT Top 10.

GitHub

https://github.com/scriptingxss/IoTGoat

Project Leaders

Aaron Guzman
Fotios Chantzis
Paulino Calderon

Related Projects

WebGoat
Serverless Goat
NodeGoat
RailsGoat

Collaboration

The Slack Channel

IoTGoat Google Group

Quick Download

News and Events

Coming Soon

OWASP Project Header.jpg

ByteSweep Project

ByteSweep is a Free Software IoT security analysis platform. This platform will allow IoT device makers, large and small, to conduct fully automated security checks before they ship firmware. A Free Software IoT Firmware Security Analysis Platform

ByteSweep Features:

Firmware extraction
File data enrichment
Key and password hash identification
Unsafe function use detection
3rd party component identification
CVE correlation

Share this:

What is the ByteSweep Project?

A Free Software IoT Firmware Security Analysis Platform.

GitLab

https://gitlab.com/bytesweep/bytesweep

Project Leaders

Matt Brown

Collaboration

The Slack Channel

Quick Download

https://gitlab.com/bytesweep/bytesweep/blob/master/INSTALL.md

OWASP Project Header.jpg

Firmware Security Testing Methodology

The Firmware Security Testing Methodology (FSTM) is composed of nine stages tailored to enable security researchers, software developers, consultants, hobbyists, and Information Security professionals with conducting firmware security assessments.

Stage	Description
1. Information gathering and reconnaissance	Acquire all relative technical and documentation details pertaining to the target device’s firmware
2. Obtaining firmware	Attain firmware using one or more of the proposed methods listed
3. Analyzing firmware	Examine the target firmware’s characteristics
4. Extracting the filesystem	Carve filesystem contents from the target firmware
5. Analyzing filesystem contents	Statically analyze extracted filesystem configuration files and binaries for vulnerabilities
6. Emulating firmware	Emulate firmware files and components
7. Dynamic analysis	Perform dynamic security testing against firmware and application interfaces
8. Runtime analysis	Analyze compiled binaries during device runtime
9. Binary Exploitation	Exploit identified vulnerabilities discovered in previous stages to attain root and/or code execution

The full methodology release can be downloaded via the following https://github.com/scriptingxss/owasp-fstm/releases/download/v1.0/Firmware_Security_Testing_Methodology_Version1.pdf.

Share this:

What is the Firmware Security Testing Methodology

The Firmware Security Testing Methodology Project provides:

Attack walkthroughs
Tool usage examples
Screenshots
Companion virtual machine preloaded with tools (EmbedOS) - https://github.com/scriptingxss/EmbedOS

Project Leaders

Aaron Guzman

Quick Download

https://github.com/scriptingxss/owasp-fstm/releases

IoT Attack Surface Areas Project

The OWASP IoT Attack Surface Areas (DRAFT) are as follows:

Attack Surface	Vulnerability
Ecosystem (general)	Interoperability standards Data governance System wide failure Individual stakeholder risks Implicit trust between components Enrollment security Decommissioning system Lost access procedures
Device Memory	Sensitive data Cleartext usernames Cleartext passwords Third-party credentials Encryption keys
Device Physical Interfaces	Firmware extraction User CLI Admin CLI Privilege escalation Reset to insecure state Removal of storage media Tamper resistance Debug port UART (Serial) JTAG / SWD Device ID/Serial number exposure
Device Web Interface	Standard set of web application vulnerabilities, see: OWASP Web Top 10 OWASP ASVS OWASP Testing guide Credential management vulnerabilities: Username enumeration Weak passwords Account lockout Known default credentials Insecure password recovery mechanism
Device Firmware	Sensitive data exposure (See OWASP Top 10 - A6 Sensitive data exposure): Backdoor accounts Hardcoded credentials Encryption keys Encryption (Symmetric, Asymmetric) Sensitive information Sensitive URL disclosure Firmware version display and/or last update date Vulnerable services (web, ssh, tftp, etc.) Verify for old sw versions and possible attacks (Heartbleed, Shellshock, old PHP versions etc) Security related function API exposure Firmware downgrade possibility
Device Network Services	Information disclosure User CLI Administrative CLI Injection Denial of Service Unencrypted Services Poorly implemented encryption Test/Development Services Buffer Overflow UPnP Vulnerable UDP Services DoS Device Firmware OTA update block Firmware loaded over insecure channel (no TLS) Replay attack Lack of payload verification Lack of message integrity check Credential management vulnerabilities: Username enumeration Weak passwords Account lockout Known default credentials Insecure password recovery mechanism
Administrative Interface	Standard set of web application vulnerabilities, see: OWASP Web Top 10 OWASP ASVS OWASP Testing guide Credential management vulnerabilities: Username enumeration Weak passwords Account lockout Known default credentials Insecure password recovery mechanism Security/encryption options Logging options Two-factor authentication Check for insecure direct object references Inability to wipe device
Local Data Storage	Unencrypted data Data encrypted with discovered keys Lack of data integrity checks Use of static same enc/dec key
Cloud Web Interface	Standard set of web application vulnerabilities, see: OWASP Web Top 10 OWASP ASVS OWASP Testing guide Credential management vulnerabilities: Username enumeration Weak passwords Account lockout Known default credentials Insecure password recovery mechanism Transport encryption Two-factor authentication
Third-party Backend APIs	Unencrypted PII sent Encrypted PII sent Device information leaked Location leaked
Update Mechanism	Update sent without encryption Updates not signed Update location writable Update verification Update authentication Malicious update Missing update mechanism No manual update mechanism
Mobile Application	Implicitly trusted by device or cloud Username enumeration Account lockout Known default credentials Weak passwords Insecure data storage Transport encryption Insecure password recovery mechanism Two-factor authentication
Vendor Backend APIs	Inherent trust of cloud or mobile application Weak authentication Weak access controls Injection attacks Hidden services
Ecosystem Communication	Health checks Heartbeats Ecosystem commands Deprovisioning Pushing updates
Network Traffic	LAN LAN to Internet Short range Non-standard Wireless (WiFi, Z-wave, XBee, Zigbee, Bluetooth, LoRA) Protocol fuzzing
Authentication/Authorization	Authentication/Authorization related values (session key, token, cookie, etc.) disclosure Reusing of session key, token, etc. Device to device authentication Device to mobile Application authentication Device to cloud system authentication Mobile application to cloud system authentication Web application to cloud system authentication Lack of dynamic authentication
Privacy	User data disclosure User/device location disclosure Differential privacy
Hardware (Sensors)	Sensing Environment Manipulation Tampering (Physically) Damage (Physicall)

Share this:

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

Daniel Miessler
Craig Smith

Related Projects

Collaboration

The Slack Channel

Quick Download

Coming Soon

News and Events

Coming Soon

IoT Vulnerabilities Project

Vulnerability	Attack Surface	Summary
Username Enumeration	Administrative Interface Device Web Interface Cloud Interface Mobile Application	Ability to collect a set of valid usernames by interacting with the authentication mechanism
Weak Passwords	Administrative Interface Device Web Interface Cloud Interface Mobile Application	Ability to set account passwords to '1234' or '123456' for example. Usage of pre-programmed default passwords
Account Lockout	Administrative Interface Device Web Interface Cloud Interface Mobile Application	Ability to continue sending authentication attempts after 3 - 5 failed login attempts
Unencrypted Services	Device Network Services	Network services are not properly encrypted to prevent eavesdropping or tampering by attackers
Two-factor Authentication	Administrative Interface Cloud Web Interface Mobile Application	Lack of two-factor authentication mechanisms such as a security token or fingerprint scanner
Poorly Implemented Encryption	Device Network Services	Encryption is implemented however it is improperly configured or is not being properly updated, e.g. using SSL v2
Update Sent Without Encryption	Update Mechanism	Updates are transmitted over the network without using TLS or encrypting the update file itself
Update Location Writable	Update Mechanism	Storage location for update files is world writable potentially allowing firmware to be modified and distributed to all users
Denial of Service	Device Network Services	Service can be attacked in a way that denies service to that service or the entire device
Removal of Storage Media	Device Physical Interfaces	Ability to physically remove the storage media from the device
No Manual Update Mechanism	Update Mechanism	No ability to manually force an update check for the device
Missing Update Mechanism	Update Mechanism	No ability to update device
Firmware Version Display and/or Last Update Date	Device Firmware	Current firmware version is not displayed and/or the last update date is not displayed
Firmware and storage extraction	JTAG / SWD interface In-Situ dumping Intercepting a OTA update Downloading from the manufacturers web page eMMC tapping Unsoldering the SPI Flash / eMMC chip and reading it in a adapter	Firmware contains a lot of useful information, like source code and binaries of running services, pre-set passwords, ssh keys etc.
Manipulating the code execution flow of the device	JTAG / SWD interface Side channel attacks like glitching	With the help of a JTAG adapter and gdb we can modify the execution of firmware in the device and bypass almost all software based security controls. Side channel attacks can also modify the execution flow or can be used to leak interesting information from the device
Obtaining console access	Serial interfaces (SPI / UART)	By connecting to a serial interface, we will obtain full console access to a device Usually security measures include custom bootloaders that prevent the attacker from entering single user mode, but that can also be bypassed.
Insecure 3rd party components	Software	Out of date versions of busybox, openssl, ssh, web servers, etc.

Share this:

What is the IoT Vulnerabilities Project?

The IoT Vulnerabilities Project provides:

Information on the top IoT vulnerabilities
The attack surface associated with the vulnerability
A summary of the vulnerability

Project Leaders

Daniel Miessler
Craig Smith

Related Projects

Collaboration

The Slack Channel

Resources

Top 10 IoT Vulnerabilities from 2014

News and Events

Coming Soon

Medical Device Testing

The Medical Device Testing project is intended to provide some basic attack surface considerations that should be evaluated before shipping Medical Device equipment.

Attack Surface	Vulnerability
Ecosystem (general)	Interoperability standards Data governance System wide failure Individual stakeholder risks Implicit trust between components Enrollment security Decommissioning system Lost access procedures
HL7	XML Parsing XSS Information Disclosure
Device Memory	Sensitive data Cleartext usernames Cleartext passwords Third-party credentials Encryption keys
Device Physical Interfaces	Firmware extraction User CLI Admin CLI Privilege escalation Reset to insecure state Removal of storage media Tamper resistance Debug port Device ID/Serial number exposure
Device Web Interface	Standard set of web vulnerabilities: SQL injection Cross-site scripting Cross-site Request Forgery Username enumeration Credential management vulnerabilities: Username enumeration Weak passwords Account lockout Known default credentials Insecure password recovery mechanism
Device Firmware	Sensitive data exposure: Backdoor accounts Hardcoded credentials Encryption keys Encryption (Symmetric, Asymmetric) Sensitive information Sensitive URL disclosure Firmware version display and/or last update date Vulnerable services (web, ssh, tftp, etc.) Security related function API exposure Firmware downgrade
Device Network Services	Information disclosure User CLI Administrative CLI Injection Denial of Service Unencrypted Services Poorly implemented encryption Test/Development Services Buffer Overflow UPnP Vulnerable UDP Services DoS Device Firmware OTA update block Replay attack Lack of payload verification Lack of message integrity check Credential management vulnerabilities: Username enumeration Weak passwords Account lockout Known default credentials Insecure password recovery mechanism
Administrative Interface	Standard web vulnerabilities: SQL injection Cross-site scripting Cross-site Request Forgery Username enumeration Credential management vulnerabilities: Username enumeration Weak passwords Account lockout Known default credentials Insecure password recovery mechanism Security/encryption options Logging options Two-factor authentication Inability to wipe device
Local Data Storage	Unencrypted data Data encrypted with discovered keys Lack of data integrity checks Use of static same enc/dec key
Cloud Web Interface	Standard set of web vulnerabilities: SQL injection Cross-site scripting Cross-site Request Forgery Credential management vulnerabilities: Username enumeration Weak passwords Account lockout Known default credentials Insecure password recovery mechanism Transport encryption Two-factor authentication
Third-party Backend APIs	Unencrypted PII sent Encrypted PII sent Device information leaked Location leaked
Update Mechanism	Update sent without encryption Updates not signed Update location writable Update verification Update authentication Malicious update Missing update mechanism No manual update mechanism
Mobile Application	Implicitly trusted by device or cloud Username enumeration Account lockout Known default credentials Weak passwords Insecure data storage Transport encryption Insecure password recovery mechanism Two-factor authentication
Vendor Backend APIs	Inherent trust of cloud or mobile application Weak authentication Weak access controls Injection attacks Hidden services
Ecosystem Communication	Health checks Heartbeats Ecosystem commands Deprovisioning Pushing updates
Network Traffic	LAN LAN to Internet Short range Non-standard Wireless (WiFi, Z-wave, XBee, Zigbee, Bluetooth, LoRA) Protocol fuzzing
Authentication/Authorization	Authentication/Authorization related values (session key, token, cookie, etc.) disclosure Reusing of session key, token, etc. Device to device authentication Device to mobile Application authentication Device to cloud system authentication Mobile application to cloud system authentication Web application to cloud system authentication Lack of dynamic authentication
Data Flow	What data is being captured? How does it move within the ecosystem? How is it protected in transit? How is it protected at rest? Who is that data shared with?
Hardware (Sensors)	Sensing Environment Manipulation Tampering (Physically) Damaging (Physically) Failure state analysis

Share this:

What is the Medical Attack Surfaces project?

The Medical Attack Surfaces project provides:

A simple way for testers, manufacturers, developers, and users to get an understanding of the complexity of a modern medical environment
Allows people to visualize the numerous attack surfaces that need to be defended within medical equipment ecosystems

Project Leaders

Daniel Miessler

Related Projects

Collaboration

The Slack Channel

Resources

News and Events

Daniel Miessler presented on using Adaptive Testing Methodologies to evaluate the security of medical devices at RSA 2017.

Firmware Analysis Project

The Firmware Analysis Project is intended to provide security testing guidance for the IoT Attack Surface "Device Firmware":

Section
Device Firmware Vulnerabilities	Out-of-date core components Unsupported core components Expired and/or self-signed certificates Same certificate used on multiple devices Admin web interface concerns Hardcoded or easy to guess credentials Sensitive information disclosure Sensitive URL disclosure Encryption key exposure Backdoor accounts Vulnerable services (web, ssh, tftp, etc.)
Manufacturer Recommendations	Ensure that supported and up-to-date software is used by developers Ensure that robust update mechanisms are in place for devices Ensure that certificates are not duplicated across devices and product lines. Ensure supported and up-to-date software is used by developers Develop a mechanism to ensure a new certificate is installed when old ones expire Disable deprecated SSL versions Ensure developers do not code in easy to guess or common admin passwords Ensure services such as SSH have a secure password created Develop a mechanism that requires the user to create a secure admin password during initial device setup Ensure developers do not hard code passwords or hashes Have source code reviewed by a third party before releasing device to production Ensure industry standard encryption or strong hashing is used
Device Firmware Guidance and Instruction	Firmware file analysis Firmware extraction Dynamic binary analysis Static binary analysis Static code analysis Firmware emulation File system analysis
Device Firmware Tools	Firmwalker Firmware Modification Kit Angr binary analysis framework Binwalk firmware analysis tool Binary Analysis Tool Firmadyne Firmware Analysis Comparison Toolkit ByteSweep
Vulnerable Firmware	Damn Vulnerable Router Firmware OWASP IoTGoat

Share this:

What is the Firmware Analysis Project?

The Firmware Analysis Project provides:

Security testing guidance for vulnerabilities in the "Device Firmware" attack surface
Steps for extracting file systems from various firmware files
Guidance on searching a file systems for sensitive of interesting data
Information on static analysis of firmware contents
Information on dynamic analysis of emulated services (e.g. web admin interface)
Testing tool links
A site for pulling together existing information on firmware analysis

Project Leaders

Craig Smith

Related Projects

Collaboration

The Slack Channel

Resources

News and Events

Coming Soon

IoT Logging Events

This 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.

Event Category	Events
Request Exceptions	Attempt to Invoke Unsupported HTTP Method Unexpected Quantity of Characters in Parameter Unexpected Type of Characters in Parameter
Authentication Exceptions	Multiple Failed Passwords High Rate of Login Attempts Additional POST Variable Deviation from Normal GEO Location
Session Exceptions	Modifying the Existing Cookie Substituting Another User's Valid SessionID or Cookie Source Location Changes During Session
Access Control Exceptions	Modifying URL Argument Within a GET for Direct Object Access Attempt Modifying Parameter Within a POST for Direct Object Access Attempt Forced Browsing Attempt
Ecosystem Membership Exceptions	Traffic Seen from Disenrolled System Traffic Seen from Unenrolled System Failed Attempt to Enroll in Ecosystem Multiple Attempts to Enroll in Ecosystem
Device Access Events	Device Case Tampering Detected Device Logic Board Tampering Detected
Administrative Mode Events	Device Entered Administrative Mode Device Accessed Using Default Administrative Credentials
Input Exceptions	Double Encoded Character Unexpected Encoding Used
Command Injection Exceptions	Blacklist Inspection for Common SQL Injection Values Abnormal Quantity of Returned Records
Honey Trap Exceptions	Honey Trap Resource Requested Honey Trap Data Used
Reputation Exceptions	Suspicious or Disallowed User Source Location

Share this:

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

Daniel Miessler

Related Projects

The OWASP AppSensor Project

Collaboration

The Slack Channel

Quick Download

Coming Soon

News and Events

Coming Soon

PROJECT INFO
What does this OWASP project offer you?

RELEASE(S) INFO
What releases are available for this project?

what	is this project?
Name: OWASP Internet of Things Project
Purpose: N/A
License: CC-BY 3.0 for documentation and GPLv3 for code.
who	is working on this project?
Project Leader(s): Daniel Miessler Craig Smith
Project Contributor(s): Justin Klein Keane] Yunsoul
how	can you learn more?
Project Pamphlet: Not Yet Created
Project Presentation:
Mailing list: N/A
Project Roadmap: Not Yet Created
Key Contacts
Contact Daniel Miessler to contribute to this project Contact Daniel Miessler to review or sponsor this project

current release
Not Yet Published
last reviewed release
Not Yet Reviewed

other releases

@@ Line 5: / Line 5: @@
 {| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |-
 | style="border-right: 1px dotted gray;padding-right:25px;" valign="top" |
+== 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 separated into the following categories - Seek & Understand, Validate & Test, and Governance.
+==Updated!==
+The OWASP IoT Project for 2018 has been released![[File:OWASP 2018 IoT Top10 Final.jpg|center|thumb|1301x1301px]]
+== Philosophy ==
+The OWASP Internet of Things Project was started in 2014 as a way help Developers, Manufacturers, Enterprises, and Consumers to make better decisions regarding the creation and use of IoT systems.
+This continues today with the 2018 release of the OWASP IoT Top 10, which represents the top ten things to avoid when building, deploying, or managing IoT systems. The primary theme for the 2018 OWASP Internet of Things Top 10 is simplicity. Rather than having separate lists for risks vs. threats vs. vulnerabilities—or for developers vs. enterprises vs. consumers—the project team elected to have a single, unified list that captures the top things to avoid when dealing with IoT Security.
+The team recognized that there are now dozens of organizations releasing elaborate guidance on IoT Security—all of which are designed for slightly different audiences and industry verticals. We thought the most useful resource we could create is a single list that addresses the highest priority issues for manufacturers, enterprises, and consumers at the same time.
+The result is the [https://www.owasp.org/images/1/1c/OWASP-IoT-Top-10-2018-final.pdf 2018 OWASP IoT Top 10].
+== Methodology ==
+The project team is a collection of volunteer professionals from within the security industry, with experience spanning multiple areas of expertise, including: manufacturers, consulting, security testers, developers, and many more.
-==OWASP Internet of Things (IoT) Project==
+The project was conducted in the following phases:
+# '''Team Formation''': finding people who would be willing to contribute to the 2018 update, both as SMEs and as project leaders to perform various tasks within the duration of the project.
+# '''Project Review:''' analysis of the 2014 project to determine what’s changed in the industry since that release, and how the list should be updated given those changes.
+# '''Data Collection''': collection and review of multiple vulnerability sources (both public and private), with special emphasis on which issues caused the most actual impact and damage.
+# '''Sister Project Review''': a review of dozens of other IoT Security projects to ensure that we’d not missed something major and that we were comfortable with both the content and prioritization of our release. Examples included: [https://cloudsecurityalliance.org/artifacts/csa-iot-controls-matrix/ CSA IoT Controls Matrix], [https://api.ctia.org/wp-content/uploads/2018/08/CTIA-IoT-Cybersecurity-Certification-Test-Plan-V1_0.pdf CTIA], [http://iot.stanford.edu/ Stanford’s Secure Internet of Things Project], [https://nvlpubs.nist.gov/nistpubs/ir/2018/NIST.IR.8200.pdf NISTIR 8200], [https://www.enisa.europa.eu/publications/baseline-security-recommendations-for-iot/at_download/fullReport ENISA IoT Baseline Report], [https://assets.publishing.service.gov.uk/government/uploads/system/uploads/attachment_data/file/747413/Code_of_Practice_for_Consumer_IoT_Security_October_2018.pdf Code of Practice for Consumer IoT Security,] and others.
+# '''Community Draft Feedback''': release of the draft to the community for review, including multiple Twitter calls for comments, the use of a public feedback form, and a number of public talks where feedback was gathered. The feedback was then reviewed by the team along with initial Data Collection, as well as Sister Project Review, to create the list contents and prioritization.
+# '''Release:''' release of the project to the public in December 2018.
-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 Future of the OWASP IoT Top 10 ==
+The team has a number of activities planned to continue improving on the project going forward.
-''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''.
+Some of the items being discussed include:
+* Continuing to improve the list on a two-year cadence, incorporating feedback from the community and from additional project contributors to ensure we are staying current with issues facing the industry.
+* Mapping the list items to other OWASP projects, such as the ASVS, and perhaps to other projects outside OWASP as well.
+* Expanding the project into other aspects of IoT—including embedded security, ICS/ SCADA,etc.
+* Adding use and abuse cases, with multiple examples, to solidify each concept discussed.
+* Considering the addition of reference architectures, so we can not only tell people what to avoid, but how to do what they need to do securely.
-The project looks to define a structure for various IoT sub-projects such as Attack Surface Areas, Testing Guides and Top Vulnerabilities.
+Participation in the OWASP IoT Project is open to the community. We take input from all participants — whether you’re a developer, a manufacturer, a penetration tester, or someone just trying to implement IoT securely. You can find the team meeting every other Friday in the the #iot-security room of the OWASP Slack Channel.
-[[File:iot-project.png|400px|thumb|center]]
+'''''The OWASP IoT Security Team, 2018'''''
 ==Licensing==
@@ Line 38: / Line 72: @@
 * Developer, Consumer and Manufacturer Guidance
 * Design Principles
+* IoTGoat
 == Project Leaders ==
@@ Line 43: / Line 78: @@
 * Daniel Miessler
 * Craig Smith
+* Vishruta Rudresh
+* Aaron Guzman
 == Contributors ==
 * [https://www.owasp.org/index.php/User:Justin_C._Klein_Keane Justin Klein Keane]
 * Saša Zdjelar
+== IoT Top 2018 Contributors ==
+* Vijayamurugan Pushpanathan
+* Alexander Lafrenz
+* Masahiro Murashima
+* Charlie Worrell
+* José A. Rivas (jarv)
+* Pablo Endres
+* Ade Yoseman
+* Cédric Levy-Bencheotn
+* Jason Andress
+* Amélie Didion - Designer
 == Related Projects ==
@@ Line 53: / Line 102: @@
 * [[OWASP_Mobile_Security_Project|OWASP Mobile Security]]
 * [[OWASP_Top_Ten_Project|OWASP Web Top 10]]
-* [[OWASP_.NET_Project|OWASP .NET]]
+* [https://www.owasp.org/index.php/OWASP_Embedded_Application_Security OWASP Embedded Application Security]
-* [[Java|OWASP Java and JVM]]
+* [https://www.owasp.org/index.php/C-Based_Toolchain_Hardening OWASP C-based Toolchain Hardening]
-* [[C/C++|OWASP C/C++]]
 | style="padding-left:25px;width:200px;" valign="top" |
 == Collaboration ==
-[https://owasp-iot-security.slack.com The Slack Channel]
+[https://owasp.slack.com The OWASP Slack Channel]
 Hint: If you're new to Slack, [https://lists.owasp.org/pipermail/owasp-community/2015-July/000703.html join OWASP's slack channel first], then join #iot-security within OWASP's channel.
-<!-- Hey Guys - Andy Lewis here.  I'm not great w/slack but when I browse to https://owasp-iot-security.slack.com/signup
-I'm getting "This team's administrator has not enabled email signups." and "Ask your administrator to send you an invitation."
-I'm adding this comment in hopes of being able to get in contact w/someone from the project after Blackhat/Defcon.
-If you're reading this, could you please reach out to me
-[email protected]
-or open up the slack channel to auto-OK @owasp.org addresses?
-Thanks
-Andy
--->
 == Quick Download ==
+[https://www.owasp.org/images/1/1c/OWASP-IoT-Top-10-2018-final.pdf OWASP IoT Top Ten 2018]
 [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/7/71/Internet_of_Things_Top_Ten_2014-OWASP.pdf OWASP IoT Top Ten 2014 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]
 [https://www.owasp.org/images/b/bd/OWASP-IoT.pptx OWASP IoT Project Overview]
 == News and Events ==
+* OWASP [https://www.owasp.org/index.php/OWASP_Internet_of_Things_Project#tab=IoTGoat IoTGoat Project] underway
+* New firmware security analysis tool, ByteSweep
+* IoT ASVS and Testing Guide set to kick off in 2019
 * Added a [https://owasp-iot-security.slack.com/ Slack channel]
 * Added a sub-project; [https://www.owasp.org/index.php/OWASP_Internet_of_Things_Project#tab=IoT_Security_Policy_Project IoT Security Policy Project]
-* Daniel Miessler gave his [https://www.youtube.com/watch?v=RhxHHD790nw IoT talk at DEFCON 23]
-* Migrating the IoT Top Ten to be under the IoT Project
-* HP Study Reveals 70 Percent of Internet of Things Devices Vulnerable to Attack
 ==Classifications==
@@ Line 108: / Line 143: @@
     | colspan="2" align="center" | [[File:Project_Type_Files_DOC.jpg|link=]]
     |}
+|}
+= IoT Top 10 =
+<div style="width:100%;height:160px;border:0,margin:0;overflow: hidden;">[[File:OWASP_Project_Header.jpg|link=]]</div>
+== Internet of Things (IoT) Top 10 2018 ==
+The [https://www.owasp.org/images/1/1c/OWASP-IoT-Top-10-2018-final.pdf OWASP IoT Top 10 - 2018] is now available.
+* I1 Weak Guessable, or Hardcoded Passwords
+* I2 Insecure Network Services
+* I3 Insecure Ecosystem Interfaces
+* I4 Lack of Secure Update Mechanism
+* I5 Use of Insecure or Outdated Components
+* I6 Insufficient Privacy Protection
+* I7 Insecure Data Transfer and Storage
+* I8 Lack of Device Management
+* I9 Insecure Default Settings
+* I10 Lack of Physical Hardening
+== Internet of Things (IoT) Top 10 2014 ==
+* [[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]]
+= OWASP IoT Top 10 2018 Mapping Project =
+{| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |-
+| style="border-right: 1px dotted gray;padding-right:25px;" valign="top" |
+== IoT Top 10 2018 Mapping Project ==
+The OWASP IoT Mapping Project is intended to provide a mapping of the OWASP IoT Top 10 2018 to industry publications and sister projects. The goal is to provide resources that enable practical uses for the OWASP IoT Top 10 . As with all Top 10 lists, they should be used as a first step and expanded upon according to the applicable IoT ecosystem.
+Mappings are structured with control categories, tests, or recommendations in the left column, descriptions in the middle column, and their mapping to the OWASP IoT Top 10 2018 list in the right column. Each mapping may not have a 1 to 1 relation; however, similar recommendations and/or controls are listed. For mappings that are not applicable to the IoT Top 10 2018 list, an "N/A" is provided as the mapping.
+An example mapping of the IoT Top 10 2014 is provided below.
+[[File:2014 2018Mapping.png|center|frameless|746x746px]]
+For additional mappings, please visit the following link: https://scriptingxss.gitbook.io/owasp-iot-top-10-mapping-project/<nowiki/>{{Social Media Links}}
+| style="padding-left:25px;width:300px;border-right: 1px dotted gray;padding-right:25px;" valign="top" |
+== What is the IoT Top 10 Mapping Project? ==
+The OWASP IoT Mapping Project is intended to provide a mapping of the OWASP IoT Top 10 2018 to industry publications and sister projects. The goal is to provide resources that enable practical uses for the OWASP IoT Top 10 . As with all Top 10 lists, they should be used as a first step and expanded upon according to the applicable IoT ecosystem.
+Mappings include the following:
+* [https://scriptingxss.gitbook.io/owasp-iot-top-10-mapping-project/mappings/owasp-iot-top-10-2014 OWASP IoT Top 10 2014]
+* [https://scriptingxss.gitbook.io/owasp-iot-top-10-mapping-project/mappings/gsma-iot-security-assessment-checklist GSMA IoT Security Assessment Checklist]
+* [https://scriptingxss.gitbook.io/owasp-iot-top-10-mapping-project/mappings/code-of-practice Code of Practice (UK Government)]
+* [https://scriptingxss.gitbook.io/owasp-iot-top-10-mapping-project/mappings/enisa-baseline-security-recommendations-for-iot ENISA Baseline Security Recommendations for IoT]
+and more...
+== GitBook ==
+Mappings are hosted on GitBook using the following link https://scriptingxss.gitbook.io/owasp-iot-top-10-mapping-project/
+== Project Leaders ==
+* Aaron Guzman
+== Collaboration ==
+[https://owasp.slack.com The Slack Channel]
+|}
+= IoTGoat =
+<div style="width:100%;height:160px;border:0,margin:0;overflow: hidden;">[[File:OWASP_Project_Header.jpg|link=]]</div>
+{| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |-
+| style="border-right: 1px dotted gray;padding-right:25px;" valign="top" |
+== IoTGoat Project ==
+IoT Goat is a deliberately insecure firmware based on OpenWrt. The project’s goal is to teach users about the most common vulnerabilities typically found in IoT devices. The vulnerabilities will be based on the top 10 vulnerabilities as documented by OWASP: [[OWASP_Internet_of_Things_Project|https://www.owasp.org/index.php/OWASP_Internet_of_Things_Project]]. IoTGoat is expected to be released by December 2019.
+To get more information on getting started or how to contribute, visit the project's Github: https://github.com/scriptingxss/IoTGoat
+{{Social Media Links}}
+| style="padding-left:25px;width:300px;border-right: 1px dotted gray;padding-right:25px;" valign="top" |
+== What is the IoTGoat Project? ==
+The IoTGoat Project is a deliberately insecure firmware based on OpenWrt. The project’s goal is to teach users about the most common vulnerabilities typically found in IoT devices. The vulnerabilities will be based on the IoT Top 10.
+== GitHub ==
+https://github.com/scriptingxss/IoTGoat
+== Project Leaders ==
+* Aaron Guzman
+* Fotios Chantzis
+* [[User:Calderpwn|Paulino Calderon]]
+== Related Projects ==
+* WebGoat
+* Serverless Goat
+* NodeGoat
+* RailsGoat
+== Collaboration ==
+[https://owasp.slack.com The Slack Channel]
+[https://groups.google.com/forum/#!forum/iotgoat IoTGoat Google Group]
+== Quick Download ==
+* [https://docs.google.com/presentation/d/1SJfabCBxvC3GWnmBCqisO5pyLzkB1-EVcR7s8baT0dE/edit?usp=sharing Project Kick-off Slides]
+* [https://strozfriedberg.webex.com/recordingservice/sites/strozfriedberg/recording/playback/5529b228ac514bed8cc050a9dee0f0df Project Kick-off Meeting]
+* [https://docs.google.com/spreadsheets/d/1KXX2K7ikkve6wmdfAVu-sZONgKEBuAkRij_paJUgX2w/edit?usp=sharing Project Task List]
+== News and Events ==
+* Coming Soon
+|}
+= ByteSweep =
+[[File:OWASP_Project_Header.jpg|link=]]
+{| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |-
+| style="border-right: 1px dotted gray;padding-right:25px;" valign="top" |
+== ByteSweep Project ==
+ByteSweep is a Free Software IoT security analysis platform. This platform will allow IoT device makers, large and small, to conduct fully automated security checks before they ship firmware. A Free Software IoT Firmware Security Analysis Platform
+ByteSweep Features:
+* Firmware extraction
+* File data enrichment
+* Key and password hash identification
+* Unsafe function use detection
+* 3rd party component identification
+* CVE correlation
+{{Social Media Links}}
+| style="padding-left:25px;width:300px;border-right: 1px dotted gray;padding-right:25px;" valign="top" |
+== What is the ByteSweep Project? ==
+A Free Software IoT Firmware Security Analysis Platform.
+== GitLab ==
+https://gitlab.com/bytesweep/bytesweep
+== Project Leaders ==
+* Matt Brown
+== Collaboration ==
+[https://owasp.slack.com The Slack Channel]
+== Quick Download ==
+* https://gitlab.com/bytesweep/bytesweep/blob/master/INSTALL.md
+|}
+= Firmware Security Testing Methodology =
+[[File:OWASP_Project_Header.jpg|link=]]
+{| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |-
+| style="border-right: 1px dotted gray;padding-right:25px;" valign="top" |
+== Firmware Security Testing Methodology ==
+The Firmware Security Testing Methodology (FSTM) is composed of nine stages tailored to enable security researchers, software developers, consultants, hobbyists, and Information Security professionals with conducting firmware security assessments.
+{| class="wikitable"
+|'''Stage'''
+|'''Description'''
+|-
+|1. Information gathering and reconnaissance
+|Acquire all relative technical and documentation details  pertaining to the target device’s firmware
+|-
+|2. Obtaining  firmware
+|Attain firmware using one or more of the proposed methods listed
+|-
+|3. Analyzing firmware
+|Examine the target firmware’s characteristics
+|-
+|4. Extracting  the filesystem
+|Carve filesystem contents from the target firmware
+|-
+|5. Analyzing filesystem contents
+|Statically analyze extracted filesystem configuration  files and binaries for vulnerabilities
+|-
+|6. Emulating  firmware
+|Emulate firmware files and components
+|-
+|7. Dynamic analysis
+|Perform dynamic security testing against firmware and  application interfaces
+|-
+|8. Runtime  analysis
+|Analyze compiled binaries during device runtime
+|-
+|9. Binary Exploitation
+|Exploit identified vulnerabilities discovered in previous  stages to attain root and/or code execution
+|}The full methodology release can be downloaded via the following https://github.com/scriptingxss/owasp-fstm/releases/download/v1.0/Firmware_Security_Testing_Methodology_Version1.pdf.
+{{Social Media Links}}
+| style="padding-left:25px;width:300px;border-right: 1px dotted gray;padding-right:25px;" valign="top" |
+== What is the Firmware Security Testing Methodology ==
+The Firmware Security Testing Methodology Project provides:
+*Attack walkthroughs
+*Tool usage examples
+*Screenshots
+*Companion virtual machine preloaded with tools (EmbedOS) - <nowiki>https://github.com/scriptingxss/EmbedOS</nowiki>
+== Project Leaders ==
+* Aaron Guzman
+== Quick Download ==
+* https://github.com/scriptingxss/owasp-fstm/releases
 |}
@@ Line 354: / Line 621: @@
 == Collaboration ==
-[https://owasp-iot-security.slack.com The Slack Channel]
+[https://owasp.slack.com The Slack Channel]
 == Quick Download ==
@@ Line 867: / Line 1,134: @@
 * [http://www.binaryanalysis.org/en/home Binary Analysis Tool]
 * [https://github.com/firmadyne/firmadyne Firmadyne]
+* Firmware Analysis Comparison Toolkit
+* [https://gitlab.com/bytesweep/bytesweep ByteSweep]
 |-
 |
@@ Line 872: / Line 1,141: @@
 |
 * [https://github.com/praetorian-inc/DVRF Damn Vulnerable Router Firmware]
+* [https://github.com/scriptingxss/IoTGoat OWASP IoTGoat]
 |-
-|}
+|
+|}{{Social Media Links}}
-{{Social Media Links}}
 | style="padding-left:25px;width:300px;border-right: 1px dotted gray;padding-right:25px;" valign="top" |
@@ Line 899: / Line 1,168: @@
 * [[OWASP_Mobile_Security_Project|OWASP Mobile Security]]
 * [[OWASP_Top_Ten_Project|OWASP Web Top 10]]
+* [https://www.owasp.org/index.php/OWASP_Embedded_Application_Security OWASP Embedded Application Security Project]
 == Collaboration ==
@@ Line 1,022: / Line 1,292: @@
 |}
-= ICS/SCADA =
-<div style="width:100%;height:160px;border:0,margin:0;overflow: hidden;">[[File:OWASP_Project_Header.jpg|link=]]</div>
-{| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |-
-| style="border-right: 1px dotted gray;padding-right:25px;" valign="top" |
-== ICS/SCADA Project ==
-The OWASP ICS/SCADA Top 10 software weaknesses are as follows:
-{| class="wikitable" style="text-align: left" border="1"
-! Rank and ID
-! Title
-|-
-| '''1 - CWE-119'''
-|
-* Improper Restriction of Operations within the Bounds of a Memory Buffer
-|-
-| '''2 - CWE-20'''
-|
-* Improper Input Validation
-|-
-| '''3 - CWE-22'''
-|
-* Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
-|-
-| '''4 - CWE-264'''
-|
-* Permissions, Privileges, and Access Controls
-|-
-| '''5 - CWE-200'''
-|
-* Information Exposure
-|-
-| '''6 - CWE-255'''
-|
-* Credentials Management
-|-
-| '''7 - CWE-287'''
-|
-* Improper Authentication
-|-
-| '''8 - CWE-399'''
-|
-* Resource Management Errors
-|-
-| '''9 - CWE-79'''
-|
-* Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
-|-
-| '''10 - CWE-189'''
-|
-* Numeric Errors
-|-
-|}
-{{Social Media Links}}
-| style="padding-left:25px;width:300px;border-right: 1px dotted gray;padding-right:25px;" valign="top" |
-== What is the ICS/SCADA Project? ==
-The ICS/SCADA Project provides:
-* A list of the Top 10 most dangerous software weaknesses
-== Project Leaders ==
-* NJ Ouchn
-== Related Projects ==
-* [[OWASP_Mobile_Security_Project|OWASP Mobile Security]]
-* [[OWASP_Top_Ten_Project|OWASP Web Top 10]]
-== Collaboration ==
-[https://owasp-iot-security.slack.com The Slack Channel]
-== Quick Download ==
-* Coming Soon
-== News and Events ==
-* Coming Soon
-|}
-= IoT Security Policy Project =
-<div style="width:100%;height:160px;border:0,margin:0;overflow: hidden;">[[File:OWASP_Project_Header.jpg|link=]]</div>
-{| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |-
-| style="border-right: 1px dotted gray;padding-right:25px;" valign="top" |
-== IoT Security Policy Project ==
-The OWASP IoT Security Policy Project provides:
-{{Social Media Links}}
-| style="padding-left:25px;width:300px;border-right: 1px dotted gray;padding-right:25px;" valign="top" |
-== What is the IoT Security Policies Project? ==
-The IoT Security Policy Project provides:
-== Project Leaders ==
-* Saša Zdjelar
-== Related Projects ==
-== Collaboration ==
-[https://owasp-iot-security.slack.com The Slack Channel]
-== Quick Download ==
-* Coming Soon
-== News and Events ==
-* Coming Soon
-|}
-= 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
-[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.
-===Talks===
-RSA Conference San Francisco <br>
-[https://www.owasp.org/images/5/51/RSAC2015-OWASP-IoT-Miessler.pdf Securing the Internet of Things: Mapping IoT Attack Surface Areas with the OWASP IoT Top 10 Project] <br>
-Daniel Miessler, Practice Principal <br>
-April 21, 2015 <br>
---- <br>
-Defcon 23 <br>
-[https://www.owasp.org/images/3/36/IoTTestingMethodology.pdf IoT Attack Surface Mapping] <br>
-Daniel Miessler <br>
-August 6-9, 2015
-===Podcasts===
-* [http://iotpodcast.com/ The Internet of Things Podcast]
-* [http://www.iot-inc.com/ IoT Inc]
-* [https://craigsmith.net/iot-this-week/ IoT This Week]
-* [http://farstuff.com/ Farstuff: The Internet of Things Podcast]
-===IoT Conferences===
-* [http://www.iotevents.org Internet of Things Events]
-Conference Call for Papers
-* [http://www.wikicfp.com/cfp/servlet/tool.search?q=internet+of+things&year=t WikiCFP - Internet of Things]
-* [http://www.wikicfp.com/cfp/servlet/tool.search?q=iot&year=t WikiCFP - IoT]
 =Project About=
@@ Line 1,228: / Line 1,315: @@
 | links_name1 =
 }}

Difference between revisions of "OWASP Internet of Things Project"

Latest revision as of 07:02, 1 November 2019

OWASP Internet of Things (IoT) Project

Updated!

Philosophy

Methodology

The Future of the OWASP IoT Top 10

Licensing

What is the OWASP Internet of Things Project?

Project Leaders

Contributors

IoT Top 2018 Contributors

Related Projects

Collaboration

Quick Download

News and Events

Classifications

Internet of Things (IoT) Top 10 2018

Internet of Things (IoT) Top 10 2014

IoT Top 10 2018 Mapping Project

What is the IoT Top 10 Mapping Project?

GitBook

Project Leaders

Collaboration

IoTGoat Project

What is the IoTGoat Project?

GitHub

Project Leaders

Related Projects

Collaboration

Quick Download

News and Events

ByteSweep Project

What is the ByteSweep Project?

GitLab

Project Leaders

Collaboration

Quick Download

Firmware Security Testing Methodology

What is the Firmware Security Testing Methodology

Project Leaders

Quick Download

IoT Attack Surface Areas Project

What is the IoT Attack Surface Areas Project?

Project Leaders

Related Projects

Collaboration

Quick Download

News and Events

IoT Vulnerabilities Project

What is the IoT Vulnerabilities Project?

Project Leaders

Related Projects

Collaboration

Resources

News and Events

Medical Device Testing

What is the Medical Attack Surfaces project?

Project Leaders

Related Projects

Collaboration

Resources

News and Events

Firmware Analysis Project

What is the Firmware Analysis Project?

Project Leaders

Related Projects

Collaboration

Resources

News and Events

IoT Logging Events

What is the IoT Security Logging Project?

Project Leaders

Related Projects

Collaboration

Quick Download

News and Events

Navigation menu

Search