Meet NGC Reg 5.260 cybersecurity duties with evidence ready to show
NGC Reg 5.260 is the section of Nevada Gaming Commission Regulation 5 that sets cybersecurity requirements for gaming operators. It requires covered entities to perform a risk assessment, adopt cybersecurity best practices such as ISO/IEC 27001, NIST SP 800-53 or CIS Controls, report material cybersecurity incidents to the Nevada Gaming Control Board, and keep written records for at least five years. Amendments adopted on 29 January 2026 shortened the initial notification window to 24 hours.
Is NGC Reg 5.260 right for your organisation?
Regulation 5.260 applies to holders of a nonrestricted Nevada gaming licence that operate games, and to licensees operating a race book, a sports pool or interactive gaming. Newly licensed covered entities must complete the risk assessment and best practices requirement within 90 days of being licensed. Group I licensees also need a designated cybersecurity lead, an annual internal audit review and an annual independent attestation.
It is a legal or regulatory requirement for organisations in scope.
- Issued by
- Nevada Gaming Commission
- Enforced by
- Nevada Gaming Control Board
- Latest amendment
- Adopted and effective 29 January 2026
- Applies to
- Nonrestricted, race book, sports pool and interactive gaming licensees
- Incident notice
- To the Board Chair within 24 hours of activating the incident response plan, with an initial report within 5 calendar days
- Assessment route
- Group I licensees: annual internal audit review and annual independent attestation
- Record retention
- At least five years from creation
- Type
- Regulation (mandatory)
- Region
- Nevada, US
- In OneClickComply
- Supported today
OneClickComply makes it simple
Nevada Gaming Regulation 5.260 is mapped in OneClickComply's control library and available on request. OneClickComply links the regulation's risk assessment, incident response and record keeping duties to the controls you already run for ISO 27001 or NIST, collects evidence automatically from your connected systems, and keeps a dated audit trail ready for your internal auditor and independent attestation.
Requirements covered
Seven subsections covering purpose, definitions, risk assessment and best practices (subsection 3), incident notification and reporting (subsection 4), Group I licensee duties (subsection 5), documentation and five year retention (subsection 6) and due diligence (subsection 7).
Manual NGC Reg 5.260 vs. OneClickComply
- Risk assessments live in spreadsheets that are out of date as soon as systems change
- Proving you follow your chosen best practices means chasing screenshots across many tools
- A 24 hour notification clock leaves no time to locate the incident response plan and contacts
- Annual internal audit and attestation reviews turn into weeks of evidence gathering
- Keeping five years of cybersecurity records in one retrievable place is hard to manage
- A live risk register keeps your assessment current as your environment changes
- Evidence is collected automatically from connected systems and mapped to each control
- Documented incident response procedures and owners are ready when the clock starts
- Auditors get organised, dated evidence for each requirement in one place
- Records and evidence are stored centrally so you can answer Board requests quickly
Everything you need for NGC Reg 5.260
Risk register for the initial risk assessment and ongoing cybersecurity risk monitoring
Controls mapped to ISO 27001, NIST and CIS so your chosen best practices are evidenced once
Incident response plan and policies generated by AutoComplete from your real environment
Continuous monitoring that alerts you when cybersecurity controls drift
Automated evidence collection with dated records kept for the five year retention period
Ask an Auditor and virtual CISO support for Group I reviews and attestation preparation
Three steps to NGC Reg 5.260 compliance
Connect & scan
Connect your cloud, identity and SaaS tools. OneClickComply checks them against NGC Reg 5.260 and shows you exactly where you stand.
Fix & generate
OneClickFix remediates technical gaps in one click, and AutoComplete generates NGC Reg 5.260-aligned policies from your real environment.
Monitor & evidence
Continuous monitoring keeps you compliant, and our in-house audit team is on hand when you need expert guidance.
Nevada Gaming Regulation 5.260 (Cybersecurity) requirements
All seven subsections of Regulation 5.260 as amended on 29 January 2026, with the lettered incident reporting and Group I paragraphs listed separately.
| Reference | Requirement |
|---|---|
| 5.260(1) | Purpose: protect information systems and personal information |
| 5.260(2) | Definitions, including covered entity and cybersecurity incident |
| 5.260(3) | Risk assessment and cybersecurity best practices |
| 5.260(4) | Material cybersecurity incident obligations and waivers |
| 5.260(4)(a) | Notify the Chair within 24 hours |
| 5.260(4)(b) | Initial Cybersecurity Incident Response report within 5 calendar days |
| 5.260(4)(c) | Written updates every 30 days until resolved |
| 5.260(4)(d) | Provide specific incident information on request |
| 5.260(4)(e) | Investigation report including root cause |
| 5.260(4)(f) | Notify the Board of completed external investigations |
| 5.260(5)(a) | Group I: designate a qualified cybersecurity individual |
| 5.260(5)(b) | Group I: annual internal audit verification |
| 5.260(5)(c) | Group I: annual independent review and written attestation |
| 5.260(6) | Documentation and five year record retention |
| 5.260(7) | Due diligence and disciplinary action |
Always check the official NGC Reg 5.260 text for the exact wording.
NGC Reg 5.260 FAQs
What is Nevada Gaming Regulation 5.260?
Nevada Gaming Regulation 5.260 is the cybersecurity section of Nevada Gaming Commission Regulation 5. It requires covered gaming operators to protect their information systems and patron and employee personal information by performing a risk assessment, adopting cybersecurity best practices, reporting material cybersecurity incidents to the Nevada Gaming Control Board, documenting compliance and keeping records for at least five years.
Who must comply with Regulation 5.260?
Covered entities must comply. These are holders of a nonrestricted gaming licence that operate or expose games for play, and holders of licences allowing a race book, a sports pool or interactive gaming. Group I licensees, as defined in Regulation 6.010, have additional duties, including a designated cybersecurity lead and annual independent review and attestation.
How quickly must a cybersecurity incident be reported in Nevada?
Since the amendments adopted on 29 January 2026, a covered entity must notify the Board Chair as soon as practicable and no later than 24 hours after activating its incident response procedures. It must submit an Initial Cybersecurity Incident Response report within 5 calendar days, then give written updates every 30 days until the incident is resolved, and complete an investigation report covering root cause.
Which cybersecurity framework does Regulation 5.260 require?
Regulation 5.260 does not mandate one framework. Each covered entity develops the cybersecurity best practices it deems appropriate after a risk assessment. The regulation gives CIS Version 8, COBIT 5, ISO/IEC 27001 and NIST SP 800-53 as examples, and points to the NIST Cybersecurity Framework for risk assessment guidance, so many operators build on ISO 27001 or NIST.
What happens if a licensee does not comply with Regulation 5.260?
Failure to exercise proper due diligence in complying with Regulation 5.260 is treated as an unsuitable method of operation and may result in disciplinary action by Nevada gaming regulators. The regulation itself does not set a fixed fine; consequences are handled through the state's gaming disciplinary process, which can affect a licensee's standing.
What are the annual audit requirements for Group I licensees?
Group I licensees must, at least annually, have their internal auditor or another independent cybersecurity expert verify through observations, examinations and employee inquiries that best practices are being followed. They must also engage an independent accountant or other independent expert each year to review the practices and attest in writing that they comply with the regulation.
How does Regulation 5.260 relate to ISO 27001?
ISO/IEC 27001 is named in Regulation 5.260 as an example of acceptable cybersecurity best practices. An organisation already running an ISO 27001 information security management system will have much of the risk assessment, control and documentation work in place, but must still meet Nevada-specific duties such as Board incident reporting deadlines, Group I attestation and five year record retention.
Does OneClickComply support Nevada Gaming Regulation 5.260?
Yes, on request. Nevada Gaming Regulation 5.260 is mapped in OneClickComply's control library and available on request rather than live as a standard framework. OneClickComply can map its requirements to controls you already operate for frameworks such as ISO 27001, collect evidence automatically and support your internal audit and attestation preparation. It does not issue attestations itself.
Related standards
All standards- Nevada Consumer Health Data and Data Security Law (NRS 603A)Law · US
- Nevada SB 220 (Online Privacy Opt-Out of Sale)Law · US
- HIPAA Administrative Simplification RegulationsRegulation · US
- NISPOM (32 CFR Part 117)Regulation · US
- NYDFS Cybersecurity Regulation (23 NYCRR Part 500)Regulation · US
- HIPAA Security RuleRegulation · US
- Unclassified Naval Nuclear Propulsion Information (U-NNPI)Regulation · US
- TSA Security Directive 1580/82-2022-01: Rail Cybersecurity Mitigation Actions and TestingRegulation · US
Get NGC Reg 5.260 ready, not stressed
Automate controls, gather evidence continuously and stay audit-ready, all on one platform.