There are billions of Internet of Things devices in the world that perform critical functions and transform business processes, but they are also alarmingly vulnerable to risks that can lead to third-party IoT vulnerabilities. Here’s why: Manufacturers rely on third-party vendors that develop components with potential entry points for attackers.
Some might argue that the data breach liability corresponds directly to the third-party, but at the end of the day, the company whose customer information is stolen is the one who suffers the biggest impact. So who’s in charge of securing the components of IoT devices and minimizing this third-party risk?
The recent discovery of the Ripple20 vulnerabilities, affecting hundreds of millions of Internet of Things (IoT) devices, is the latest reminder of the dangers that third-party IoT vulnerabilities pose to connected devices. This set of vulnerabilities was threatening connected devices in nearly every sector – industrial controllers, power grids, medical, home, networking, transportation, enterprise, retail, defense, etc.
There has always been a push to shift liability to other parties in the value chain, especially when a vendor is involved. There’s also the issue of traceability. According to the researchers who found the Ripple20 vulnerabilities, which were set to be presented at the Black Hat information security conference:
A recent study by the Ponemon Institute found that six out of ten organizations do not monitor the cyber-risks of IoT devices developed by third-parties, meaning they can eventually supply vulnerable products and be exposed to financial loss and reputational damage.
Security is usually an afterthought to new technology, but IoT devices are nothing new and will keep spreading throughout organizations and business processes — carrying healthcare data, payment information or access to the protocols of a smart home. Securing their components is a must amidst a huge promise to improve efficiency in decade old industries and provide insight for predictive analysis to help shape the way we interact with the world.
While it’s true that third-parties need to make a bigger effort to develop secure components, organizations that rely on them also need to be more aware of who they’re choosing to work with. Whether it be hardware, connectivity or additional services, they need to ensure their providers have the proper measures, assessments and checks in place.
Our ThirdPartyTrust platform allows organizations from any industry to streamline third-party risk management (TPRM) workflows. With the capability to customize vendor questionnaires, request industry standard questionnaires and certifications, it’s easy to include the relevant security checks in the overall assessment of an onboarding third-party. ThirdPartyTrust is a purpose-built TPRM tool that accelerates the third-party assessment/questionnaire review process through workflow automation and centralized communication.
For example, you might want to know which of your third-parties are using a certain component or protocol that is known to be vulnerable to cyber risk, and prioritize it according to your risk appetite. Is it something you can accept, or is it a deal breaker?
At a high level, there are several areas to address around IoT security:
Every enterprise, in some way or another, will be impacted by a connected device and having a framework to follow is, simply, a must.
To learn more about how ThirdPartyTrust can help you streamline your TPRM program, request your free trial now:
Cookie | Duration | Description |
---|---|---|
cookielawinfo-checkbox-analytics | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics". |
cookielawinfo-checkbox-functional | 11 months | The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional". |
cookielawinfo-checkbox-necessary | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary". |
cookielawinfo-checkbox-others | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other. |
cookielawinfo-checkbox-performance | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance". |
viewed_cookie_policy | 11 months | The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data. |