Hospitality IT in Las Vegas: Payments, Wi-Fi, POS, and Gaming
How Las Vegas restaurants, bars, hotels, and small gaming operators plan payment security under PCI DSS v4.0.1, guest and staff Wi-Fi separation, POS rollouts, and the Nevada Gaming Control Board's information technology standards.
What hospitality IT planning covers in Las Vegas
Hospitality IT in Las Vegas comes down to four plans. Protect card payments under PCI DSS v4.0.1, the current version, which Nevada law (NRS 603A.215) requires covered businesses that accept payment cards to follow. Keep guest Wi-Fi apart from staff, payment, and gaming systems. Roll out point-of-sale (POS) stations outside service hours. If you hold a gaming license, plan around the Nevada Gaming Control Board's Information Technology standards and the cybersecurity rules in Gaming Regulation 5.260.
Which rules apply to a Las Vegas hospitality business?
Two rules reach almost every business that takes cards. Two more apply only to gaming licensees. Each is published by the body named here, checked November 2026.
| Rule | Published by | Who it covers | Key dates |
|---|---|---|---|
| PCI DSS v4.0.1 | PCI Security Standards Council | Entities that store, process, or transmit cardholder data, including merchants | Published June 2024. v4.0 retired December 31, 2024. Future-dated requirements effective March 31, 2025 |
| NRS 603A.215 | Nevada Legislature (state law) | Data collectors doing business in Nevada that accept payment cards for sales of goods or services | Comply with the current PCI DSS by the dates PCI DSS sets |
| Information Technology MICS, Version 9 | Nevada Gaming Control Board | Group I licensees' gaming and entertainment tax related applications, databases, and operating systems | Effective April 1, 2023 |
| Regulation 5.260, Cybersecurity | Nevada Gaming Commission and Nevada Gaming Control Board | Nonrestricted licensees that operate games, and licensees for race books, sports pools, or interactive gaming | Comply with the risk assessment rule within 90 days of being licensed |
Payment security under PCI DSS v4.0.1
PCI DSS v4.0.1 is the only active version of the standard the PCI Security Standards Council supports. It is a limited revision of v4.0 with no added or deleted requirements. Of the 64 new requirements in v4.x, 51 were future-dated and became effective March 31, 2025, so an assessment now has to consider the ones that apply.
Your acquirer or payment brand sets validation
The PCI Security Standards Council says whether you must validate compliance is set by payment brands and acquirers, and tells merchants to contact their acquirer (merchant bank) or payment brand. Ask which Self-Assessment Questionnaire (SAQ) fits your setup. There are several, each for a specific type of environment.
Fewer places with card data means less to protect
The Council strongly recommends isolating the cardholder data environment from the rest of the network as a method that may reduce the scope of an assessment. It also points to keeping card data in as few places as possible.
Encryption at the terminal
A point-to-point encryption (P2PE) solution protects card data from the moment the card is accepted to a secure point of decryption. The Council states that merchants using PCI-listed P2PE solutions have fewer applicable PCI DSS requirements. Check the Council's listings before you rely on that.
Nevada adds a legal reason
NRS 603A.215 requires a data collector doing business in Nevada that accepts payment cards to comply with the current PCI DSS for those transactions. It also says a data collector in compliance is not liable for damages for a breach, unless gross negligence or intentional misconduct caused it. Ask your attorney how it applies to you.
See the How to read a merchant processing statement and the Cybersecurity and resilience.
Keep guest Wi-Fi apart from staff, payment, and gaming systems
Give guests, staff, payment devices, and any gaming systems their own networks, and control what each one can reach. The PCI Security Standards Council says segmentation is not a PCI DSS requirement, but adequate segmentation may reduce the scope of an assessment. For gaming licensees subject to the IT MICS, the Board requires any guest network to be logically separated from the network serving gaming and entertainment tax related applications and devices, with guest traffic non-routable to it.
| Option | What it involves | Usually fits when |
|---|---|---|
| Separate Wi-Fi names and VLANs on shared equipment | One set of access points and switches carries several networks. Firewall rules decide what each network can reach | A single restaurant, bar, or small hotel with one team managing the network |
| Physically separate network for payment or gaming systems | Dedicated switches, ports, or cabling for the systems that need the most isolation | Gaming systems, or a payment setup where your acquirer or assessor wants clear isolation |
| Guest internet on its own circuit | Guest Wi-Fi leaves the building over a separate internet connection from business systems | Hotels and venues with heavy guest use, or when guest traffic slows the POS |
| PCI-listed P2PE payment devices | Card data is encrypted at the terminal until it reaches the solution's secure point of decryption | You want fewer applicable PCI DSS requirements and your processor offers a listed solution |
- Count the networks you need. Guest, staff, payment and POS, cameras and other connected devices, and, for licensees, gaming systems.
- Write down what each network may reach. Guest Wi-Fi should reach the internet and nothing else on site.
- Test from the guest side. Join guest Wi-Fi and confirm you cannot reach a POS station, printer, camera recorder, or server.
- Re-check every year. The Council says to validate the scope of the cardholder data environment, including any segmentation, as part of the annual PCI DSS assessment.
See the Business Wi-Fi and network refresh guide and the Network and Wi-Fi services.
How to roll out POS stations without closing service
Treat each POS station as one build that repeats: terminal, payment device, printer, cash drawer, and network drop, configured and tested before it reaches the counter. Install outside service hours, one area or site at a time, with a spare on hand. Choose hardware after the POS software and processor are settled, because they decide which devices are supported.
- Settle the software and processor first. Hardware is scoped around the POS software and processor you have chosen, not the other way around.
- Draw the card data flow. The Council says a data flow diagram helps you understand every place card data moves and whether segmentation isolates it.
- Ask your acquirer about validation. Know which SAQ, if any, applies before you buy devices, since each SAQ is written for a specific type of environment.
- Check every counter. Confirm power, a network drop, and mounting space at each station before equipment arrives.
- Stage and test. Configure each station before install day and run a test transaction on the live network.
- Plan spares and rollback. Keep a spare terminal on site and a way back to the old station if a cutover fails.
- Retire old devices with care. Remove them from the network and wipe or destroy any storage before disposal.
See the Technology procurement and the Hardware and device refresh services.
What the Gaming Control Board publishes on information technology
The Nevada Gaming Control Board publishes Minimum Internal Control Standards (MICS) by chapter, including one for Information Technology. Under Regulation 6.090, each Group I licensee describes its procedures in a written system of internal control, and the Chair adopts and publishes the minimum standards. The Board lists the Information Technology chapter under Version 9, effective April 1, 2023. Version 9.1, effective December 1, 2026, revises the Card Games and Interactive Gaming chapters.
| Topic | What the IT MICS say | MICS |
|---|---|---|
| Scope | Apply to gaming and entertainment tax related applications and their underlying databases and operating systems | Note 1 |
| IT service providers | Document the provider, the services it performs, and the management official responsible for the relationship | #1 |
| Passwords | Changed at least once every 90 days; at least 8 characters with at least two of the listed criteria | #7 |
| Lockout | Accounts lock automatically after 3 failed login attempts | #7 |
| Backups | Daily backup and recovery procedures; backup media moved right away to a separate, secured location | #26, #27 |
| Guest networks | If offered, logically separated from the network serving gaming and entertainment tax related applications and devices, with guest traffic non-routable to it | #46 |
| Production networks | Secured from outside traffic, for example by firewall or routers | #47 |
| Vendor remote access | Vendor accounts stay disabled until needed; remote access only when approved by authorized IT personnel | #57, #58 |
Group I or Group II
Regulation 6.010 defines both as nonrestricted licensees, at or above, or below, gross revenue amounts the Board sets for each fiscal year and posts on its website. Group II licensees follow internal control procedures the Chair publishes under Regulation 6.100.
POS and box office systems
For an entertainment tax related box office or POS system, the IT MICS do not apply when its manufacturer is engaged to operate it as the IT service provider, the licensee has only installed the user terminals, and the manufacturer performs the administrative functions. Confirm who runs each system before you decide what is in scope.
Read the current chapter
The Board lists each MICS version on its Audit Division pages and announces revisions in industry notices, such as Notice 2026-60 for Version 9.1. Check the current text before you plan, and direct questions to the Board.
Regulation 5.260: cybersecurity duties for gaming licensees
Regulation 5.260 covers holders of a nonrestricted license that operate games, and holders of licenses for a race book, sports pool, or interactive gaming. Each covered entity performs an initial risk assessment, develops the cybersecurity best practices it deems appropriate, and keeps monitoring risk. The regulation names CIS Version 8, COBIT 5, ISO/IEC 27001, and NIST SP 800-53 as examples of best practices.
- Risk assessment. Comply fully with the risk assessment rule within 90 days of being licensed.
- Incident notice. After a cybersecurity incident that meets the regulation's threshold, notify the Chair as soon as practicable and no later than 24 hours after activating your incident response plan.
- Initial report. Within 5 calendar days, submit an Initial Cybersecurity Incident Response report or request a meeting with the Chair of activating the plan, then send written updates every 30 days until the incident is resolved.
- Investigation. Perform, or have a third party perform, an investigation and document the results in a report.
- Group I duties. Designate a qualified individual for the program. At least annually, have an internal auditor or other independent entity review it, and have an independent accountant or other independent entity attest in writing that it complies.
- Records. Keep the records the section requires for at least five years from creation, unless the Chair approves otherwise in writing.
See the Managed detection and response and the Backup and disaster recovery.
How to plan hospitality IT, step by step
Work from an inventory of what takes cards and what connects to what. Most of the effort is in the inventory and the network rules. The installation is scheduled around service hours.
- List every card-accepting device and system at each site, with your processor and acquirer.
- Ask your acquirer which validation and SAQ apply, and keep the answer in writing.
- Map your networks: guest, staff, payment and POS, cameras, and gaming systems if you hold a license.
- Pick a separation option for each site and write down what each network may reach.
- If you hold a gaming license, confirm your group under Regulation 6, the MICS chapters that apply, and whether Regulation 5.260 covers you.
- Check backups and vendor access against the IT MICS if gaming or entertainment tax systems are in scope.
- Stage POS stations and network changes, then schedule installs outside service hours with a rollback plan.
- Keep the diagrams, network rules, and vendor contacts where your team and your auditor can find them.
See the Days Dynamics in Las Vegas and the Typical pricing for Days Dynamics services.
Frequently asked questions
Does Nevada law require PCI DSS compliance?
For businesses it covers, yes. NRS 603A.215 requires a data collector doing business in Nevada that accepts payment cards for sales of goods or services to comply with the current version of PCI DSS, as adopted by the PCI Security Standards Council, for those transactions.
What changed in PCI DSS v4.0.1?
It is a limited revision of v4.0 that corrects formatting and typographical errors and clarifies intent. The Council states there are no added or deleted requirements. PCI DSS v4.0 was retired December 31, 2024, leaving v4.0.1 as the only active version.
Is network segmentation required by PCI DSS?
No. The Council states that network segmentation is not a PCI DSS requirement. It strongly recommends it, because adequate segmentation may reduce the scope of the cardholder data environment and the assessment.
Do the Gaming Control Board's IT MICS apply to our POS system?
They apply to gaming and entertainment tax related applications and their databases and operating systems. A POS that is not gaming or entertainment tax related is outside them. For an entertainment tax related POS, see the manufacturer exception in Note 2 of the chapter. Confirm your case with the Board.
Which gaming licensees does Regulation 5.260 cover?
Holders of a nonrestricted license that operate games, and holders of licenses for a race book, sports pool, or interactive gaming. Covered entities classified as Group I licensees have added duties, including an annual independent review.
What does a network refresh for a restaurant or bar cost?
Days Dynamics publishes typical ranges of $600 to $1,500 per installed access point and $8,000 to $25,000 for a small-site refresh of switching, firewall, and Wi-Fi. These are typical ranges, not a quote. Your price is confirmed in writing after a site walk or floor-plan review.
Does Days Dynamics work on site in Henderson and North Las Vegas?
Yes. Days Dynamics is based in Las Vegas and works on site across Las Vegas, Henderson, North Las Vegas, and Boulder City, including site walks, network and access point setup, and installation coordinated around service hours.
Plan payments, Wi-Fi, and POS for your venue with Days Dynamics
Send us your sites, the POS software and processor you use, and how guest and staff Wi-Fi are set up today. If you hold a gaming license, tell us your license type. We will map the networks to separate and a rollout sequence that fits your service hours. A planning call is planning support, not a quote, an audit, or a commitment on licensing, availability, or delivery dates.
Sources
Primary sources checked when this guide was written. Dates and product status can change, so confirm on the source before you rely on them.
- PCI Security Standards Council: PCI DSS overview (opens in a new tab)
- PCI Security Standards Council: Document Library (opens in a new tab)
- PCI SSC blog: Just Published: PCI DSS v4.0.1 (opens in a new tab)
- PCI SSC blog: Now is the time to adopt the future-dated requirements of PCI DSS v4.x (opens in a new tab)
- PCI SSC FAQ: When should an entity implement requirements noted as best practices until a future date? (opens in a new tab)
- PCI SSC FAQ: How do I reduce the scope of a PCI DSS assessment? (opens in a new tab)
- PCI SSC Glossary: Network segmentation (opens in a new tab)
- PCI SSC: Merchant resources (opens in a new tab)
- PCI SSC: Point-to-Point Encryption (P2PE) (opens in a new tab)
- Nevada Legislature: NRS Chapter 603A, Security and Privacy of Personal Information (opens in a new tab)
- Nevada Gaming Control Board: Minimum Internal Control Standards (opens in a new tab)
- Nevada Gaming Control Board: MICS Information Technology, Version 9 (opens in a new tab)
- Nevada Gaming Control Board: Notice 2026-60, Version 9.1 of the MICS (opens in a new tab)
- Nevada Gaming Commission and Control Board: Regulation 6, Accounting Regulations (opens in a new tab)
- Nevada Gaming Commission and Control Board: Regulation 5, Operation of Gaming Establishments (opens in a new tab)
Related services
Related resources
Turn the checklist into a plan
The 2-minute IT quiz turns this checklist into ranked priorities for your situation, before any contact details.
