# NIST800 171 3.1.1 — Account Management

- Source: https://support.icompaas.com/support/solutions/articles/a_gen_nist800171_311_f9d738f935-nist800-171-311-account-management
- Section: [Solutions](https://support.icompaas.com/support/solutions) › [NIST SP 800-171 Readiness](https://support.icompaas.com/support/solutions/c_gen_nist800171) › [Access Control](https://support.icompaas.com/support/solutions/folders/f_gen_cgennist800171_accesscontrol)
- Last updated: 2026-05-30
- Publisher: iCompaas, Inc. (https://www.icompaas.com)

NIST800 171 · Control 3.1.1 · Priority: high · Component: Access Control

### What this control covers

This control defines the management of system accounts, including the creation, modification, enabling, disabling, and removal of accounts. It specifies the required account types (e.g., individual, group, service) and outlines the process for granting and revoking access based on authorization and intended usage. It also mandates the monitoring of account use, disabling inactive or expired accounts, and notifying relevant personnel when access is no longer needed. This control supports the Account Management System capability within the Access Control (3.1) 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.

Identity analytics (Okta, SailPoint, Access Analyzer) demonstrates least-privilege. Signed policy or standard documents the safeguard. Focus: Account Management.

### Quick checklist

-   Account — Management / Creation
-   Access — Management / Creation
-   Access Control — Management / Creation
-   System — Management / Creation
-   Personnel — Management / Creation
-   Risk — Management / Creation

### Related articles on this site

-   [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.1.1 Limit information system access to authorized users, processes acting on behalf of authorized users, or devices (including other information systems).](https://support.icompaas.com/support/solutions/articles/62000229223-nist-800-171-3-1-1-limit-information-system-access-to-authorized-users-processes-acting-on-behalf-of)
-   [NIST 800-171 3.1.2 Limit system access to the types of transactions and functions that authorized users are permitted to execute.](https://support.icompaas.com/support/solutions/articles/62000229224-nist-800-171-3-1-2-limit-system-access-to-the-types-of-transactions-and-functions-that-authorized-us)
-   [NIST 800-171 3.1.5 Employ the principle of least privilege, including for specific security functions and privileged accounts.](https://support.icompaas.com/support/solutions/articles/62000229227-nist-800-171-3-1-5-employ-the-principle-of-least-privilege-including-for-specific-security-functions)

## Related compliance guidance

- [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): The CUI requirements CMMC Level 2 assesses, the SPRS score, POA&M rules and the phased DFARS rollout.
- [NIST SP 800-53 Rev. 5: a practical implementation guide for cloud teams](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5): The federal catalogue 800-171 is derived from — useful when a contract also cites a FedRAMP baseline.