ETSI TS 133 117 V14.5.0 (2019-04)

Universal Mobile Telecommunications System (UMTS); LTE; Catalogue of general security assurance requirements (3GPP TS 33.117 version 14.5.0 Release 14)

RTS/TSGS-0333117ve50

General Information

• Status: Published
• Publication Date: 29-Apr-2019
• Technical Committee: 3GPP SA 3 - Security
• Current Stage: 12 - Completion
• Completion Date: 30-Apr-2019

Standards Content (Sample)

ETSI TS 133 117 V14.5.0 (2019-04)






TECHNICAL SPECIFICATION
Universal Mobile Telecommunications System (UMTS);
LTE;
Catalogue of general security assurance requirements
(3GPP TS 33.117 version 14.5.0 Release 14)

---------------------- Page: 1 ----------------------
3GPP TS 33.117 version 14.5.0 Release 14 1 ETSI TS 133 117 V14.5.0 (2019-04)



Reference
RTS/TSGS-0333117ve50
Keywords
LTE,SECURITY,UMTS
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: [phone]  Fax: [phone]

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:
http://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
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 2019.
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 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.
ETSI

---------------------- Page: 2 ----------------------
3GPP TS 33.117 version 14.5.0 Release 14 2 ETSI TS 133 117 V14.5.0 (2019-04)
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
http://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.117 version 14.5.0 Release 14 3 ETSI TS 133 117 V14.5.0 (2019-04)
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 . 7
4 Catalogue of security requirements and related test cases . 7
4.1 Introduction . 7
4.1.1 Pre-requisites for testing . 7
4.1.2 Use of tools in testing . 7
4.1.3 Documentation Requirements . 8
4.2 Security functional requirements and related test cases . 8
4.2.1 Introduction. 8
4.2.2 Security functional requirements deriving from 3GPP specifications and related test cases . 8
4.2.2.1 Security functional requirements deriving from 3GPP specifications – general approach . 8
4.2.3 Technical baseline. 9
4.2.3.1 Introduction . 9
4.2.3.2 Protecting data and information . 9
4.2.3.2.1 Protecting data and information – general . 9
4.2.3.2.2 Protecting data and information – Confidential System Internal Data . 9
4.2.3.2.3 Protecting data and information in storage . 10
4.2.3.2.4 Protecting data and information in transfer . 10
4.2.3.2.5 Logging access to personal data . 11
4.2.3.3 Protecting availability and integrity . 12
4.2.3.3.1 System handling during overload situations . 12
4.2.3.3.2 Boot from intended memory devices only . 12
4.2.3.3.3 System handling during excessive overload situations . 13
4.2.3.3.4 System robustness against unexpected input. . 15
4.2.3.3.5 Network Product software package integrity. 15
4.2.3.4 Authentication and authorization . 16
4.2.3.4.1 Authentication policy . 16
4.2.3.4.2 Authentication attributes. 19
4.2.3.4.2.1 Account protectionby at least one authentication attribute. . 19
4.2.3.4.3 Password policy . 22
4.2.3.4.4 Specific Authentication use cases . 29
4.2.3.4.5 Policy regarding consecutive failed login attempts . 30
4.2.3.4.6 Authorization and access control . 32
4.2.3.5 Protecting sessions . 33
4.2.3.5.1 Protecting sessions – logout function . 33
4.2.3.5.2 Protecting sessions – Inactivity timeout . 34
4.2.3.6 Logging . 35
4.2.3.6.1 Security event logging . 35
4.2.3.6.2 Log transfer to centralized storage . 37
4.2.3.6.3 Protection of security event log files . 38
4.2.4 Operating systems . 39
4.2.4.1 General operating system requirements and related test cases . 39
4.2.4.1.1 Availability and Integrity. 39
4.2.4.1.2 Authentication and Authorization. 43
4.2.4.2 UNIX® specific requirements and related test cases . 44
4.2.4.2.1 General . 44
4.2.4.2.2 System account identification . 44
ETSI

---------------------- Page: 4 ----------------------
3GPP TS 33.117 version 14.5.0 Release 14 4 ETSI TS 133 117 V14.5.0 (2019-04)
4.2.5 Web Servers . 45
4.2.5.1 HTTPS . 45
4.2.5.2 Logging . 45
4.2.5.2.1 Webserver logging . 45
4.2.5.3 HTTP User sessions . 46
4.2.5.4 HTTP input validation. 48
4.2.6 Network devices . 48
4.2.6.1 Protection of data and information . 48
4.2.6.2 Protecting availability and integrity . 48
4.2.6.2.1 Packet filtering. 48
4.2.6.2.2 Interface robustness requirements . 49
4.2.6.2.3 GTP-C Filtering . 49
4.2.6.2.3 GTP-U Filtering . 52
4.3 Security requirements and related test cases related to hardening . 54
4.3.1 Introduction. 54
4.3.2 Technical Baseline . 54
4.3.2.1 No unnecessary or insecure services / protocols . 54
4.3.2.2 Restricted reachability of services . 56
4.3.2.3 No unused software . 57
4.3.2.4 No unused functions . 58
4.3.2.5 No unsupported components . 60
4.3.2.6 Remote login restrictions for privileged users. 61
4.3.2.7 Filesystem Authorization privileges . 62
4.3.3 Operating Systems . 62
4.3.3.1 General operating system requirements and test cases . 62
4.3.3.1.1 IP-Source address spoofing mitigation . 62
4.3.3.1.2 Minimized kernel network functions . 64
4.3.3.1.3 No automatic launch of removable media . 68
4.3.3.1.4 SYN Flood Prevention . 69
4.3.3.1.5 Protection from buffer overflows . 70
4.3.3.1.6 External file system mount restrictions . 71
4.3.4 Web Servers . 72
4.3.4.1 General . 72
4.3.4.2 No system privileges for web server . 72
4.3.4.3 No unused HTTP methods . 73
4.3.4.4 No unused add-ons . 73
4.3.4.5 No compiler, interpreter, or shell via CGI or other server-side scripting . 74
4.3.4.6 No CGI or other scripting for uploads. 75
4.3.4.7 No execution of system commands with SSI . 76
4.3.4.8 Access rights for web server configuration . 76
4.3.4.9 No default content . 77
4.3.4.10 No directory listings . 77
4.3.4.11 Web server information in HTTP headers . 78
4.3.4.12 Web server information in error pages . 79
4.3.4.13 Minimized file type mappings. 79
4.3.4.14 Restricted file access . 80
4.3.4.15 Execute rights exclusive for CGI/Scripting directory . 81
4.3.5 Network Devices . 81
4.3.5.1 Traffic Separation . 81
4.4 Basic vulnerability testing requirements . 82
Annex A (informative): Change history . 87
History . 88

ETSI

---------------------- Page: 5 ----------------------
3GPP TS 33.117 version 14.5.0 Release 14 5 ETSI TS 133 117 V14.5.0 (2019-04)
Foreword
rd
This Technical Specification has been produced by the 3 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: 6 ----------------------
3GPP TS 33.117 version 14.5.0 Release 14 6 ETSI TS 133 117 V14.5.0 (2019-04)
1 Scope
The present document contains objectives, requirements and test cases that are deemed applicable, possibly after
adaptation, to several network product classes.
Several network product classes share very similar if not identical security requirements for some aspects. Therefore,
these are collected in this "catalogue" document applicable to many network product classes. In addition to this
catalogue, requirements specific to different network product classes will be captured in separate documents.
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 Specification set".
[3] IETF RFC 3871: "Operational Security Requirements for Large Internet Service Provider (ISP) IP
Network Infrastructure".
[4] 3GPP TR 33.926: "Security Assurance Specification (SCAS) threats and critical assets in 3GPP
network product classes".
[5] 3GPP TS 33.310: "Network Domain Security (NDS); Authentication Framework (AF)".
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].
Machine Accounts: These will be used for authentication and authorization from system to system or between
applications on a system and cannot be assigned to a single person or a group of persons.
Personal data: any information relating to an identified or identifiable natural person ('data subject').
Identifiable person: one who can be identified, directly or indirectly, in particular by reference to an identification
number, name or to one or more factors specific to his physical, physiological, mental, economic, cultural or social
identity.
NOTE: personal data can be gathered from user data and traffic data.
Sensitive data: data that may be used for authentication or may help to identify the user, such as user names,
passwords, PINs, cryptographic keys, IMSIs, IMEIs, MSISDNs, or IP addresses of the UE, as well as files of a system
that are needed for the functionality such as firmware images, patches, drivers or kernel modules.
System group account: a predefined system account in the network product, usually with special privileges, which has
a predefined user id and hence cannot be tied to a single user (individual) in a normal operating environment.
EXAMPLE: the 'root' account.
ETSI

---------------------- Page: 7 ----------------------
3GPP TS 33.117 version 14.5.0 Release 14 7 ETSI TS 133 117 V14.5.0 (2019-04)
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].
CIS Center for Internet Security
4 Catalogue of security requirements and related test
cases
4.1 Introduction
4.1.1 Pre-requisites for testing
The SCAS tests, as described in the present specification, are to be applied to a network product whose software and
hardware has been brought into use so that the network product can provide the intended functionality, either in a real
network environment or in a simulated environment. This implies that, before any testing is performed, the hardware
and software has been installed correctly, the network product is powered on, and communication has been established
over all standardized interfaces and OAM interfaces related with the network product's functionality, as described in the
vendor's documentation.
Communication over external non standardized Interfaces that may exist and are marked as optional, according to the
vendor's documentation, shall also be established during testing unless they are explicitly marked as "not
recommended" in the vendor's documentation.
For each of the enabled external communication interfaces there may be various optional capabilities. During testing, all
such capabilities shall be enabled unless they are explicitly marked as "not recommended" in the vendor's
documentation.
In some cases a testcase might require configuration changes as part of the execution steps or pre-conditions. After such
test is executed and prior any further test execution it needs to be ensured that the state of the ToE is restored back in
the original state.
SCAS testing is not about security in operations and deployments. So, in particular, SCAS testing is independent of any
operator guidelines or considerations on specific deployment scenarios.
4.1.2 Use of tools in testing
The following text shall apply to all test cases described in the present document:
The present document takes into account that the landscape of testing tools evolves more rapidly than SCAS
specifications. It is therefore allowed that, for each requirement, the actual test carried out may deviate from the
stepwise description of the test case in the present document if the following conditions are fulfilled:
(1) The test is carried out by preferably using Commercial-of-the-Shelf (COTS) and Free-Open-Source-Software
(FOSS) tools that are available for other testers that may want to repeat the test. In case a tool not in any of these
two categories is used then evidence of the quality assurance of the tool needs to be provided. This applies only
to tools used to perform the actual test and not supportive tools needed for setting up the testing environment like
for example traffic generators/ simulators.
In cases where a test lab is not able to obtain the necessary tools to perform the test, vendor proprietary test tools
may be used by the test lab as long the test tool is controlled under a suitable quality management system
(QMS). The test lab ensures that this QMS is in place in order to avail of a vendor’s test tool.
Additionally in cases where the accredited test lab does not have the necessary test environment to perform a
test, it shall be possible for the accredited test lab personnel to perform the test in a vendor's test lab. In such
cases the accredited lab should record details of test environment, test set-up used and how the test was
performed.
ETSI

---------------------- Page: 8 ----------------------
3GPP TS 33.117 version 14.5.0 Release 14 8 ETSI TS 133 117 V14.5.0 (2019-04)
(2) The tester provides evidence, e.g. by referring to the documentation of the tool, that the tool is suitable to verify
the requirement, and the scope of testing is equal or larger to the one of the test case described in the present
document. The evidence needs to be sufficiently detailed for experts in the field of testing, not for the general
public.
(3) The tester provides evidence that the tool has been actually used for testing the network product (e.g. by
providing a trace).
4
...