DiscoverThe Backup Wrap-Up
The Backup Wrap-Up

The Backup Wrap-Up

Author: W. Curtis Preston (Mr. Backup)

Subscribed: 37Played: 1,512
Share

Description

Formerly known as "Restore it All," The Backup Wrap-up podcast turns unappreciated backup admins into cyber recovery heroes. After a brief analysis of backup-related news, each episode dives deep into one topic that you can use to better protect your organization from data loss, be it from accidents, disasters, or ransomware.  

The Backup Wrap-up is hosted by W. Curtis Preston (Mr. Backup) and his co-host Prasanna Malaiyandi. Curtis' passion for backups began over 30 years ago when his employer, a $35B bank, lost its purchasing database – and the backups he was in charge of were worthless. After miraculously not being fired, he resolved to learn everything he could about a topic most people try to get away from.  His co-host, Prasanna, saw similar tragedies from the vendor side of the house and also wanted to do whatever he could to stop that from happening to others.

A particular focus lately has been the scourge of ransomware that is plaguing IT organizations across the globe.  That's why in addition to backup and disaster recovery, we also touch on information security techniques you can use to protect your backup systems from ransomware.  If you'd like to go from being unappreciated to being a cyber recovery hero, this is the podcast for you. 
371 Episodes
Reverse
Microsoft 365 backup is something a lot of people still think they don’t need, and KPMG learned the hard way why that’s wrong. In August 2020, one admin tried to change the Teams retention policy for a single user and instead wiped out the private chat history of 145,000 employees. Microsoft couldn’t bring it back.This is an encore episode. We brought it back because it’s one of the most popular episodes we’ve ever done, and not just in downloads. People listened to most of it, and some came back for more. It’s the first of seven episodes in our Cloud Disasters encore series. I recorded a new intro that ties it to November’s massive Microsoft outage. An outage is annoying. Losing your data is a whole different story.Prasanna and I walk through what happened at KPMG and how it happened. The feature that deleted all that data was a retention policy. Some people point to that exact feature as the reason you don’t need Microsoft 365 backup. Retention policies are built for compliance and e-discovery. They’re good at keeping data you’re supposed to keep, and they’re good at making data disappear on schedule. What they can’t do is restore your stuff to a point in time. Get them wrong and they’ll delete everything.We also talk about:the retention lock checkbox that would have saved KPMG’s old chats, and what it does to your storage billwhy this could just as easily have been every email or SharePoint file in the companythe legal mess when “our admin made a mistake” lands in the middle of pending litigationa Valentine’s Day phishing test that made an entire company feel loved for about five minutesIf you’re on the fence about Microsoft 365 backup, listen to this one. If you’re not, send it to someone who is.Chapters00:00 Encore intro: an outage vs. losing your data01:34 Imagine every Teams chat disappearing03:22 Welcome to the show05:24 Why hardly anyone backs up Microsoft 36509:01 What happened at KPMG11:29 How Microsoft 365 retention policies work15:19 Retention is for compliance, not recovery18:08 How the deletion probably happened21:51 What KPMG should have done24:27 What Reddit and The Register had to say26:27 It could have been email or SharePoint28:04 Why not just delete the user?29:07 Adverse inference and the legal fallout31:24 The cloud isn’t magic32:49 Humans are still the #1 reason we back up33:52 A Valentine’s Day phishing test gone wrong36:16 Advice for smaller companies
Credential theft is how one stolen laptop turns into a full-blown breach. In this episode, Prasanna and I sit down with Dr. Mike Saylor to walk through how it happens and how to stop it.Mike opens with a story that should make every IT person wince. A credit union employee had a logged-in laptop at a coffee shop, turned around, and it was gone. BitLocker didn’t help, because the machine was unlocked. The attackers harvested local credentials, learned how the credit union’s business processes worked, and then phished other employees from the inside while posing as the person who lost the laptop.From there we get into how attackers think. Their first move is reconnaissance: what do I have, what’s it worth, and how do I keep access before somebody wipes it? Mike explains why the victim has about 30 minutes to respond, why a fear-based culture makes that window worse, and why you need a documented stolen-laptop playbook before you need it.We also cover the stuff that makes credential theft so easy. Shared local admin passwords. Predictable new-user passwords with an exclamation point on the end (yes, really). Service accounts whose passwords never change. Default SNMP strings. Mike explains Kerberoasting in plain English and shares new research on how an unprotected printer can lead to a complete network takeover.Then we talk about how to prevent credential theft. That means LAPS or a similar tool for unique local admin passwords, just-in-time credentials that expire on their own, tiered administration, and separate user and admin accounts for every admin. Mike tells the story of a database admin who deleted something in production because her test and production credentials were the same. We finish with alerting: what to alert on, why you’ll get a flood of false positives at first, and why my new freezer sensor proves the point.If you manage credentials for anyone, this one’s worth your time.Chapters00:00 - Intro01:49 - Welcome, Prasanna, and too many Reacher books03:37 - Dr. Mike Saylor joins04:07 - The stolen credit union laptop05:42 - Reconnaissance and persistence: what attackers do first08:31 - Privileged credentials that never change10:36 - The 30-minute window after a stolen laptop13:19 - Security culture and automated incident response15:06 - Shared local admin passwords17:23 - Predictable default passwords18:20 - What attackers harvest: everything19:01 - Kerberoasting explained24:01 - Default credentials and the printer problem25:22 - When the proof of concept becomes production26:46 - The Brocade Silkworm story28:07 - LAPS and just-in-time credentials30:30 - Tiered administration and separate admin accounts35:00 - Alerting on authentication events36:10 - Expect false positives (and my freezer)39:16 - Alert fatigue vs. alert annoyance41:27 - Wrap-up
Network segmentation best practices can be the difference between ransomware taking out one laptop and ransomware taking out your whole company. Prasanna, my co-author Dr. Mike Saylor, and I talk about how to stop running a flat network, what VLANs and microsegmentation actually do, and where you should start.Mike and I wrote Learning Ransomware Response and Recovery around one basic idea: assume breach. You’re probably going to get hit, so the real question is how big the blast radius will be. Is it a plop, or does it take out the whole building?We start with the old hard, crunchy exterior and soft, chewy interior model, and why so many billion-dollar organizations still run flat networks. Spoiler: laziness, budget, and management decisions all play a part. Mike explains VLANs with a hotel key card analogy that will make sense to those who aren’t network people. Then we take it a step further into microsegmentation, where access is based on what you’re there to do instead of where you’re plugged in.Then we talk about:Get buy-in from on high.Inventory everything.Tag your workloads and build policy around those tags.Start with your crown jewels and work your way out. That means the stuff with tight RTOs and RPOs, plus the stuff you really don’t want ending up on the internet.Roll it out in phases instead of trying to rebuild everything in a day.Document every single rule, or the next guy will tear it all down and go flat again.We also talk about why IT shouldn’t be the one deciding what’s critical (that’s what a business impact analysis is for) and how to wall off your backup network. You’ll also hear about the night before Y2K when the security team blocked my NetBackup ports one too many times and I lost it. And Mike explains how he used network segmentation to win an argument with a teenager.If you’re a backup person who’s never had to think much about the network, this one’s for you.Chapters:00:00 – Intro01:26 – Welcome, Prasanna and Dr. Mike Saylor02:41 – My first client with firewalls on the inside04:43 – Assume breach and the blast radius06:24 – Grenades, house locks, and panic rooms08:41 – What a flat network looks like09:42 – Why so many companies still run flat networks10:18 – VLANs explained with a hotel analogy13:22 – Going further with microsegmentation14:51 – The management overhead problem15:15 – Why undocumented segmentation falls apart18:45 – Leadership buy-in and starting with inventory20:07 – Rolling it out in phases21:16 – Tags, policy, and allow rules22:56 – Default deny (and Mike says “it depends”)24:00 – Start with your crown jewels28:18 – Why IT shouldn’t decide what’s critical30:38 – The night I lost my mind over segmentation33:00 – Monitor traffic and wall off your backup network34:35 – Final thoughts, home networks, and the chicken coop36:04 – Mike’s teenager gets her own segment
Application whitelisting best practices can stop malware your antivirus never sees coming, but almost nobody follows them. Dr. Mike Saylor joins Prasanna and me to talk about why, and what it really takes to build an approved software list that sticks.We start with SocGholish, a fake browser update campaign that’s been around since 2018. Every download is built just for the victim, so pattern-based tools can’t spot it. That’s exactly the kind of threat an approved software list shuts down.Then we get into the hard part. You have to inventory every application in your environment, figure out who needs what, decide who pays for it, and build a process for exceptions. Mike explains why politics and overhead keep most companies from doing it. He also explains why shadow IT means your procurement process probably isn’t catching what you think it is.We compare whitelisting with the simpler option of not letting users install software at all. We also talk about AppLocker, EDR policies, Office macros, MDM for mobile devices, and blocking executables in temp directories. Prasanna asks whether AI can take some of the friction out of software approvals, and Mike gives him a one-word answer. I also share a tip that makes the inventory step a lot less painful: run your whitelisting tool in audit-only mode first and let it build the list for you.We wrap up with the good, better, best versions of this control. I tell a story about an old boss, Perl, and a bank policy that ended with him getting fired. And there’s a reminder that you will always need support from the top. Someone will always think they’re the exception, and senior management has to be willing to tell them they’re not.If you’ve ever wondered whether locking down software installs is worth the fight, this episode is for you.Chapters:00:00:00 – Intro00:01:30 – Welcome, Prasanna and Dr. Mike Saylor00:02:37 – SocGholish and fake browser updates00:04:57 – How often do companies really whitelist?00:05:18 – Inventory, licensing, and exceptions00:07:08 – Shadow IT and the $30 NDA00:10:08 – Who actually does this00:11:01 – Politics and overhead00:12:12 – Just don’t let users install software00:14:37 – AppLocker and EDR policies00:15:47 – Can AI reduce the friction?00:17:08 – Layered responses to a single threat00:18:47 – Office macros and click-through users00:20:49 – Is whitelisting a silver bullet?00:21:29 – Signatures and the ideal whitelisting process00:25:41 – Mobile devices and MDM00:28:44 – Temp directories and executables00:31:55 – How do you learn what you don’t know?00:33:19 – Audit mode as your inventory00:35:05 – AI agents, integrations, and CoSnitch00:38:07 – Good, better, best00:40:33 – The Perl story00:43:21 – Final thoughts
Building an incident response team is something you do before the incident, not during it. Prasanna, Dr. Mike Saylor, and I walk through who needs to be on that team, why each person matters, and how to get them lined up now so nobody’s scrambling when ransomware hits.We’re back after a few weeks off, and we came back with a topic I care a lot about. When I cracked a rim on my Tesla, I didn’t watch YouTube videos and grab a wrench. I called a team of people who know tires. Your cyber incident deserves the same treatment. Mike puts it plainly: you don’t want to be recruiting people when the house is on fire.We cover the core roles. There’s the incident commander, who keeps the business off the backs of the people putting out the fire. There are the subject matter experts on the tech side. And there’s the executive sponsor, who makes the calls you’re not allowed to make. We talk about why legal, compliance, PR, and finance need a seat at the table. We also explain why “there is no evidence customer data was accessed” is a very different sentence from “customer data was not accessed.” (Looking at you, LastPass.)Then we get into the outside help: your cyber insurance carrier, a third-party incident response firm with a retainer already signed, law enforcement, and your vendors. Mike explains what the FBI will and won’t do for you. He covers why you can’t just pay a ransom to anyone on the OFAC list, and why calling Bob on a Sunday is not a plan.If your current incident response plan is “we’ll figure it out,” this episode is for you. Listen in, then go write down some names.Chapters:00:00 Cold open01:30 We’re back (and Gemini let me down)03:27 Why you need a team, not YouTube University04:29 Know your team before the house is on fire07:43 Fire crews, training, and the USS Constellation09:27 Incident response is a business problem12:02 Core roles: leaders and subject matter experts14:14 Executive sponsors and who comes back first16:09 Asset lists, owners, and pre-authorization17:11 Incident commander vs. incident leads20:00 Legal, compliance, and attorney-client privilege22:59 PR and the LastPass problem24:47 Finance and cyber insurance27:07 Third-party incident response teams and retainers32:06 Bringing in law enforcement33:48 Sanctions, Bitcoin, and paying the ransom38:05 Vendors who answer the phone on a weekend39:34 Write it down and name your deputies40:20 Tabletop exercises43:06 Wrap-up
loading
Comments