NIST SP 800-53 Rev 5
SC - System and Communications Protection

NIST SP 800-53 Rev 5 NIST800-SC-22: SC-22 Architecture and Provisioning for Name/Address Resolution Service

Ensure the systems that collectively provide name/address resolution service for an organization are fault-tolerant and implement internal and external role separation.

Maintained by Gerard BlokdykVerified against the published standard Control text last updated

What else in your programme already covers this

This control maps to 47 controls across 32 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.

PCI DSS 4.0 · 4 controls

  • 1.2.3 1.2.3 Accurate network diagram of CDE connections
  • 1.2.4 1.2.4 Accurate data-flow diagram for account data
  • 1.2.5 1.2.5 Allowed services, protocols and ports justified
  • 1.4.3 1.4.3 Anti-spoofing measures at trusted boundary

SOC 2 · 4 controls

  • SOC2-CC5.2 CC5.2 General controls over technology (COSO principle 11)
  • SOC2-CC6.1 CC6.1 Logical access security over protected information assets
  • SOC2-CC6.6 CC6.6 Protection against threats from outside the system boundary
  • SOC2-CC8.1 CC8.1 Managing changes to procedures, software, data and infrastructure

ISO 27701:2019 · 2 controls

  • 6.10.1 Network security management
  • 6.11.1 Security requirements of information systems

BSI IT-Grundschutz · 1 control

  • BSI-01 Account management and provisioning

CIS Controls v8 · 1 control

  • CIS-4.9 Configure Trusted DNS Servers on Enterprise Assets

FedRAMP High · 1 control

  • SC-22 Architecture and Provisioning for Name/Address Resolution Service

FedRAMP Moderate · 1 control

  • SC-22 Architecture and Provisioning for Name/Address Resolution Service
  • B.6.1 B.6.1 Domain Name Service (DNS) Requirements

ISO 27001:2022 · 1 control

  • 8.27 Secure system architecture and engineering principles

ISO/IEC 27010:2015 · 1 control

  • 27010-9.2 Authentication of Sources

ISO/IEC 27043:2015 · 1 control

  • ISO27043-12 User access management and provisioning

ISO/SAE 21434 · 1 control

  • ISO21434-12 User access management and provisioning
  • NISTPF-5 Protect-P Access Control (PR.AC-P)

NIST SP 800-190 · 1 control

  • SC-22 SC-22 Architecture and Provisioning for Name/Address Resolution Service
  • SC-22 SC-22 Architecture and Provisioning for Name/Address Resolution Service
  • SC-22 SC-22 Architecture and Provisioning for Name/Address Resolution Service

NIST SP 800-88 · 1 control

  • NISTSP88-1 Media Sanitization Policy, Roles, and Decision Framework

NIST SP 800-92 · 1 control

  • NISTSP92-4 Log Management: Time Synchronisation, Parsing, Storage, Integrity, Access Control
  • ORANWG11-3 Cryptography, TLS, SSH, IPsec, and PKI Lifecycle Management

OWASP SAMM · 1 control

  • OWASPSAMM-2 Design: Threat Assessment, Security Requirements, Security Architecture
  • OMANCS-3 Identity and Access Management, Authentication, Privileged Access

OpenSSF Scorecard · 1 control

  • OSSFSC-3 Build, CI/CD Security, Workflow Permissions, Dangerous Patterns

PTES · 1 control

  • PTESPHASE-2 Intelligence Gathering (OSINT)
  • SHAREASSESS-2 Access Control, Identity, Authentication

SLSA · 1 control

  • SUPCHAIN-1 Build Integrity - Source, Build, Provenance
  • SIGSTORE-2 Transparency Log (Rekor) and Verification

South Korea ISMS-P · 1 control

  • ISMSP-AC-02 User Account Management

Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected.

Other controls in SC - System and Communications Protection

You are reading one control. How much of NIST SP 800-53 Rev 5 have you already done?

NIST SP 800-53 Rev 5 NIST800-SC-22 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of NIST SP 800-53 Rev 5 your existing evidence covers. Hold ISO 27001:2022 and 163 of 1014 NIST SP 800-53 Rev 5 controls already carry evidence.

Each report names every control your existing framework evidences, every one it does not, the reasoning behind each claim, and the claims that were argued against and rejected. 342 were rejected on the ISO 27001:2022 pair alone.

Query this from an agent

The graph holds this control, the 47 it maps to, and the evidence behind each claim, over MCP and REST.