{"id":994,"date":"2015-08-13T16:03:11","date_gmt":"2015-08-13T23:03:11","guid":{"rendered":"https:\/\/blogs.plm.automation.siemens.com\/t5\/Polarion-Blog\/How-to-Address-the-IoT-and-Risk-Management-Disconnect\/ba-p\/380988"},"modified":"2026-03-26T05:33:46","modified_gmt":"2026-03-26T09:33:46","slug":"how-to-address-the-iot-and-risk-management-disconnect","status":"publish","type":"post","link":"https:\/\/blogs.sw.siemens.com\/polarion\/how-to-address-the-iot-and-risk-management-disconnect\/","title":{"rendered":"How to Address the IoT and Risk Management Disconnect"},"content":{"rendered":"

The rush is on. It’s called the Internet of Things (IoT). Physical things with software embedded in them, some of which connects to remote resources via the internet. It’s clear there are benefits to be reaped, but the connectivity creates a whole new landscape<\/STRONG> for risk analysis<\/STRONG> and risk management<\/STRONG>. To date, these disciplines largely take place as a thing apart, in a silo, or \u201cblack box\u201d as it were. Output goes to Requirements Management – which all too often takes place in another silo, apart from software development and product engineering. If the news we’re seeing lately is any indication, this approach which served us well in years past just isn’t cutting it anymore.<\/SPAN>
\n<\/p>\n

\"ImageBy now, the recent news about the vulnerability<\/A><\/STRONG> in Chrysler automobiles is almost “old news”. Following close on its heels came the U.S. FDA warning<\/STRONG><\/A> about hackable medical devices. These are unlikely to be the last such stories we’ll be seeing. We already saw a year of record recalls in the automotive industry in 2014<\/A>.<\/p>\n

Between pressures to innovate and go to market quickly, the vulnerabilities of “traditional” approaches to both software and hardware engineering are being exposed, to the high cost of both producers and consumers.<\/SPAN>
\n

What Can Be Done to Improve Matters?<\/B><\/H2>
\nWhile there is no magic bullet that is going to solve all the problems associated with the rapid paradigm shift, there are things that innovative companies can do… and are<\/EM> doing every day. They are rapidly coming to understand the value and importance of a unified development platform<\/B> that creates an ecosystem where:
\n