← Book home
Part 4 · RAN, Mobility, and Roaming Security
18

Non-Standalone and Standalone Security

Why "5G" on the status bar doesn't always mean 5G security

“The phone shows 5G. The marketing says 5G. But if it's NSA, the security is LTE's — anchored in a 4G core that never heard of SUCI.” — THE NSA REALITY

Most early 5G was Non-Standalone (NSA): a 5G radio bolted onto a 4G core for speed-to-market. NSA delivers 5G data rates but inherits LTE's security model — no SUCI, no user-plane integrity origin, no SBA. Standalone (SA) is the real 5G security architecture this book describes. This chapter explains the NSA options, EN-DC security, the LTE-anchor dependency, and the security gains of migrating to SA.

🎯 Learning objectives
📘 Standards reference box — Chapter 18
SpecificationTitleRelease / version verified
TS 33.401EPS security — EN-DC / dual connectivity securityRel-18 edition
TS 33.5015G security (SA)Rel-18, v18.11.0 (2026-04)
TS 37.340Multi-connectivity (EN-DC) overall descriptionRel-18/19 edition

Checked June 2026 — verify against the latest 3GPP version. NSA security is anchored in TS 33.401 (LTE), not TS 33.501.

18.1 NSA Options and EN-DC

FIGURE 18.1NSA Option 3/3a/3x — the Anchor Is LTE
EPC (4G core) — the ANCHOR MME, S/PGW — all control plane & security here LTE eNB (master) NR gNB (secondary) UE (shows "5G") dual connectivity (EN-DC) control + anchor 3a/3x: UP split here in ALL Option-3 variants the LTE eNB is master and the EPC is the anchor → security is LTE's (TS 33.401), regardless of the 5G radio
Purpose: the defining fact of NSA. The 5G NR is a secondary leg for throughput; the LTE eNB and 4G EPC own the control plane and security — so NSA security is LTE security.
FIGURE 18.2EN-DC Security Architecture
K_ASME (LTE)EPS key hierarchy K_eNB (master)LTE eNB security derive S-K_gNB S-K_gNB (secondary)for the NR SCG bearers SCG bearer keys (NR side) the pointthe NR leg's keys descendfrom the LTE hierarchy
Purpose: how the NR leg is keyed in NSA. The secondary gNB receives an S-KgNB derived from the LTE master's KeNB — so even the 5G radio's keys are rooted in LTE, not 5G.
FIGURE 18.3S-KgNB Derivation and the SN Counter
K_eNB (master)+ SN Counter (freshness) KDF S-K_gNB→ NR SCG bearer keys SN Counterincrements per secondarykey refresh → avoids reuse
Purpose: the freshness mechanism for the secondary leg. The SN Counter plays the role NCC plays in SA handovers — ensuring each S-KgNB is fresh.
FIGURE 18.4SCG Bearer Security Setup Flow
UE eNB (master) gNB (secondary) ① SgNB Addition (S-K_gNB) ② Ack (NR config) ③ RRCConnectionReconfig (SCG + SN Counter) ④ UE derives S-K_gNB, SCG bearers up on NR
Purpose: how an NSA secondary leg comes up securely. The master adds the secondary, passes the SN Counter, and the UE derives the matching S-KgNB — all within LTE's security framework.

18.2 The LTE Security Ceiling

FIGURE 18.5NSA Inherits LTE's Security Ceiling
NR radio — fast data rates ✓ …but security is CAPPED at LTE ✗ no SUCI — IMSI still exposable ✗ no user-plane integrity ✗ no SBA/SEPP — Diameter roaming, weaker home control the NR leg adds speed, not security — the anchor decides the security level
Purpose: the headline. NSA's 5G is real for throughput and unreal for security — every 5G security advance in this book requires SA.
FIGURE 18.6What NSA Cannot Give You — vs SA
capability NSA SA SUCI identity concealment user-plane integrity SBA security (mTLS+OAuth)✗ (EPC) SEPP roaming security✗ (Diameter) network slicing security (NSSAA)limited increased home control every "✗" is a chapter of this book that simply doesn't apply until you deploy SA
Purpose: the migration motivation in one table. The "✗" column is the list of 5G security features a subscriber forfeits on NSA — the concrete reason SA matters.
FIGURE 18.7SA Security Model — the Real 5G (Recap)
STANDALONE 5G = the architecture this book describes ✓ SUCI (Ch 4) ✓ 5G-AKA + home control (Ch 5–6) ✓ full key hierarchy (Ch 7) ✓ UP integrity (Ch 9) ✓ SBA mTLS+OAuth (Ch 10) ✓ SEPP roaming (Ch 13) ✓ slicing security (Ch 20) ✓ NPN, edge (Ch 21–22) ✓ everything else SA is the prerequisite for 5G security — not an optimization
Purpose: the contrast and the recap. SA unlocks the whole book; the chapter references show how much of "5G security" simply requires SA to exist.
FIGURE 18.8NSA → SA Migration — Security Gains by Phase
NSA (Option 3)5G speed, LTE securityno SUCI/UP-IP/SBA SA deployedSUCI, 5G-AKA, UP-IP,SBA, SEPP switch ON SA-onlyslicing/NPN/edge securityfull 5G posture the security business case for SA: each migration phase activates concrete protections that NSA cannot offer
Purpose: migration as a security upgrade, not just a performance one. Moving to SA is what switches on the protections — a concrete argument for prioritizing it.
FIGURE 18.9Mixed NSA/SA Network — Threat Picture
NSA coverage areas LTE-level security IMSI exposable, no UP integrity attacker's preferred target force UE here to strip protections SA coverage areas full 5G security SUCI, UP integrity, SBA, SEPP the protected zone monitor for forced downgrades to NSA
Purpose: the operational reality during migration. A mixed network has a heterogeneous security posture; attackers herd UEs toward the weaker NSA areas — so monitoring must span both and watch for forced downgrades.
FIGURE 18.10Migration Risk Checklist
NSA → SA MIGRATION — SECURITY CHECKLIST ☑ confirm SUCI, UP integrity, SBA, SEPP are ACTIVE on SA (not just deployed) ☑ monitor the share of traffic still on NSA/LTE-level security ☑ watch for forced-downgrade attempts (UE pushed from SA to NSA/LTE) ☑ secure BOTH cores during transition (EPC and 5GC coexist) ☑ don't let "5G on the status bar" be mistaken for "5G security" in risk assessments
Purpose: the migration security job on one card. The transition period is a heterogeneous-security window that needs active management, not just a capacity rollout.

18.3 The Practical Operator View

Common misconfiguration risks

18.4 Threats and Mitigations

ThreatVectorDefense
Identity exposureNSA has no SUCImigrate to SA; until then accept LTE limits
User-plane modificationNSA has no UP integritySA with UP integrity required
Forced downgradepush UE SA→NSA/LTEmonitor downgrades, prioritize SA coverage
Roaming attacksNSA uses DiameterSA + SEPP
Misrepresented posture"5G" ≠ 5G securityaccurate risk assessment

18.5 Terminology, Example, Checklist

TermMeaning
NSA / SANon-Standalone (LTE-anchored) / Standalone (full 5GC)
EN-DCE-UTRA–NR Dual Connectivity (the NSA radio model)
Option 3/3a/3xNSA variants differing in where user-plane traffic splits
S-K_gNBSecondary gNB key derived from the LTE K_eNB
SCG bearerSecondary Cell Group bearer (the NR leg in EN-DC)

Real network example. An operator's security questionnaire to an enterprise customer claimed "5G security including user-plane integrity protection." The enterprise's own auditor checked and found the service ran on NSA — an LTE core with a 5G radio, which has no user-plane integrity at all. The claim was simply false for that deployment: NSA's security is TS 33.401 (LTE), and the advertised 5G protections don't exist until SA. The operator had conflated "5G radio" with "5G security." Fix: correct the security documentation to reflect the actual (NSA/LTE) posture, and fast-track SA for the enterprise slice that genuinely needed UP integrity. The status bar said 5G; the security spec said LTE — and only one of them was true.

Chapter Summary

? Review Questions

  1. In NSA Option 3, which node is master and which core is the anchor, and what does that mean for security?
  2. How is the NR leg keyed in EN-DC, and from what does S-K_gNB derive?
  3. List five 5G security capabilities NSA cannot provide and why.
  4. Why is SA a prerequisite (not an optimization) for 5G security?
  5. What is a forced-downgrade attack in a mixed NSA/SA network, and how do you detect it?
  6. Why must both EPC and 5GC be secured during migration?
  7. A vendor claims "5G UP integrity" on an NSA deployment. Why is this false?
  8. What does the SN Counter do in EN-DC, and what SA mechanism is it analogous to?
🧪 Mini lab — NSA vs SA posture audit

For a network (real or hypothetical) running both NSA and SA: (1) For a UE on NSA, list which of these are active: SUCI, UP integrity, SBA core security, SEPP roaming. (2) Repeat for a UE on SA. (3) Identify which of your services/slices genuinely need the SA-only protections and would be misrepresented if claimed on NSA. (4) Design the monitoring that would tell you what fraction of traffic is on NSA (LTE-level) security at any moment, and alert on forced downgrades. (5) Write one honest sentence describing your network's security posture that distinguishes "5G radio" from "5G security." This audit is exactly what separates a marketing claim from a defensible compliance statement.