A user must authenticate again before resuming a terminal or session that has been idle for longer than 15 minutes. The guidance notes this can be applied at system level for all sessions on a machine or at application level, and gives a password-protected screensaver after 15 minutes idle as one example. Applicability: not intended for point-of-sale terminal user accounts that are limited to a single card number per transaction, and not meant to stop legitimate activities from running while a console or PC is unattended. Objective under the customized approach: only the authorized user can use a user session.
This control maps to 32 controls across 14 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.
Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected.
PCI DSS 4.0 8.2.8 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of PCI DSS 4.0 your existing evidence covers. Hold ISO 27001:2022 and 139 of 280 PCI DSS 4.0 controls already carry evidence.
Each report names every control your existing framework evidences, every one it does not, the reasoning behind each claim, and the claims that were argued against and rejected. 415 were rejected on the ISO 27001:2022 pair alone.
The graph holds this control, the 32 it maps to, and the evidence behind each claim, over MCP and REST.