Enhance Security of Office of Information Technology
Concerning measures to enhance the office of information technology's security procedures.
Official status: Became Law
Prime sponsors
- Janice Marchman (Senate) — Prime Sponsor
- Mark Baisley (Senate) — Prime Sponsor
- Brianna Titone (House) — Prime Sponsor
- Rebecca Keltie (House) — Prime Sponsor
Progress (from the official record)
Official summary
Official text — shown in English exactly as published by the official source. The official text controls.
The act allows the joint technology committee (JTC), within 90 days after the day that the chief information security officer of the office of information technology (security officer) files a written information technology security compliance report (compliance report) with the JTC as required by the act, to vote to request that the legislative audit committee direct the state auditor to conduct a special information technology security audit (IT security audit) of the office of information technology (OIT) if the compliance report indicates that one or more audit recommendations made by the state auditor is unresolved 2 or more years past the implementation date for the audit recommendation or if a material discrepancy exists between a representation in the compliance report and a previous audit finding. If the JTC votes to request an IT security audit and if the legislative audit committee votes to direct the audit, the act requires: The state auditor to conduct the IT security audit; The state auditor to obtain input from OIT when the state auditor determines the scope and boundaries of the audit; The state auditor to submit the IT security audit report to the legislative audit committee, the JTC, the joint budget committee, and the governor; and OIT to reimburse the state auditor for the auditor's costs incurred in completing the IT security audit. The act requires OIT to establish, maintain, keep, update, and make available to state agency information technology leadership and the members of the JTC a list of all active information technology vendor contracts for state agencies. The act specifies that, except in the case of an information technology security emergency, OIT shall not publish or implement a technical information technology standard, and that the standard is void, unless the standard: Was publicly posted; and Received approval from the security officer if the standard relates to security, access controls, or the handling of data. The act requires OIT to ensure that, if an information technology contract provides ongoing service and delivery to Coloradans, the contract maintains current architecture diagrams that are updated at least annually. The act prohibits the chief information officer from delegating a duty, responsibility, or power of the security officer. The act requires the security officer to submit 2 annual reports to the JTC. The first report is a written compliance report that includes OIT's current compliance status with applicable security standards; all open audit recommendations regarding OIT made by the state auditor and the date on which each recommendation was made; and a timeline for remediation and a mitigation plan or compensation controls for each open audit recommendation made by the state auditor. The second report is a written statewide information technology security risk report (security risk report) that assesses the overall security risk posture of state agency information technology systems. To support the preparation of the security risk report, the security officer may conduct evaluations of state agency information technology systems, including penetration testing, vulnerability scanning, configuration evaluations, and vendor and system reviews. Each state agency shall provide to the security officer, upon request, the access and information necessary to conduct evaluations of state agency technology systems, including system access, product information, and architecture information. The act requires the security officer, or the chief information officer if the security officer is unavailable, to perform the duties and uphold the responsibilities assigned to the security officer pursuant to law. (Note: This summary applies to this bill as enacted.)
Status timeline
| Date | Location | Action |
|---|---|---|
| 05/01/2026 | Senate | Introduced In Senate - Assigned to Business, Labor, & Technology |
| 05/05/2026 | Senate | Senate Committee on Business, Labor, & Technology Refer Amended to Appropriations |
| 05/07/2026 | Senate | Senate Committee on Appropriations Refer Unamended - Consent Calendar to Senate Committee of the Whole |
| 05/07/2026 | Senate | Senate Second Reading Special Order - Passed with Amendments - Committee |
| 05/08/2026 | Senate | Senate Third Reading Passed - No Amendments |
| 05/08/2026 | House | Introduced In House - Assigned to State, Civic, Military, & Veterans Affairs |
| 05/09/2026 | House | House Committee on State, Civic, Military, & Veterans Affairs Refer Unamended to Appropriations |
| 05/12/2026 | House | House Committee on Appropriations Refer Unamended to House Committee of the Whole |
| 05/12/2026 | House | House Second Reading Special Order - Passed - No Amendments |
| 05/13/2026 | House | House Third Reading Passed - No Amendments |
| 05/22/2026 | Senate | Signed by the President of the Senate |
| 05/22/2026 | House | Signed by the Speaker of the House |
| 05/22/2026 | Governor | Sent to the Governor |
| 06/02/2026 | Governor | Governor Signed |
Recorded votes
- 05/12/2026 — House Appropriations: “Refer Senate Bill 26-185 to the Committee of the Whole.” — the motion passed on a vote of 10–0.
- 05/09/2026 — House State, Civic, Military, & Veterans Affairs: “Refer Senate Bill 26-185 to the Committee on Appropriations.” — the motion passed on a vote of 11–0.
- 05/07/2026 — Senate Appropriations: “Refer Senate Bill 26-185 to the Committee of the Whole and with a recommendation that it be placed on the consent calendar.” — the motion passed on a vote of 7–0.
- 05/05/2026 — Senate Business, Labor, & Technology: “Refer Senate Bill 26-185, as amended, to the Committee on Appropriations.” — the motion passed on a vote of 5–0.
Proposed amendments (1 proposed amendment)
| Amendment | Committee / floor hearing | Offered | Disposition | Official document |
|---|---|---|---|---|
| L.001 | Committee amendment — Business, Labor, & Technology (Senate) | 05/05/2026 | Passed | View official document |
Source: Colorado General Assembly (leg.colorado.gov) · Data as of
Full text
- Signed Act version (official PDF), 06/03/2026
- Final Act version (official PDF), 05/21/2026
- Rerevised version (official PDF), 05/13/2026
- Revised version (official PDF), 05/12/2026
- Reengrossed version (official PDF), 05/08/2026
- Engrossed version (official PDF), 05/07/2026
- Introduced version (official PDF), 05/01/2026
Official record
View SB26-185 on leg.colorado.gov
Source: Colorado General Assembly (leg.colorado.gov) · Data as of
Verify this record
This record carries a fingerprint of its official content, computed by our data pipeline with the SHA-256 algorithm — a real computation over the record itself, not a badge we award ourselves. Anyone can recompute it from the official source and compare.
SHA-256 fingerprint
e8c4b86b0998b943cf269d96a480b6f070547f865d45dd7e00cf1009f936b50b
What it covers: the record exactly as the official source publishes it — its identifiers (bill number, session, jurisdiction), its official title and long title, its official summary, its status, its sponsors in published order, every recorded action, every recorded vote, and the link to each official text version — assembled in a fixed canonical form described on the How this data works page.
The fingerprint does not cover our retrieval date (the “Data as of” stamp in the source line): re-fetching unchanged official content produces the same fingerprint, while any change to the official content changes it.
If you recompute the fingerprint from the official source and get a different value, one of us is out of date — please report it through the corrections log.
