Tech-invite3GPPspaceIETF RFCsSIP
Quick21222324252627282931323334353637384‑5x
Top   in Index   Prev   Next

TS 33.516
5G Security Assurance Specification (SCAS) –
Authentication Server Function (AUSF)

V17.0.0 (PDF)  2022/03  12 p.
V16.2.0 (PDF)  2020/12  12 p.
Rapporteur:
Dr. Jost, Christine
Ericsson LM

Content for  TS 33.516  Word version:  17.0.0

Here   Top

 

1  Scopep. 6

The present document contains objectives, requirements and test cases that are specific to the AUSF 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 AUSF network product class.

2  Referencesp. 6

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]
TR 21.905: "Vocabulary for 3GPP Specifications".
[2]
TS 33.501: (Release 15): "Security architecture and procedures for 5G system".
[3]
TS 33.117: "Catalogue of general security assurance requirements".
[4]
TR 33.926: "Security Assurance Specification (SCAS) threats and critical assets in 3GPP network product classes".
Up

3  Definitions of terms, symbols and abbreviationsp. 6

3.1  Termsp. 6

For the purposes of the present document, the terms given in TR 21.905 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.

3.2  Symbolsp. 6

Void.

3.3  Abbreviationsp. 7

For the purposes of the present document, the abbreviations given in TR 21.905 and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905.

4  AUSF-specific security requirements and related test casesp. 7

4.1  Introductionp. 7

AUSF specific security requirements include both requirements derived from AUSF specific security functional requirements in relevant specifications as well as security requirements introduced in the present document derived from the threats specific to AUSF as described in TR 33.926.

4.2  AUSF-specific adaptations of security functional requirements and related test casesp. 7

4.2.1  Introductionp. 7

The present clause describes the security functional requirements and the corresponding test cases for AUSF network product class. The proposed security requirements are classified in two groups:
  • Security functional requirements derived from TS 33.501 and detailed in clause 4.2.2.
  • General security functional requirements which include requirements not already addressed in TS 33.501 but whose support is also important to ensure that AUSF conforms to a common security baseline detailed in clause 4.2.3.
Up

4.2.2  Security functional requirements on the AUSF deriving from 3GPP specifications and related test casesp. 7

The general approach in TS 33.117, clause 4.2.2.1 and all the requirements and test cases in TS 33.117, clause 4.2.2.2 related to SBA/SBI aspect apply to the AUSF network product class.
There are no AUSF-specific test cases according to the security functional requirements on the AUSF deriving from TS 33.501 and security requirements derived from the threats specific to AUSF as described in TR 33.926.
Up

4.2.3  Technical Baselinep. 7

4.2.3.1  Introductionp. 7

The present clause provides baseline technical requirements.

4.2.3.2  Protecting data and informationp. 7

4.2.3.3  Protecting availability and integrityp. 8

There are no AUSF-specific additions to clause 4.2.3.3 of TS 33.117.

4.2.3.4  Authentication and authorizationp. 8

There are no AUSF-specific additions to clause 4.2.3.4 of TS 33.117.

4.2.3.5  Protecting sessionsp. 8

There are no AUSF-specific additions to clause 4.2.3.5 of TS 33.117.

4.2.3.6  Loggingp. 8

There are no AUSF-specific additions to clause 4.2.3.6 of TS 33.117.

4.2.4  Operating Systemsp. 8

There are no AUSF -specific additions to clause 4.2.4 of TS 33.117.

4.2.5  Web Serversp. 8

There are no AUSF -specific additions to clause 4.2.5 of TS 33.117.

4.2.6  Network Devicesp. 8

There are no AUSF-specific additions to clause 4.2.6 of TS 33.117.

4.3  AUSF-specific adaptations of hardening requirements and related test casesp. 8

4.3.1  Introductionp. 8

The present clause contains AUSF-specific adaptations of hardening requirements and related test cases.

4.3.2  Technical baselinep. 8

There are no AUSF-specific additions to clause 4.3.2 of TS 33.117.

4.3.3  Operating systemsp. 8

There are no AUSF-specific additions to clause 4.3.3 of TS 33.117.

4.3.4  Web serversp. 9

There are no AUSF-specific additions to clause 4.3.4 of TS 33.117.

4.3.5  Network devicesp. 9

There are no AUSF-specific additions to clause 4.3.5 of TS 33.117.

4.3.6  Network functions in service-based architecturep. 9

There are no AUSF-specific additions to clause 4.3.6 in TS 33.117.

4.4  AUSF-specific adaptations of basic vulnerability testing requirements and related test casesp. 9

There are no AUSF-specific additions to clause 4.4 of TS 33.117.

$  Change Historyp. 10


Up   Top