FedRAMP High
IA - Identification and Authentication

FedRAMP High IA-8: Identification and Authentication (Non-Organizational Users)

Uniquely identify and authenticate non-organizational users (e.g., federal customers).

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

What else in your programme already covers this

This control maps to 36 controls across 22 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 · 5 controls

  • 8.2.1 8.2.1 Unique ID assigned to every user
  • 8.2.4 8.2.4 User ID lifecycle changes authorized
  • 8.2.7 8.2.7 Third-party remote access accounts controlled
  • 8.3.1 8.3.1 Access authenticated with at least one factor
  • 8.4.2 8.4.2 MFA for all non-console CDE access

CIS Controls v8 · 4 controls

  • CIS-14.3 Train Workforce Members on Authentication Best Practices
  • CIS-6.3 Require MFA for Externally-Exposed Applications
  • CIS-6.6 Establish and Maintain an Inventory of Authentication and Authorization Systems
  • CIS-6.7 Centralize Access Control
  • NIST-CSF-PR.AA-01 Identities and credentials for authorized users, services, and hardware are managed by the organization
  • NIST-CSF-PR.AA-02 Identities are proofed and bound to credentials based on the context of interactions
  • NIST-CSF-PR.AA-03 Users, services, and hardware are authenticated
  • ASBv3-IM-9 Secure user access to existing applications
  • IM-1 Use centralized identity and authentication system

ISO 27001:2022 · 2 controls

  • 5.16 Identity management
  • 8.5 Secure authentication

ISO 27002:2022 · 2 controls

  • 5.16 Identity management
  • 8.5 Secure authentication

SOC 2 · 2 controls

  • SOC2-CC6.1 CC6.1 Logical access security over protected information assets
  • SOC2-CC6.2 CC6.2 Registering and authorising users before issuing credentials
  • E8-MFA-ML1 Multi-Factor Authentication - Maturity Level 1
  • ANSSI-HYG-25 Secure Dedicated Network Interconnections with Partners
  • SEC02-BP04 Rely on a centralized identity provider
  • MYHR-REG-2 Healthcare recipient registration and identity verification

C5 (Germany) · 1 control

CMMC 2.0 · 1 control

HIPAA Security Rule · 1 control

  • 164.312(d) Person or Entity Authentication (Standard)
  • 161R1-IA-8 Identification and Authentication (Non-Organizational Users)
  • 03.05.01 User Identification and Authentication
  • NIST800-IA-8 IA-8 Identification and Authentication (Non-organizational Users)
  • IA-8 IA-8 Identification and Authentication (Non-organizational Users)
  • IA-8 IA-8 Identification and Authentication (Non-organizational Users)
  • IA-8 IA-8 Identification and Authentication (Non-organizational Users)
  • 164.312(d) Person or Entity Authentication (Standard)

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 - Identification and Authentication

You are reading one control. How much of FedRAMP High have you already done?

FedRAMP High IA-8 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of FedRAMP High your existing evidence covers. Hold C5 (Germany) and 119 of 410 FedRAMP High 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. 6 were rejected on the C5 (Germany) pair alone.

Query this from an agent

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