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 where mobile devices attach to the operator's infrastructure. Attacks in this layer include IMSI catching, rogue base stations and downgrade attacks; defenses rest on mutual authentication, integrity-protected signaling and Open RAN supply-chain hygiene.

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

To place HTTP/2 Security in 5G in the wider telecom-security picture, review A5/0, DNS, FCC, GNSS Spoofing, ICMP and NTP — each entry cross-references back to this page so you can walk the topic in either direction.

Related terms

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.