What it asks for. The organisation must determine its cryptographic uses and implement the types of cryptography required for each use.
In practice. This means a cryptography standard that lists approved algorithms, key lengths and protocols for uses such as data at rest, data in transit, signing and hashing, with deprecated options banned. Organisations should keep an inventory of where cryptography is used to support migration, including future post-quantum transitions. Auditors look for the standard, configuration evidence and scan results. Validated cryptographic modules may be required in some regulated settings.
Common gaps. Weak or deprecated algorithms remain in legacy systems and libraries. Few organisations have a cryptographic inventory, which makes planned migrations hard. Developers sometimes write their own cryptography instead of using vetted libraries.