SAML: Security Services TC
Defining and maintaining a standard, XML-based framework for creating and exchanging security information between online partners
Defining and maintaining a standard, XML-based framework for creating and exchanging security information between online partners
Defining a well-documented collection of algorithms, mechanisms and methods, including test-vectors, that can be used in other Technical Committees.
Providing a guideline for developing operational solutions to privacy issues
Enhancing PKCS #11 standard for cryptographic tokens controlling authentication information (personal identity, cryptographic keys, certificates, digital signatures, biometric data)
Advancing interoperability standards for enterprise encryption key management
Supporting delivery of personalized user experiences, establish a Customer Data Platform standard
Supporting automated information sharing for cybersecurity situational awareness, real-time network defense, and sophisticated threat analysis
Defining a set of standardized protocols to elevate trust in an electronic identity
Surveying methods of authenticating electronic identities to make them more useful for governments, businesses, and individuals engaged in eGovernment and eCommerce.
Providing a privacy-by-design framework for behavioral data collection and processing
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 as “crypto-key”).
June 2020
Cite as:
[PKCS11-Base-v3.0] PKCS #11 Cryptographic Token Interface Base Specification Version 3.0.
Edited by Chris Zimman and Dieter Bong. 15 June 2020.
OASIS Standard.
https://docs.oasis-open.org/pkcs11/pkcs11-base/v3.0/os/pkcs11-base-v3.0-os.html.
Latest stage: https://docs.oasis-open.org/pkcs11/pkcs11-base/v3.0/pkcs11-base-v3.0.html.
PKCS #11 specifications define a platform-independent API to cryptographic tokens, such as hardware security modules and smart cards. “Current Mechanisms” defines mechanisms that are used with the current version of PKCS #11.
June 2020
Cite as:
[PKCS11-Current-v3.0] PKCS #11 Cryptographic Token Interface Current Mechanisms Specification Version 3.0.
Edited by Chris Zimman and Dieter Bong. 15 June 2020.
OASIS Standard.
https://docs.oasis-open.org/pkcs11/pkcs11-curr/v3.0/os/pkcs11-curr-v3.0-os.html.
Latest stage: https://docs.oasis-open.org/pkcs11/pkcs11-curr/v3.0/pkcs11-curr-v3.0.html.
No results with the selected filters