Municipal cybersecurity audit: scope, preparation, and deliverables

Scope a municipal cybersecurity audit, prepare evidence without exposing resident data, and turn findings into an action plan for essential services.

01

Start with resident services

If the permit portal goes offline on Monday morning, who can accept an application at the counter? How long before staff lose track of cases? These questions are a better starting point than counting patched workstations. A municipal cybersecurity audit connects a service, its dependencies, and evidence that its safeguards work.

This guide is for municipal leadership, IT managers, and service owners in Quebec. Adapt the engagement to local needs. Its purpose is to decide which risks to address and what work to fund; it does not grant certification.

02

Define scope before requesting quotes

Give bidders the same service list and require explicit exclusions. For each service, name an owner, users, suppliers, fallback procedures, and the consequence of an outage. Agree on sites, environments, dates, permitted methods, and stop conditions.

Distinguish document review, configuration assessment, and penetration testing. An interview with a portal provider does not authorize testing its platform. If the contract only provides access to a control report, state that limitation in the scope.

03

Prepare evidence without exposing residents

Request a dated network diagram, critical application inventory, contract owners, remote access rules, incident procedures, and recent restore exercise reports. Identify who maintains each document and what period it covers.

Use restricted encrypted sharing, a screen demonstration, or a redacted export. A role list is often enough to examine privileges; do not request passwords, recovery keys, mailbox contents, or resident files. Agree on a retention period and who will delete working copies.

04

Separate administrative IT from operational systems

For a pumping station or building control system, start with the operator: review data flows, maintenance access, local procedures if connectivity fails, and power dependencies. Mistakes can affect a physical process. Authorization for an office IT assessment should not trigger active scanning, restarts, or failover tests.

Fictional example: a contractor demonstrates that maintenance access uses a VPN. Ask who approves each session, which equipment it can reach, and how access ends when the contract expires. If only the VPN configuration is available, draw conclusions about VPN access and record controller permissions as unverified.

05

Test controls with an explicit sample

Follow concrete workflows: employee onboarding and departure, a vendor intervention, a file restore, and suspicious email reporting. Connect each item of evidence to a question. For a departure, compare the approved request, actual account disablement, and residual access to an outsourced application.

Record dates, the population, and sample selection. Three properly processed departures demonstrate performance in those cases, not across every account. Missing evidence calls for follow-up; it does not prove a control is absent.

06

Ask for four usable deliverables

Request a leadership brief, risk register, restricted technical appendix, and action plan suitable for costing. The brief should explain service impacts and funding decisions. The register should separate observed facts, assumptions, and limitations.

Fictional example: the permits team expects service recovery within eight hours. Backup jobs show success, but nobody can produce a timed restore result. The defensible finding is “recovery time unproven.” Restore in isolation, time the exercise, and have the permit manager open a test case. The closure evidence is the signed exercise record, not a software invoice.

07

Turn findings into decisions

As an example, assign owners and deadlines to priority risks within 30 days. By day 60, run approved tests and obtain estimates for larger projects. By day 90, report closure evidence, remaining gaps, and risks leadership explicitly agrees to defer. Adapt timing to peak service periods.

A targeted Microsoft 365 or Active Directory assessment can examine identities and privileges in more depth. It does not automatically cover municipal service continuity, industrial systems, or vendor contracts. Have the proposal define that boundary.