Configure security policies
Review branch security settings that protect player PCs, staff access, browser behavior, downloads, tools, and session end behavior.
The branch has a practical security baseline that protects player PCs without blocking normal gameplay.
Before you start
- Set up Agent PCs and approve test devices.
- Know which games, launchers, and websites the venue allows.
- Use a supervisor or owner account for security settings.
Start with a baseline
Security settings should match the risk level of the venue. Start with controls that protect the branch without creating constant staff workarounds.
- Protect system tools and settings customers should not use.
- Review browser and download behavior before public use.
- Set session-end behavior that returns PCs to a controlled state.
Test on an Agent PC
Security policy is only useful if it works on real player PCs with the games and launchers customers use.
- Test policies on one PC before the whole floor.
- Open normal games and launchers after changing policy.
- Check staff recovery actions if a PC gets stuck.
Review regularly
Security needs change when the venue adds games, browsers, launchers, or staff processes.
- Review policy after adding major games.
- Ask staff which customer actions create support issues.
- Keep a safe rollback path for settings that are too restrictive.
Verify it worked
- A player PC returns to controlled state after a test session.
- Allowed games and launchers still open normally.
- Restricted system areas are not easy for customers to access.
Troubleshooting
A game or launcher stops working after a security change.
Test the policy on one PC, identify the blocked behavior, and adjust before applying broadly.
Customers can access Windows areas they should not use.
Review restricted tools, browser, downloads, and session-end policies for the affected Agent PCs.