IT that keeps board records public, bond funds on target, water flowing safely.IT that keeps boardrecordspublicbondfundsontargetwaterflowingsafely
Districts run through contractors. We give your board one clear security baseline that every contractor works within.
Special districts and MUDs
A public body run by contractors
A utility district looks small on paper: a board, a website and a handful of service providers. But it collects public money, issues bonds, runs water and sewer systems and keeps public records. When nobody owns IT, those responsibilities spread across personal inboxes and vendor systems. Here’s how that goes wrong and how we fix it.
01 · The pressure
Public money and water service, few employees
Residents expect clean water, working sewer lines and accurate bills. Contractors running construction expect timely payments from bond proceeds. The board approves invoices at monthly meetings, and the bookkeeper releases funds. Directors trade emails about agendas, contracts and disputes. All of it is public business. A diverted payment or a compromised water plant connection hurts residents directly, and the board answers for it at the next meeting with the public watching.
- Bond-funded construction paid by wire
- Board business conducted largely by email
- Water and sewer service residents depend on
Microsoft 365QuickBooks OnlineBadger Meter BEACONSensus FlexNetNeptune 360Esri ArcGIS
02 · How it breaks
Personal inboxes and fake contractor invoices
District incidents usually start outside the district’s own systems. A director’s personal email gets phished, and the attacker learns which contractor is due a large payment. Someone then emails the bookkeeper from a lookalike domain with new bank details. Or the water operator’s remote access to plant controls uses a shared password and no MFA. District files sit in a former director’s personal cloud account, and the website runs on an unpatched plugin.
- Phished personal email of a director
- Lookalike contractor domains and new bank details
- Shared passwords on operator remote access
Microsoft 365QuickBooks OnlineBadger Meter BEACONSensus FlexNetNeptune 360Esri ArcGIS
03 · What we change
District-owned accounts and verified payments
Directors get district-owned email accounts with MFA, so public business stays in one place the district controls and can search. Board documents move to managed storage with retention. We help the board adopt a written payment-change rule the bookkeeper follows: verify by phone with known contacts, and require board-level approval for changes. With the operator, we secure the boundary around plant controls, replacing shared remote access with named, logged sessions.
- District email and storage for every director
- Written payment-change rule for the bookkeeper
- Named, logged remote access for the operator
Microsoft 365QuickBooks OnlineBadger Meter BEACONSensus FlexNetNeptune 360Esri ArcGIS
04 · The after
A board that can show its homework
When a resident files a records request, the district’s attorney can pull email from district accounts instead of asking directors to search personal inboxes. Contractor payments follow a rule everyone knows. The operator’s access to plant controls is logged and reviewable. If the system is large enough to need AWIA assessments, the IT and cybersecurity portion is documented. Directors leave the board without taking district files with them.
- Records requests answered from district accounts
- Contractor payments verified every time
- Operator access logged and reviewable
Microsoft 365QuickBooks OnlineBadger Meter BEACONSensus FlexNetNeptune 360Esri ArcGIS