It's really pretty simple. If you put data unencrypted in the cloud, it can be (usefully) stolen. If you run applications on your computers that you didn't write, they may have Trojan horses in them. If you run any standard OS or software on a network, you are subject to 0-day defects that could steal anything on that computer or plant software that watches future activities.
Plan accordingly. In practice, this means strategically-placed air gaps and encryption, as well as turning off automatic software execution when USB drives or CD/DVD's are plugged in, running updated software and virus checkers (but don't trust either to find everything), and most importantly, employee training. If you aren't doing any of those, start with employee training. Employees with security training will help you find your weaknesses -- without training, they only create additional weaknesses.
What are the engineering and design challenges in creating successful IoT devices? These devices are usually small, resource-constrained electronics designed to sense, collect, send, and/or interpret data. Some of the devices need to be smart enough to act upon data in real time, 24/7. Are the design challenges the same as with embedded systems, but with a little developer- and IT-skills added in? What do engineers need to know? Rick Merritt talks with two experts about the tools and best options for designing IoT devices in 2016. Specifically the guests will discuss sensors, security, and lessons from IoT deployments.