Gsma Fs.38 «SIMPLE - 2024»

The adoption of GSMA FS.38 offers numerous benefits for mobile network operators, device manufacturers, and application developers:

One of the most common questions is: How does FS.38 compare to ETSI EN 303 645 or NISTIR 8259?

is a comprehensive cybersecurity guideline published by the GSMA Fraud and Security Group (FASG). It provides MNOs, vendors, and security auditors with a standardized framework to assess, design, and validate the security posture of SIP-based architectures. gsma fs.38

It introduces the concept of comparing fields across different protocols (e.g., SIP vs. Diameter) to identify discrepancies that signal potential fraud or security breaches. Integration with Other GSMA Standards

: Core IP Multimedia Subsystem (IMS) network infrastructure elements tucked behind the perimeter SBCs. The adoption of GSMA FS

Operators realized they needed a way to assess, rate, and trust the devices begging access to their infrastructure. Thus, GSMA FS.38 was born—providing a standardized framework for IoT security assessments.

: Safeguards the Session Initiation Protocol used for call setup. It introduces the concept of comparing fields across

GSMA FS.38 is a technical specification developed by the GSMA (Global System for Mobile Communications Association) that focuses on the functional and technical requirements for 5G network slicing. Network slicing is a critical aspect of 5G technology, enabling the creation of multiple, independent networks on top of a shared physical infrastructure. This allows network operators to provide a range of services with diverse performance characteristics, tailored to specific use cases and applications.

| # | Control | Description | |---|---|---| | 8 | | The device must uniquely authenticate to the network and any application server. Use of GSMA’s IoT SAFE (SIM Applet for Secure End-2-End Communication) is recommended. | | 9 | Resilience Against Input Attacks | Input validation to prevent buffer overflows, injection attacks, or malformed packet crashes. | | 10 | Wireless Interface Security | For Bluetooth, Wi-Fi, or LoRa interfaces, implement least-privilege pairing and disable insecure legacy modes (e.g., WPA2-PSK with weak passphrases). | | 11 | Privacy Controls | Minimize data collection. Ensure user consent is obtained. Use anonymization or pseudonymization where personally identifiable information (PII) is transmitted. |

| Feature | | ETSI MEC (Multi-access Edge Compute) | LF Edge (OpenHorizon) | | :--- | :--- | :--- | :--- | | Primary Focus | Federated trust & roaming | Network integration (UPF, RAN) | Device & software management | | Inter-Provider | Excellent (Built for roaming) | Poor (Single operator only) | Moderate (Requires custom adapters) | | Maturity | Spec v1.0 (2023) | Commercial deployments (v2.x) | Mature (IBM origin) | | Best Use Case | Cross-operator edge roaming | Single operator / on-prem edge | Large-scale device fleets |

To appreciate FS.38, one must distinguish it from adjacent standards. Unlike the ETSI EN 303 645 (Consumer IoT security), which focuses on the home device, FS.38 is specifically tuned for wide-area cellular networks. Unlike the NIST IR 8259 series, which is general-purpose, FS.38 explicitly references GSM-specific elements (IMSI catching, false base stations, SMS vulnerabilities).