RFC 9493

Subject Identifiers for Security Event Tokens, December 2023

File formats:

icon for HTML icon for text file icon for v3pdf icon for XML icon for inline errata
Also available: XML file for editing
 
Status:
PROPOSED STANDARD
Authors:
A. Backman, Ed.
M. Scurtescu
P. Jain
Stream:
IETF
Source:
secevent (sec)

Cite this RFC: TXT  |  XML  |   BibTeX

DOI:  https://doi.org/10.17487/RFC9493

Discuss this RFC: Send questions or comments to the mailing list id-event@ietf.org

Other actions: View Errata  |  Submit Errata  |  Find IPR Disclosures from the IETF  |  View History of RFC 9493


Abstract

Security events communicated within Security Event Tokens may support a variety of identifiers to identify subjects related to the event. This specification formalizes the notion of Subject Identifiers as structured information that describes a subject and named formats that define the syntax and semantics for encoding Subject Identifiers as JSON objects. It also establishes a registry for defining and allocating names for such formats as well as the JSON Web Token (JWT) "sub_id" Claim.


For the definition of Status, see RFC 2026.

For the definition of Stream, see RFC 8729.




Advanced Search