OASIS Members and other interested parties,
OASIS and the PKCS 11 TC [1] are pleased to announce that two Committee Specifications are now available for public review and comment.
The OASIS PKCS 11 Technical Committee develops enhancements to improve the PKCS #11 standard for ease of use in code libraries, open source applications, wrappers, and enterprise/COTS products: implementation guidelines, usage tutorials, test scenarios and test suites, interoperability testing, coordination of functional testing, development of conformance profiles, and providing reference implementations.
The TC received four Statements of Use from Entrust, Utimaco, and Keyfactor, and Information Security Corporation [3].
The candidate specification and related files are available here:
PKCS #11 Specification Version 3.2
Committee Specification 01
14 November 2025
https://docs.oasis-open.org/pkcs11/pkcs11-spec/v3.2/cs01/pkcs11-spec-v3.2-cs01.docx (Authoritative)
https://docs.oasis-open.org/pkcs11/pkcs11-spec/v3.2/cs01/pkcs11-spec-v3.2-cs01.html
https://docs.oasis-open.org/pkcs11/pkcs11-spec/v3.2/cs01/pkcs11-spec-v3.2-cs01.pdf
Zip: pkcs11-spec-v3.2-cs01.zip
PKCS #11 Profiles Version 3.2
Committee Specification 01
14 November 2025
https://docs.oasis-open.org/pkcs11/pkcs11-profiles/v3.2/cs01/pkcs11-profiles-v3.2-cs01.docx (Authoritative)
https://docs.oasis-open.org/pkcs11/pkcs11-profiles/v3.2/cs01/pkcs11-profiles-v3.2-cs01.html
https://docs.oasis-open.org/pkcs11/pkcs11-profiles/v3.2/cs01/pkcs11-profiles-v3.2-cs01.pdf
Zip: https://docs.oasis-open.org/pkcs11/pkcs11-profiles/v3.2/cs01/pkcs11-profiles-v3.2-cs01.zip
A related Usage Guide that compliments the Committee Specifications above can be found here: https://docs.oasis-open.org/pkcs11/pkcs11-ug/v3.2/cn01/
Members of the PKCS 11 TC[1] approved this specification by Special Majority Vote [2]. The specification had been released for public review as required by the TC Process [4].
Public Review Period
The 60-day public review is now open and ends 17 May 2026 at 23:59 UTC.
This is an open invitation to comment. OASIS solicits feedback from potential users, developers and others, whether OASIS members or not, for the sake of improving the interoperability and quality of its technical work.
Comments may be submitted to the project by any person through the use of the project's Comment Facility. Members of the TC should submit feedback directly to the TC's members-only mailing list. All others should follow the instructions listed here.
If you have any questions or trouble submitting your comment, please contact the TC Administrator at: tc-admin@oasis-open.org.
All comments submitted to OASIS are subject to the OASIS Feedback License, which ensures that the feedback you provide carries the same obligations at least as the obligations of the TC members. In connection with this public review we call your attention to the OASIS IPR Policy [4] applicable especially [5] to the work of this technical committee. All members of the TC should be familiar with this document, which may create obligations regarding the disclosure and availability of a member's patent, copyright, trademark and license rights that read on an approved OASIS specification.
OASIS invites any persons who know of any such claims to disclose these if they may be essential to the implementation of the above specification, so that notice of them may be posted to the notice page for this TC's work.
========== Additional References:
[1] OASIS PKCS 11 TC
https://groups.oasis-open.org/communities/tc-community-home2?CommunityKey=922ef643-1e10-4d65-a5ea-018dc7d3f0a4#overview
[2] Approval ballot:
https://groups.oasis-open.org/higherlogic/ws/public/ballot?id=3911
[3] Links to Statements of Use
[4] https://www.oasis-open.org/policies-guidelines/ipr/
[5] https://www.oasis-open.org/committees/pkcs11/ipr.php
https://www.oasis-open.org/policies-guidelines/ipr/#RF-on-RAND-Mode