|
TECHNICAL SPECIFICATION
LTE;
Security assurance specification
for the PGW network product class
(3GPP TS 33.250 version 15.0.0 Release 15)
---------------------- Page: 1 ----------------------
3GPP TS 33.250 version 15.0.0 Release 15 1 ETSI TS 133 250 V15.0.0 (2018-09)
Reference
RTS/TSGS-0333250vf00
Keywords
LTE,SECURITY
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE
Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88
Important notice
The present document can be downloaded from:
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 only prevailing document 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 documents is available at
If you find errors in the present document, please send your comment to one of the following services:
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 2018.
All rights reserved.
TM TM TM
DECT , PLUGTESTS , UMTS and the ETSI logo are trademarks of ETSI registered for the benefit of its Members.
TM TM
3GPP and LTE are trademarks of ETSI registered for the benefit of its Members and
of the 3GPP Organizational Partners.
oneM2M logo is protected for the benefit of its Members.
GSM and the GSM logo are trademarks registered and owned by the GSM Association.
ETSI
---------------------- Page: 2 ----------------------
3GPP TS 33.250 version 15.0.0 Release 15 2 ETSI TS 133 250 V15.0.0 (2018-09)
Intellectual Property Rights
Essential patents
IPRs essential or potentially essential to normative deliverables 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 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 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.
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 being references to the corresponding ETSI deliverables.
The cross reference between GSM, UMTS, 3GPP and ETSI identities can be found under
.
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.250 version 15.0.0 Release 15 3 ETSI TS 133 250 V15.0.0 (2018-09)
Contents
Intellectual Property Rights . 2
Foreword . 2
Modal verbs terminology . 2
Foreword . 5
1 Scope . 6
2 References . 6
3 Definitions and abbreviations . 6
3.1 Definitions . 6
3.2 Abbreviations . 6
4 PGW-specific security requirements and related test cases . 7
4.1 Introduction . 7
4.2 PGW-specific security functional adaptations of requirements and related test cases . 7
4.2.1 Introduction. 7
4.2.2 Security functional requirements on the PGW deriving from 3GPP specifications and related test
cases . 7
4.2.2.1 Security functional requirements on the PGW deriving from 3GPP specifications – General
approach . 7
4.2.2.2 Per-user based packet filtering . 7
4.2.2.3 Charging ID Uniqueness . 8
4.2.2.4 TEID UNIQUENESS. 9
4.2.2.5 Mobility binding . 10
4.2.2.6 Inactive emergency PDN connection release . 11
4.2.3 Technical baseline. 12
4.2.3.1 Introduction . 12
4.2.3.2 Protecting data and information . 12
4.2.3.2.1 Protecting data and information – general . 12
4.2.3.2.2 Protecting data and information – unauthorized viewing . 12
4.2.3.2.3 Protecting data and information in storage . 12
4.2.3.2.4 Protecting data and information in transfer . 12
4.2.3.2.5 Logging access to personal data . 12
4.2.3.3 Protecting availability and integrity . 12
4.2.3.4 Authentication and authorization . 12
4.2.3.5 Protecting sessions . 12
4.2.3.5.1 Unpredictable GTP TEID . 12
4.2.3.6 Logging . 13
4.2.4 Operating systems . 13
4.2.5 Web servers . 13
4.2.6 Network devices . 13
4.2.6.1 Protection of Data and Information . 13
4.2.6.2 Protecting availability and integrity . 13
4.2.6.3 IP Address reallocation interval . 13
4.2.6.4 MS/UE-Mutual Access Prevention . 14
4.3 PGW-specific adaptations of hardening requirements and related test cases . 15
4.3.1 Introduction. 15
4.3.2 Technical baseline. 15
4.3.3 Operating systems . 15
4.3.4 Web servers . 15
4.3.5 Network devices . 15
4.3.5.1 Traffic separation . 15
4.3.5.2 User Plane Traffic Differentiation . 16
4.4 PGW-specific adaptations of basic vulnerability testing requirements and related test cases . 17
Annex A (informative): Change history . 18
History . 19
ETSI
---------------------- Page: 4 ----------------------
3GPP TS 33.250 version 15.0.0 Release 15 4 ETSI TS 133 250 V15.0.0 (2018-09)
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.
ETSI
---------------------- Page: 5 ----------------------
3GPP TS 33.250 version 15.0.0 Release 15 5 ETSI TS 133 250 V15.0.0 (2018-09)
1 Scope
The present document contains requirements and test cases that are specific to the PGW network product class. It refers
to the Catalogue of General Security Assurance Requirements and formulates specific adaptions of the requirements
and test cases given there, as well as specifying requirements and test cases unique to the PGW 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 TR 41.001: "GSM Release specifications".
[3] 3GPP TS 33.117: "Catalogue of General Security Assurance Requirements".
[4] 3GPP TR 33.916: "Security assurance scheme for 3GPP network products for 3GPP network
product classes".
[5] 3GPP TS 33.401: "3GPP System Architecture Evolution (SAE); Security architecture".
[6] 3GPP TS 23.401: "General Packet Radio Service (GPRS) enhancements for Evolved Universal
Terrestrial Radio Access Network (E-UTRAN) access".
[7] 3GPP TS 33.102: "3G security; Security architecture".
[8] 3GPP TS 32.251: "Telecommunication management; Charging management; Packet Switched
(PS) domain charging".
[9] 3GPP TS 23.060: "General Packet Radio Service (GPRS); Service description; Stage 2".
3 Definitions and abbreviations
3.1 Definitions
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 Abbreviations
For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An
abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in
3GPP TR 21.905 [1].
ETSI
---------------------- Page: 6 ----------------------
3GPP TS 33.250 version 15.0.0 Release 15 6 ETSI TS 133 250 V15.0.0 (2018-09)
4 PGW-specific security requirements and related test
cases
4.1 Introduction
The structure of the present document is aligned with TS 33.117[3] such that the PGW-specific adaptation of a generic
requirement in 33.117[3], clause 4, can be always found in clause 4 of present document.
The text on pre-requisites for testing in clause 4.1.2 of TS 33.117 [3] applies also to the present document.
4.2 PGW-specific security functional adaptations of
requirements and related test cases
4.2.1 Introduction
4.2.2 Security functional requirements on the PGW deriving from 3GPP
specifications and related test cases
4.2.2.1 Security functional requirements on the PGW deriving from 3GPP
specifications – General approach
In addition to the requirements and test cases in TS 33.117[3], clause 4.2.2, a PGW shall satisfy the following:
It is assumed for the purpose of the present SCAS that a PGW conforms to all mandatory security-related provisions
pertaining to a PGW in:
- 3GPP TS 33.401[5]: "EPS security architecture";
- other 3GPP specifications that make reference to TS 33.401[5] or are referred to from TS 33.401[5] (e.g. TS
23.401 [6] , TS 23.060[9], etc.);
- 3GPP TS 32.251[8]: " Packet Switched (PS) domain charging".
Since the PDN GW is the gateway which terminates the SGi interface, the security procedures pertaining to the PGW
are typically related to gateway functions. For example:
- Per-user based packet filtering (by e.g. deep packet inspection).
- Every IP-CAN bearer shall be assigned a unique identity number for billing purposes. (i.e. the Charging Id).
- The TEID is a unique identifier within one IP address of a logical node.
4.2.2.2 Per-user based packet filtering
Requirement Name: Per-user based packet filtering
Requirement Reference: TBA
Requirement Description: This requirement is identical to per-user based packet filtering (by e.g. deep packet
inspection) as specified in TS 23.401, clause 4.4.3.3.
Threat References: TBA
Security Objective References: TBA
Test Case:
Purpose:
Verify that PGW supports a Per-user based packet filtering.
Pre-Conditions:
ETSI
---------------------- Page: 7 ----------------------
3GPP TS 33.250 version 15.0.0 Release 15 7 ETSI TS 133 250 V15.0.0 (2018-09)
- The tester has a privilege to configure the filtering policy on the PGW to make the PGW can filter the packets
per-user
- Some UE (e.g. UE1 and UE2) are registered on the PGW.
- The PGW can receive the packets from the UE1 and UE2.
- A network traffic analyser on the PGW (e.g. tcpdump) is available.
Execution Steps
1. The tester configures the different filtering policy for the UE1and the UE2 on the PGW, e.g. the PGW
forwards the packets from the UE1 to SGi and drops the packets from the UE2.
2. The tester sends the packets from the UE1 to the PGW.
3. The tester sends the packets from the UE2 to the PGW.
4. The tester checks the filtered packets using the network traffic analyser.
Expected Results:
The PGW can filter the packets per- user according the configured filtering policy, e.g. the PGW forwards the packets
from the UE1 to SGi in the step 2 and drops the packets from the UE2 in the step 3.
Expected format of evidence:
Evidence suitable for the interface, e.g. screenshot contains the operation results, pcap file demonstrating that the UE2’s
packets are correctly received but unavailable on the SGi interface while the UE1’s packets are correctly sent to SGi.
4.2.2.3 Charging ID Uniqueness
Requirement Name: Charging ID Uniqueness
Requirement Reference: TBA
Requirement Description: "Every IP-CAN bearer shall be assigned a unique identity number for billing purposes. (i.e.
the Charging Id)" as specified in 3GPP TS 32.251 [8], clause 5.1.1.
Note: A charging ID is not assigned to more than one active IP-CAN bearers at the same time.The reuse of Charging
ID is possible after an IP-CAN session has been terminated and the Charging ID related to this IP-CAN
session has been released.
Threat References: TBA
Security Objective References: TBA
Test Case:
Purpose:
Verify that the Charging ID value set in the Information Element Bearer Context within a CreateSessionResponse is
unique.
Pre-Conditions:
Test environment with P-GW and S-GW, PCRF. PCRF and S-GW may be real nodes or simulated.
The tester is able to trace traffic between the P-GW and the S-GW (real or simulated)
Execution Step
1. The tester intercepts the traffic between the P-GW
...