Security requirements
Compiled text through Nov 15, 2021
Register checked through Jul 29, 2026
Later Register activity found — review the notice before relying on the compiled text.
Dates and status
- Compiling agency
- Executive Department
- Text status
- Source receipt
- Compiled text through
- Nov 15, 2021
- Register checked through
- July 29, 2026/Vol. XLVIII, Issue 30 (2026-07-29)
- Activity status
- Later Register activity found — review the notice before relying on the compiled text.
- Latest notice
- TAF-46-21-00009-P · Proposed rule · Nov 17, 2021
- Source snapshot
- Jun 6, 2026
The MCS shall support either a hierarchical role structure whereby user and password define program or individual-menu-item access or logon program/device security based strictly on user and password or personal identification number. In addition, the MCS shall not permit the alteration of any significant log information communicated from the gaming device. Additionally, there shall be a provision for system administrator notification and user lockout or audit trail entry, after a set number of unsuccessful login attempts.
The MCS shall not permit the alteration of any accounting or significant-event-log information that was properly communicated from the gaming device without supervised access controls. In the event that financial data is changed, an automated audit log shall be capable of being produced to document:
If supported, a MCS may provide redundant functionality to check gaming device game software. The following information shall be reviewed for validity prior to implementation: