Private equity investments in public safety software leave rural fire departments with few affordable options

Fire department software may become too expensive 
for rural communities to buy. (Adobe Stock photo)

Rural fire departments have long relied on affordable software to track incidents and operations. But because of changes in software company ownership stemming from a flush of private equity investment "fire chiefs around the country are scrambling to manage shrinking options and soaring costs," reports Mike Baker of The New York Times.

Over the past decade, a handful of private equity firms have backed companies that are "aggressively investing in public safety systems, where tax dollars provide a steady source of revenue," Baker explains.

The fire-software services company, ESO, serves as an example. Investor dollars enabled ESO to buy up its competitors, shut them down, and push fire chiefs with few options to purchase ESO systems, which are priced significantly higher.

When the Norfolk Volunteer Fire Department in northern Connecticut learned ESO had acquired its former software system and was shutting it down, ESO offered Norfolk an alternative system that "would raise the community’s costs from $795 per year to more than $5,000," Baker reports. Norfolk Fire scrambled and found a cheaper competitor, but shortly thereafter, ESO bought that company, too.

Volunteer fire departments are common, comprising 85% of the roughly 30,000 fire departments across the U.S., and many already struggle to maintain staffing and equipment standards. Norfolk's fire department has turned to using "silent auctions and karaoke fund-raisers to help sustain operations," Baker reports.

ESO maintains that its cost increases support innovation. But ESO improvements may never reach most rural fire departments; in fact, climbing costs could push some back to using paper records.

Hackers who claim to be the 'Cyber Army of Russia Reborn' disrupt a water tower system in rural Texas

The FBI has been investigating the hack in Muleshoe, Tex.
(City of Muleshoe, Texas photo via CNN)

While the number of computer hacks on American businesses by foreign actors has steadily increased, a hack in Muleshoe, Texas, in January might be the "first disruption of U.S. water system by Russia," reports Ellen Nakashima of The Washington Post. A Muleshoe citizen drove past the town's water tower, saw it was overflowing and alerted the police. "Authorities soon determined the system that controlled the city's water supply had been hacked. . . . Thousands of gallons of water had flowed into the street and drain pipes."

The hackers, who identified themselves as the Cyber Army of Russia Reborn, "Posted a video online of the town's water-control systems showing how they reset the controls," Nakashima writes. Using the messaging platform Telegram, the hackers posted a caption that read, "We're starting another raid on the USA." The hackers proceeded to explain how they were going to target U.S. infrastructure.

Location of Muleshoe, Tex., pop
5,200 (Wikipedia map)

Experts from the cyber security firm Mandiant believe "that the water tank overflow in a Texas panhandle town may well be linked to one of the most infamous Russian government hacking groups," Nakashima reports. "If confirmed, analysts say it would mark a worrisome escalation by Moscow in its attempts to disrupt critical U.S. infrastructure by targeting one of its weakest sectors: water utilities."

The notorious Russian hacking group, nicknamed "Sandworm, has achieved notoriety for briefly turning out the lights in parts of Ukraine at least three different times; hacking the Olympics Opening Games in South Korea in 2018; and launching NotPetya, one of the most damaging cyberattacks ever that cost businesses worldwide tens of billions of dollars," Nakashima explains.

Muleshoe's city manager, Ramon Sanchez, told Nakashima, "You don't think that's going to happen to you. It's always going to happen to the other guy." Nakashima reports, "Sanchez said the hackers brute-forced the password for the system's control system interface, which was run by a vendor. That password hadn't been changed in more than a decade."