Access information is information that lets someone reach encrypted technical data in unencrypted form, such as decryption keys, network access codes and passwords (120.55). Giving access information to a foreign person requires the same authorisation as releasing the underlying data where it can enable access, viewing or possession of the unencrypted data (120.56(b)); under the EAR a comparable authorisation is needed to transfer access information with knowledge that it will result in an unauthorised release of technology or software (734.19(a)). Software licence keys are classified under the same ECCN as the software or hardware they unlock, so a licence requirement that later attaches to the item (for example an Entity List addition) attaches to later key transfers too (734.19(b)).
This control maps to 2 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 2 it maps to, and the evidence behind each claim, over MCP and REST.