8.2.7 Third-party remote access accounts controlled

Where a third party reaches, supports or maintains system components remotely, the accounts it uses must be: switched on only for as long as needed and switched off when idle; and monitored for unexpected activity. The guidance advises that where round-the-clock access is genuinely needed it be recorded, justified, watched and linked to particular service needs, and suggests start and stop dates aligned with the service contract. Objective under the customized approach: remote access by third parties is unusable unless specifically authorized, and management oversees its use.

Source: PCI DSS v4.0.1, 8.2.7. The statement above is our statement of the clause, read from the published text and cited so you can check it against the official text, not the instrument verbatim. Open PCI DSS v4.0.1 in the compliance library.

Version 4.0.1 is the active version; 4.0 has been retired. Appendix A1 applies only to multi-tenant service providers, A2 only to card-present POS POI terminals that still use SSL or early TLS, and A3 only when a payment brand or acquirer requires it. Which requirements apply to you follows your validation type.