hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
a8e35547135823fb19e74805f967dfe3 | 33.129-1 | 3.3 Abbreviations
| For the purposes of the present document, the abbreviations given in 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 TR 21.905 [1].
|
a8e35547135823fb19e74805f967dfe3 | 33.129-1 | 4 Adaptations of TS 33.117 catalogue of security requirements and related use cases
| Editor's Note: It may be worth updating the structure of this to mirror TS 33.117 (as done in TS 33.129-2)
|
a8e35547135823fb19e74805f967dfe3 | 33.129-1 | 4.1 Introduction
| |
a8e35547135823fb19e74805f967dfe3 | 33.129-1 | 4.1.1 General
| The present document was developed based on the guidance and methodology described in 3GPP TR 33.916 [3]. 3GPP has organized SCAS documents by publishing one Technical Specification (TS) per architectural network element. In contrast, this document takes a different approach and collects all LI SCAS in the present docu... |
a8e35547135823fb19e74805f967dfe3 | 33.129-1 | 4.1.2 Use of tools in testing
| |
a8e35547135823fb19e74805f967dfe3 | 33.129-1 | 4.1.3 Documentation requirements
| |
a8e35547135823fb19e74805f967dfe3 | 33.129-1 | 4.1.4 Requirements list
| The following TS 33.126 [5] requirements are tested in the present document:
TS 33.126 R6.6-30: The CSP shall ensure that non-authorized personnel or processes (including automated or Artificial Intelligence based systems) that are part of the service cannot detect that interception is taking place.
|
a8e35547135823fb19e74805f967dfe3 | 33.129-1 | 4.1.5 Document Part Organization
| Editor's Note: The part structure of 33.129 should be re-visited when the maturity of the project warrants it, and likely not settle to its final form until the project is ~80%+ along.
- Part 1 - Common
- The present document contains the general framework of LI SCAS. This part contains descriptions of threats and at... |
a8e35547135823fb19e74805f967dfe3 | 33.129-1 | 4.2 Security functional requirements and related test cases specific to LI functions
| |
a8e35547135823fb19e74805f967dfe3 | 33.129-1 | 4.2.1 Introduction
| The present clause describes the security functional requirements and the corresponding test cases for LI functions. The proposed security requirements are classified in two groups:
- Security functional requirements derived from TS 33.501 [11] and detailed in clause 4.2.2.
- General security functional requirements ... |
a8e35547135823fb19e74805f967dfe3 | 33.129-1 | 4.2.2 Security functional requirements on LI functions deriving from 3GPP specifications and related test cases
| |
a8e35547135823fb19e74805f967dfe3 | 33.129-1 | 4.2.2.1 General
| The general approach in TS 33.117 [2] clause 4.2.2.2 applies to LI functions. The relevant requirements and test cases for the product class of the NF in which the LI function is embedded also apply. Unless otherwise specified, the requirements and test cases in TS 33.117 [2] clause 4.2.2.3 related to SBA / SBI do not ... |
a8e35547135823fb19e74805f967dfe3 | 33.129-1 | 4.2.2.3 Security functional requirements on LI functions deriving from 3GPP specifications and related test cases – general interface aspects
| |
a8e35547135823fb19e74805f967dfe3 | 33.129-1 | 4.2.2.3.1 Introduction
| The purpose of the sub-clauses of clause 4.2.2.3 is to identify and describe the general baseline requirements from the interfaces in the LI architecture and the corresponding test cases. The general baseline requirements are applicable to all LI functions within the LI system independent of a specific network product ... |
a8e35547135823fb19e74805f967dfe3 | 33.129-1 | 4.2.2.3.2 Protection at the transport layer
| Editor's Note: Rewrite test from TS 33.129-2 4.2.2.3, 4.2.2.4, and 4.2.2.5 to apply to non-X1.
|
a8e35547135823fb19e74805f967dfe3 | 33.129-1 | 4.2.2.3.3 Authorization of NF service access
| Editor's Note: Move TS 33.129-2 4.2.2-4.2.9 here?
|
a8e35547135823fb19e74805f967dfe3 | 33.129-1 | 4.2.2.4 Credential affinity
| |
a8e35547135823fb19e74805f967dfe3 | 33.129-1 | 4.2.2.5 Credential expiry
| |
a8e35547135823fb19e74805f967dfe3 | 33.129-1 | 4.2.2.6 Credential chain of trust
| |
a8e35547135823fb19e74805f967dfe3 | 33.129-1 | 4.2.2.7 Credential binding
| |
a8e35547135823fb19e74805f967dfe3 | 33.129-1 | 4.2.2.8 Element of LI binding
| |
a8e35547135823fb19e74805f967dfe3 | 33.129-1 | 4.2.3 Technical baseline
| |
a8e35547135823fb19e74805f967dfe3 | 33.129-1 | 4.2.3.1 Introduction
| The present clause provides baseline technical requirements.
|
a8e35547135823fb19e74805f967dfe3 | 33.129-1 | 4.2.3.2 Protecting data and information
| |
a8e35547135823fb19e74805f967dfe3 | 33.129-1 | 4.2.3.2.1 Protecting data and information – general
| |
a8e35547135823fb19e74805f967dfe3 | 33.129-1 | 4.2.3.2.1.1 Introduction
| The tests listed in clause 4.2.3.2.1 of TS 33.117 [2] shall be applied with the additions and clarifications included in the following sub-clauses.
|
a8e35547135823fb19e74805f967dfe3 | 33.129-1 | 4.2.3.2.1.2 A crypto inventory exists
| Requirement Name: Standard Cryptographic Primitives
Requirement Reference: TBD
Requirement Description: Only standardized cryptographic algorithms and primitives published by accredited organizations shall be used.
References:
Asset reference: AS-LI-FUNCTION
Attacker reference: TBD
Threat reference: TBD
T... |
a8e35547135823fb19e74805f967dfe3 | 33.129-1 | 4.2.3.2.1.3 Replaceable crypto modules
| Editor's Note: candidate for tweaking. Perhaps too strict? Perhaps TS 102 232 and TS 33.128 should be enhanced to require this modularity.
Requirement Name: Modular Cryptographic Implementations
Requirement Reference: TBD
Requirement Description: Cryptographic methods need to be implemented in replaceable modules. S... |
a8e35547135823fb19e74805f967dfe3 | 33.129-1 | 4.2.3.2.1.4 Replaceable crypto methods
| Editor's Note: candidate for tweaking. Perhaps too strict? Perhaps TS 102 232 and TS 33.128 should be enhanced to require this modularity.
Requirement Name: Configurable Cryptographic Methods
Requirement Reference: TBD
Requirement Description: Applications need to support configuration of cryptographic methods and p... |
a8e35547135823fb19e74805f967dfe3 | 33.129-1 | 4.2.3.2.2 Protecting data and information – unauthorized viewing
| |
a8e35547135823fb19e74805f967dfe3 | 33.129-1 | 4.2.3.2.2.1 Introduction
| The tests listed in clause 4.2.3.2.2 of TS 33.117 [2] shall be applied with the additions and clarifications included in the following sub-clauses.
Editor's note: It is unclear if these belong here as these seem to be more applicable to NE-embedded.
|
a8e35547135823fb19e74805f967dfe3 | 33.129-1 | 4.2.3.2.2.2 General-purpose logs cannot contain LI data
| Requirement Name: Confidentiality of LI Identifiers
Requirement Reference: TS 33.126: R6.6 - 30 Undetectability by Non-Authorized Parties
Requirement Description: General-purpose logs cannot contain Lawful Interception (LI) identifiers or other sensitive LI information. Only LI-protected audit logs, only accessible t... |
a8e35547135823fb19e74805f967dfe3 | 33.129-1 | 4.2.3.2.2.3 General-purpose logs cannot contain LI data (comms?)
| Requirement Name: Confidentiality of LI Identifiers
Requirement Reference: TS 33.126: R6.6 - 30 Undetectability by Non-Authorized Parties
Requirement Description: General-purpose logs cannot contain sensitive LI information. Only LI-protected audit logs, only accessible to LI-cleared personnel, may contain such detai... |
a8e35547135823fb19e74805f967dfe3 | 33.129-1 | 4.2.3.2.2.4 LI logging is segregated from non-LI logging
| Requirement Name: Segregation of LI Logging
Requirement Reference: TS 33.126: R6.6 - 30 Undetectability by Non-Authorized Parties
Requirement Description: LI audit and operational logs need to be segregated from all non-LI logging subsystems. Access to LI logs need to be restricted to LI-cleared personnel only.
Refe... |
a8e35547135823fb19e74805f967dfe3 | 33.129-1 | 4.2.3.2.2.5 LI target leak, log leak
| Editor's Note: This test seems equivalent to 4.2.3.2.2.2 and 4.2.3.2.2.3 above. Not sure whether to use this for something else or delete it). (Network logs perhaps?)
|
a8e35547135823fb19e74805f967dfe3 | 33.129-1 | 4.2.3.2.3 Protecting data and information in storage
| |
a8e35547135823fb19e74805f967dfe3 | 33.129-1 | 4.2.3.2.3.1 Introduction
| The following addition and clarifications to clause 4.2.3.2.3 of TS 33.117 [2] apply for LI functions.
|
a8e35547135823fb19e74805f967dfe3 | 33.129-1 | 4.2.3.2.3.2 No unencrypted LI data
| |
a8e35547135823fb19e74805f967dfe3 | 33.129-1 | 4.2.3.2.4 Protecting data and information in transfer
| |
a8e35547135823fb19e74805f967dfe3 | 33.129-1 | 4.2.3.2.4.1 Introduction
| The following addition and clarifications to clause 4.2.3.2.4 of TS 33.117 [2] apply for LI functions.
|
a8e35547135823fb19e74805f967dfe3 | 33.129-1 | 4.2.3.2.4.2 No unencrypted internal comms
| |
a8e35547135823fb19e74805f967dfe3 | 33.129-1 | 4.2.3.2.4.3 Network observation by VI admin
| |
a8e35547135823fb19e74805f967dfe3 | 33.129-1 | 4.2.3.2.4.4 Firewalls between virtual entities
| |
a8e35547135823fb19e74805f967dfe3 | 33.129-1 | 4.2.3.2.5 Logging access to personal data
| There are no LI-specific additions to clause 4.2.3.2.5 of TS 33.117 [2].
|
a8e35547135823fb19e74805f967dfe3 | 33.129-1 | 4.2.3.3 Protecting availability and integrity
| |
a8e35547135823fb19e74805f967dfe3 | 33.129-1 | 4.2.3.3.1 Introduction
| The tests listed in TS 33.117 [2] clause 4.2.3.3 shall be applied with the additions and clarifications included in the following sub-clauses.
|
a8e35547135823fb19e74805f967dfe3 | 33.129-1 | 4.2.3.3.2 Vulnerability patching – original code
| TBD – not sure is this is within scope of SCAS
|
a8e35547135823fb19e74805f967dfe3 | 33.129-1 | 4.2.3.3.3 Vulnerability patching – open source
| TBD – not sure is this is within scope of SCAS
|
a8e35547135823fb19e74805f967dfe3 | 33.129-1 | 4.2.3.4 Authentication and authorization
| |
a8e35547135823fb19e74805f967dfe3 | 33.129-1 | 4.2.3.4.1 Introduction
| The tests listed in TS 33.117 [2] clause 4.2.3.4 shall be applied with the additions and clarifications included in the following sub-clauses.
|
a8e35547135823fb19e74805f967dfe3 | 33.129-1 | 4.2.3.4.2 Logging of failed authentication attempts
| |
a8e35547135823fb19e74805f967dfe3 | 33.129-1 | 4.2.3.4.3 No non-LI accounts
| |
a8e35547135823fb19e74805f967dfe3 | 33.129-1 | 4.2.3.4.4 Unique credentials
| |
a8e35547135823fb19e74805f967dfe3 | 33.129-1 | 4.2.3.4.5 System hardening of VM accounts
| |
a8e35547135823fb19e74805f967dfe3 | 33.129-1 | 4.2.3.5 Protecting sessions
| There are no LI-specific additions to clause 4.2.3.5 of TS 33.117 [2].
|
a8e35547135823fb19e74805f967dfe3 | 33.129-1 | 4.2.3.6 Logging
| |
a8e35547135823fb19e74805f967dfe3 | 33.129-1 | 4.2.3.6.1 Introduction
| The tests listed in TS 33.117 [2] clause 4.2.3.6 shall be applied with the additions and clarifications included in the following sub-clauses.
|
a8e35547135823fb19e74805f967dfe3 | 33.129-1 | 4.2.3.6.2 Mandatory log-disabling alarms
| |
a8e35547135823fb19e74805f967dfe3 | 33.129-1 | 4.2.3.6.3 Loud logs
| |
a8e35547135823fb19e74805f967dfe3 | 33.129-1 | 4.2.4 Operating Systems
| There are no LI-specific additions to clause 4.2.4 of TS 33.117 [2].
|
a8e35547135823fb19e74805f967dfe3 | 33.129-1 | 4.2.5 Web Servers
| There are no LI-specific additions to clause 4.2.5 of TS 33.117 [2].
|
a8e35547135823fb19e74805f967dfe3 | 33.129-1 | 4.2.6 Network Devices
| There are no LI-specific additions to clause 4.2.6 of TS 33.117 [2].
|
a8e35547135823fb19e74805f967dfe3 | 33.129-1 | 4.3 Adaptations of hardening requirements and related test cases specific to LI functions
| |
a8e35547135823fb19e74805f967dfe3 | 33.129-1 | 4.3.1 Introduction
| Clause 4.3 specifies the LI function-specific adaptations of hardening requirements and related test cases.
|
a8e35547135823fb19e74805f967dfe3 | 33.129-1 | 4.3.2 Technical baseline
| |
a8e35547135823fb19e74805f967dfe3 | 33.129-1 | 4.3.2.1 Introduction
| The following additions to clause 4.3.2 in TS 33.117 [2] apply for LI functions.
|
a8e35547135823fb19e74805f967dfe3 | 33.129-1 | 4.3.2.2 Third-party components are up-to-date
| |
a8e35547135823fb19e74805f967dfe3 | 33.129-1 | 4.3.3 Operating systems
| There are no LI-specific additions to clause 4.3.3 in TS 33.117 [2].
|
a8e35547135823fb19e74805f967dfe3 | 33.129-1 | 4.3.4 Web servers
| |
a8e35547135823fb19e74805f967dfe3 | 33.129-1 | 4.3.4.1 Introduction
| The following additions to clause 4.3.4 in TS 33.117 [2] apply for LI functions.
|
a8e35547135823fb19e74805f967dfe3 | 33.129-1 | 4.3.4.2 Only POST allowed (for Xn)
| |
a8e35547135823fb19e74805f967dfe3 | 33.129-1 | 4.3.4.3 Third-party components are up-to-date
| |
a8e35547135823fb19e74805f967dfe3 | 33.129-1 | 4.3.5 Network devices
| There are no LI-specific additions to clause 4.3.5 in TS 33.117 [2].
|
a8e35547135823fb19e74805f967dfe3 | 33.129-1 | 4.3.6 Network functions in service-based architecture
| There are no LI-specific additions to clause 4.3.6 in TS 33.117 [2].
|
a8e35547135823fb19e74805f967dfe3 | 33.129-1 | 4.4 Adaptations of basic vulnerability testing requirements and related test cases specific to LI functions
| |
a8e35547135823fb19e74805f967dfe3 | 33.129-1 | 4.4.1 Introduction
| There are no LI specific additions to clause 4.4.1 of TS 33.117 [2].
|
a8e35547135823fb19e74805f967dfe3 | 33.129-1 | 4.4.2 Port Scanning
| There are no LI specific additions to clause 4.4.2 of TS 33.117 [2].
|
a8e35547135823fb19e74805f967dfe3 | 33.129-1 | 4.4.3 Vulnerability scanning
| There are no LI specific additions to clause 4.4.3 of TS 33.117 [2].
|
a8e35547135823fb19e74805f967dfe3 | 33.129-1 | 4.4.4 Robustness and fuzz testing
| The test cases under clause 4.4.4 of TS 33.117 [2] are applicable to LI functions.
|
a8e35547135823fb19e74805f967dfe3 | 33.129-1 | 5 Security Elements
| |
a8e35547135823fb19e74805f967dfe3 | 33.129-1 | 5.1 Assets
| |
a8e35547135823fb19e74805f967dfe3 | 33.129-1 | 5.1.1 Assets Overview
| Assets are categorized more granularly than functional blocks. These are the specific elements that, if exposed or influenced, could compromise LI.
Table 5.1.1-1: Asset definitions
Name
Description
AS-TARGET
Target Identities(s)
A network or service identity that uniquely identifies a target for interception f... |
a8e35547135823fb19e74805f967dfe3 | 33.129-1 | 5.1.2 Detailed Asset Descriptions
| Editor's Note: Review all of these and compare them to TR 33.926 to remove overlap and deconflict. Align the format, naming, etc. with the Annexes in 33.926?
|
a8e35547135823fb19e74805f967dfe3 | 33.129-1 | 5.1.2.1 Target Identifiers
| Asset Code: AS-TARGET
Asset Name: Target Identities
Asset Description:
A network or service identity that uniquely identifies a target for interception from all other non-targets within one or more CSP services. One target may have one or several target identities. The Target Identity can be a long-term subscription... |
a8e35547135823fb19e74805f967dfe3 | 33.129-1 | 5.1.2.2 LI Access Credentials
| Asset Code: AS-LI-CREDS
Asset Name: LI Access Credentials
Asset Description:
These are the authentication elements used to authorize and secure LI operations. They may include passwords, API tokens, client certificates, SSH keys, or internal authorization grants.
|
a8e35547135823fb19e74805f967dfe3 | 33.129-1 | 5.1.2.3 Network Function
| Editor's Note: Reframe this in terms of TS 33.926 GNP and provide reference for the assumptions mentioned below.
Asset Code: AS-NF
Asset Name: Network Function
Asset Description:
A network function (NF) encompasses any virtualized or physical function that plays a role in packet handling, control signaling, or serv... |
a8e35547135823fb19e74805f967dfe3 | 33.129-1 | 5.1.2.4 Network Service
| Asset Code: AS-NETWORK-SERVICE
Asset Name: Network Service
Asset Description:
This can be thought of simplistically as a chain of network functions. However, this category includes the end-to-end behavior of services delivered by the network, including latency, throughput, jitter, and session continuity.
|
a8e35547135823fb19e74805f967dfe3 | 33.129-1 | 5.1.2.5 LI Function
| Asset Code: AS-LI-FUNCTION
Asset Name: LI Function
Asset Description:
This asset represents the internal mechanisms and runtime state of the LI function itself. It includes service status flags, job queues, inter-process communication, service mesh labels, and other operational artifacts.
|
a8e35547135823fb19e74805f967dfe3 | 33.129-1 | 5.1.2.6 LI Product Delivery
| Asset Code: AS-LI-PRODUCT
Asset Name: LI Product Delivery
Asset Description:
This refers to the delivery chain that carries LI content and Intercept Related Information (IRI) from network function Points of Interception (POIs) to the mediation function (MDF), and from there to the Law Enforcement Monitoring Facility... |
a8e35547135823fb19e74805f967dfe3 | 33.129-1 | 5.1.2.7 LEMF Attributes
| Asset Code: AS-LEMF
Asset Name: LEMF Attributes
Asset Description:
This includes the IP address, domain name, or network path of the LEMF endpoint. If the LEMF is statically assigned or its routing patterns are predictable, adversaries may correlate traffic to or from the LEMF to active surveillance.
|
a8e35547135823fb19e74805f967dfe3 | 33.129-1 | 5.1.2.8 Network User Behaviour
| Asset Code: AS-USER-PATTERN
Asset Name: Network User Behaviour Attributes
Asset Description:
These are behavioural signatures or application-layer patterns associated with end users. They may include traffic types, flow durations, usage spikes, or session frequency.
|
a8e35547135823fb19e74805f967dfe3 | 33.129-1 | 5.1.2.9 Crypto Store
| Asset Code: AS-CRYPTO-STORE
Asset Name: Crypto Store
Asset Description:
This includes keystores, certificate chains, and lists of trusted Certificate Authorities (CAs) used within LI systems or the broader network.
|
a8e35547135823fb19e74805f967dfe3 | 33.129-1 | 5.1.2.10 API or Configuration State
| Asset Code: AS-API-CONF
Asset Name: API or Configuration State
Asset Description:
This encompasses the current state and metadata of network APIs, configuration templates, or orchestrator settings used in service delivery.
|
a8e35547135823fb19e74805f967dfe3 | 33.129-1 | 5.1.2.11 LI Product
| Asset Code: AS-LI-PRODUCT
Asset Name: LI Product
Asset Description:
The LI product comprises content (e.g. voice, SMS, data) and metadata (e.g. call records, IP flow info) delivered as IRI to the LEMF. This is among the highest-value assets in the system and the direct object of the lawful interception operation.
|
a8e35547135823fb19e74805f967dfe3 | 33.129-1 | 5.2 Attackers
| |
a8e35547135823fb19e74805f967dfe3 | 33.129-1 | 5.2.1 Attackers Overview
| Attackers can be human or automated. The following table lists the attackers considered in the present multi-part document.
Table 5.2-1: Attacker definitions
Code
Name
Description
AT-INTERNAL
Internal administrator
Has privileged access to network functions or management interfaces but no LI authorization. May ... |
a8e35547135823fb19e74805f967dfe3 | 33.129-1 | 5.2.2 Detailed Attacker Descriptions
| |
a8e35547135823fb19e74805f967dfe3 | 33.129-1 | 5.2.2.1 Internal Administrator
| Attacker Code: AT-INTERNAL
Attacker Name: Internal Administrator
Attacker Description:
An internal administrator refers to a human actor with privileged access to core network systems, but without explicit authorization to access or manage Lawful Interception (LI) functions. This attacker may hold legitimate operati... |
a8e35547135823fb19e74805f967dfe3 | 33.129-1 | 5.2.2.2 Internal Administrator Granular Breakdown
| |
a8e35547135823fb19e74805f967dfe3 | 33.129-1 | 5.2.2.2.1 Internal Log Auditor
| Attacker Code: AT-INTERNAL-LOG
Attacker Name: Internal Log Auditor
Attacker Description:
This attacker has legitimate access to system and application logs for operational, compliance, or troubleshooting purposes. While not authorized for LI access, they may infer surveillance activity by observing timing correlatio... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.