Nevada Gaming Control Board Cybersecurity Requirements
Nevada's cybersecurity requirements for gaming licensees: Nevada Gaming Commission Regulation 5.260 (risk assessment and best practices within 90 days of licensing, notice to the Board Chair within 24 hours of activating the incident response plan, a 5-day initial incident report and 30-day updates since January 2026, and for Group I licensees a designated responsible individual, annual internal audit and independent attestation) and the Gaming Control Board's 68 Information Technology Minimum Internal Control Standards, with the Group II Internal Control Procedures mapped. Built from the codified regulation and the Board's published standards, read in full.
Nevada Gaming Control Board Cybersecurity Requirements is a compliance framework from United States - Nevada with 15 domains and 79 controls that map to 194 other frameworks. The largest domains are IT MICS: user, generic, service and default accounts – Nevada Gaming Control Board Cybersecurity Requirements (11 controls), IT MICS: recordkeeping and electronic records – Nevada Gaming Control Board Cybersecurity Requirements (10 controls), IT MICS: network security and data protection – Nevada Gaming Control Board Cybersecurity Requirements (9 controls). Every control below carries what it requires and what an assessor expects to see.
Framework summaries on this platform are interpretations grounded in the published source, for educational and compliance planning purposes. They do not reproduce or replace the official standards. Refer to the authoritative source for the definitive text. Framework names and trademarks belong to their respective organisations.
Framework Domains (15)
IT MICS: administrative access – Nevada Gaming Control Board Cybersecurity Requirements
| Code | Title |
|---|---|
| nevada-gaming-control-board-cybersecurity-requirements::MICS-IT-24 | IT MICS #24 Administration of security and system parameters limited to supervised IT personnel |
| nevada-gaming-control-board-cybersecurity-requirements::MICS-IT-25 | IT MICS #25 Daily check of two-person administrator access for system-based and system-supported games |
IT MICS: backups and recovery – Nevada Gaming Control Board Cybersecurity Requirements
| Code | Title |
|---|---|
| nevada-gaming-control-board-cybersecurity-requirements::MICS-IT-26 | IT MICS #26 Daily backup of application data, executables and databases |
| nevada-gaming-control-board-cybersecurity-requirements::MICS-IT-27 | IT MICS #27 Backup media moved at once to a separate secured location |
| nevada-gaming-control-board-cybersecurity-requirements::MICS-IT-28 | IT MICS #28 Daily review of backup logs, 30 days of evidence |
| nevada-gaming-control-board-cybersecurity-requirements::MICS-IT-29 | IT MICS #29 Documented backup and restore procedures |
| nevada-gaming-control-board-cybersecurity-requirements::MICS-IT-30 | IT MICS #30 Annual recovery test covering every system within three years |
IT MICS: change control, IT independence and software – Nevada Gaming Control Board Cybersecurity Requirements
| Code | Title |
|---|---|
| nevada-gaming-control-board-cybersecurity-requirements::MICS-IT-60 | IT MICS #60 Documented change control for the production environment |
| nevada-gaming-control-board-cybersecurity-requirements::MICS-IT-61 | IT MICS #61 IT department independent of gaming and entertainment operations |
| nevada-gaming-control-board-cybersecurity-requirements::MICS-IT-62 | IT MICS #62 IT personnel have no access to wagering instruments and gaming forms |
| nevada-gaming-control-board-cybersecurity-requirements::MICS-IT-63 | IT MICS #63 In-house development process for gaming and entertainment software |
| nevada-gaming-control-board-cybersecurity-requirements::MICS-IT-64 | IT MICS #64 Associated equipment reporting form and approval record for each in-house change |
| nevada-gaming-control-board-cybersecurity-requirements::MICS-IT-65 | IT MICS #65 Documentation and testing of changes to purchased software |
IT MICS: creation of wagering instruments – Nevada Gaming Control Board Cybersecurity Requirements
| Code | Title |
|---|---|
| nevada-gaming-control-board-cybersecurity-requirements::MICS-IT-41 | IT MICS #41 Board-approved system for creating wagering instruments |
| nevada-gaming-control-board-cybersecurity-requirements::MICS-IT-42 | IT MICS #42 Instruments and data files created independently of the gaming area |
| nevada-gaming-control-board-cybersecurity-requirements::MICS-IT-43 | IT MICS #43 Record of wagering instrument creation |
| nevada-gaming-control-board-cybersecurity-requirements::MICS-IT-44 | IT MICS #44 Monthly review and test of wagering instrument data files |
| nevada-gaming-control-board-cybersecurity-requirements::MICS-IT-45 | IT MICS #45 Documented procedures and results of the data file review and test |
IT MICS: data access control – Nevada Gaming Control Board Cybersecurity Requirements
| Code | Title |
|---|---|
| nevada-gaming-control-board-cybersecurity-requirements::MICS-IT-66 | IT MICS #66 Stored transaction history and event logs cannot be altered |
| nevada-gaming-control-board-cybersecurity-requirements::MICS-IT-67 | IT MICS #67 Critical system data non-alterable outside normal processing |
| nevada-gaming-control-board-cybersecurity-requirements::MICS-IT-68 | IT MICS #68 External communication only through a Board-approved secure interface |
IT MICS: network security and data protection – Nevada Gaming Control Board Cybersecurity Requirements
| Code | Title |
|---|---|
| nevada-gaming-control-board-cybersecurity-requirements::MICS-IT-46 | IT MICS #46 Guest networks logically segregated and non-routable to gaming networks |
| nevada-gaming-control-board-cybersecurity-requirements::MICS-IT-47 | IT MICS #47 Production gaming networks secured from outside traffic, detecting and reporting security events |
| nevada-gaming-control-board-cybersecurity-requirements::MICS-IT-48 | IT MICS #48 Network shared drives for regulated software restricted to authorized personnel |
| nevada-gaming-control-board-cybersecurity-requirements::MICS-IT-49 | IT MICS #49 Automatic locking of consoles, terminals, portable devices and kiosks |
| nevada-gaming-control-board-cybersecurity-requirements::MICS-IT-50 | IT MICS #50 Network equipment administrator credentials restricted and disabled on termination |
| nevada-gaming-control-board-cybersecurity-requirements::MICS-IT-51 | IT MICS #51 Data loss and exfiltration: prevent, detect and report |
| nevada-gaming-control-board-cybersecurity-requirements::MICS-IT-52 | IT MICS #52 Information security policies for confidentiality, integrity and availability |
| nevada-gaming-control-board-cybersecurity-requirements::MICS-IT-53 | IT MICS #53 Patron personally identifiable information protection procedures |
| nevada-gaming-control-board-cybersecurity-requirements::MICS-IT-54 | IT MICS #54 Regulation 5.260 risk assessment and incident reports available to auditors and the Board |
IT MICS: physical access – Nevada Gaming Control Board Cybersecurity Requirements
| Code | Title |
|---|---|
| nevada-gaming-control-board-cybersecurity-requirements::MICS-IT-4 | IT MICS #4 Secured area with redundant power and physical security for critical IT systems |
| nevada-gaming-control-board-cybersecurity-requirements::MICS-IT-5 | IT MICS #5 Access to critical IT areas restricted to authorized IT personnel |
| nevada-gaming-control-board-cybersecurity-requirements::MICS-IT-6 | IT MICS #6 Record of each non-IT access to critical IT areas |
IT MICS: recordkeeping and electronic records – Nevada Gaming Control Board Cybersecurity Requirements
| Code | Title |
|---|---|
| nevada-gaming-control-board-cybersecurity-requirements::MICS-IT-31 | IT MICS #31 List of all Board-regulated systems with versions and approval numbers |
| nevada-gaming-control-board-cybersecurity-requirements::MICS-IT-32 | IT MICS #32 Current list of enabled generic, system and default accounts |
| nevada-gaming-control-board-cybersecurity-requirements::MICS-IT-33 | IT MICS #33 List of administrator accounts used by IT service providers |
| nevada-gaming-control-board-cybersecurity-requirements::MICS-IT-34 | IT MICS #34 Six-monthly review of the account lists by IT management |
| nevada-gaming-control-board-cybersecurity-requirements::MICS-IT-35 | IT MICS #35 Retain user access listings one day a month for five years |
| nevada-gaming-control-board-cybersecurity-requirements::MICS-IT-36 | IT MICS #36 Current network topology, server deployment and inventory documentation |
| nevada-gaming-control-board-cybersecurity-requirements::MICS-IT-37 | IT MICS #37 Electronic signature set-up controlled so no one person can forge a signature |
| nevada-gaming-control-board-cybersecurity-requirements::MICS-IT-38 | IT MICS #38 Electronic signature procedures: types, authentication and storage |
| nevada-gaming-control-board-cybersecurity-requirements::MICS-IT-39 | IT MICS #39 Unalterable storage of scanned documents with index, reproduction controls and quarterly review |
| nevada-gaming-control-board-cybersecurity-requirements::MICS-IT-40 | IT MICS #40 Alterable electronic storage only with equivalent controls |
IT MICS: remote access – Nevada Gaming Control Board Cybersecurity Requirements
| Code | Title |
|---|---|
| nevada-gaming-control-board-cybersecurity-requirements::MICS-IT-55 | IT MICS #55 Written remote access procedures for each application with vendor support access |
| nevada-gaming-control-board-cybersecurity-requirements::MICS-IT-56 | IT MICS #56 Complete record of each remote access session |
| nevada-gaming-control-board-cybersecurity-requirements::MICS-IT-57 | IT MICS #57 Vendor accounts disabled until needed and after use |
| nevada-gaming-control-board-cybersecurity-requirements::MICS-IT-58 | IT MICS #58 Vendor remote access enabled only with IT approval |
| nevada-gaming-control-board-cybersecurity-requirements::MICS-IT-59 | IT MICS #59 Automatic logging of remote access to the production network |
IT MICS: service providers and cloud computing – Nevada Gaming Control Board Cybersecurity Requirements
| Code | Title |
|---|---|
| nevada-gaming-control-board-cybersecurity-requirements::MICS-IT-1 | IT MICS #1 IT service provider documentation |
| nevada-gaming-control-board-cybersecurity-requirements::MICS-IT-2 | IT MICS #2 Cloud computing service provider documentation |
| nevada-gaming-control-board-cybersecurity-requirements::MICS-IT-3 | IT MICS #3 Oversight procedures for cloud computing service providers |
IT MICS: system parameters and event logs – Nevada Gaming Control Board Cybersecurity Requirements
| Code | Title |
|---|---|
| nevada-gaming-control-board-cybersecurity-requirements::MICS-IT-10 | IT MICS #10 User access listings with the required fields |
| nevada-gaming-control-board-cybersecurity-requirements::MICS-IT-11 | IT MICS #11 Event log retention: seven days, 30 days for administrator logs |
| nevada-gaming-control-board-cybersecurity-requirements::MICS-IT-12 | IT MICS #12 Weekly independent review of daily event logs |
| nevada-gaming-control-board-cybersecurity-requirements::MICS-IT-7 | IT MICS #7 Logical security and password parameters |
| nevada-gaming-control-board-cybersecurity-requirements::MICS-IT-8 | IT MICS #8 System event logging of security-relevant events |
| nevada-gaming-control-board-cybersecurity-requirements::MICS-IT-9 | IT MICS #9 Application exception reports with before and after values |
IT MICS: user, generic, service and default accounts – Nevada Gaming Control Board Cybersecurity Requirements
| Code | Title |
|---|---|
| nevada-gaming-control-board-cybersecurity-requirements::MICS-IT-13 | IT MICS #13 Approval and provisioning of user accounts for new employees |
| nevada-gaming-control-board-cybersecurity-requirements::MICS-IT-14 | IT MICS #14 Transfers: previous access disabled before new access is used |
| nevada-gaming-control-board-cybersecurity-requirements::MICS-IT-15 | IT MICS #15 One active account at a time where multiple accounts create a segregation conflict |
| nevada-gaming-control-board-cybersecurity-requirements::MICS-IT-16 | IT MICS #16 Release of locked-out accounts |
| nevada-gaming-control-board-cybersecurity-requirements::MICS-IT-17 | IT MICS #17 Disable accounts on termination: immediately for remote access, 48 hours for administrators and providers, five days for others |
| nevada-gaming-control-board-cybersecurity-requirements::MICS-IT-18 | IT MICS #18 Quarterly independent review of application user access listings |
| nevada-gaming-control-board-cybersecurity-requirements::MICS-IT-19 | IT MICS #19 Generic operating system accounts locked to the application |
| nevada-gaming-control-board-cybersecurity-requirements::MICS-IT-20 | IT MICS #20 No generic accounts at application level except inquiry-only |
| nevada-gaming-control-board-cybersecurity-requirements::MICS-IT-21 | IT MICS #21 Service accounts protected against misuse |
| nevada-gaming-control-board-cybersecurity-requirements::MICS-IT-22 | IT MICS #22 Default accounts configured to minimise misuse |
| nevada-gaming-control-board-cybersecurity-requirements::MICS-IT-23 | IT MICS #23 Other default accounts disabled unless needed, passwords changed every 90 days if kept |
Regulation 5.260: Group I oversight and records – Nevada Gaming Control Board Cybersecurity Requirements
| Code | Title |
|---|---|
| nevada-gaming-control-board-cybersecurity-requirements::5.260(5)(a) | 5.260(5)(a) Group I: designate a qualified individual responsible for the cybersecurity best practices |
| nevada-gaming-control-board-cybersecurity-requirements::5.260(5)(b) | 5.260(5)(b) Group I: annual internal audit verification that the best practices are followed |
| nevada-gaming-control-board-cybersecurity-requirements::5.260(5)(c) | 5.260(5)(c) Group I: annual independent review with written attestation of compliance |
| nevada-gaming-control-board-cybersecurity-requirements::5.260(6) | 5.260(6) Document every compliance procedure and result, keep records five years, produce them on request |
Regulation 5.260: cybersecurity incidents – Nevada Gaming Control Board Cybersecurity Requirements
| Code | Title |
|---|---|
| nevada-gaming-control-board-cybersecurity-requirements::5.260(4)(a) | 5.260(4)(a) Notify the Chair within 24 hours of activating the cybersecurity incident response plan |
| nevada-gaming-control-board-cybersecurity-requirements::5.260(4)(b) | 5.260(4)(b) Initial Cybersecurity Incident Response report within 5 calendar days, or a meeting with the Chair and the form within 30 days |
| nevada-gaming-control-board-cybersecurity-requirements::5.260(4)(c) | 5.260(4)(c) Written updates to the Board every 30 days until the incident is fully resolved and documented |
| nevada-gaming-control-board-cybersecurity-requirements::5.260(4)(d) | 5.260(4)(d) Specific information about the incident on the Board's request |
| nevada-gaming-control-board-cybersecurity-requirements::5.260(4)(e) | 5.260(4)(e) Investigation and report covering root cause, extent and preventive actions |
| nevada-gaming-control-board-cybersecurity-requirements::5.260(4)(f) | 5.260(4)(f) Notify the Board when an external investigation is complete and share its results on request |
Regulation 5.260: risk assessment and cybersecurity best practices – Nevada Gaming Control Board Cybersecurity Requirements
| Code | Title |
|---|---|
| nevada-gaming-control-board-cybersecurity-requirements::5.260(3) | 5.260(3) Initial risk assessment, cybersecurity best practices and ongoing monitoring, within 90 days of licensing |
Your Compliance Coverage
If you comply with Nevada Gaming Control Board Cybersecurity Requirements, you already cover:
GLI-33 - Gaming Laboratories International Event Wagering Systems
14%
12 controls mapped
Compare →Vietnam Law on Cybersecurity (No. 116/2025/QH15)
6%
5 controls mapped
Compare →Privacy Act 1988 (Australia)
6%
5 controls mapped
Compare →+ 191 more: Nigeria Data Protection Act 2023 (NDPA) (6%), Nebraska Data Privacy Act (6%)
See all 194 mapped frameworks ↓Maps to 194 other frameworks
Coverage is not the same as your position
This page shows what Nevada Gaming Control Board Cybersecurity Requirements overlaps with in general. Where your organisation actually stands, against the standard you are going for and the certifications you already hold, is a different question. Same graph and the same recorded refutations, scoped to you rather than to a pair.
The Compliance Position Diagnostic, $5,000 fixed, ten business daysWhat is Nevada Gaming Control Board Cybersecurity Requirements and who does it apply to?
Nevada Gaming Control Board Cybersecurity Requirements is a compliance framework from United States - Nevada with 15 domains and 79 controls. Nevada's cybersecurity requirements for gaming licensees: Nevada Gaming Commission Regulation 5.260 (risk assessment and best practices within 90 days of licensing, notice to the Board Chair within 24 hours of activating the incident response plan, a 5-day initial incident report and 30-day updates since January 2026, and for Group I licensees a designated responsible individual, annual internal audit and independent attestation) and the Gaming Control Board's 68 Information Technology Minimum Internal Control Standards, with the Group II Internal Control Procedures mapped. Built from the codified regulation and the Board's published standards, read in full. It is used by organisations to establish and maintain compliance with industry standards and regulatory requirements.
What does Nevada Gaming Control Board Cybersecurity Requirements actually require?
Nevada Gaming Control Board Cybersecurity Requirements has 79 controls organised across 15 domains. The largest domains are IT MICS: user, generic, service and default accounts – Nevada Gaming Control Board Cybersecurity Requirements (11 controls), IT MICS: recordkeeping and electronic records – Nevada Gaming Control Board Cybersecurity Requirements (10 controls), IT MICS: network security and data protection – Nevada Gaming Control Board Cybersecurity Requirements (9 controls). Each control defines specific requirements that organisations must implement to achieve compliance.
If I already comply with another framework, how much of Nevada Gaming Control Board Cybersecurity Requirements do I already cover?
Nevada Gaming Control Board Cybersecurity Requirements maps to 194 other compliance frameworks. The top mapping partners are GLI-33 - Gaming Laboratories International Event Wagering Systems (14% coverage), Vietnam Law on Cybersecurity (No. 116/2025/QH15) (6% coverage), Privacy Act 1988 (Australia) (6% coverage). Use our comparison tool to explore control-level mappings between frameworks.
How do I implement Nevada Gaming Control Board Cybersecurity Requirements?
Start your Nevada Gaming Control Board Cybersecurity Requirements compliance journey by running a self-assessment on our platform to identify your current compliance posture. Our AI advisory can answer specific questions about Nevada Gaming Control Board Cybersecurity Requirements requirements, and cross-framework mapping helps you leverage existing controls from other frameworks you may already comply with. Create a free account to access all 79 controls and track your progress.
Start Your Compliance Journey
Create a free account to run self-assessments, get AI advisory, and track your compliance progress across 1,121 frameworks.
Get Started Free →Free forever, no credit card required