Well, yet another data breach from yet another business that couldn’t afford top-shelf security, or didn’t understand the need for it. At this point, I think we should probably assume that all our data has been stolen, and it always will be.
We’ve focused for a long time on the idea of “let’s keep our information secure,” and it hasn’t been too long before we started to admit defeat with ideas like, “don’t use the same passwords on every site, so that if one is breaches, the others remain secure.” I think it’s probably time to move to an assumption that nothing can stop our data from being stolen.
That can actually change how you act.
For example, consider making everyone in our life invest in a password manager of some kind – even if, God help us all, that’s a paper journal you buy on Amazon. We really do need distinct passwords for each site, and they need to be phrases like “I-am-Using-Twitter-Right-Now-12345” or something. Forget 8 characters; make ’em long. Doing so makes it significantly harder for bad guys with hash tables to reverse-engineer your password, should they obtain hashes in a breach.
Press everyone to use tap-to-pay whenever possible, and kvetch to local merchants who don’t yet support tap-to-pay. NFC payment systems create a unique, per-transaction code that’s essentially useless anywhere else. If that number gets captured in a breach, it doesn’t matter. More websites need to start accepting Apple/Samsung/Whatever Pay as well, so that we’re not asking them to store permanent credit cards which will eventually be breached.
When asked to create “security questions” for account recovery (“what’s your mother’s maiden name?”), use a distinct, fake answer for each website, and note those in your password management tool or journal. For example, I’ve one website where my “mother’s maiden name” is DarthAvon. But there’s more you can do to protect yourself than making fun of Mom.Read More
As many of you know, Missy Januszko and I wrote The DSC Book some time ago. As we’ve moved on in our careers, we’ve not had the time to update the book – although we still feel it’s valuable and is worthy of being updated and expanded. So we’ve come up with a solution.
Effective immediately, The DSC Book is now an open-source project, “owned” by DSCCommunity.org. It remains available on Leanpub for a minimum price of $0, and if you choose to pay more, all proceeds go to The DevOps Collective‘s IT scholarship programs. The GitHub repo is public.
If you’d like to contribute to the book – and that includes noting any typos or other errors, as well as adding or updating material – please fork the repo, make your changes, and submit a pull request.
Missy and I want to thank everyone who supported us by purchasing the book, and we want to thank everyone who’ll contribute to the book’s contents in the future.
Yesterday’s post was in response to a colleague who’s been asked to speak at an upcoming conference panel. Part of the title of the panel is “Breaking Silos,” and I love that phrase.
A colleague was recently asked to speak at a conference panel, and one of the suggested talking points was, “How to evaluate new technologies for your business (e.g. set/lead or follow trends and standards?).”
In almost any instance like that, given a choice between X and Y, I almost always try to go with “Purple.”
Looks like DevOps Camp will be happening in July this year, and you can get all the details you might need, as well as sign up.
You might be wondering what Camp is all about.
Speedometers are fascinating devices. At least, the old mechanical ones used to be.
We live in a world where new tech is bring introduced all the time. How do you tell which ones are right for you to spend time learning about, adopting, and using? Here’s a simple list, and new tech pretty much has to check off 3 or more of these in order to have a shot at staying with us.
Looking for some therapy and was hoping you could help. We are mainly an on-premise Microsoft shop and I have been tasked to use system center orchestrator to orchestrate some of our more tedious tasks. The therapy part comes in with are there any more communities that even use SCORCH and how or what can I move my orchestrations over to?
On a I side note, I have been working SCCM for about 20years, nothing earthshattering but I help keep us up and running. So when I was task to start creating orchestration you and the ps community were a God send. Thank you so much for all the help you have already provide us all. Thank you.