ETSI TS 133 513 V17.2.0 (2023-06)

5G; 5G Security Assurance Specification (SCAS); User Plane Function (UPF) (3GPP TS 33.513 version 17.2.0 Release 17)

RTS/TSGS-0333513vh20

General Information

• Status: Not Published
• Technical Committee: 3GPP SA 3 - Security
• Current Stage: 8 - TB approval
• Completion Date: 16-Jun-2023

Standards Content (Sample)

ETSI TS 133 513 V17.2.0 (2023-07)
TECHNICAL SPECIFICATION
5G;
5G Security Assurance Specification (SCAS);
User Plane Function (UPF)
(3GPP TS 33.513 version 17.2.0 Release 17)
---------------------- Page: 1 ----------------------
3GPP TS 33.513 version 17.2.0 Release 17 1 ETSI TS 133 513 V17.2.0 (2023-07)
Reference
RTS/TSGS-0333513vh20
Keywords
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE
Tel.: [phone] Fax: [phone]
Siret N° 348 623 562 00017 - APE 7112B
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° w061004871
Important notice
The present document can be downloaded from:
https://www.etsi.org/standards-search

The present document may be made available in electronic 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 prevailing version of an ETSI

deliverable is the one made publicly available in PDF format at www.etsi.org/deliver.

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 documents 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

If you find a security vulnerability in the present document, please report it through our

Coordinated Vulnerability Disclosure Program:
https://www.etsi.org/standards/coordinated-vulnerability-disclosure
Notice of disclaimer & limitation of liability

The information provided in the present deliverable is directed solely to professionals who have the appropriate degree of

experience to understand and interpret its content in accordance with generally accepted engineering or

other professional standard and applicable regulations.

No recommendation as to products and services or vendors is made or should be implied.

No representation or warranty is made that this deliverable is technically accurate or sufficient or conforms to any law

and/or governmental rule and/or regulation and further, no representation or warranty is made of merchantability or fitness

for any particular purpose or against infringement of intellectual property rights.

In no event shall ETSI be held liable for loss of profits or any other incidental or consequential damages.

Any software contained in this deliverable is provided "AS IS" with no warranties, express or implied, including but not

limited to, the warranties of merchantability, fitness for a particular purpose and non-infringement of intellectual property

rights and ETSI shall not be held liable in any event for any damages whatsoever (including, without limitation, damages

for loss of profits, business interruption, loss of information, or any other pecuniary loss) arising out of or related to the use

of or inability to use the software.
Copyright Notification

No part may be reproduced or utilized in any form 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 in all media.
© ETSI 2023.
All rights reserved.
ETSI
---------------------- Page: 2 ----------------------
3GPP TS 33.513 version 17.2.0 Release 17 2 ETSI TS 133 513 V17.2.0 (2023-07)
Intellectual Property Rights
Essential patents

IPRs essential or potentially essential to normative deliverables may have been declared to ETSI. The declarations

pertaining to these essential IPRs, if any, are 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 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 Directives including the ETSI IPR Policy, no investigation regarding the essentiality of IPRs,

including IPR searches, has been carried out by ETSI. No guarantee can be given as 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.
Trademarks

The present document may include trademarks and/or tradenames which are asserted and/or registered by their owners.

ETSI claims no ownership 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 with those trademarks.

DECT™, PLUGTESTS™, UMTS™ and the ETSI logo are trademarks of ETSI registered for the benefit of its

Members. 3GPP™ and LTE™ are trademarks of ETSI registered for the benefit of its Members and of the 3GPP

Organizational Partners. oneM2M™ logo is a trademark of ETSI registered for the benefit of its Members and of the

oneM2M Partners. GSM and the GSM logo are trademarks registered and owned by the GSM Association.

Legal Notice

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. These shall be

interpreted as being references to the corresponding ETSI deliverables.

The cross reference between 3GPP and ETSI identities can be found under https://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

provisions).

"must" and "must not" are NOT allowed in ETSI deliverables except when used in direct citation.

ETSI
---------------------- Page: 3 ----------------------
3GPP TS 33.513 version 17.2.0 Release 17 3 ETSI TS 133 513 V17.2.0 (2023-07)
Contents

Intellectual Property Rights ................................................................................................................................ 2

Legal Notice ....................................................................................................................................................... 2

Modal verbs terminology .................................................................................................................................... 2

Foreword ............................................................................................................................................................. 4

1 Scope ........................................................................................................................................................ 6

2 References ................................................................................................................................................ 6

3 Definitions of terms, symbols and abbreviations ..................................................................................... 6

3.1 Terms .................................................................................................................................................................. 6

3.2 Symbols .............................................................................................................................................................. 6

3.3 Abbreviations ..................................................................................................................................................... 7

4 UPF-specific security requirements and related test cases ....................................................................... 7

4.1 Introduction ........................................................................................................................................................ 7

4.2 UPF-specific security functional requirements and related test cases ................................................................ 7

4.2.1 Introduction................................................................................................................................................... 7

4.2.2 Security functional requirements on the UPF deriving from 3GPP specifications and related test

cases .............................................................................................................................................................. 7

4.2.2.0 General .................................................................................................................................................... 7

4.2.2.1 Confidentiality protection of user data transported over N3 interface. ................................................... 7

4.2.2.2 Integrity protection of user data transported over N3 interface ............................................................... 8

4.2.2.3 Replay protection of user data transported over N3 interface ................................................................. 9

4.2.2.4 Protection of user data transported over N9 interface Within a PLMN .................................................. 9

4.2.2.5 Signalling Data Protection .................................................................................................................... 10

4.2.2.6 TEID uniqueness ................................................................................................................................... 11

4.2.2.7 IPUPS .................................................................................................................................................... 12

4.2.2.8 Protection against malformed GTP-U messages ................................................................................... 13

4.2.3 Technical baseline....................................................................................................................................... 13

4.2.3.1 Introduction ........................................................................................................................................... 13

4.2.3.2 Protecting data and information............................................................................................................. 13

4.2.3.2.1 Protecting data and information – general ....................................................................................... 13

4.2.3.2.2 Protecting data and information – unauthorized viewing ................................................................ 14

4.2.3.2.3 Protecting data and information in storage ...................................................................................... 14

4.2.3.2.4 Protecting data and information in transfer ...................................................................................... 14

4.2.3.2.5 Logging access to personal data ...................................................................................................... 14

4.2.3.3 Protecting availability and integrity ....................................................................................................... 14

4.2.3.4 Authentication and authorization ........................................................................................................... 14

4.2.3.5 Protecting sessions ................................................................................................................................ 14

4.2.3.6 Logging ................................................................................................................................................. 14

4.2.4 Operating systems ....................................................................................................................................... 14

4.2.5 Web Servers ................................................................................................................................................ 14

4.2.6 Network Devices ........................................................................................................................................ 14

4.3 UPF-specific adaptations of hardening requirements and related test cases .................................................... 14

4.3.1 Introduction................................................................................................................................................. 14

4.3.2 Technical baseline....................................................................................................................................... 14

4.3.3 Operating systems ....................................................................................................................................... 15

4.3.4 Web servers ................................................................................................................................................ 15

4.3.5 Network devices ......................................................................................................................................... 15

4.3.6 Network functions in service-based architecture ........................................................................................ 15

4.4 UPF-specific adaptations of basic vulnerability testing requirements and related test cases ........................... 15

Annex A (informative): Change history ....................................................................................................... 16

History .............................................................................................................................................................. 17

ETSI
---------------------- Page: 4 ----------------------
3GPP TS 33.513 version 17.2.0 Release 17 4 ETSI TS 133 513 V17.2.0 (2023-07)
Foreword

This Technical Specification has been produced by the 3rd Generation 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 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 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 substance, i.e. technical enhancements, corrections,

updates, etc.

z the third digit is incremented when editorial only changes have been incorporated in the document.

In the present document, modal verbs have the following meanings:
shall indicates a mandatory requirement to do something
shall not indicates an interdiction (prohibition) to do something

The constructions "shall" and "shall not" are confined to the context of normative provisions, and do not appear in

Technical Reports.

The constructions "must" and "must not" are not used as substitutes for "shall" and "shall not". Their use is avoided

insofar as possible, and they are not used in a normative context except in a direct citation from an external, referenced,

non-3GPP document, or so as to maintain continuity of style when extending or modifying the provisions of such a

referenced document.
should indicates a recommendation to do something
should not indicates a recommendation not to do something
may indicates permission to do something
need not indicates permission not to do something

The construction "may not" is ambiguous and is not used in normative elements. The unambiguous constructions

"might not" or "shall not" are used instead, depending upon the meaning intended.

can indicates that something is possible
cannot indicates that something is impossible

The constructions "can" and "cannot" are not substitutes for "may" and "need not".

will indicates that something is certain or expected to happen as a result of action taken by an agency

the behaviour of which is outside the scope of the present document

will not indicates that something is certain or expected not to happen as a result of action taken by an

agency the behaviour of which is outside the scope of the present document

might indicates a likelihood that something will happen as a result of action taken by some agency the

behaviour of which is outside the scope of the present document
ETSI
---------------------- Page: 5 ----------------------
3GPP TS 33.513 version 17.2.0 Release 17 5 ETSI TS 133 513 V17.2.0 (2023-07)

might not indicates a likelihood that something will not happen as a result of action taken by some agency

the behaviour of which is outside the scope of the present document
In addition:
is (or any other verb in the indicative mood) indicates a statement of fact

is not (or any other negative verb in the indicative mood) indicates a statement of fact

The constructions "is" and "is not" do not indicate requirements.
ETSI
---------------------- Page: 6 ----------------------
3GPP TS 33.513 version 17.2.0 Release 17 6 ETSI TS 133 513 V17.2.0 (2023-07)
1 Scope

The present document contains requirements and test cases that are specific to the UPF network product class. It refers

to the Catalogue of General Security Assurance Requirements and formulates specific adaptions of the requirements

and test cases. It also specifies the requirements and test cases unique to the UPF network product class.

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.
- 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 3GPP 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 TR 21.905: "Vocabulary for 3GPP Specifications".

[2] 3GPP TS 33.501 (Release 15): "Security architecture and procedures for 5G system".

[3] 3GPP TS 33.117: "Catalogue of general security assurance requirements".
[4] 3GPP TS 23.501: "System Architecture for 5G system".

[5] 3GPP TS 29.281: "General Packet Radio System (GPRS) Tunnelling Protocol User Plane

(GTPv1-U) ".

[6] 3GPP TS 23.060: "General Packet Radio Service (GPRS); Service description; Stage 2".

[7] 3GPP TR 33.926: "Security Assurance Specification (SCAS) threats and critical assets in 3GPP

network product classes".

[8] 3GPP TS 33.501 (Release 16): "Security architecture and procedures for 5G system".

3 Definitions of terms, symbols and abbreviations
3.1 Terms

For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [1] and the following

apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP

TR 21.905 [1].
3.2 Symbols
Void.
ETSI
---------------------- Page: 7 ----------------------
3GPP TS 33.513 versio
...