Cloud Authorization Use Cases Version 0 Committee Note 01 19 November 2014



Download 225.11 Kb.
Page2/11
Date conversion29.11.2017
Size225.11 Kb.
1   2   3   4   5   6   7   8   9   10   11

1.2References


The following references are used to provide definitions of and information on terms used throughout this document:

[NIST-SP800-145]

P. Mell, T. Grance, The NIST Definition of Cloud Computing SP800-145. National Institute of Standards and Technology (NIST) - Computer Security Division – Computer Security Resource Center (CSRC), January 2011. http://csrc.nist.gov/publications/nistpubs/800-145/SP800-145.pdf.

[REST-Def]

Fielding, Architectural Styles and the Design of Network-based Software Architectures. 2000. http://www.ics.uci.edu/~fielding/pubs/dissertation/top.

[RFC 1510]

IETF RFC, J. Kohl, C. Neuman. The Kerberos Network Authentication Requestor (V5). IETF RFC 1510, September 1993. http://www.ietf.org/rfc/rfc1510.txt.

[RFC 1738]

IETF RFC, Berners-Lee, et. al., Uniform Resource Locators (URL), IETF RFC 1738, December 1994. http://www.ietf.org/rfc/rfc1738.txt

[RFC 3986]

IETF RFC, Berners-Lee, et. al., Uniform Resource Locators (URL), IETF RFC 3986, January 2005. http://tools.ietf.org/html/rfc3986

[RFC 4949]

R. Shirley. et al., Internet Security Glossary, Version 2, IETF RFC 4949, August 2009. http://www.ietf.org/rfc/rfc4949.txt.

[SAML-Core-2.0]

OASIS Standard, Security Assertion Markup Language Assertions and Protocols for the OASIS Security Assertion Markup Language (SAML) V2.0, March 2005. http://docs.oasis-open.org/security/saml/v2.0/saml-core-2.0-os.pdf.

[SAML-Gloss-2.0]

OASIS Standard, Glossary for the OASIS Security Assertion Markup Language (SAML) V2.0, March 2005. http://docs.oasis-open.org/security/saml/v2.0/saml-glossary-2.0-os.pdf.

[W3C-XML]

W3C Extensible Markup Language (XML) Standard homepage. http://www.w3.org/XML/

[W3C-XML-1.0]

W3C Recommendation, Extensible Markup Language (XML) 1.0 (Fifth Edition),26 November 2008. http://www.w3.org/TR/xml/

[X.idmdef]

Recommendation ITU-T X.1252, Baseline identity management terms and definitions, International Telecommunication Union – Technical Communication Standardization Sector (ITU-T), April 2010. http://www.itu.int/rec/T-REC-X.1252-201004-I/

Use Case Composition


Use cases have been submitted from various TC members, but for ease of consumption and comparison, each has been presented using an agreed upon "Use Case Template" (described below) along with notable categorizations.

1.3Use Case Template


Each use case is presented using the following template sections:

  • Categories Covered

  • Applicable Deployment and Service Models

  • Actors

  • Systems

  • Notable Services

  • Dependencies

  • Assumptions

  • Process Flow

1.3.1Description / User Story


This section contains a general description of the use case in consumer language that highlights the compelling need for one or more aspects of Identity Management while interacting with a cloud deployment model.

1.3.2Goal or Desired Outcome


A general description of the intended outcome of the use case including any artifacts created.

1.3.3Notable Categorizations and Aspects


A listing of the Identity Management categories covered by the use case (as identified in section XXX)

1.3.4Featured Deployment and Service Models

This category contains a listing of one or more the cloud deployment or service models that are featured in the use case. The use case may feature one or more deployment or service models to present a concrete use case, but still be applicable to additional models. The deployment and service model definitions are those from [NIST-SP800-145] unless otherwise noted.

These categories and values include:



  • Featured (Cloud) Deployment Models

  • Private

  • Public

  • Community

  • Hybrid

  • None featured – This value means that use case may apply to any cloud deployment model.

  • Featured Service Models

  • Software-as-a-Service (SaaS)

  • Platform-as-a-Service (PaaS)

  • Infrastructure-as-a-Service (IaaS)

  • Other (i.e. other “as-a-Service” Models) – This value indicates that the use case should define its specific service model within the use case itself.

  • None featured – This value means that the use case may apply to any cloud deployment model.

1.3.5Actors


This category lists the actors that take part in the use case. These actors describe humans that perform a role within the cloud use case and should be reflected in the Process Flow section of each use case.

1.3.6Notable Services


A category lists any services (security or otherwise) that significantly contribute to the key aspects of the use case.

1.3.7Systems

This category lists any significant entities that are described as part of the use case, but do not require a more detailed description of their composition or structure in order to present the key aspects of the use case.

1.3.8Dependencies


A listing of any dependencies the use case has as a precondition.

1.3.9Assumptions


A listing of any assumptions made about the use case including its actors, services, environment, etc.

1.3.10Process Flow


This section contains a detailed, stepwise flow of the significant actions that comprise the use case.



1   2   3   4   5   6   7   8   9   10   11


The database is protected by copyright ©hestories.info 2017
send message

    Main page