ColoradoSigned into law2026 Regular Session

SB26-185 Enhance Security of Office of Information Technology

Latest: Jun 2, 2026 · Governor Signed

What it means

Our plain-English summary and constitutional analysis for this bill is not published yet. Every analysis is reviewed by an editor before it appears here.

How they voted

7 committee, procedural and amendment votes

House: BILL

64 yes · 1 no

May 13, 2026 · Result: pass

PartyYesNo
Democrat1–
Democratic41–
Republican211
How each member voted (64)

1 of 65 members on the official record could not be matched to our officials list and are not shown individually. The tally above is the official one.

Party shown is each member's current party in our records. Official vote record

House: Refer Senate Bill 26-185 to the Committee of the Whole.

10 yes · 0 no · 1 other

May 12, 2026 · Result: pass

PartyYesOther / excused
Democratic71
Republican3–
How each member voted (11)

Party shown is each member's current party in our records. Official vote record

House: Refer Senate Bill 26-185 to the Committee on Appropriations.

11 yes · 0 no

May 9, 2026 · Result: pass

PartyYes
Democratic8
Republican3
How each member voted (11)

Party shown is each member's current party in our records. Official vote record

Senate: BILL

34 yes · 0 no · 1 other

May 8, 2026 · Result: pass

PartyYesOther / excused
Democratic23–
Republican111
How each member voted (35)

Party shown is each member's current party in our records. Official vote record

Senate: Refer Senate Bill 26-185 to the Committee of the Whole and with a recommendation that it be placed on the consent calendar.

7 yes · 0 no

May 7, 2026 · Result: pass

PartyYes
Democratic4
Republican3
How each member voted (7)

Party shown is each member's current party in our records. Official vote record

Senate: Refer Senate Bill 26-185, as amended, to the Committee on Appropriations.

5 yes · 0 no

May 5, 2026 · Result: pass

PartyYes
Democratic3
Republican2
How each member voted (5)

Party shown is each member's current party in our records. Official vote record

Senate: Adopt amendment L.001

? yes · ? no

May 5, 2026 · Result: pass

Member-by-member votes are not loaded for this roll call yet. The tally above is from the official record.

Party shown is each member's current party in our records. Official vote record

Where it stands

  1. May 1, 2026 · Senate

    Introduced

    Introduced In Senate - Assigned to Business, Labor, & Technology

  2. May 5, 2026 · Senate

    Sent to committee

    Senate Committee on Business, Labor, & Technology Refer Amended to Appropriations

  3. May 8, 2026 · Senate

    Passed Senate

    Senate Third Reading Passed - No Amendments

  4. May 8, 2026 · House

    Introduced

    Introduced In House - Assigned to State, Civic, Military, & Veterans Affairs

  5. May 9, 2026 · House

    Sent to committee

    House Committee on State, Civic, Military, & Veterans Affairs Refer Unamended to Appropriations

  6. May 12, 2026 · House

    Sent to committee

    House Committee on Appropriations Refer Unamended to House Committee of the Whole

  7. May 13, 2026 · House

    Passed House

    House Third Reading Passed - No Amendments

  8. May 22, 2026 · House

    Passed House

    Signed by the Speaker of the House

  9. May 22, 2026 · Senate

    Passed Senate

    Signed by the President of the Senate

  10. Jun 2, 2026 · Governor

    Became law

    Governor Signed

Full official history (14 actions)
  • May 1, 2026SenateIntroduced In Senate - Assigned to Business, Labor, & Technology
  • May 5, 2026SenateSenate Committee on Business, Labor, & Technology Refer Amended to Appropriations
  • May 7, 2026SenateSenate Second Reading Special Order - Passed with Amendments - Committee
  • May 7, 2026SenateSenate Committee on Appropriations Refer Unamended - Consent Calendar to Senate Committee of the Whole
  • May 8, 2026SenateSenate Third Reading Passed - No Amendments
  • May 8, 2026HouseIntroduced In House - Assigned to State, Civic, Military, & Veterans Affairs
  • May 9, 2026HouseHouse Committee on State, Civic, Military, & Veterans Affairs Refer Unamended to Appropriations
  • May 12, 2026HouseHouse Second Reading Special Order - Passed - No Amendments
  • May 12, 2026HouseHouse Committee on Appropriations Refer Unamended to House Committee of the Whole
  • May 13, 2026HouseHouse Third Reading Passed - No Amendments
  • May 22, 2026GovernorSent to the Governor
  • May 22, 2026HouseSigned by the Speaker of the House
  • May 22, 2026SenateSigned by the President of the Senate
  • Jun 2, 2026GovernorGovernor Signed

Supporters and opponents

No documented positions yet. Every position we list links to its public source.

Official summary

Read the official summary (openstates)
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; andOIT 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; andReceived 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.)