CACrown ArchivesThe cinema collection
Menu
Research dossier · General Reference

PKCS

group of public-key cryptography standards devised and published by RSA Security Inc

Cross-disciplinary reference desk with index cards, atlas, dictionary and catalogue
General referenceInterpretive dossier study · Crown Archives visual atlas
Record originEnglish Wikipedia
Text licenseCC BY-SA 4.0
Source revisionMay 4, 2026
Entity authorityQ1193215
Source-derived summary

Public Key Cryptography Standards (PKCS) are a group of public-key cryptography intervendor standards first developed by RSA Security, with involvement from Apple, Digital, Lotus Development, Microsoft, MIT, Northern Telecom, and Sun Microsystems, first published in June 1991.

The PKCS series of standards began development internally at RSA Laboratories in March 1991 with the "broad design goals" of maintaining compatibility with existing Privacy-Enhanced Mail (PEM) protocol certificates, allow handling of arbitrary data, adding richer information in certificate attributes, supporting Diffie-Hellman key exchange, and creating protocols to be some day incorporated into International Telecommunication Union X.200 standards by basing it on existing ITU-T standards such as ASN.1 and BER.

PKCS then taken by RSA to the US National Institute of Standards and Technology's Open Systems Interconnection Workshop, an organization created in 1983 by NIST at the request of industry to provide a forum for industry co-operation in computer interconnection protocols. Development of the PKCS protocols was undertaken in the 1991 sessions of the OSI Workshop under the Security Special Interest Group chaired by Trusted Information Systems. However, PKCS did not appear in the final OSI Workshop yearly publication

and was instead published as an OSI working document, the first publicly available version of the protocols. Though not industry standards because the company retained control over them, some of the standards have moved into the "standards track" processes of relevant standards organizations since May 1997, such as the IETF and the PKIX working group.

Key Updates (2023–2025):

Integration of PKCS #7 and PKCS #12 into broader standards like S/MIME and TLS.

Evolution of PKCS #11 to support newer hardware and cloud services; support for NIST's ML-DSA and ML-KEM.

Involvement of PKCS standards in post-quantum cryptography efforts, with NIST's ongoing standardization.

Growing adoption of PKCS standards in the context of blockchain and digital assets.

See also

Cryptographic Message Syntax

References

General

Jean-Sébastien Coron, Marc Joye, David Naccache, and Pascal Paillier (2000). "New Attacks on PKCS #1 v1.5 Encryption" (PDF). EUROCRYPT. pp.

Editorial summary

“PKCS” enters the record as group of public-key cryptography standards devised and published by RSA Security Inc. Crown Archives preserves that source wording while asking what PKCS, group and public-key can confirm, complicate or overturn.

Editorial reviewA dependable orientation record for establishing vocabulary, names and a first evidence trail. The current lead gives the account dated anchors—1991, 1983, 1997, 2023—that can be checked directly. The selected authority fields contribute no independent date. Its strongest next move is a source search built around PKCS, group and public-key.
Editorial analysis

Why this record matters

“PKCS” is worth following because a concise public description often conceals a longer documentary argument. Here, PKCS, group and public-key provides the most credible route into that argument.

Evidence profile

The citation trail is more important than the brevity of the summary: it shows where individual claims can be examined in context. The source revision retrieved here is dated May 4, 2026. The linked authority identifier is Q1193215. None of the 0 selected statements returned an explicit reference. The first chronological checks are 1991, 1983, 1997 and 2023.

Critical limits

Overview language is designed for orientation and should not be treated as a substitute for the evidence cited beneath it. The source lead contains qualifying language; that uncertainty should survive quotation, summary and reuse. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.

How to read it

Use the entry as an orientation point, then follow its citations and revision history. Names, dates and institutional relationships should be checked against the original record.

Best used for
  • Subject orientation
  • Search vocabulary
  • Locating named sources
Verify next

The closest primary source, responsible institution and strongest cited specialist reference.

Three-step research path

  1. Establish the record: confirm the title “PKCS”, its source revision and the description used here.
  2. Expand the search: follow PKCS primary sources, PKCS archive and PKCS research across catalogues and specialist indexes.
  3. Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.

Questions for further research

  1. Which source most directly establishes the central claim about “PKCS”?
  2. Which institution is responsible for the underlying evidence?
  3. What terminology or title could unlock a more precise catalogue search?
Subject index

Search terms from this dossier

Source & attribution

This entry incorporates text from PKCS” on English Wikipedia. Contributors are listed in the page history. Text is available under the Creative Commons Attribution-ShareAlike 4.0 License. Selected authority identifiers and statements are retrieved from Wikidata under CC0; their references and qualifiers remain part of the verification path.