ETSI TS 133 222-2017 Digital cellular telecommunications system (Phase 2+) (GSM) Universal Mobile Telecommunications System (UMTS) LTE Generic Authentication Architecture (GAA) Acc.pdf

1、 ETSI TS 133 222 V14.0.0 (2017-04) Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); LTE; Generic Authentication Architecture (GAA); Access to network application functions using Hypertext Transfer Protocol over Transport Layer Security (

2、HTTPS) (3GPP TS 33.222 version 14.0.0 Release 14) TECHNICAL SPECIFICATION ETSI ETSI TS 133 222 V14.0.0 (2017-04)13GPP TS 33.222 version 14.0.0 Release 14Reference RTS/TSGS-0333222ve00 Keywords GSM,LTE,SECURITY,UMTS ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE Tel.: +33 4 92 94

3、 42 00 Fax: +33 4 93 65 47 16 Siret N 348 623 562 00017 - NAF 742 C Association but non lucratif enregistre la Sous-Prfecture de Grasse (06) N 7803/88 Important notice The present document can be downloaded from: http:/www.etsi.org/standards-search The present document may be made available in elect

4、ronic versions and/or in print. The content of any electronic and/or print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any existing or perceived difference in contents between such versions and/or in print, the only prevailing do

5、cument is the print of the Portable Document Format (PDF) version kept on a specific network drive within ETSI Secretariat. Users of the present document should be aware that the document may be subject to revision or change of status. Information on the current status of this and other ETSI documen

6、ts is available at https:/portal.etsi.org/TB/ETSIDeliverableStatus.aspx If you find errors in the present document, please send your comment to one of the following services: https:/portal.etsi.org/People/CommiteeSupportStaff.aspx Copyright Notification No part may be reproduced or utilized in any f

7、orm or by any means, electronic or mechanical, including photocopying and microfilm except as authorized by written permission of ETSI. The content of the PDF version shall not be modified without the written authorization of ETSI. The copyright and the foregoing restriction extend to reproduction i

8、n all media. European Telecommunications Standards Institute 2017. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTMand the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members. 3GPPTM and LTE are Trade Marks of ETSI registered for the benefit of its Members and of the 3GPP Org

9、anizational Partners. oneM2M logo is protected for the benefit of its Members GSM and the GSM logo are Trade Marks registered and owned by the GSM Association. ETSI ETSI TS 133 222 V14.0.0 (2017-04)23GPP TS 33.222 version 14.0.0 Release 14Intellectual Property Rights IPRs essential or potentially es

10、sential to the present document may have been declared to ETSI. The information pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found in ETSI SR 000 314: “Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs not

11、ified to ETSI in respect of ETSI standards“, which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web server (https:/ipr.etsi.org/). Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee can be given as

12、 to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web server) which are, or may be, or may become, essential to the present document. Foreword This Technical Specification (TS) has been produced by ETSI 3rd Generation Partnership Project (3GPP). The presen

13、t document may refer to technical specifications or reports using their 3GPP identities, UMTS identities or GSM identities. These should be interpreted as being references to the corresponding ETSI deliverables. The cross reference between GSM, UMTS, 3GPP and ETSI identities can be found under http:

14、/webapp.etsi.org/key/queryform.asp. Modal verbs terminology In the present document “shall“, “shall not“, “should“, “should not“, “may“, “need not“, “will“, “will not“, “can“ and “cannot“ are to be interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of

15、provisions). “must“ and “must not“ are NOT allowed in ETSI deliverables except when used in direct citation. ETSI ETSI TS 133 222 V14.0.0 (2017-04)33GPP TS 33.222 version 14.0.0 Release 14Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 5g3Introduction 5g3

16、1 Scope 6g32 References 6g33 Definitions, symbols and abbreviations . 7g33.1 Definitions 7g33.2 Abbreviations . 8g34 Overview of the Security Architecture . 8g35 Authentication schemes 9g35.1 Reference model . 9g35.2 General requirements and principles 9g35.2.1 Requirements on the UE . 9g35.2.2 Requ

17、irements on the NAF 9g35.3 Shared key-based UE authentication with certificate-based NAF authentication 10g35.3.0 Procedures. 10g35.3.1 TLS profile 11g35.3.1.0 General 11g35.3.1.1 Protection mechanisms 12g35.3.1.2 Void. 12g35.3.1.3 Authentication of the AP/AS. 12g35.3.1.4 Authentication Failures . 1

18、2g35.3.1.5 Set-up of Security parameters . 12g35.3.1.6 Error cases . 12g35.4 Shared key-based mutual authentication between UE and NAF 13g35.4.0 Procedures. 13g35.4.1 TLS Profile . 14g35.4.1.0 General 14g35.4.1.1 Protection mechanisms 14g35.4.1.2 Authentication of the AP/AS. 15g35.4.1.3 Authenticati

19、on Failures . 15g35.4.1.4 Set-up of Security parameters . 15g35.5 Certificate based mutual authentication between UE and application server . 15g35.5.1 General 15g35.5.2 TLS Profile . 15g35.5.2.1 General 15g35.5.2.2 Protection mechanisms 16g35.5.2.3 void . 16g36 Use of Authentication Proxy 17g36.1 A

20、rchitectural view 17g36.2 Requirements and principles 18g36.4 Reference points . 19g36.4.1 Ua reference point . 19g36.4.2 AP-AS reference point 19g36.5 Management of UE identity . 19g36.5.1 Granularity of Authentication and Access Control by AP 19g36.5.1.1 Authorised Participant of GBA . 19g36.5.1.2

21、 Authorised User of Application 20g36.5.2 Transfer of Asserted Identity from AP to AS . 20g36.5.2.1 Authorised Participant of GBA . 20g3ETSI ETSI TS 133 222 V14.0.0 (2017-04)43GPP TS 33.222 version 14.0.0 Release 146.5.2.2 Authorised User of Application Anonymous to AS 20g36.5.2.3 Authorised User of

22、 Application with Transferred Identity asserted to AS 20g36.5.2.4 Authorised User of Application with Transferred Identity asserted to AS and Check of User Inserted Identity 21g3Annex A (informative): Technical Solutions for Access to Application Servers via Authentication Proxy and HTTPS . 22g3Anne

23、x B (informative): Guidance on Certificate-based mutual authentication between UE and application server . 23g3Annex C (informative): Considerations for GBA security using a web browser and Javascript . 24g3C.1 Usage Scenario . 24g3C.2 Threats 24g3C.3 Control of GBA Credentials and GBA Module in the

24、 UE. 24g3C.3.1 General . 24g3C.3.2 Control Mechanism 1 Same Origin Authentication Tokens . 25g3C.3.3 Control Mechanism 2 Server Authenticated TLS . 25g3C.3.4 Control Mechanism 3 - Channel Binding . 25g3C.3.5 Control Mechanism 4 Key Usage 25g3C.4 Security Considerations 26g3C.4.1 General Scripting Se

25、curity Considerations . 26g3C.4.2 GBA key control 26g3C.4.3 User grants 26g3C.4.4 Root CAs in Browser . 26g3Annex D (normative): Security measures for usage of GBA with a web browser . 27g3D.1. Extension of Protocol Mechanism used on Ua Reference Point 27g3D.1.1 General 27g3D.1.2 Key derivation 27g3

26、D.1.3 Channel binding . 27g3D.1.3.1 Background 27g3D.1.3.2 Channel binding using RFC 5705 and RFC 5929 28g3D.2 Sequence flow 28g3D.2.1 Sequence flow with channel binding 28g3D.3 Javascript GBA API description 32g3D.3.1 GBA API Description 32g3D.3.2 API usage . 33g3Annex -E (informative): Change hist

27、ory . 34g3History 36g3ETSI ETSI TS 133 222 V14.0.0 (2017-04)53GPP TS 33.222 version 14.0.0 Release 14Foreword This Technical Specification has been produced by the 3rdGeneration Partnership Project (3GPP). The contents of the present document are subject to continuing work within the TSG and may cha

28、nge following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: Version x.y.z where: x the first digit: 1 presented to TSG for information; 2 pres

29、ented to TSG for approval; 3 or greater indicates TSG approved document under change control. y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. z the third digit is incremented when editorial only changes have been incorporated in

30、 the document. Introduction A number of services might be accessed over HTTP. For the Presence Service, it shall be possible to manage the data on the Presence Server over the Ut reference point, which is based on HTTP. Other services like conferencing, messaging, push, etc. might be accessed using

31、HTTP. Access to services over HTTP can be done in a secure manner. The present document describes how the access over HTTP can be secured using TLS in the Generic Authentication Architecture. ETSI ETSI TS 133 222 V14.0.0 (2017-04)63GPP TS 33.222 version 14.0.0 Release 141 Scope The present document

32、specifies secure access methods to Network Application Functions (NAF) using HTTP over TLS in the Generic Authentication Architecture (GAA), and provides Stage 2 security requirements, principles and procedures for the access. The present document describes both direct access to an Application Serve

33、r (AS) and access to an Application Server through an Authentication Proxy (AP). NOTE: Any application specific details for access to Applications Servers are not in scope of this specification and are covered in separate documents. An example of such a document is TS 33.141 5, which specifies the s

34、ecurity for presence services. 2 References The following documents contain provisions which, through reference in this text, constitute provisions of the present document. - References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. - F

35、or a specific reference, subsequent revisions do not apply. - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as t

36、he present document. 1 3GPP TS 23.002: “Network architecture“. 2 3GPP TS 22.250: “IP Multimedia Subsystem (IMS) group management“; Stage 1“. 3 3GPP TS 33.220: “Generic Authentication Architecture (GAA); Generic Bootstrapping Architecture“. 4 3GPP TR 33.919: “Generic Authentication Architecture (GAA)

37、; System description“. 5 3GPP TS 33.141: “Presence Service; Security“. 6 Void. 7 Void. 8 Void. 9 IETF RFC 2818 (2000): “HTTP Over TLS“. 10 IETF RFC 2617 (1999): “HTTP Authentication: Basic and Digest Access Authentication“. 11 IETF RFC 3310 (2002): “Hypertext Transfer Protocol (HTTP) Digest Authenti

38、cation Using Authentication and Key Agreement (AKA)“. 12 IETF RFC 2616 (1999): “Hypertext Transfer Protocol (HTTP) HTTP/1.1“. 13 3GPP TS 33.210: “3G Security; Network Domain Security; IP network layer security“. 14 Void. 15 Void. 16 3GPP TS 33.221: “Generic Authentication Architecture (GAA); Support

39、 for subscriber certificates“. 17 Void. 18 3GPP TS 24.109: “Bootstrapping interface (Ub) and network application function interface (Ua); Protocol details“. ETSI ETSI TS 133 222 V14.0.0 (2017-04)73GPP TS 33.222 version 14.0.0 Release 1419 3GPP TS 29.109: “Generic Authentication Architecture (GAA), Z

40、h and Zn Interface based on the Diameter protocol; Stage 3“. 20 3GPP TS 33.310: “Network Domain Security (NDS); Authentication Framework (AF)“. 21 V oid. 22 Void. 23 3GPP TR 21.905: “Vocabulary for 3GPP Specifications“. 24 W3C Working Draft (Jan 22, 2013): “HTML5.1 Nightly A vocabulary and associate

41、d APIs for HTML and XHTML“, work in progress, http:/dev.w3.org/html5/spec/. 25 IETF RFC 5929 (2010): “Channel Bindings for TLS“. 26 W3C Working Draft (Oct 20, 2011): “File API“, work in progress, http:/www.w3.org/TR/FileAPI/. 27 W3C Candidate Recommendation (Dec 8, 2011): “Web Storage“, work in prog

42、ress, http:/www.w3.org/TR/webstorage/ 28 3GPP TS 33.203: “3G security; Access security for IP-based services“. 29 IETF RFC 5705 (2010): “Keying Material Exporters for Transport Layer Security (TLS)“. 3 Definitions, symbols and abbreviations 3.1 Definitions For the purposes of the present document, t

43、he terms and definitions given in TR 21.905 23 and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 23. GBA web session: A GBA web session consists of a sequence of related HTTP request/response transactions toget

44、her with some associated server-side state with the following additional requirement: During a GBA web session, a NAF can identify that the messages relate to the same individual GBA enabled terminal and a particular browser instance running in that terminal. The lifetime of the session is the lifet

45、ime of the Ks_js_NAF which is equal or shorter than the Ks_NAF lifetime and it is also equal or shorter than the lifetime of the TLS session, which was used to derive the Ks_js_NAF. NOTE: The NAF and the UE may have to recalculate the key, when the TLS session is re-established. HTML5: HTML5 is a W3

46、C specification 24 that defines the fifth major revision of the Hypertext Markup Language (HTML), the standard language for describing the contents and appearance of Web pages. HTML FORM: A HTML form is a section of a HTML document containing normal content, markup, special elements called controls

47、(checkboxes, radio buttons, text fields, password fields, etc.) and labels on those controls. End users generally “complete“ a form on a web page by modifying its controls (entering text, selecting radio buttons, etc.), before submitting the form to an agent for processing (e.g., to a web server).HT

48、TPS: For the purpose of this document, HTTPS refers to the general concept securing the HTTP protocol using TLS. In some contexts, like in the IETF, the term HTTPS is used to refer to the reserved port number (443) for HTTP/TLS traffic. JavaScript: JavaScript is a prototype-based scripting language

49、that was formalized in the ECMAScript language standard. JavaScript is primarily used in the form of client-side JavaScript, implemented as part of a Web browser in order to provide enhanced user interfaces and dynamic websites. Reverse Proxy: A reverse proxy is a web server system that is capable of serving web pages sourced from other web servers (AS), making these pages look like they originated at the reverse proxy. Same origin policy: Same origin policy is a security mechanism in a client bro