Implement FedRAMP-defined cryptographic uses and approved cryptography (FIPS 140 validated).
Maintained by Gerard Blokdyk·Verified against the published standard ·Control text last updated
What else in your programme already covers this
This control maps to 39 controls across 22 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.
3.5.1.1 Hashes of PAN use keyed cryptographic functions
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
3.6.1 Procedures are defined and implemented to protect cryptographic keys used to protect stored account data against disclosure and misuse that include: • Access to keys is restricted to the fewest number of custodians necessary.
3.7.1 Key-management policies and procedures are implemented to include generation of strong cryptographic keys used to protect stored account data
You are reading one control. How much of FedRAMP High have you already done?
FedRAMP High SC-13 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.