NIST SP 800-172
IA

NIST SP 800-172 3.5.3e: Prohibit Connection of Unknown or Unverified System Components

Employ automated or manual and procedural mechanisms that prevent a system component from connecting to organizational systems unless the component is known, authenticated, in a properly configured state, or covered by a trust profile.

What else in your programme already covers this

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

  • ASBv3-IM-2 Protect identity and authentication systems
  • IM-4 Authenticate server and services
  • IM-6 Use strong authentication controls
  • IM-7 Restrict resource access based on conditions

NIST SP 800-161 Rev 1 · 4 controls

PCI DSS 4.0 · 4 controls

  • 8.3.1 All user access to system components for users and administrators is authenticated via at least one of the following authentication factors: • Something you know, such as a password or passphrase. • Something you
  • 8.4.1 MFA is implemented for all non-console access into the CDE for personnel with administrative access
  • 8.4.2 MFA is implemented for all non-console access into the CDE
  • 8.4.3 MFA is implemented for all remote access originating from outside the entity's network that could access or impact the CDE

CIS Controls v8 · 3 controls

  • CIS-6.3 Require MFA for Externally-Exposed Applications
  • CIS-6.4 Require MFA for Remote Network Access
  • CIS-6.5 Require MFA for Administrative Access

FedRAMP High · 3 controls

  • IA-2 Identification and Authentication (Organizational Users)
  • IA-2(1) MFA to Privileged Accounts
  • IA-2(2) MFA to Non-Privileged Accounts

FedRAMP Moderate · 3 controls

  • IA-2 Identification and Authentication (Organizational Users)
  • IA-2(1) MFA to Privileged Accounts
  • IA-2(2) MFA to Non-Privileged Accounts

ISO 27001:2022 · 3 controls

  • 6.7 Remote working
  • 8.2 Privileged access rights
  • 8.5 Secure authentication

ISO 27002:2022 · 3 controls

  • 6.7 Remote working
  • 8.2 Privileged access rights
  • 8.5 Secure authentication

C5 (Germany) · 2 controls

  • C5-AM-03 Commissioning of Hardware
  • C5-COS-02 Security requirements for connections in the Cloud Service Provider's network

CMMC 2.0 · 2 controls

NIST SP 800-171 Rev 3 · 2 controls

  • 03.05.01 User Identification and Authentication
  • 03.05.03 Multi-Factor Authentication

NIST SP 800-53 Rev 5 · 2 controls

  • NIST800-IA-2 Identification and authentication of organizational users
  • NIST800-IA-3 Device identification and authentication

HIPAA Security Rule · 1 control

  • 164.312(d) Person or Entity Authentication (Standard)
  • IA-2 Identification and Authentication (Organizational Users)
  • IA-2 Identification and Authentication (Organizational Users)
  • IA-2 Identification and Authentication (Organizational Users)
  • 164.312(d) Person or Entity Authentication (Standard)

SOC 2 · 1 control

  • SOC2-CC6.1 Implements logical access security software, infrastructure and architectures over protected information assets

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 IA

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

NIST SP 800-172 3.5.3e is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of NIST SP 800-172 your existing evidence covers. Hold NIST SP 800-53 Rev 5 and 24 of 35 NIST SP 800-172 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. 5 were rejected on the NIST SP 800-53 Rev 5 pair alone.

Query this from an agent

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