
Sign up to save your podcasts
Or


With Microsoft and the FAA dealing with major outages last week, and our recording platform apparently deciding to join the party, we're pulling an episode from the Get NIST-y archives.
Back in January, Mike and Jared talked about what "continuous" monitoring actually means for MSPs, particularly when you've got legacy equipment, unknown dependencies, and systems that don't necessarily appreciate being poked.
We also get into vendor monitoring and how much oversight is actually reasonable for a small business.
It's a slightly different conversation from last week's outages, but the underlying problem is the same: how do you keep systems secure without breaking the things you're trying to protect?
Originally aired January 27, 2026.
Have your own questions? Get them answered at https://blacksmithinfosec.com/ask
Your client bought a company, didn't tell you, and wants everybody working by Monday. Mike and I talk through what actually needs to happen first, with a little disagreement about whether your QBRs should have caught this. We also get into who owns compliance when the client's answer is basically, "You do our IT, so you handle it."
Get NIST-y is Blacksmith InfoSec's cybersecurity and compliance podcast for MSPs and SMBs.
- Get people the limited access they need while you assess the acquired environment.
- Sort out who supports which users when the old IT provider and the new one are both involved.
- Assign a client-side owner who can make risk decisions and hold executives accountable for training.
We answer:
- How do I explain that handling IT doesn't mean I can own my client's compliance decisions?
- My client bought a company and wants everyone connected by Monday. Where do we start?
Free, open source shared responsibility matrix generator mentioned in the show: https://srm.blacksmithinfosec.com/
Listen, follow Get NIST-y, and send us a question: https://blacksmithinfosec.com/nisty/
Another questionnaire lands in your inbox, and apparently that's included in the monthly fee now. Then there's the backup job that says it succeeded, right up until someone needs a restore. Mike and I talk through getting paid for compliance work and testing backups without turning it into a full-time job.
- Define what's included in the client's order form or scope of work.
- Help with questionnaire answers without making claims about apps you don't manage.
- Rotate restore tests across clients, and ask where the backups live. Another vendor can still mean the same data center.
- Test the failure alerts, too. Make sure a failed job actually creates a ticket, sends an email, or pages somebody.
We answer:
- How should MSPs charge for compliance work clients assume is included?
- What's a realistic backup-testing approach across 50 clients?
Make sure to follow the podcast or ask your own questions at:
https://blacksmithinfosec.com/nisty/
The client bought the AI tool, the MSP enabled it, and six months later nobody can say who approved what. Ignacio sent us a question about who owns those settings and what needs to be in writing. Then we get into when a client is too risky to keep, because you won't have much of a business left if you fire everyone who makes a decision you don't like.
- Approving an AI tool doesn't approve every connector. Different data means another risk conversation.
- Get written approval from someone with authority, and agree on when to revisit the decision. Don't leave a risk marked "accepted" forever.
- Ask why the client is refusing. Replacing an elevator system and buying an MFA security key are very different budget problems.
We answer:
- Who should approve AI settings, the MSP or the client, and what evidence should the MSP keep?
- When is a client too risky to keep, even after they've signed off on the risks?
We also share our IT Nation Connect Global plans: Rocket Fuel Factory's pre-day, PitchIT, and a couple of speaking sessions. Check it out at https://rff.events
Make sure to follow the podcast or ask your own questions at:
https://blacksmithinfosec.com/nisty/
Blacksmith InfoSec, Lemhi, and Synthreo are the three PitchIT finalists headed to the stage at IT Nation Connect.
So naturally, we invited John Harden and Callen Sapien onto Get NIST-y and tried to start a fight.
It...sort of worked.
John, Callen, Mike, and Jared get into AI liability, agent rot, whether MSPs actually understand their clients’ businesses, why the industry might be a little too addicted to recurring revenue, vendor due diligence, the usefulness (or uselessness) of SOC 2, and the danger of trusting a green check mark just because a tool gave it to you.
There are disagreements. John repeatedly claims he isn’t spicy while being spicy. And somehow we end up talking about AI agents, long-distance phone bills, toll fraud, and letting our tools break out of their cages before PitchIT.
The fun part is that this is what “competition” looks like when the competitors actually like each other.
Friends first. Competitors 97th.
Come November, though? Somebody still has to win.
Make sure to follow Get NIST-y or ask your own question at:
https://blacksmithinfosec.com/nisty/
Your client asked you to delete an ex-employee's data. The mailbox is gone, but copies are still sitting in backups. So what exactly did you just promise?
Jared and Mike talk deletion, retention and the limits of "storage is cheap" on Get NIST-y, the cybersecurity and compliance podcast for MSPs.
- Deleting active data versus letting copies age out of immutable backups.
- Why keeping unnecessary data means more could be exposed in a breach.
- How a one-year email archive rule can disrupt an 18-month sales cycle.
We answer:
- What should an MSP promise when a client asks for data to be deleted?
- How do you help a small business decide what to keep without pretending to be its lawyer?
Make sure to follow the podcast or ask your own questions at: https://blacksmithinfosec.com/nisty/
Your client knows about the security gap. They understand the recommendation. And they still say no.
Now what?
This week on Get NIST-y, Jared and Mike talk about when risk acceptance is legitimate, when it still means the client isn't compliant, who actually has authority to sign off on company risk, and why compensating controls and policy exceptions need to be reviewed instead of becoming permanent infrastructure.
Because a “risk-based approach” doesn't mean every risk magically gets fixed. It means somebody understands the tradeoff, makes the decision, owns it, and documents the hell out of it.
Want to get your own questions answered? Head over to https://blacksmithinfosec.com/ask
Following NIST or CIS is useful, but does it prove your MSP can actually operate under pressure? Chris "CJ" Johnson from GTIA joins us to talk about the Cybersecurity Trustmark, what security maturity looks like in practice, and why proof of controls is not the same as mature governance.
Takeaways:
We answer:
Make sure to follow the podcast or ask your own questions at:
https://blacksmithinfosec.com/nisty/
Antivirus, backups, and MFA are a start. They won't tell you how payroll runs when the check printer is inaccessible or keep your risk register current six months later. This week, Jared and Mike talk about what a small business actually needs and how to keep that work going.
- Identify the client's critical data and the processes that keep the business running.
- Check the less obvious dependencies, from break-glass accounts to the payroll check printer.
- Use CIS Implementation Group 1 as a starting point, then keep improving.
- Schedule user audits, policy reviews, and risk assessments as recurring work.
We answer:
- What should a 50-person company with antivirus, backups, and MFA be doing repeatedly to have a minimum viable security program?
- How do you keep that program alive when policies go stale, evidence goes missing, and nobody updates the risk register?
Make sure to follow the podcast or ask your own questions at: https://blacksmithinfosec.com/nisty/
It started with one questionnaire. Now you're the compliance department, and apparently that's included in the flat rate. On Get NIST-y, Blacksmith InfoSec's cybersecurity and compliance podcast for MSPs, we're talking about who owns the program and who pays for the work.
- Name one executive owner at the client before work starts. Your day-to-day contact doesn't have to be that person.
- Check the contract before charging for new work. Catching up on patching you already owed is different from adding a managed compliance service.
We answer:
- Our client wants to "get compliant," but every task comes back to us. When do we insist on an internal owner?
- How do we keep questionnaire help from turning into unlimited compliance work under a flat-rate MSP agreement?
Make sure to follow the podcast or ask your own questions at:
https://blacksmithinfosec.com/nisty/