{"resourceId":"denver-co-auditor-ai-governance-audit-nine-recommendations-20261023","versions":[{"version":"external-c5ea7484cc1866b2f77b5c939f6d3d9214880305f1dd5d7e9b7020ead5f5550f","resource":{"id":"denver-co-auditor-ai-governance-audit-nine-recommendations-20261023","title":"Denver auditor's AI governance audit: Technology Services agrees to nine fixes, from an AI inventory to defining AI security incidents, with most due in late 2027","organization":"City and County of Denver, Office of the Auditor and Technology Services","sector":"City IT governance and audit","geography":"Denver, Colorado, United States","publishedAt":"Agency response dated 6 October 2026; audit released 23 October 2026 (Denverite)","publicationDate":"2026-10-06","eventDate":"2026-10-23","sourceName":"Denver Auditor's Office","sourceLabel":"Government audit agency response document","sourceUrl":"https://denvergov.org/files/assets/public/v/1/auditor/documents/audit-services/audit-reports/2026/agency-responses/ts_artificial_intelligence_governance_response_template_10.05.26-final-ts-responses.pdf","evidenceClass":"government-audit","outcomeClass":"cautionary","topics":["governance-procurement","data-security","operating-model"],"finding":"Denver's auditor found that the city's Technology Services AI-governance framework needs improving, and the department agreed to all nine recommendations. They include a formal AI risk-management process, defining trustworthy AI using the NIST framework, tracking which vendors embed AI in their products, a complete AI inventory with an approved and denied list visible to all staff, organisation-wide AI data-protection controls, post-deployment performance reviews, and a written definition of AI security incidents such as prompt injection. Most target dates fall between October and December 2027; data-protection controls are due by 31 December 2026. Press coverage on 23 October said the airport has no AI framework at all.","sledRelevance":"Why now: the audit was released on 23 October. A large city that already runs resident-facing AI was told by its own auditor that basic governance plumbing, such as an inventory, vendor AI mapping and incident definitions, is not yet formalised.","evidence":"Official agency response listing each recommendation, agreement and target date. The audit's underlying test results were not in the opened document.","architectureImplications":"Asks for AI-risk mapping in vendor intake, including how AI systems interact with each other, and for the AI inventory to sit in the asset system of record.","governanceImplications":"Treats NIST AI RMF 1.0 as the minimum definition of trustworthy AI and requires performance metrics for AI that makes operational decisions to be available for stakeholder oversight.","securityPrivacyImplications":"AI data-loss-prevention controls are being deployed but have synchronisation issues; AI security incidents (prompt injection, model extraction, data exfiltration) are not yet defined in policy.","caveats":"Response document only; findings detail and airport response not opened. Long target dates mean gaps may persist through 2027.","streamIds":["local-government"],"roles":{"sales":"Framing: an auditor has now written the governance to-do list for a major city. Denver agreed to nine recommendations, from an AI inventory to defining AI security incidents, with most due by late 2027. Other cities will expect the same questions from their auditors. That supports bounded conversations about inventory, vendor AI mapping and monitoring, but this document says nothing about whether any AI tool worked, so it cannot support claims about savings or service gains.","engineering":"Framing: the recommendations are concrete engineering asks. Track every AI system and vendor-embedded feature in the asset system of record, map how AI systems interact, deploy AI data-loss prevention across the organisation, and define incident classes such as prompt injection and model extraction. Engineers should check what telemetry and asset data exist today, because the inventory and post-deployment monitoring depend on it. Delivery dates for data-protection controls come first, so DLP coverage is the earliest testable item.","delivery":"Framing: this is a multi-year remediation programme with dated commitments. Delivery would sequence data-protection controls first (due 31 December 2026), then incident definitions (April 2027), then risk management, inventory and output-impact policy (late 2027). Interpretation: tying each recommendation to a named owner, as Denver did, makes audit follow-up easier to evidence. Acceptance should mirror the auditor's wording. Progress reports to the auditor should show evidence, such as inventory exports and incident playbooks, rather than status claims."},"roleDetails":{"sales":{"customerProblem":"The city runs AI but lacks a formal risk process, complete inventory, vendor AI mapping and an AI incident definition, and its auditor is now tracking fixes.","stakeholders":["Chief AI and information officer","City auditor","CISO and data protection team","Enterprise architecture and AI director","Procurement","Airport business technologies leaders"],"discoveryQuestions":["Is your AI inventory in the asset system of record, and does it include vendor-embedded AI?","Which AI systems make operational decisions, and what metrics do stakeholders see?","Have you defined an AI security incident?","When is your next IT audit?"],"valueHypothesis":"Bounded: audit-ready governance tooling and processes could shorten remediation, but this source gives no cost or effort estimates.","potentialEngagement":"An audit-readiness review mapping current AI controls against the nine Denver recommendations, with a prioritised remediation plan.","unsupportedClaims":["That any Denver AI tool delivered or failed to deliver benefits","Remediation cost or timeline estimates","That NIST alignment satisfies an auditor"]},"engineering":{"fit":"Cities with several AI tools in production and a central IT or AI office.","architectureIntegration":"Inventory in the IT asset system of record; vendor intake captures AI features and system-to-system interactions; AI DLP across the tenant; post-deployment monitoring by an AI working group.","prerequisites":["Asset management system","Vendor intake workflow","DLP platform","Incident management process"],"constraints":["Colorado and city regulations still evolving","Target dates of late 2027","DLP synchronisation issues noted"],"security":"Define AI incident classes (prompt injection, model extraction, cyberattacks, data exfiltration, unauthorised access) and verify data-protection controls periodically.","proofOfValue":["Reconcile the AI inventory against procurement records","Test AI DLP rules on sample sensitive data","Run a tabletop exercise on a prompt-injection incident"]},"delivery":{"work":"Implement nine agreed audit recommendations covering risk management, regulation monitoring, trustworthy AI definition, output-impact policy, risk mapping, inventory, data protection, performance review and incident definition.","dependencies":["Auditor follow-up schedule","Technology Services staffing","Mayor's Office legislative team","Vendor cooperation on AI disclosure"],"ownership":"Denver Technology Services, with named points of contact per recommendation.","skillsAdoption":"Staff need clarity on allowable AI use; an approved and denied AI list visible to all employees supports that.","governanceCheckpoints":["AI data-protection controls by 31 Dec 2026","AI incident definition by 30 Apr 2027","Risk management, inventory and output policy by late 2027","Auditor follow-up review"],"acceptanceCriteria":["Proposed: 100% of AI systems and AI-embedding vendors listed in the asset system","Proposed: approved and denied AI list published to all staff and updated on a set cadence","Proposed: post-deployment review completed for each production AI system"],"risks":["Target dates slip beyond 2027","Inventory misses vendor-embedded AI","Airport remains without a framework"]}},"retrievedAt":"2026-10-23T22:11:48-05:00","enrichedAt":"2026-10-23T22:16:35-05:00","enrichmentBasis":"retrieved source","accessibilityWorkforceImplications":"Staff need clearer rules on allowable AI use; the audit asks for an approved and denied AI list visible to every employee.","procurementImplications":"Vendor intake must capture AI features embedded in products and how AI systems interact, so procurement becomes an AI risk control point.","operatingModelImplications":"Assigns named Technology Services owners to each recommendation and gives an AI working group responsibility for post-deployment review.","sourceVerification":{"openedUrl":"https://denvergov.org/files/assets/public/v/1/auditor/documents/audit-services/audit-reports/2026/agency-responses/ts_artificial_intelligence_governance_response_template_10.05.26-final-ts-responses.pdf","referenceExcerpt":"Technology Services should create procedures and processes for monitoring evolving AI regulations.","promptVersion":"sled-research-v4.0","model":null,"basis":"agent-reported inspection"}}}]}