Service providers only (an additional requirement). A service provider with remote access to customer premises must use distinct authentication factors for each customer premises. The guidance explains the risk (one compromised shared factor could expose many customers) and notes that technologies giving a unique credential per connection, such as single-use passwords, could also meet the intent. Applicability: applies only when the assessed entity is a service provider; it does not cover a provider reaching its own shared services environments that host multiple customer environments. If provider staff use shared factors for remote access to customer premises, those factors must differ for each customer and be handled under Requirement 8.2.2. Objective under the customized approach: a service provider credential used at one customer is unusable at every other customer.
This control maps to 19 controls across 9 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.3 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 19 it maps to, and the evidence behind each claim, over MCP and REST.