This sounds very interesting. After doing additional research, according to the International Electrotechnical Commission (IEC), this standard is designed to provide a flexible framework to address and mitigate current and future vulnerabilities in industrial automation and control systems (IACS). I wonder if they could provide and example of a future vulnerability in this area. Carolyn Mathas, any examples?
The focus of this standard is how to set up a cyber security management program. The ANSI/ISA-62443-3-3 standard is the first standard from ISA-99 which provides technical cyber security standards for the control systems that make up an IACS—the first standard to address systems.
While there are several industry-segmented standard covering water, infrastructure, oil and gas, etc., cyber security is left to the user to implement. Sometimes that's not possible as the systems aren't capable of meeting the requirements of the individual standards. ANSI/ISA-62443-3-3 defines these capabilities. End users can now define compliance to the ANSI/ISA-62443-3-3 standard as their requirement in their procurement specification. Naturally, issues of cyber security and implementation continue to evolve—somewhat rapidly, so there is a futures element of this. Like several standards, however, a basis of certification from which to go forward is always preferable compared with everyone to their own devices. This certification is currently ISASecure, from the ISA Security Compliance Institute (ICSI). Now, with the new standard, certification for these systems will be labeled ISASecure SSA. Systems that have been designed for this level of security will be easily identified.
As to a specific future vulnerability on a system level, there are so many current ones with systems the constant target of hacking, and nothing sufficient in place to protect so many, I think the criminal mind would be better than mine to think of a future vulnerability! Hacking and undermining are constantly evolving.
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.