United States - Nevada

Nevada Gaming Control Board Cybersecurity Requirements

106 controls. 200 other frameworks in our corpus share controls with it. Here is all of it, and how much of it you are already doing.

Page built . This page is derived from the framework corpus, which changes when the corpus is extended rather than daily.

106 controls 200 frameworks share controls with it United States - Nevada verified against its source document

Every control below is one this framework asks for. The right hand column counts how many other frameworks in our corpus carry the same control, which is the difference between doing this work once and doing it again for the next standard.

There is no implementation kit for this framework yet. The control list and the overlap above are free and complete.

What you already have

Frameworks whose controls overlap this one, most first. If you run any of them, the count is roughly what you have already evidenced.

Every control

CodeControlAlso in
NGCB-1Regulation 5.260 Scope, Applicability, and Licensee Categories67
NGCB-2Cybersecurity Best Practices Framework Adoption0
NGCB-3Risk Assessment, Risk Management, and Ongoing Risk Monitoring0
NGCB-4Designated Cybersecurity Officer and Personnel Training0
NGCB-5Technical Security Controls - Access + Network + Encryption + Vulnerability + Logging61
NGCB-6Incident Response, 72-Hour NGCB Notification, and Independent Investigation150
NGCB-7Patron and Employee Data Protection + Data Inventory + Vendor Management56
NGCB-8Annual Independent Cybersecurity Assessment + Reporting + Board Oversight61
5.260(3)5.260(3) Initial risk assessment, cybersecurity best practices and ongoing monitoring, within 90 days of licensing0
5.260(4)(a)5.260(4)(a) Notify the Chair within 24 hours of activating the cybersecurity incident response plan0
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 days0
5.260(4)(c)5.260(4)(c) Written updates to the Board every 30 days until the incident is fully resolved and documented0
5.260(4)(d)5.260(4)(d) Specific information about the incident on the Board's request0
5.260(4)(e)5.260(4)(e) Investigation and report covering root cause, extent and preventive actions0
5.260(4)(f)5.260(4)(f) Notify the Board when an external investigation is complete and share its results on request0
5.260(5)(a)5.260(5)(a) Group I: designate a qualified individual responsible for the cybersecurity best practices0
5.260(5)(b)5.260(5)(b) Group I: annual internal audit verification that the best practices are followed0
5.260(5)(c)5.260(5)(c) Group I: annual independent review with written attestation of compliance0
5.260(6)5.260(6) Document every compliance procedure and result, keep records five years, produce them on request0
ENFORCEEnforcement and the Chair's waiver power0
M1IT MICS: service providers and cloud computing0
M10IT MICS: remote access0
M11IT MICS: change control, IT independence and software0
M12IT MICS: data access control0
M2IT MICS: physical access0
M3IT MICS: system parameters and event logs0
M4IT MICS: user, generic, service and default accounts0
M5IT MICS: administrative access0
M6IT MICS: backups and recovery0
M7IT MICS: recordkeeping and electronic records0
M8IT MICS: creation of wagering instruments0
M9IT MICS: network security and data protection0
MICS-IT-1IT MICS #1 IT service provider documentation0
MICS-IT-10IT MICS #10 User access listings with the required fields1
MICS-IT-11IT MICS #11 Event log retention: seven days, 30 days for administrator logs0
MICS-IT-12IT MICS #12 Weekly independent review of daily event logs0
MICS-IT-13IT MICS #13 Approval and provisioning of user accounts for new employees0
MICS-IT-14IT MICS #14 Transfers: previous access disabled before new access is used0
MICS-IT-15IT MICS #15 One active account at a time where multiple accounts create a segregation conflict0
MICS-IT-16IT MICS #16 Release of locked-out accounts0
MICS-IT-17IT MICS #17 Disable accounts on termination: immediately for remote access, 48 hours for administrators and providers, five days for others0
MICS-IT-18IT MICS #18 Quarterly independent review of application user access listings0
MICS-IT-19IT MICS #19 Generic operating system accounts locked to the application0
MICS-IT-2IT MICS #2 Cloud computing service provider documentation0
MICS-IT-20IT MICS #20 No generic accounts at application level except inquiry-only0
MICS-IT-21IT MICS #21 Service accounts protected against misuse0
MICS-IT-22IT MICS #22 Default accounts configured to minimise misuse0
MICS-IT-23IT MICS #23 Other default accounts disabled unless needed, passwords changed every 90 days if kept0
MICS-IT-24IT MICS #24 Administration of security and system parameters limited to supervised IT personnel0
MICS-IT-25IT MICS #25 Daily check of two-person administrator access for system-based and system-supported games0
MICS-IT-26IT MICS #26 Daily backup of application data, executables and databases1
MICS-IT-27IT MICS #27 Backup media moved at once to a separate secured location0
MICS-IT-28IT MICS #28 Daily review of backup logs, 30 days of evidence0
MICS-IT-29IT MICS #29 Documented backup and restore procedures0
MICS-IT-3IT MICS #3 Oversight procedures for cloud computing service providers0
MICS-IT-30IT MICS #30 Annual recovery test covering every system within three years0
MICS-IT-31IT MICS #31 List of all Board-regulated systems with versions and approval numbers0
MICS-IT-32IT MICS #32 Current list of enabled generic, system and default accounts0
MICS-IT-33IT MICS #33 List of administrator accounts used by IT service providers0
MICS-IT-34IT MICS #34 Six-monthly review of the account lists by IT management0
MICS-IT-35IT MICS #35 Retain user access listings one day a month for five years0
MICS-IT-36IT MICS #36 Current network topology, server deployment and inventory documentation0
MICS-IT-37IT MICS #37 Electronic signature set-up controlled so no one person can forge a signature0
MICS-IT-38IT MICS #38 Electronic signature procedures: types, authentication and storage0
MICS-IT-39IT MICS #39 Unalterable storage of scanned documents with index, reproduction controls and quarterly review0
MICS-IT-4IT MICS #4 Secured area with redundant power and physical security for critical IT systems1
MICS-IT-40IT MICS #40 Alterable electronic storage only with equivalent controls1
MICS-IT-41IT MICS #41 Board-approved system for creating wagering instruments0
MICS-IT-42IT MICS #42 Instruments and data files created independently of the gaming area0
MICS-IT-43IT MICS #43 Record of wagering instrument creation0
MICS-IT-44IT MICS #44 Monthly review and test of wagering instrument data files0
MICS-IT-45IT MICS #45 Documented procedures and results of the data file review and test0
MICS-IT-46IT MICS #46 Guest networks logically segregated and non-routable to gaming networks0
MICS-IT-47IT MICS #47 Production gaming networks secured from outside traffic, detecting and reporting security events0
MICS-IT-48IT MICS #48 Network shared drives for regulated software restricted to authorized personnel0
MICS-IT-49IT MICS #49 Automatic locking of consoles, terminals, portable devices and kiosks0
MICS-IT-5IT MICS #5 Access to critical IT areas restricted to authorized IT personnel0
MICS-IT-50IT MICS #50 Network equipment administrator credentials restricted and disabled on termination0
MICS-IT-51IT MICS #51 Data loss and exfiltration: prevent, detect and report0
MICS-IT-52IT MICS #52 Information security policies for confidentiality, integrity and availability0
MICS-IT-53IT MICS #53 Patron personally identifiable information protection procedures1
MICS-IT-54IT MICS #54 Regulation 5.260 risk assessment and incident reports available to auditors and the Board0
MICS-IT-55IT MICS #55 Written remote access procedures for each application with vendor support access0
MICS-IT-56IT MICS #56 Complete record of each remote access session1
MICS-IT-57IT MICS #57 Vendor accounts disabled until needed and after use1
MICS-IT-58IT MICS #58 Vendor remote access enabled only with IT approval0
MICS-IT-59IT MICS #59 Automatic logging of remote access to the production network0
MICS-IT-6IT MICS #6 Record of each non-IT access to critical IT areas0
MICS-IT-60IT MICS #60 Documented change control for the production environment0
MICS-IT-61IT MICS #61 IT department independent of gaming and entertainment operations0
MICS-IT-62IT MICS #62 IT personnel have no access to wagering instruments and gaming forms0
MICS-IT-63IT MICS #63 In-house development process for gaming and entertainment software0
MICS-IT-64IT MICS #64 Associated equipment reporting form and approval record for each in-house change0
MICS-IT-65IT MICS #65 Documentation and testing of changes to purchased software0
MICS-IT-66IT MICS #66 Stored transaction history and event logs cannot be altered0
MICS-IT-67IT MICS #67 Critical system data non-alterable outside normal processing1
MICS-IT-68IT MICS #68 External communication only through a Board-approved secure interface1
MICS-IT-7IT MICS #7 Logical security and password parameters1
MICS-IT-8IT MICS #8 System event logging of security-relevant events1
MICS-IT-9IT MICS #9 Application exception reports with before and after values1
MICSITThe Information Technology MICS (Group I) and ICPs (Group II)0
R1Regulation 5.260: risk assessment and cybersecurity best practices0
R2Regulation 5.260: cybersecurity incidents0
R3Regulation 5.260: Group I oversight and records0
REG5260NGC Regulation 5.260 Cybersecurity: purpose, definitions, covered entities and history0
STATUSStatus in September 2026 and what is pending0

Tell me when Nevada Gaming Control Board Cybersecurity Requirements files something new

One email when a public company newly discloses something this framework governs, naming the company and what our corpus says it puts in scope. Nothing else, and one click to stop.

What an auditor will ask you to produce

The artefacts named on the failure modes this framework speaks to.

  • System security plans
  • Standard operating procedures
  • Current-as-at dates and approval records
  • Revenue analysis
  • Exemption documentation
  • Annual applicability review
  • TPSP register
  • AOC collection log
  • contractual responsibility matrix
  • monitoring cadence

How programmes fail on this

Failure modes named by this framework and others. Each opens the full record.

What this page is

A control-level reference for Nevada Gaming Control Board Cybersecurity Requirements, drawn from our framework corpus. Control codes and titles are references to the standard, not reproductions of it. The overlap counts and the auditor artefacts are our own work and are the part you will not find elsewhere.

Measure this against what you already run · All frameworks · Today's edition