SCIM Use Cases for SECEVENTS
draft-hunt-secevent-usecases-00

Document Type Active Internet-Draft (individual)
Last updated 2017-07-02
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                       P. Hunt, Ed.
Internet-Draft                                                    Oracle
Intended status: Standards Track                               M. Ansari
Expires: January 1, 2018                                           Cisco
                                                           June 30, 2017

                      SCIM Use Cases for SECEVENTS
                    draft-hunt-secevent-usecases-00

Abstract

   This specification defines the SCIM use cases for the SECEVENTs
   working group.

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 http://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 1, 2018.

Copyright Notice

   Copyright (c) 2017 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
   (http://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
   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.

Hunt & Ansari            Expires January 1, 2018                [Page 1]
Internet-Draft        draft-hunt-secevent-usecases             June 2017

Table of Contents

   1.  Introduction and Overview . . . . . . . . . . . . . . . . . .   2
     1.1.  Notational Conventions  . . . . . . . . . . . . . . . . .   3
     1.2.  Definitions . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  SCIM Background . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  High-Level Requirements . . . . . . . . . . . . . . . . . . .   5
     3.1.  SCIM Event Trigger Requirements . . . . . . . . . . . . .   5
     3.2.  SCIM Security Model Considerations  . . . . . . . . . . .   5
     3.3.  Control Plane Assumptions . . . . . . . . . . . . . . . .   6
     3.4.  Network and Protocol Operational Considerations . . . . .   8
     3.5.  Dynamic Filtering Considerations  . . . . . . . . . . . .   8
     3.6.  Directory and Application Provisioning  . . . . . . . . .   8
   4.  Use Cases . . . . . . . . . . . . . . . . . . . . . . . . . .   9
     4.1.  Scenario 1[P0]: Cloud-to-Enterprise PUSH and Cloud-to-
           Cloud PUSH  . . . . . . . . . . . . . . . . . . . . . . .   9
     4.2.  Scenario 2[P0]: Cloud-to-Enterprise POLLING . . . . . . .  12
     4.3.  Scenario 3[P2]: Cloud-to-Mobile Application PUSH  . . . .  16
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .  16
   6.  Privacy Considerations  . . . . . . . . . . . . . . . . . . .  17
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  17
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  17
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .  17
     8.2.  Informative References  . . . . . . . . . . . . . . . . .  17
   Appendix A.  Acknowledgments  . . . . . . . . . . . . . . . . . .  18
   Appendix B.  Change Log . . . . . . . . . . . . . . . . . . . . .  18
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  19

1.  Introduction and Overview

   SCIM is a system intended for provisioning identities (such as
   enterprise users or consumers) and other objects across security
   domains to a cloud based service providers.  SCIM defines an
   extensible JSON [RFC7643] document format and profiles HTTP protocol
   [RFC7644].  In practice, SCIM service providers are applications
   supporting pre-provisioning support, or may be a service provider
   directory upon which applications are integrated.

   This document defines the operational requirements SCIM deployers
   have for the use of triggers, as defined in the SCIM Use Cases
   specification [RFC7642], and used in the form of security events and
   the requirements for management based on SCIM architectural
   assumptions.

Hunt & Ansari            Expires January 1, 2018                [Page 2]
Show full document text