In July 2025, York City, Pennsylvania faced every municipal leader's nightmare. Ransomware brought the city to a standstill - email down for two weeks, parking systems offline for three, financial audits pushed even further behind. Hackers demanded $1 million. Negotiators settled at $500,000, paid by insurance. The city's deductible was $25,000. But the real cost? Staff diverted for weeks, lost parking revenue, damaged public trust, political fallout. While York City's story made headlines, it wasn't an outlier. It was a preview of what's coming to a municipality near you.
In our work responding to ransomware incidents across Pennsylvania and beyond, we've seen this pattern repeat: preparation matters enormously, and most municipalities don't have it. This is not fear-mongering. It's math. And you need to understand it before the screens go black.
I started writing SSP’s (System Security Plans) well before the original Executive Order mandated deadline of December 31st 2017 and have since written at least 50 SSP’s for defense contractors of every imaginable type and size. There wasn’t a lot of guidance on how to do this at that time, other than to have a very thorough and complete understanding of the nearly 500-page NIST 800-53 framework.

