The HSM's security policy permits no function that is unauthorised or unnecessary: API functions and commands that are not required are disabled before commissioning; PIN-block translation follows Requirement 3, with no non-ISO formats unless an approved business need exists; acquiring HSMs never support PIN change and never output PINs in clear text; and the configuration is documented, then signed and dated by those responsible for it.
This control maps to 1 controls across 1 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.
The graph holds this control, the 1 it maps to, and the evidence behind each claim, over MCP and REST.