All non-console administrative access must be encrypted with strong cryptography. The guidance explains the purpose (stopping an eavesdropper capturing administrator IDs, passwords and other authorization factors), gives out-of-band technologies such as lights-out management, IPMI and KVM switches with remote capability as examples of non-console access, and recommends that protocols not fall back to weaker, insecure versions. Applicability: this includes administrative access through application programming interfaces (APIs) and interfaces reached by browser. Objective under the customized approach: administrative authorization factors in cleartext cannot be read or captured from any network transmission.
This control maps to 36 controls across 19 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 2.2.7 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 36 it maps to, and the evidence behind each claim, over MCP and REST.