Get Full Government Meeting Transcripts, Videos, & Alerts Forever!
Get email alerts on the Cybersecurity topic
No spam. Unsubscribe anytime.
Budget committee urges staff to bring cybersecurity cost options; avoids immediate allocation
Summary
Members pressed staff for detailed cybersecurity options and cost estimates but opted not to designate a specific dollar amount from the $467,000 unallocated funds, instead recommending that council consider the issue after staff returns with proposals.
Committee members identified cybersecurity as an important need and requested a staff presentation with cost options before allocating contingency funds.
Why it matters: several committee members and staff—citing the city's existing IT replacement set-aside—said the city needs more detail before committing any portion of the $467,000. The IT set-aside account contains $75,000 for equipment replacement; committee members suggested leaving general funds in contingency until staff (Greg, the IT lead) can present proposals, quotes and a recommended funding path.
Tyler told the committee that one administrative option is to place a not-yet-specified amount in an IT set-aside account and have staff return with quotes for council approval. Committee members expressed concern that an arbitrary early allocation could create the impression that a small amount solved the problem, only to discover later that costs were higher.
One committee member suggested using an executive session to discuss technical cybersecurity details prior to public action, to avoid putting sensitive security information on the public record. The committee did not approve any immediate allocation for cybersecurity; the committee's recommendation to place the unallocated $467,000 into council contingency preserves the council's ability to set aside an amount later after staff presents options.
Next steps: staff to prepare a cybersecurity options presentation with cost estimates and implementation timelines for council consideration.
