Grab a fork! Unravelling the Internet of Things' standards spaghetti The great thing about standards is that there are always so many to choose from. We've seen the standards forest grow countless times before. The Internet of Things is a vast digital petri dish for them, and they just keep growing. Recently we've acquired another initiative to pull together vendors working in IoT. It's called …
Does anyone else find it alarming that Danny could only find two opportunities to mention the word "security" in the entire article - and one of those was part of a company name?
The BrickerBot's author's work isn't over yet: https://www.bleepingcomputer.com/news/security/brickerbot-dev-claims-cyber-attack-that-affected-over-60-000-indian-modems/
"Let's just hope that your smart thermostat is smart enough to accommodate some fairly hefty firmware updates. In the future, it may need them."
Don't you mean :
"Let's just hope that your smart thermostat survives for a few months before it's orphaned and never updated again"
"Let's just hope that your smart thermostat is smart enough to accommodate some fairly hefty firmware updates. In the future, it may need them."
My greenhouse's "smart thermostat" has been running for over thirty years. It maintains the temperature to within 2 degrees either way quite nicely. I haven't needed to update any code for at least thirty of those years. Why not? Because it works as intended. It's a thermostat, and just does thermostat stuff. Nothing needs updating. Perhaps a point for the IoT folks to ponder ...
Good point. Hm... I think I'll just go for installing a cabinet with DIN rails and relays next to the incoming data network. Manual overrides on everything... a Raspberry Pi with an onto isolator on the GPIO... custom web interface that's responsive and can be webapp'd onto the home screen... should last a decade or more. I pity the fool that has to rely on Google et al supporting their shit for the lifetime of the house.
Independent security certification for IoT devices.
Devices that continue to perform their intended function without connection to a remote server.
Obligated period of support from manufacturer with clearly stated end-of-life behavior.
Clear explanation of what kind of data is recorded and how it is used.
Data handling and retention policy that takes data security seriously and puts privacy first.
Business practices that don't rely on monetizing customer data to ensure continued solvency.
Now I just need to start on step one of my plan for world domination and we should have usable IoT devices in no time.
This post has been deleted by its author
and other s**t coding patterns I'm all for it.
Maybe some of those code monkeys who "write" the s**t for IoT tat might drop that in, rather than whatever b**locks code source they normally cut and paste their vuln ridden code from.
You have to ask what's the goal you want to achieve?
I think most IoT ideas are s**t, but do we all agree that secure IoT is better than insecure IoT?
The next PC that a botnet of compromised IoT things attacks could be yours.
Or worse yet, mine.
The Register 
Biting the hand that feeds IT
Copyright. All rights reserved © 1998–2024
