PCI DSS 4.0 3.4.2: 3.4.2 Remote access blocks copying or relocating PAN
When personnel use remote-access technologies, technical controls must stop them from copying and/or moving PAN, apart from people who hold explicit, documented approval plus a defined, legitimate business reason. Guidance notes a virtual desktop as an example of such technology, that these tools often have settings to disable copy and move functions, and that storage devices include local and virtual drives, removable media, network drives and cloud storage. Applicability: saving PAN to removable electronic media, local hard drives or any other storage device brings those devices into PCI DSS scope. Objective under the customized approach: unauthorized personnel cannot copy or relocate PAN through remote-access technologies. Future-dated: treated as a best practice up to 31 March 2025 and mandatory since then.
This control maps to 36 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.
NIST-CSF-DE.CM-03 Personnel activity and technology usage are monitored to find potentially adverse events
NIST-CSF-PR.AA-05 Access permissions, entitlements, and authorizations are defined in a policy, managed, enforced, and reviewed, and incorporate the principles of least privilege and separation of duties
NIST-CSF-PR.DS-10 The confidentiality, integrity, and availability of data-in-use are protected
NIST-CSF-PR.IR-01 Networks and environments are protected from unauthorized logical access and usage
You are reading one control. How much of PCI DSS 4.0 have you already done?
PCI DSS 4.0 3.4.2 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.