From the Local Government edition of October 18, 2026
Smart Cities Dive (15 Oct 2026): UserEvidence/SolarWinds survey finds only 19% of state and local IT pros report an active AI oversight framework while ~80% say adoption aligns with oversight planning
UserEvidence survey commissioned by SolarWinds (reported by Smart Cities Dive) · State and local government IT governance survey · United States and United Kingdom public sector (state/local breakouts reported)
- Publisher
- Smart Cities Dive
- Original publication
- October 15, 2026 (Smart Cities Dive); underlying SolarWinds press release dated September 22, 2026
- Source retrieved
- 2026-10-19
What happened
Smart Cities Dive reported on 15 October 2026 that a UserEvidence survey for SolarWinds of more than 800 U.S. and U.K. public-sector IT professionals found a gap between perceived and actual AI governance. Nearly 80% of public-sector IT leaders said AI adoption aligns with oversight planning, yet only 37% reported a formal, actively enforced AI governance framework; among state and local respondents, only 19% reported an active AI oversight framework and 20% said any such framework exists. Thirty-five percent said they are loosening security or compliance restrictions to enable AI access; nearly 45% reported rising AI-related security incidents year over year. State and local respondents were mostly methodical (68%) rather than aggressive (12%) on adoption. Generative AI dominates (77% using or piloting Copilot/ChatGPT/Gemini); 35% report using or piloting agentic tools. Why now: Dive’s 15 October write-up emphasises state/local breakouts not highlighted in earlier vendor coverage and is new to the archive.
Why it matters
Quantifies the governance confidence gap for state and local IT audiences that SLED buyers and overseers keep citing anecdotally—useful when arguing for enforced frameworks before scaling copilots or agents.
Evidence and measured results
Smart Cities Dive article opened via WebFetch (curl HTML was a JS/cookie wall). SolarWinds 22 Sept press release opened for commissioning context; full survey methodology PDF not independently re-analysed beyond figures quoted in Dive.
Limitations and uncertainty
Vendor-commissioned survey (SolarWinds); trade-press secondary report. Exact sampling frame and question wording beyond Dive’s summary not verified here. Press release dated 22 Sept; Dive article is the freshness hook.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-10-18; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- Local-government leaders believe AI oversight is keeping pace when enforced frameworks are often absent.
- Stakeholders
- CIO/CISO
- City/county manager
- Audit/oversight committee
- Agency AI owners
- Procurement
- Discovery questions
- Do you have a formal, actively enforced AI governance framework?
- How is employee AI use monitored for adherence?
- Are AI-specific security policies in place?
- Have AI-related incidents risen, and are they tracked?
- Value hypothesis
- Closing the confidence-to-controls gap may reduce unowned risk before scaling copilots/agents; survey is descriptive, not causal.
- Potential engagement
- Governance-gap assessment mapped to framework, adherence monitoring and AI security policy pillars.
- Unsupported claims
- That SolarWinds tooling is required to close the gap
- Causal link from survey answers to breach outcomes
- Representativeness beyond the sampled IT professionals
Pre-sales engineering
Role takeaway
- Fit
- Environments where genAI is piloted but not yet in standard monitoring or zero-trust scope.
- Architecture and integration
- AI tool inventory in monitoring; policy enforcement points; incident taxonomy for AI-related events.
- Prerequisites
- Written enforceable AI framework
- Owner for adherence monitoring
- Baseline of AI-related incidents
- Constraints
- Pressure to loosen security for access
- Vendor-commissioned evidence base
- Federal vs state/local maturity differences
- Security
- Do not trade away compliance controls to unlock AI; track AI-related incidents explicitly.
- Proof of value
- Percent of AI tools in standard monitoring
- Documented enforced framework
- Incident trend with AI tag
Delivery
Role takeaway
- Work
- Inventory AI use, adopt/enforce framework, wire monitoring and incident processes, brief overseers.
- Dependencies
- CIO/CISO
- Agency owners
- Audit
- Security operations
- Ownership
- CIO/CISO with named agency AI owners.
- Skills and adoption
- Adherence monitoring, AI incident playbooks, overseer briefing literacy.
- Governance checkpoints
- Framework adoption
- Monitoring coverage review
- Quarterly incident trend to audit committee
- Acceptance criteria
- Proposed: active framework documented and enforced
- Proposed: >80% of known AI tools in monitoring
- Proposed: AI incident category live in ticketing
- Risks
- Survey misread as product justification
- Continued control-loosening
- Agentic pilots without oversight
- Over-generalising U.K./U.S. pooled results
Implementation considerations
Lighthouse Advisory interpretation across the operating dimensions a public-sector buyer must settle before this evidence becomes a design. Each note answers the question under its heading for this specific source.
Architecture and integration
What must connect, and where does the AI sit in the workflow?
Survey implies monitoring and zero-trust gaps: fewer than 40% fully integrate AI tools into standard monitoring; U.S. zero-trust fully implemented for only 24% of respondents.
Governance
Who approves, reviews and stays accountable for outcomes?
Confidence without enforced frameworks and inconsistent employee-adherence monitoring create unowned risk; SolarWinds advisor quote frames the gap as where risk accumulates.
Security and privacy
What data, permissions and controls need testing?
Loosened controls for AI access coexist with rising AI-related incidents; agentic tools (35%) raise autonomous-action risk without matching oversight rates.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Skills and complexity barriers to zero trust cited; headcount/budget growth not closing specialised AI/security expertise gaps per press-release context.
Procurement
What should contracts, pricing and exit terms secure?
Buyers claiming governed adoption may lack enforceable frameworks—diligence should request framework artefacts, not attestations alone.
Operating model
Which teams own the service once it runs?
Methodical local-government adopters still report thin active oversight; genAI tooling outpaces monitoring integration.
Publication history
- 2026-10-18Local Government · Issue 436 resources
Stable resource ID: smart-cities-dive-userevidence-solarwinds-ai-governance-gap-20261015