Subject Identifiers for Security Event Tokens
draft-ietf-secevent-subject-identifiers-05
Security Events Working Group A. Backman, Ed.
Internet-Draft Amazon
Intended status: Standards Track M. Scurtescu
Expires: January 25, 2020 Coinbase
July 24, 2019
Subject Identifiers for Security Event Tokens
draft-ietf-secevent-subject-identifiers-05
Abstract
Security events communicated within Security Event Tokens may support
a variety of identifiers to identify the subject and/or other
principals related to the event. This specification formalizes the
notion of subject identifiers as named sets of well-defined claims
describing the subject, a mechanism for representing subject
identifiers within a [JSON] object such as a JSON Web Token [JWT] or
Security Event Token [SET], and a registry for defining and
allocating names for these claim sets.
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on January 25, 2020.
Copyright Notice
Copyright (c) 2019 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
Backman & Scurtescu Expires January 25, 2020 [Page 1]
Internet-Draft secevent-subject-identifiers July 2019
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Notational Conventions . . . . . . . . . . . . . . . . . . . 3
3. Subject Identifiers . . . . . . . . . . . . . . . . . . . . . 3
3.1. Account Subject Identifier Type . . . . . . . . . . . . . 3
3.2. Email Subject Identifier Type . . . . . . . . . . . . . . 4
3.2.1. Email Canonicalization . . . . . . . . . . . . . . . 4
3.3. Phone Number Subject Identifier Type . . . . . . . . . . 5
3.4. Issuer and Subject Subject Identifier Type . . . . . . . 5
3.5. Aliases Subject Identifier Type . . . . . . . . . . . . . 6
4. Subject Identifiers in JWTs . . . . . . . . . . . . . . . . . 7
4.1. "sub_id" Claim . . . . . . . . . . . . . . . . . . . . . 7
4.2. "sub_id" and "iss-sub" Subject Identifiers . . . . . . . 8
5. Privacy Considerations . . . . . . . . . . . . . . . . . . . 9
5.1. Identifier Correlation . . . . . . . . . . . . . . . . . 9
6. Security Considerations . . . . . . . . . . . . . . . . . . . 10
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10
7.1. Security Event Subject Identifier Types Registry . . . . 10
7.1.1. Registration Template . . . . . . . . . . . . . . . . 10
7.1.2. Initial Registry Contents . . . . . . . . . . . . . . 11
7.1.3. Guidance for Expert Reviewers . . . . . . . . . . . . 12
7.2. JSON Web Token Claims Registration . . . . . . . . . . . 12
7.2.1. Registry Contents . . . . . . . . . . . . . . . . . . 12
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 13
8.1. Normative References . . . . . . . . . . . . . . . . . . 13
8.2. Informative References . . . . . . . . . . . . . . . . . 14
Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 14
Change Log . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 15
1. Introduction
As described in section 1.2 of [SET], the subject of a security event
may take a variety of forms, including but not limited to a JWT
principal, an IP address, a URL, etc. Furthermore, even in the case
where the subject of an event is more narrowly scoped, there may be
multiple ways by which a given subject may be identified. For
Show full document text