IoT Security Advice: Assume Breach. Plan for What Comes Next.
Stop assuming your device won’t be compromised & start planning for what happens when it is. Learn why defense in depth, credential revocation & real update validation are essential to surviving inevitable attacks.
•1:27•HD•0 views
IoT Security Advice: Assume Breach. Plan for What Comes Next.
Transcript
So if I could give IoT manufacturers one piece of advice, it would be that given enough time, money and resources, an attacker will always get in, no matter how safe the device is designed or assumed to be.
So they assume a lot of IoT devices are a lot of IoT manufacturers assume that, you know, an attacker won't find the UART port. It's beneath, a you know, it's beneath the sealed plastic container or, you know, we've a poxied over it. no No one's going to get that.
So they assume that people are not going to pull the the application down and reverse it to find hard coded credentials or hardcoded certificates, or they assume people aren't going to use a wire shack, shark tap to monitor the communication between their device and maybe the network router or another device.
um So the question shouldn't be, will they get in? It's what happens next when they eventually do.
So you need to design your product so that not a single point of compromise leads to a full control. You know, credentials need to be able to be revoked.
Firmware updates require real validation and sensitive operations require multi layers of trust. So as I said before, build with failure in mind, have contingency plans, have defense in depth.