# NIST800 53 IA-2 — Identification And Authentication (Organizational Users)

- Source: https://support.icompaas.com/support/solutions/articles/a_gen_nist80053_ia2_64b1fb82b7-nist800-53-ia-2-identification-and-authentication-organizational-users
- Section: [Solutions](https://support.icompaas.com/support/solutions) › [NIST](https://support.icompaas.com/support/solutions/62000112528) › [Identification and Authentication](https://support.icompaas.com/support/solutions/folders/f_gen_62000112528_identificationandauthentication)
- Last updated: 2026-05-30
- Publisher: iCompaas, Inc. (https://www.icompaas.com)

NIST800 53 · Control IA-2 · Priority: high · Component: Identification and Authentication

### What this control covers

Uniquely identify/authenticate organizational users, linking identities to processes for secure local/network/remote access using passwords, authenticators, or biometrics. This control supports the Authentication capability within the Identification and Authentication family.

### Why it matters

Risk is the language an executive team understands; this control connects technical reality to board-level decisions and budget allocation.

### How to implement

#### AWS

Codify the policy intent as **SCPs, AWS Config conformance packs, and Security Hub standards** so the cloud enforces what the document says.

#### Azure

Codify in **Azure Policy initiatives** (built-in regulatory compliance for CIS, ISO 27001, SOC 2, HIPAA) and assign at management-group level.

#### GCP

Use **Cloud Identity** (or Workspace) as the IdP and **IAM** for resource access. Grant roles at the lowest scope (project > folder > org) using **Workload Identity Federation** for CI/CD and **service accounts** for workloads — never download service-account keys when avoidable. Enable **Policy Intelligence** recommenders to right-size privileges and detect dormant identities.

#### Google Workspace

Enforce **2-Step Verification** (preferably hardware keys for admins) for the entire org, set session length to ≤ 12 hours, and disable less-secure-app access. Use **Context-Aware Access** levels to restrict admin sign-in by IP/device posture. Provision and de-provision users via **SCIM** from your HRIS so leavers lose access on day one.

#### GitHub

Require **SSO + SCIM** from your IdP on the organisation; enforce **2FA** org-wide and use **fine-grained PATs** (or, better, GitHub Apps) instead of classic tokens. Restrict **outside collaborators**, require signed commits on protected branches, and use **OIDC** from Actions to short-lived AWS/GCP/Azure credentials rather than stored secrets.

#### Zoho Mail

Make **two-factor authentication** mandatory for all users (TOTP, OneAuth, or YubiKey) in _Admin Console → Security_. Configure **SAML SSO** against your IdP and disable password-based logins for admins. Use **role-based privileges** (Admin / Spam Moderator / Mail Account Admin) and review the _Login history_ report monthly for anomalies.

#### On-premises

Maintain a policy library with a documented review cadence (annual minimum); store in your GRC tool with attestation tracking. Map each policy to controls so an audit pull cites the exact policy clause.

### Evidence to collect

-   `identity_scan` — See the iCompaas Evidence library for the canonical source for this evidence type.
-   `policy_document` — A signed, version-controlled policy stating leadership intent and the named owner.
-   `infra_scan` — See the iCompaas Evidence library for the canonical source for this evidence type.

Identity analytics (Okta, SailPoint, Access Analyzer) demonstrates least-privilege. Signed policy or standard documents the safeguard. Focus: Identification And Authentication (Organizational Users).

### Quick checklist

-   Access — Management / Authentication
-   Security — Management / Authentication
-   Network — Management / Authentication
-   Review — Management / Authentication
-   Remote — Management / Authentication
-   Authenticate — Management / Authentication

### Related articles on this site

-   [NIST 800-171 3.5.2 Authenticate (or verify) the identities of users, processes, or devices, as a prerequisite to allowing access to organizational systems.](https://support.icompaas.com/support/solutions/articles/62000229290-nist-800-171-3-5-2-authenticate-or-verify-the-identities-of-users-processes-or-devices-as-a-prer)
-   [CMMC 2.0 IA.1.077 Authenticate (or verify) the identities of those users, processes, or devices, as a prerequisite to allowing access to organizational information systems.](https://support.icompaas.com/support/solutions/articles/62000229475-cmmc-2-0-ia-1-077-authenticate-or-verify-the-identities-of-those-users-processes-or-devices-as-a)
-   [Ensure Access Review is Set Up for External Users in Azure AD Privileged Identity Management (PIM](https://support.icompaas.com/support/solutions/articles/62000229788-ensure-access-review-is-set-up-for-external-users-in-azure-ad-privileged-identity-management-pim)
-   [NIST 800-171 3.5.3 Use multifactor authentication for local and network access to privileged accounts and for network access to non-privileged accounts.\[24\] \[25\].](https://support.icompaas.com/support/solutions/articles/62000229291-nist-800-171-3-5-3-use-multifactor-authentication-for-local-and-network-access-to-privileged-accounts)

## Related compliance guidance

- [NIST SP 800-53 Rev. 5: a practical implementation guide for cloud teams](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5): How the 800-53 catalogue, baselines and the Risk Management Framework fit together, and which controls take the most work in the cloud.
- [NIST SP 800-171 and CMMC: a practical guide to protecting CUI in the cloud](https://support.icompaas.com/compliance/nist-sp-800-171-rev-3): If the driver is a DoD or federal contract handling CUI, 800-171 (and CMMC) is the scope you actually need.