Framework overlap

Does 3GPP 5G Security Architecture (TS 33.501) cover NIST SP 800-183?

You hold 3GPP 5G Security Architecture (TS 33.501) and have been told to do NIST SP 800-183. Here is how much overlaps, control by control.

7% of NIST SP 800-183 you already have

3GPP 5G Security Architecture (TS 33.501) already covers about 7% of NIST SP 800-183, leaving 28 of 30 controls as genuinely new work.

Already covered 0 Likely covered 2 New work 28

No control in 3GPP 5G Security Architecture (TS 33.501) maps directly to one in NIST SP 800-183. Everything counted as covered is covered because both map to the same third standard, which is what a crosswalk is, but it is an inference rather than a lookup.

What is genuinely new work

Nothing in 3GPP 5G Security Architecture (TS 33.501) reaches these. This is the list to scope.

NoT.ELEM.COST
Cost Element
NoT.ELEM.DEV
Device ID Element
NoT.ELEM.ENV
Environment Element
NoT.ELEM.GEO
Geographic Location Element
NoT.ELEM.OWN
Owner Element
NoT.ELEM.SNAP
Snapshot Element
NoT.PRIM.AGGR
Aggregator Primitive
NoT.PRIM.COMM
Communication Channel Primitive
NoT.PRIM.DTRIG
Decision Trigger Primitive
NoT.PRIM.EUTIL
External Utility Primitive
NoT.PRIM.SENSOR
Sensor Primitive
NoT.RISK.MISSION
Mission Risk for NoT Deployments
NoT.SEC.AGGR
Aggregator Security
NoT.SEC.COMM
Communication Channel Security
NoT.SEC.DTRIG
Decision Trigger Security
NoT.SEC.EUTIL
External Utility Security
NoT.SEC.SENSOR
Sensor Security
NoT.TRUST.DATA
Data Trustworthiness
NoT.TRUST.IDENT
Primitive Identity Trust
NoT.TRUST.RELY
Reliability of Primitives
SP800-183-ENVIRONMENT
Operating Environment and Latency
SP800-183-P1-SENSOR
Primitive 1: Sensor
SP800-183-P2-AGGREGATOR
Primitive 2: Aggregator
SP800-183-P2-CLUSTER
Aggregator Actor: Cluster
SP800-183-P2-WEIGHT
Aggregator Actor: Weight
SP800-183-P4-EUTILITY
Primitive 4: eUtility (external utility)
SP800-183-P5-TRIGGER
Primitive 5: Decision Trigger
SP800-183-RELIABILITY
Reliability and Trust Across Primitives
Show the 2 you already have
SP800-183-DATA-FLOW
Data Flow and Snapshots
SP800-183-P3-CHANNEL
Primitive 3: Communication Channel

How this is calculated

Already covered means a mapping runs from a control in 3GPP 5G Security Architecture (TS 33.501) to that control. Likely covered means no direct mapping exists but both frameworks map to the same control in a third standard. New work means neither. We keep those separate rather than adding them into one friendlier number, because blending them would present a two-hop inference as a verified fact.

Coverage is not symmetric. Run it the other way and you will get a different number; both are correct.

From 332,959 cross-framework control mappings across 723 frameworks, 531 of them verified against their source documents. It does not tell you that you are compliant: a mapped control means the two standards ask for the same thing, not that you have done it.

Try another pair ยท Today's edition