FedRAMP High IA-5(2): Public Key-Based Authentication
Enforce authorized use of public key-based authentication; validate certificates; map identity to account.
What else in your programme already covers this
This control maps to 28 controls across 11 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.
10.1.2 Requirement 10 roles and responsibilities documented and assigned
4.2.1 Strong cryptography and security protocols are implemented as follows to safeguard PAN during transmission over open, public networks: • Only trusted keys and certificates are accepted. • Certificates used to safeguard PAN during transmission
8.3.2 Strong cryptography is used to render all authentication factors unreadable during transmission and storage on all system components
8.4.1 MFA is implemented for all non-console access into the CDE for personnel with administrative access
8.4.2 MFA is implemented for all non-console access into the CDE
NIST800-IA-9 Service Identification and Authentication. Uniquely identify and authenticate [organization-defined] before establishing communications with devices, users, or other services or applications
NIST800-SC-17 Public key infrastructure certificates
You are reading one control. How much of FedRAMP High have you already done?
FedRAMP High IA-5(2) is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of FedRAMP High your existing evidence covers. Hold C5 (Germany) and 119 of 410 FedRAMP High 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. 6 were rejected on the C5 (Germany) pair alone.