A hotel keeps its PCI DSS assessment scope narrow by isolating F&B point-of-sale and payment terminals onto dedicated VLANs with firewall rules that permit only the specific traffic those devices need, by hardening POS login credentials so a shared employee ID can't become the weak link, and by limiting POS vendor remote access to defined, logged, time-boxed sessions rather than always-on tunnels into the cardholder data environment. Everything else on the hotel network — guest Wi-Fi, room controls, PMS, cameras — should sit outside that boundary entirely, connected only through the narrow, documented exceptions an assessor can actually review. Cave Group designs and segments hotel networks around exactly this kind of scope boundary as part of its hospitality technology work.
This is a different problem than general hotel network segmentation. A pre-opening network design has to account for PMS, door locks, and room automation all talking to each other in limited, deliberate ways. PCI scope reduction is a tighter question: which devices touch cardholder data, how small can the network boundary around them be drawn, and what has to be handed to a QSA or ISA to prove it.
Which devices actually belong inside the cardholder data environment?
The cardholder data environment (CDE) is the POS terminals, the payment interface, and anything that can see, store, or influence card data in transit. On a property running Oracle Simphony, that means the POS clients (Workstation 6, Workstation 8, or Tablet 700 Series units), the Simphony database/application server, and any Oracle Payments or third-party payment interface sitting between the client and the processor. Oracle's own Simphony documentation separates these concerns into distinct guides — a dedicated Security Guide and a separate Networking Reference Guide ship alongside the installation and configuration manuals, which is itself a signal that Oracle expects network design and security hardening to be treated as their own disciplines rather than an afterthought to installing the application.
Kitchen display systems, menu management tools, loyalty integrations, and reporting dashboards that only read aggregated transaction data — not card numbers — are candidates to be pushed outside the CDE boundary, provided the firewall rules between them and the POS clients are one-directional and don't expose card data back out. That scoping decision belongs with your QSA, not with the integrator alone; ask your contractor to document, device by device, why each one is in or out.
How should POS terminals be placed: wired or wireless?
Wired POS terminals on a dedicated VLAN give you the cleanest scope boundary: a switchport-level ACL plus a firewall rule set is easier to document and verify than a wireless segment, and it removes any question about rogue AP or Wi-Fi eavesdropping risk in the CDE. Oracle's Tablet 700 Series exists for tableside and drive-through ordering where a fixed terminal isn't practical, which means a wireless path into the CDE is sometimes unavoidable — but it should run on its own SSID, mapped to the same restricted VLAN as the wired terminals, with client isolation enabled and WPA2/3-Enterprise authentication rather than a shared passphrase.
Whichever path you choose, that decision should be made before cabling and AP placement lock in, alongside hospitality networking choices covered in hotel Wi-Fi and networking. A hotel's broader hospitality technology plan should treat the POS/payment VLAN as a separate design track from guest Wi-Fi from the start, not a retrofit — the kind of network and PMS integration work Cave Group scopes alongside guest-room systems.
What should POS login credentials actually require?
Oracle's own authentication documentation is explicit that a numeric employee ID by itself is the weakest option available on a Simphony POS client. Oracle's guidance states: "Oracle does not recommend using an Employee ID as the only authentication factor for signing into POS devices. Using magnetic/RFID cards and/or fingerprints, or a combination of them, provides stronger security for your POS devices. If you are only using Employee IDs, it is recommended to configure Simphony to require at least 6 digits." (Point of Sale User Authentication)
That's a decision your F&B operations team and your integrator should settle before go-live, not after an assessor flags it: card/RFID or fingerprint authentication, or a 6-digit-minimum employee ID if biometric or card readers aren't deployed. This sits alongside — not instead of — network segmentation; weak POS login credentials widen the practical attack surface even when the VLAN boundary is sound.
What remote access should a POS vendor actually get?
A POS or payment vendor supporting Simphony needs remote access for patches, configuration changes, and troubleshooting, but that access should never be an always-on VPN tunnel straight into the CDE VLAN. Scope it instead to a jump host or bastion that logs every session, require credentials that expire or need re-approval, and disable the path entirely when it isn't actively in use. This is the single most common gap a QSA finds during a Report on Compliance review, and it is the easiest one for an integrator to close by design rather than by cleanup after the fact.
Ask your contractor whether the vendor's remote-access tool itself has been reviewed against current guidance, since remote-support software is frequently the entry point reviewers look at first.
What should an integrator hand an assessor?
A QSA or internal ISA preparing a SAQ or ROC will ask for a current network diagram showing the CDE boundary, the VLANs in and out of scope, and every firewall rule that crosses that boundary — not a general description of "segmented." Exported firewall rule sets, a device inventory tied to the diagram, and a written scope justification explaining why each excluded system (PMS, guest Wi-Fi, room controls, cameras) cannot reach the CDE are the deliverables that actually speed up an assessment instead of becoming the assessor's first finding. Build that documentation as part of the original design and update it whenever a VLAN, firewall rule, or device inventory changes — not as a scramble the week before the assessment window opens. This is the kind of network documentation Cave Group builds into its hotel technology projects from the design phase forward, alongside related work like hotel PMS integration.
Frequently asked questions
Does Oracle Simphony provide its own network segmentation guidance?
Yes. Oracle ships a dedicated Networking Reference Guide and a separate Security Guide alongside Simphony's installation and configuration documentation, describing networking best practices and site considerations as distinct subjects from application setup. (Oracle MICROS Simphony Documentation Library)
Is an employee ID alone a safe way to log into a POS terminal?
Oracle's own documentation advises against it, recommending magnetic/RFID cards or fingerprint authentication instead, and setting a minimum of 6 digits if an employee ID is the only method configured.
Should POS terminals be wired or on Wi-Fi?
Wired terminals on a dedicated VLAN give the simplest, most defensible scope boundary for an assessment. Mobile terminals like Oracle's Tablet 700 Series sometimes require Wi-Fi for tableside or drive-through ordering, which should run on an isolated SSID mapped to the same restricted VLAN with enterprise authentication, not a shared passphrase.
What should a POS vendor's remote access be limited to?
Time-boxed, logged sessions through a jump host rather than an always-on VPN directly into the cardholder data environment, with credentials disabled when not actively needed — a design point to raise with whichever contractor builds or audits the network.
Who decides which devices are inside versus outside the cardholder data environment?
That scoping call should be made jointly by your QSA or ISA and your network integrator, documented device by device, since kitchen displays, loyalty tools, and reporting dashboards that only read aggregated data are often candidates to sit outside the boundary if the firewall rules between them and POS clients are strictly one-directional.