Skip to main content

Book: Click Here to Kill Everybody by Bruce Schenier


"There is a fundamental difference between crashing your computer and losing your spreadsheet data, and crashing your pacemaker and losing your life," 

Blog Post

If you follow me across the web, you know I deeply distrust the Internet of Things. In making things easier for the non-techie, having simple or non existent security options makes them - and everyone else - more at risk for cybercrime.

I finished my Security+ book and read Click Here to Kill Everybody.





Schenier doesn't only break down how the IoT is the wild west of consumer products - There's a lot of regulations that fail to become law because, well, why bother changing it? Our data is continually at risk and companies do not care about it - and neither do we.

Target had a data breach - Do you still shop there? Will your next vacation be at Marriott after 500 million users had their data compromised? Probably. Did their systems fail predictably, safely? My bet is no.

You may say "The government implementing laws can't solve all the problems" and you would not be wrong.

Interconnected networks were built on shoddy protocols - Protocols that have updates and upgrades that are not widely implemented because it would cost too much to retool protocols that we have used for 30 years, and companies do not want to pay for that.

"We also tell them to not insert strange USB drives into their computers. Again, what else would you possibly do with a USB drive? We have to do better: we need systems that remain secure regardless of which links people click on, and regardless of which USB drives they stick into their computers."

Schenier pushes education on all levels, technologists and policy makers working closely together on what's feasible and what isn't, and encouraging people who want to enter the Cybersecurity field. With breaches everywhere you turn and a growing presence of the internet in our refrigerators, it should not be as hard as it is to break into the IT field.


It's a great, informative read with lots of footnotes and links to articles and resources that I will probably end up reading and writing about here, so please pay for the book and give it a read.
Labels:

Comments

Post a Comment

Popular posts from this blog

Connecting IoT Devices to a Registration Server (Packet Tracer, Cisco)

In Packet Tracer, a demo software made by Cisco Systems. It certainly has changed a lot since 2016. It's almost an Olympic feat to even get started with it now, but it does look snazzy. This is for the new CCNA, that integrates, among other things, IoT and Automation, which I've worked on here before. Instructions here . I don't know if this is an aspect of "Let's make sure people are paying attention and not simply following blindly", or an oversight - The instructions indicate a Meraki Server, when a regular one is the working option here. I have to enable the IoT service on this server. Also, we assign the server an IPv4 address from a DHCP pool instead of giving it a static one. For something that handles our IoT business, perhaps that's safer; Getting a new IPv4 address every week or so is a minimal step against an intruder, but it is a step. There are no devices associated with this new server; In an earlier lab (not shown), I attached them to 'H
Post a Comment
Read more

Securing Terraform and You Part 1 -- rego, Tfsec, and Terrascan

9/20: The open source version of Terraform is now  OpenTofu     Sometimes, I write articles even when things don't work. It's about showing a learning process.  Using IaC means consistency, and one thing you don't want to do is have 5 open S3 buckets on AWS that anyone on the internet can reach.  That's where tools such as Terrascan and Tfsec come in, where we can make our own policies and rules to be checked against our code before we init.  As this was contract work, I can't show you the exact code used, but I can tell you that this blog post by Cesar Rodriguez of Cloud Security Musings was quite helpful, as well as this one by Chris Ayers . The issue is using Rego; I found a cool VS Code Extension; Terrascan Rego Editor , as well as several courses on Styra Academy; Policy Authoring and Policy Essentials . The big issue was figuring out how to tell Terrascan to follow a certain policy; I made it, put it in a directory, and ran the program while in that directory
Post a Comment
Read more

Building, Breaking, and Building A CRM with Retool

 I like no- or low-code solutions to things. I've often wanted to simply push a button or move some GUI around and have the code implement itself.  I've thought about building something that's like a customer relationship management (CRM) system for keeping up with my network better than my little spreadsheet where I click links and then go like something. The general idea in this CRM Development is:  To have a GUI to add people to a NRM (Network Relationship Management).       Attach it to a database (MySQL is what I went with eventually using Amazon Relational Database service, but you can use PostGRES, and probably others).     Make sure components are connected to each other in the retool interface. This video is a good start. Watching the tutorial video, heard some SQL commands and went 'Oh no 😳" before going "Wait I know basic SQL", which is good, because you'll see.  When you get set up, there's a plethora of resources you can use -- Incl
Post a Comment
Read more