NevadaSB46783rd Regular Session (2025)SenateWALLET

AN ACT relating to governmental administration; transferring the Nevada Office of Cyber Defense Coordination of the Department of Public Safety to the Office of the Chief Information Officer within the Office of the Governor; merging the Nevada Office of Cyber Defense Coordination with the Office of Information Security in the Office of the Chief Information Officer; setting forth the duties of the Office of Information Security and Cyber Defense; providing certain records are confidential; repealing provisions relating to the Nevada Office of Cyber Defense Coordination; and providing other matters properly relating thereto.

Sponsored By: Senate Committee on Finance

Signed by Governor

BDR 19-1149

Your PRIA Score

Score Hidden

Personalized for You

How does this bill affect your finances?

Sign up for a PRIA Policy Scan to see your personalized alignment score for this bill and every other piece of legislation we track. We analyze your financial profile against policy provisions to show you exactly what matters to your wallet.

Free to start

Bill Overview

Analyzed Economic Effects

7 provisions identified: 5 benefits, 1 costs, 1 mixed.

Businesses must meet payment card security

Starting July 1, 2025, Nevada businesses that accept payment cards must follow the current PCI Data Security Standard. They must meet the compliance date set in that standard or by the PCI Security Standards Council.

Authorized security testing now allowed

Beginning July 1, 2025, people who perform authorized security testing, including penetration testing, of agency systems that use the CIO’s services do not violate computer crime laws. The testing must be authorized by the CIO’s Chief or the Deputy Director.

Cyber incident records kept confidential

Starting July 1, 2025, records that identify the detection, investigation, or response to a suspected or confirmed cyber threat are not public. The Deputy Director may share them only with state or local agencies, state cyber response teams, or law enforcement. They may be used only to prepare for or reduce risks to systems or for criminal investigations.

State agencies: cyber plan, alerts, response

Starting July 1, 2025, the state office checks agency systems for risk and sets best practices. It builds partnerships with local, higher‑ed, private, and federal partners, and can convene cyber incident response teams. Agencies that use the CIO’s equipment or services must report suspected incidents within 24 hours of discovery. The Deputy Director investigates and helps resolve material breaches. The office must publish a statewide cyber plan by January 1, 2026 and update it at least every two years. It also sends quarterly readiness updates to the Governor and an annual report by July 1 each year.

State cyber office moves to Governor

Beginning July 1, 2025, Nevada moves its cyber office to the Governor’s Chief Information Officer and merges it into a new Office of Information Security and Cyber Defense. The old cyber office laws are repealed. The CIO appoints a Deputy Director in the unclassified service; anyone serving as Deputy Chief on July 1, 2025 stays classified until they leave. Existing rules, contracts, and actions keep working and transfer to the new office.

Agencies must follow data security controls

Starting July 1, 2025, government agencies that hold personal data must, when practicable, follow current CIS Controls or matching NIST standards. The state office will publish which federal controls satisfy this rule.

Cities and counties must keep cyber plans

Effective July 1, 2025, every city and county must adopt a cybersecurity incident response plan, review it yearly, and file new or revised plans within 10 days. By December 31 each year, they must file updates or certify the plan is current. Filed plans are confidential and may be released only by court order, for a terrorism‑related emergency, or as allowed by law. The State does not reimburse local governments for extra costs from this law under NRS 354.599.

Sponsors & Cosponsors

Sponsor

  • Senate Committee on Finance

    Affiliation unavailable

Cosponsors

There are no cosponsors for this bill.

Roll Call Votes

All Roll Calls

Yes: 62 • No: 0

House vote 6/2/2025

Final Passage - Assembly (As Introduced)

Yes: 42 • No: 0

Senate vote 5/29/2025

Final Passage - Senate (As Introduced)

Yes: 20 • No: 0

Actions Timeline

  1. Chapter 513.

    6/11/2025legislature
  2. Approved by the Governor.

    6/10/2025legislature
  3. Enrolled and delivered to Governor.

    6/5/2025legislature
  4. To enrollment.

    6/4/2025Senate
  5. In Senate.

    6/3/2025Senate
  6. Read third time. Passed. Title approved. (Yeas: 42, Nays: None.) To Senate.

    6/2/2025House
  7. Taken from General File. Placed on General File for next legislative day.

    6/1/2025House
  8. Read second time.

    5/31/2025House
  9. Placed on Second Reading File.

    5/31/2025House
  10. From committee: Do pass.

    5/31/2025House
  11. Read first time. Referred to Committee on Government Affairs. To committee.

    5/29/2025House
  12. In Assembly.

    5/29/2025House
  13. Read third time. Passed. Title approved. (Yeas: 20, Nays: None, Excused: 1.) To Assembly.

    5/29/2025Senate
  14. Read second time.

    5/28/2025Senate
  15. Placed on Second Reading File.

    5/28/2025Senate
  16. From committee: Do pass.

    5/28/2025Senate
  17. From printer. To committee.

    5/16/2025Senate
  18. Read first time. Referred to Committee on Government Affairs. To printer.

    5/15/2025Senate

Bill Text

  • As Enrolled

  • As Introduced

Related Bills

Back to State Legislation