Where a system or application account is capable of interactive login, it must be managed so that: interactive use is prevented unless an exceptional circumstance requires it; interactive use lasts no longer than the exceptional circumstance requires; the business justification is documented; management explicitly approves interactive use; the individual's identity is verified before the account is made available; and each action performed is attributable to one individual user. The guidance advises that, where possible, such accounts be configured to disallow interactive login and limited to specific machines and devices. Objective under the customized approach: whenever system or application accounts are used interactively, each action is authorized and traceable to one person. Future-dated: treated as a best practice up to 31 March 2025 and mandatory since then.
This control maps to 44 controls across 15 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.6.1 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 44 it maps to, and the evidence behind each claim, over MCP and REST.