--- schema-version: v1.2.8 id: OASISPKCS-P-v3.1 title: - content: 'PKCS #11 Profiles Version 3.1' language: - en script: - Latn format: text/plain type: main link: - content: https://docs.oasis-open.org/pkcs11/pkcs11-profiles/v3.1/os/pkcs11-profiles-v3.1-os.docx type: doc - content: https://docs.oasis-open.org/pkcs11/pkcs11-profiles/v3.1/os/pkcs11-profiles-v3.1-os.html type: src - content: https://docs.oasis-open.org/pkcs11/pkcs11-profiles/v3.1/os/pkcs11-profiles-v3.1-os.pdf type: pdf type: standard docid: - id: OASIS PKCS-P-v3.1 type: OASIS primary: true docnumber: PKCS-P-v3.1 date: - type: issued value: '2023-07-23' contributor: - organization: name: - content: OASIS contact: - uri: https://www.oasis-open.org/ role: - description: - content: Standards Development Organization type: authorizer - type: publisher - organization: name: - content: PKCS 11 TC contact: - uri: https://www.oasis-open.org/committees/pkcs11/ role: - description: - content: Committee type: authorizer - person: name: given: forename: - content: Tim language: - en script: - Latn surname: content: Hudson language: - en script: - Latn role: - type: editor language: - en script: - Latn abstract: - content: Defines a platform-independent API to cryptographic tokens, such as hardware security modules and smart cards. The API itself is named “Cryptoki” (from “cryptographic token interface”) and pronounced “crypto-key”. Profiles define the use of PKCS#11 data types, objects, functions and mechanisms within specific contexts of provider and consumer interaction. These profiles define a set of normative constraints for employing PKCS#11 within a particular environment or context of use. language: - en script: - Latn format: text/plain doctype: type: standard editorialgroup: - name: PKCS 11 TC ext: schema-version: v1.0.1 technology_area: - Security