RFC 8152: CBOR Object Signing and Encryption (COSE)
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 9052, RFC 9053.
Current document in this lineage: RFC 9052 — CBOR Object Signing and Encryption (COSE): Structures and Process; RFC 9053 — CBOR Object Signing and Encryption (COSE): Initial Algorithms
In plain English — editorial summary, not part of the RFC
Concise Binary Object Representation (CBOR) is a data format designed for small code size and small message size. There is a need for the ability to have basic security services defined for this data format. This document defines the CBOR Object Signing and Encryption (COSE) protocol. This specification describes how to create and process signatures, message authentication codes, and encryption using CBOR for serialization. This specification additionally describes how to represent cryptographic keys using CBOR.
Document record
- Document ID
- RFC8152
- Published
- July 2017
- Authors
- J. Schaad
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 121
- Also known as
- —
Topics
Standards lineage
This document is one revision in a chain of 3 RFCs, each formally replacing the one before it.
- RFC 8152 (2017)
- RFC 9052 (2022)
- RFC 9053 (2022) ✓
Read the full history of CBOR Object Signing and Encryption (COSE): Initial Algorithms →
Referenced by
2 later RFCs formally update or obsolete part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8387Practical Considerations and Implementation Experiences in Securing Smart Object NetworksCurrent
May 2018
- RFC 5903Elliptic Curve Groups modulo a Prime (ECP Groups) for IKE and IKEv2Current
June 2010
- RFC 7748Elliptic Curves for SecurityCurrent
January 2016
- RFC 8813Clarifications for Elliptic Curve Cryptography Subject Public Key InformationCurrent
August 2020
- RFC 9142Key Exchange (KEX) Method Updates and Recommendations for Secure Shell (SSH)Current
January 2022
- RFC 9200Authentication and Authorization for Constrained Environments Using the OAuth 2.0 Framework (ACE-OAuth)Current
August 2022
- RFC 9201Additional OAuth Parameters for Authentication and Authorization for Constrained Environments (ACE)Current
August 2022
- RFC 9203The Object Security for Constrained RESTful Environments (OSCORE) Profile of the Authentication and Authorization for Constrained Environments (ACE) FrameworkCurrent
August 2022
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?