“Security” is a word that never fails to elicit a response, but what it means varies greatly depending on the context, even when narrowed down to the world of electronic devices.
For the consumer, “security” usually means that personal data is not available to anyone other than the specific intended recipients, but for products powered by a microcontroller, there often isn’t much end-customer data to protect. Let’s look at some other definitions of the word “security.” For software developers, “security” might mean that no one can steal their code. For OEMs, “security” could mean that no one can create clones of their device. For service providers that offer a service via an electronic device, “security” often means that no one can use their service without proper authorization or payment. For governments, “security” can mean that the device cannot be infiltrated and used as a weapon as part of a DDoS attack. All of these definitions definitely apply to microcontrollers and products based on them, regardless of market segment.
As soon as you enter the security realm, you are inundated by new terms and acronyms. The sheer quantity of jargon is mind-numbing. Let’s take it one step at a time while avoiding the difficult vocabulary. How do you go about incorporating security into your MCU-based design?