HTTP/2 Security in 5G

5G's Service-Based Architecture uses HTTP/2 (RFC 7540) for all inter-NF communication. Security on this layer requires mutual TLS for transport authentication and confidentiality, OAuth2 access tokens for fine-grained authorisation, JSON-schema validation against 3GPP-defined OpenAPI specs, and protection against known HTTP/2 abuses such as Rapid Reset (CVE-2023-44487).

Categories: Radio Access NetworkSecurity ControlsThreats and Attacks

HTTP/2 Security in 5G in context

The radio access network is the layer where mobile devices attach to the operator's infrastructure. Attacks in this layer include IMSI catching, rogue base stations, downgrade attacks and jamming, and defenses hinge on mutual authentication, integrity-protected signaling and Open RAN supply-chain hygiene.

Security controls in telecom span signaling firewalls (SS7/Diameter/GTP screening at the network edge), transport encryption (IPsec, TLS, PRINS), identity and access on OSS/BSS, and monitoring at both the packet and log level. Controls are audited against GSMA FS.11/FS.19/FS.20/FS.36 and, in Europe, NIS2 sectoral rules.

To place HTTP/2 Security in 5G in the wider telecom-security picture, review GNSS Spoofing, HTTP, Inter-Network Function Authentication, NTP, OAuth2 in 5G Core and DNS.

Related terms

Related topic hubs

  • 5G NEF Security Network Exposure Function security in the 5G core.
  • SEPP Security N32-c/N32-f, PRINS, JWE and OAuth 2.0 at the 5G roaming edge.
  • Diameter Attacks S6a IDR/PUR/CLR abuse, subscriber tracking, LTE signaling attacks.
  • 5G Security 5G SBA, SEPP, SUCI, 5G-AKA, N32 and service-based interface security.

More from the TelcoSec Glossary

Browse the full TelcoSec Glossary, the Ultimate Guide to Mobile Network Security, or the P1 Arsenal of telecom-security tools.