Cross-Framework Mapping

NIST SP 800-161vs3GPP 5G Security Architecture (TS 33.501)

See exactly how NIST SP 800-161 controls map to 3GPP 5G Security Architecture (TS 33.501). Pre-computed mappings, identified gaps, and coverage analysis.

12
Controls Mapped
19
Gaps Found
23%
Coverage

According to the TheArtOfService Compliance Knowledge Graph:

NIST SP 800-161 maps to 3GPP 5G Security Architecture (TS 33.501) with 23% coverage across 7 directly mapped controls. Analysis of 31 NIST SP 800-161 controls identifies 24 compliance gaps — primarily concentrated in NIST SP 800-161: Operations Security.

Source: TheArtOfService Knowledge Graph | 31 controls analysed | 693 frameworks | 819K+ cross-framework mappings

Control Mappings

Showing 12 of 12 mapped controls across 3 domains. Sign up to explore all 819K+ mappings across 693 frameworks.

NIST SP 800-161: Information Security Policies(2 mappings)

NIST161-04Roles and responsibilities definition2 targets
6.3SUPI and SUCI Privacy
6.5AUSF and SEAF Functions

NIST SP 800-161: Access Control(5 mappings)

NIST161-13Authentication and password management3 targets
6.4Secondary Authentication
6.5AUSF and SEAF Functions
TS33.501-6.1Authentication Framework
NIST161-14Privileged access management2 targets
TS33.501-13.1NF Registration and Discovery Security
TS33.501-13.4OAuth 2.0 Authorization Framework

NIST SP 800-161: Cryptography(5 mappings)

NIST161-16Cryptographic policy and key management
TS33.501-13.2Service Based Interface Security
NIST161-17Encryption of data at rest
TS33.501-6.6AS Security
NIST161-18Encryption of data in transit2 targets
TS33.501-13.2Service Based Interface Security
TS33.501-6.6AS Security
NIST161-20Key lifecycle management
TS33.501-13.2Service Based Interface Security

Stop Paying Consultants to Read Spreadsheets

AI-powered compliance intelligence across 693 frameworks — at a fraction of consulting costs.

$0/forever

Free

  • 693 framework browser
  • Cross-framework mappings (819K+)
  • 824 compliance assessments
  • 3 AI queries & searches per day
Get Started Free
Recommended
$49/month

Professional

  • Unlimited AI Compliance Advisory
  • Unlimited full-text search
  • Framework self-assessment
  • PDF, Excel & CSV exports
Start 7-Day Free Trial →

What are the key differences between NIST SP 800-161 and 3GPP 5G Security Architecture (TS 33.501)?

NIST SP 800-161 has 31 controls across its framework, while 3GPP 5G Security Architecture (TS 33.501) covers 28 controls. Direct mapping analysis identifies 7 overlapping controls (23% coverage). The frameworks diverge most significantly in NIST SP 800-161: Operations Security, where 6 NIST SP 800-161 controls have no direct 3GPP 5G Security Architecture (TS 33.501) equivalent.

How many controls map between NIST SP 800-161 and 3GPP 5G Security Architecture (TS 33.501)?

Of 31 total NIST SP 800-161 controls, 7 map directly to 3GPP 5G Security Architecture (TS 33.501) controls — representing 23% coverage. The remaining 24 controls represent compliance gaps requiring additional documentation or compensating controls to satisfy both frameworks simultaneously.

What are the compliance gaps when mapping NIST SP 800-161 to 3GPP 5G Security Architecture (TS 33.501)?

24 NIST SP 800-161 controls have no direct equivalent in 3GPP 5G Security Architecture (TS 33.501). The highest concentration of gaps is in NIST SP 800-161: Operations Security with 6 unmapped controls. These gaps represent areas where additional controls, policies, or documentation must be created to achieve compliance with both frameworks.

Which control domains have the most gaps between NIST SP 800-161 and 3GPP 5G Security Architecture (TS 33.501)?

The domain with the highest gap count is NIST SP 800-161: Operations Security (6 gaps). Export the full domain-by-domain gap breakdown via the Professional tier to generate a prioritised remediation roadmap.

This platform provides educational compliance tools, not legal, regulatory, or professional compliance advice. Cross-framework mappings are AI-assisted interpretations and do not reproduce or replace official standards. Framework names and trademarks belong to their respective owners. Consult qualified professionals for your specific compliance requirements. See our Terms of Service.