Home About Speaking Framework Press Podcasts Field Notes Say Hello
The Cyber Resilience Report · Episode 5 · Part 2 of 3

From MSSP to MCOP, Part 2: The Aurora Story

with Michael Pegues, former CIO, City of Aurora

How the City of Aurora, Illinois moved from alert-driven support to continuous cybersecurity operations under the MCOP model — and what it saved.

← Previous: Part 1 Next: Part 3 →

The second part looks at the MCOP model in practice at the City of Aurora, Illinois, the state’s second-largest city. Michael Pegues describes what the partnership with Data Defenders changed — the city kept accountability while the heavy lift moved off its staff — and the savings, risk reduction and public trust that followed. Cyrus Walker explains why the government cybersecurity workforce has become a revolving door and how an MCOP provides staffing stability, and the two discuss how the same model scales down to smaller villages and townships.

Key takeaways

  • An MSSP is like hiring a security guard service. An MCOP is like hiring a chief security officer and their team to design the program, train staff, set policy and run the guards.
  • Aurora saved at least $5 million in the first year after adopting the MCOP model, with savings continuing in the years after.
  • The Aurora case study reports 35,331 threats detected, 351 high-severity attacks blocked, and zero major incidents.
  • Governments train cybersecurity staff who then leave for better-paid private-sector or federal roles. An MCOP brings its own staff, which ends that revolving door and keeps institutional knowledge in place.
  • Once an MCOP is built for a large city, adding a smaller village is simple. The real obstacles are budget, procurement and bureaucracy, not the technology.

← Back to Podcasts