Official websites use .gov
A .gov website belongs to an official government organization in the United States.
Secure .gov websites use HTTPS
A lock ( ) or https:// means you’ve safely connected to the .gov website. Share sensitive information only on official, secure websites.
OWASP IoT4: Mitigating Lack of Secure Update Mechanism
In this course, you will learn how to mitigate the risks associated with lack of ability to securely update the device. This includes lack of firmware validation on device, lack of secure delivery (un-encrypted in transit), lack of anti-rollback mechanisms, and lack of notifications of security changes due to updates.
Course Overview
Learning Objectives
On successful completion of this course, learners should have the knowledge and skills to:
- List the steps of a typical update process
- Describe how to protect update connections
- Explain how to protect the update server
- List the steps to securely sign and verify an update
- Evaluate whether Secure Boot is necessary for your device at this time
- Identify types of sensitive data that should not be included in updates
Securely implement transport encryption for an Internet of Things (IoT) system
Framework Connections
The materials within this course focus on the NICE Framework Task, Knowledge, and Skill statements identified within the indicated NICE Framework component(s):
Competency Areas
Feedback
If you would like to provide feedback on this course, please e-mail the NICCS team at NICCS@mail.cisa.dhs.gov. Please keep in mind that NICCS does not own this course or accept payment for course entry. If you have questions related to the details of this course, such as cost, prerequisites, how to register, etc., please contact the course training provider directly. You can find course training provider contact information by following the link that says “Visit course page for more information...” on this page.