NIST SP 800-53 Rev 5
IA - Identification and Authentication

NIST SP 800-53 Rev 5 NIST800-IA-1: IA-1 Policy and Procedures

a. Develop, document, and disseminate to [Assignment: organization-defined personnel or roles]: 1. [Selection (one or more): organization-level; mission/business process-level; system-level] identification and authentication policy that: (a) Addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and (b) Is consistent with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines; and 2. Procedures to facilitate the implementation of the identification and authentication policy and the associated identification and authentication controls; b. Designate an [Assignment: organization-defined official] to manage the development, documentation, and dissemination of the identification and authentication policy and procedures; and c. Review and update the current identification and authentication: 1. Policy [Assignment: organization-defined frequency] and following [Assignment: organization-defined events]; and 2. Procedures [Assignment: organization-defined frequency] and following [Assignment: organization-defined events].

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

What else in your programme already covers this

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

CIS Controls v8 · 4 controls

  • CIS-12.5 Centralize Network Authentication, Authorization, and Auditing (AAA)
  • 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

ISO 27001:2022 · 3 controls

  • 5.16 Identity management
  • 5.17 Authentication information
  • 8.5 Secure authentication
  • NIST-CSF-GV.PO-01 Policy for managing cybersecurity risks is established based on organizational context, cybersecurity strategy, and priorities and is communicated and enforced
  • NIST-CSF-PR.AA-01 Identities and credentials for authorized users, services, and hardware are managed by the organization
  • NIST-CSF-PR.AA-03 Users, services, and hardware are authenticated

SOC 2 · 3 controls

  • SOC2-CC5.3 CC5.3 Deploying controls through policies and procedures (COSO principle 12)
  • SOC2-CC6.1 CC6.1 Logical access security over protected information assets
  • SOC2-CC6.2 CC6.2 Registering and authorising users before issuing credentials

ISO 27002:2022 · 2 controls

  • 5.16 Identity management
  • 5.17 Authentication information

PCI DSS 4.0 · 2 controls

  • 8.3.8 8.3.8 Authentication policies communicated to users
  • 8.1.1 8.1.1 Requirement 8 policies and procedures maintained
  • ASBv3-GS-6 Define and implement identity and privileged access strategy

C5 (Germany) · 1 control

  • C5-IDM-01 Policy for user accounts and access rights
  • ITSG33-IA Identification and Authentication (IA)
  • CCM-IAM-01 Identity and Access Management Policy and Procedures

FedRAMP High · 1 control

  • IA-1 Policy and Procedures

FedRAMP Moderate · 1 control

  • IA-1 Policy and Procedures

ISO 27701:2019 · 1 control

  • 6.2.1 Management direction for information security
  • IA-1 IA-1 Policy and Procedures
  • IA-1 IA-1 Policy and Procedures
  • IA-1 IA-1 Policy and Procedures

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 NIST SP 800-53 Rev 5 have you already done?

NIST SP 800-53 Rev 5 NIST800-IA-1 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 31 it maps to, and the evidence behind each claim, over MCP and REST.