AoU Feature Requirements

Crypto Feature Security AoU		status: draft security: YES safety: ASIL_B
version: 1 realizes: wp__requirements_comp_aou
doc__crypto_sec_feat_aou		Generic Document

This page contains Assumption of Use requirement snippets that belong to the crypto repository.

Feature AoU

pkcs11_dynload: pkcs11.h compatiblity		status: valid security: YES safety: ASIL_B
reqtype: Process version: 1
If pkcs11_dynload is used as backend for the pkcs11 provider, the selected pkcs11.h header shall match the pkcs11 module that will be loaded at runtime.
aou_req__crypto__sec_pkcs11_h_compatibility		Assumption of Use Requirement

pkcs11_dynload: No use of ALLOW_PKCS11_LIB_OVERRIDE		status: valid security: YES safety: ASIL_B
tags: environment reqtype: Process version: 1
If pkcs11_dynload is used as backend for the pkcs11 provider, the PKCS11_LIB_OVERRIDE mechanism shall not be used for series. The pkcs11 module path provided via pkcs11_lib shall be the effective and final module that will be loaded at runtime. Hint: This option is introduced only for internal use of testing and is not recommended to be used for a series project
aou_req__crypto__sec_no_pkcs11_lib_override		Assumption of Use Requirement

pkcs11_dynload: Integrity and authenticity of the pkcs11 module		status: valid security: YES safety: ASIL_B
tags: environment reqtype: Process version: 1
If pkcs11_dynload is used as backend for the pkcs11 provider, the operating system platform shall provide integrity and authenticity mechanisms for the specified pkcs11 module.
aou_req__crypto__sec_integ_auth_pkcs11_mod		Assumption of Use Requirement