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

《ETSI TS 133 222-2018 Digital cellular telecommunications system (Phase 2+) (GSM) Universal Mobile Telecommunications System (UMTS) LTE Generic Authentication Architecture (GAA) Acc.pdf》由会员分享，可在线阅读，更多相关《ETSI TS 133 222-2018 Digital cellular telecommunications system (Phase 2+) (GSM) Universal Mobile Telecommunications System (UMTS) LTE Generic Authentication Architecture (GAA) Acc.pdf（35页珍藏版）》请在麦多课文档分享上搜索。

1、 ETSI TS 133 222 V15.0.0 (2018-07) 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 15.0.0 Release 15) TECHNICAL SPECIFICATION ETSI ETSI TS 133 222 V15.0.0 (2018-07)13GPP TS 33.222 version 15.0.0 Release 15Reference RTS/TSGS-0333222vf00 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. ETSI 2018. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTMand the ETSI logo are trademarks of ETSI registered for the benefit of its Members. 3GPPTM and LTETMare trademarks of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. oneM2M logo is protect

9、ed for the benefit of its Members. GSMand the GSM logo are trademarks registered and owned by the GSM Association. ETSI ETSI TS 133 222 V15.0.0 (2018-07)23GPP TS 33.222 version 15.0.0 Release 15Intellectual Property Rights Essential patents IPRs essential or potentially essential to normative delive

10、rables 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 notified to ETSI in respect

11、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 to the existence of othe

12、r 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. Trademarks The present document may include trademarks and/or tradenames which are asserted and/or registered by their owners. ETSI claims no owner

13、ship of these except for any which are indicated as being the property of ETSI, and conveys no right to use or reproduce any trademark and/or tradename. Mention of those trademarks in the present document does not constitute an endorsement by ETSI of products, services or organizations associated wi

14、th those trademarks. Foreword This Technical Specification (TS) has been produced by ETSI 3rd Generation Partnership Project (3GPP). The present document may refer to technical specifications or reports using their 3GPP identities, UMTS identities or GSM identities. These should be interpreted as be

15、ing references to the corresponding ETSI deliverables. The cross reference between GSM, UMTS, 3GPP and ETSI identities can be found under http:/webapp.etsi.org/key/queryform.asp. Modal verbs terminology In the present document “shall“, “shall not“, “should“, “should not“, “may“, “need not“, “will“,

16、“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 provisions). “must“ and “must not“ are NOT allowed in ETSI deliverables except when used in direct citation. ETSI ETSI TS 133 222 V15.0.0 (2018-07)33GPP TS 3

17、3.222 version 15.0.0 Release 15Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 5g3Introduction 5g31 Scope 6g32 References 6g33 Definitions, symbols and abbreviations . 7g33.1 Definitions 7g33.2 Abbreviations . 8g34 Overview of the Security Architecture .

18、8g35 Authentication schemes 8g35.1 Reference model . 8g35.2 General requirements and principles 9g35.2.1 Requirements on the UE . 9g35.2.2 Requirements on the NAF 9g35.3 Shared key-based UE authentication with certificate-based NAF authentication 9 g35.3.0 Procedures. 9g35.3.1 TLS profile 11g35.3.1.

19、0 General 11g35.3.1.1 Protection mechanisms 11g35.3.1.2 Void. 11g35.3.1.3 Authentication of the AP/AS. 11g35.3.1.4 Authentication Failures . 11g35.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 12g35.4.0 Procedures. 1

20、2g35.4.1 TLS Profile . 14g35.4.1.0 General 14g35.4.1.1 Protection mechanisms 14g35.4.1.2 Authentication of the AP/AS. 14g35.4.1.3 Authentication Failures . 14g35.4.1.4 Set-up of Security parameters . 14g35.5 Certificate based mutual authentication between UE and application server . 14g35.5.1 Genera

21、l 14g35.5.2 TLS Profile . 15g35.5.2.1 General 15g35.5.2.2 Protection mechanisms 15g35.5.2.3 void . 15g36 Use of Authentication Proxy 16g36.1 Architectural view 16g36.2 Requirements and principles 17g36.4 Reference points . 17g36.4.1 Ua reference point . 17g36.4.2 AP-AS reference point 17g36.5 Manage

22、ment of UE identity . 18g36.5.1 Granularity of Authentication and Access Control by AP 18g36.5.1.1 Authorised Participant of GBA . 18g36.5.1.2 Authorised User of Application 18g36.5.2 Transfer of Asserted Identity from AP to AS . 18g36.5.2.1 Authorised Participant of GBA . 19g3ETSI ETSI TS 133 222 V

23、15.0.0 (2018-07)43GPP TS 33.222 version 15.0.0 Release 156.5.2.2 Authorised User of Application Anonymous to AS 19g36.5.2.3 Authorised User of Application with Transferred Identity asserted to AS 19g36.5.2.4 Authorised User of Application with Transferred Identity asserted to AS and Check of User In

24、serted Identity 19g3Annex A (informative): Technical Solutions for Access to Application Servers via Authentication Proxy and HTTPS . 20g3Annex B (informative): Guidance on Certificate-based mutual authentication between UE and application server . 21g3Annex C (informative): Considerations for GBA s

25、ecurity using a web browser and Javascript . 22g3C.1 Usage Scenario . 22g3C.2 Threats 22g3C.3 Control of GBA Credentials and GBA Module in the UE. 22g3C.3.1 General . 22g3C.3.2 Control Mechanism 1 Same Origin Authentication Tokens . 23g3C.3.3 Control Mechanism 2 Server Authenticated TLS . 23g3C.3.4

26、Control Mechanism 3 - Channel Binding . 23g3C.3.5 Control Mechanism 4 Key Usage 23g3C.4 Security Considerations 24g3C.4.1 General Scripting Security Considerations . 24g3C.4.2 GBA key control 24g3C.4.3 User grants 24g3C.4.4 Root CAs in Browser . 24g3Annex D (normative) Security measures for usage of

27、 GBA with a web browser . 25g3D.1 Extension of Protocol Mechanism used on Ua Reference Point 25g3D.1.1 General . 25g3D.1.2 Key derivation 25g3D.1.3 Channel binding . 25g3D.1.3.1 Background . 25g3D.1.3.2 Channel binding using RFC 5705 and RFC 5929 . 26g3D.2 Sequence flow 26g3D.2.1 Sequence flow with

28、channel binding 26g3D.3 Javascript GBA API description 30g3D.3.1 GBA API Description 30g3D.3.2 API usage . 31g3Annex -E (informative): Change history . 32g3History 34g3ETSI ETSI TS 133 222 V15.0.0 (2018-07)53GPP TS 33.222 version 15.0.0 Release 15Foreword This Technical Specification has been produc

29、ed by the 3rdGeneration Partnership Project (3GPP). The contents of the present document are subject to continuing work within the TSG and may change 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 chang

30、e 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 presented to TSG for approval; 3 or greater indicates TSG approved document under change control. y the second digit is incremented for all changes of substan

31、ce, i.e. technical enhancements, corrections, updates, etc. z the third digit is incremented when editorial only changes have been incorporated in 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 Pre

32、sence Server over the Ut reference point, which is based on HTTP. Other services like conferencing, messaging, push, etc. might be accessed using 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

33、 Generic Authentication Architecture. ETSI ETSI TS 133 222 V15.0.0 (2018-07)63GPP TS 33.222 version 15.0.0 Release 151 Scope The present document specifies secure access methods to Network Application Functions (NAF) using HTTP over TLS in the Generic Authentication Architecture (GAA), and provides

34、Stage 2 security requirements, principles and procedures for the access. The present document describes both direct access to an Application Server (AS) and access to an Application Server through an Authentication Proxy (AP). NOTE: Any application specific details for access to Applications Servers

35、 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 security for presence services. 2 References The following documents contain provisions which, through reference in this text, constitute provisions of the

36、 present document. - References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. - For 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 3G

37、PP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the 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.

38、220: “Generic Authentication Architecture (GAA); Generic Bootstrapping Architecture“. 4 3GPP TR 33.919: “Generic Authentication Architecture (GAA); 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 (

39、1999): “HTTP Authentication: Basic and Digest Access Authentication“. 11 IETF RFC 3310 (2002): “Hypertext Transfer Protocol (HTTP) Digest Authentication Using Authentication and Key Agreement (AKA)“. 12 IETF RFC 2616 (1999): “Hypertext Transfer Protocol (HTTP) HTTP/1.1“. 13 3GPP TS 33.210: “3G Secur

40、ity; Network Domain Security; IP network layer security“. 14 Void. 15 Void. 16 3GPP TS 33.221: “Generic Authentication Architecture (GAA); Support for subscriber certificates“. 17 Void. 18 3GPP TS 24.109: “Bootstrapping interface (Ub) and network application function interface (Ua); Protocol details

41、“. ETSI ETSI TS 133 222 V15.0.0 (2018-07)73GPP TS 33.222 version 15.0.0 Release 1519 3GPP TS 29.109: “Generic Authentication Architecture (GAA), Zh 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.2

42、2 Void. 23 3GPP TR 21.905: “Vocabulary for 3GPP Specifications“. 24 W3C Working Draft (Jan 22, 2013): “HTML5.1 Nightly A vocabulary and associated 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

43、20, 2011): “File API“, work in progress, http:/www.w3.org/TR/FileAPI/. 27 W3C Candidate Recommendation (Dec 8, 2011): “Web Storage“, work in progress, 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 Ex

44、porters for Transport Layer Security (TLS)“. 3 Definitions, symbols and abbreviations 3.1 Definitions For the purposes of the present document, the 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

45、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 together with some associated server-side state with the following additional requirement: During a GBA web session, a NAF can identify that the messages relate

46、 to the same individual GBA enabled terminal and a particular browser instance running in that terminal. The lifetime of the session is the lifetime 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 use

47、d 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 W3C specification 24 that defines the fifth major revision of the Hypertext Markup Language (HTML), the standard language for describing the contents and app

48、earance of Web pages. HTML FORM: A HTML form is a section of a HTML document containing normal content, markup, special elements called controls (checkboxes, radio buttons, text fields, password fields, etc.) and labels on those controls. End users generally “complete“ a form on a web page by modify

49、ing its controls (entering text, selecting radio buttons, etc.), before submitting the form to an agent for processing (e.g., to a web server).HTTPS: 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 that was formalized in the ECMAScript language standard. J