# AC-02 Account Management

NIST SP 800-53 control. Family: AC Access Control. Function: preventative. Baselines: low, moderate, high. Mapping licence: CC BY-SA 4.0.

Statement: a. Define and document the types of accounts allowed and specifically prohibited for use within the system; b. Assign account managers; c. Require [Assignment: organization-defined prerequisites and criteria] for group and role membership; d. Specify: 1. Authorized users of the system; 2. Group and role membership; and 3. Access authorizations (i.e., privileges) and [Assignment: organization-defined attributes (as required)] for each account; e. Require approvals by [Assignment: organization-defined personnel or roles] for requests to create accounts; f. Create, enable, modify, disable, and remove accounts in accordance with [Assignment: organization-defined policy, procedures, prerequisites, and criteria]; g. Monitor the use of accounts; h. Notify account managers and [Assignment: organization-defined personnel or roles] within: 1. [Assignment: organization-defined time period] when accounts are no longer required; 2. [Assignment: organization-defined time period] when users are terminated or transferred; and 3. [Assignment: organization-defined time period] when system usage or need-to-know changes for an individual; i. Authorize access to the system based on: 1. A valid access authorization; 2. Intended system usage; and 3. [Assignment: organization-defined attributes (as required)]; j. Review accounts for compliance with account management requirements [Assignment: organization-defined frequency]; k. Establish and implement a process for changing shared or group account authenticators (if deployed) when individuals are removed from the group; and l. Align account management processes with personnel termination and transfer processes.
Guidance: Examples of system account types include individual, shared, group, system, guest, anonymous, emergency, developer, temporary, and service. Identification of authorized system users and the specification of access privileges reflect the requirements in other controls in the security plan. Users requiring administrative privileges on system accounts receive additional scrutiny by organizational personnel responsible for approving such accounts and privileged access, including system owner, mission or business owner, senior agency information security officer, or senior agency official for privacy. Types of accounts that organizations may wish to prohibit due to increased risk include shared, group, emergency, anonymous, temporary, and guest accounts. Where access involves personally identifiable information, security programs collaborate with the senior agency official for privacy to establish the specific conditions for group and role membership; specify authorized users, group and role membership, and access authorizations for each account; and create, adjust, or remove system accounts in accordance with organizational policies. Policies can include such information as account expiration dates or other factors that trigger the disabling of accounts. Organizations may choose to define access privileges or other attributes by account, type of account, or a combination of the two. Examples of other attributes required for authorizing access include restrictions on time of day, day of week, and point of origin. In defining other system account attributes, organizations consider system-related requirements and mission/business requirements. Failure to consider these factors could affect system availability. Temporary and emergency accounts are intended for short-term use. Organizations establish temporary accounts as part of normal account activation procedures when there is a need for short-term accounts without the demand for immediacy in account activation. Organizations establish emergency accounts in response to crisis situations and with the need for rapid account activation. Therefore, emergency account activation may bypass normal account authorization processes. Emergency and temporary accounts are not to be confused with infrequently used accounts, including local logon accounts used for special tasks or when network resources are unavailable (may also be known as accounts of last resort). Such accounts remain available and are not subject to automatic disabling or removal dates. Conditions for disabling or deactivating accounts include when shared/group, emergency, or temporary accounts are no longer required and when individuals are transferred or terminated. Changing shared/group authenticators when members leave the group is intended to ensure that former group members do not retain access to the shared or group account. Some types of system accounts may require specialized training.

## Enhancements (12)
- AC-02(01) Automated System Account Management. Baselines: moderate, high
- AC-02(02) Automated Temporary and Emergency Account Management. Baselines: moderate, high
- AC-02(03) Disable Accounts. Baselines: moderate, high
- AC-02(04) Automated Audit Actions. Baselines: moderate, high
- AC-02(05) Inactivity Logout. Baselines: moderate, high
- AC-02(06) Dynamic Privilege Management
- AC-02(07) Privileged User Accounts
- AC-02(08) Dynamic Account Management
- AC-02(09) Restrictions on Use of Shared and Group Accounts
- AC-02(11) Usage Conditions. Baselines: high
- AC-02(12) Account Monitoring for Atypical Usage. Baselines: high
- AC-02(13) Disable Accounts for High-risk Individuals. Baselines: moderate, high
Withdrawn by NIST: AC-02(10) (now in AC-02).
Each enhancement's statement: /api/v1/controls/AC-02?fields=enhancements

## Patterns that use it (17)
- Critical (9): SP-011 Cloud Computing Pattern; SP-019 Secure Ad-Hoc File Exchange Pattern; SP-021 Realtime Collaboration Pattern; SP-022 Board of Directors Room; SP-026 PCI Full Environment; SP-029 Zero Trust Architecture; SP-032 Modern Authentication; SP-037 Privileged User Management; SP-044 SaaS Identity Lifecycle Management
- Important (8): SP-013 Data Security Pattern; SP-015 Secure Remote Working; SP-025 Advanced Monitoring and Detection; SP-028 Secure DevOps Pipeline Pattern; SP-031 Security Monitoring and Response; SP-034 Cyber Resilience; SP-036 Incident Response; SP-054 CBDC and Digital Currency Infrastructure (draft)

## Clauses by framework (82 frameworks)
- iso_27001_2022: A.5.15, A.5.16, A.5.18, A.8.2. OSA's own, not in NIST's crosswalk: A.5.15
- iso_27002_2022: 5.15, 5.18, 8.2
- cobit_2019: DSS05
- pci_dss_v4: 2.2.1, 2.2.2, 7.2, 8.2, 8.6
- nist_csf_2: DE.CM-01, DE.CM-03, PR.AA-01, PR.AA-05, PR.DS-10
- cis_controls_v8: CIS 4.7, CIS 5, CIS 5.1, CIS 5.3, CIS 5.5, CIS 5.6, CIS 6, CIS 6.1, CIS 6.2, CIS 6.6, CIS 6.7, CIS 6.8, CIS 12.5
- soc2_tsc: CC6.1, CC6.6, CC6.6-POF2
- finos_ccc: CCC-C11
- iso_42001_2023: A.3.2
- iec_62443: 3-3 SR 1.3
- asd_e8: E8-5, E8-5 ML1, E8-5 ML2, E8-5 ML3
- nis2: Art. 21(2)(i)
- apra_cps_234: Para 22-23
- mas_trm: 9
- bsi_grundschutz: OPS.1.1.2, ORP.4
- anssi: Hygiene.6, Hygiene.7, Hygiene.11, Hygiene.13, Hygiene.32, SecNumCloud.10.2
- osfi_b13: B-13.3.2
- finma_circular: IV.B.d(59), IV.B.d(60), IV.C(61)
- gdpr: Art.5(1)(f), Art.25(2), Art.32(1)(b), Art.32(4)
- dora: Art.9(4)(c), Art.9(4)(d)
- bio2: 5.15, 5.18, 8.2
- rbi_csf: Annex1.8, ITGRCA.19
- fisc: FISC.T2
- lgpd_bcb: BCB.Art.3, BCB.PIX, LGPD.Art.46
- hkma_tme1: TME1.8.1, TME1.8.2
- mlps_2: 8.1.4.2, 8.1.7.2
- dnb_good_practice: DNB.8.5, DNB.17.2
- cra: CRA.I.2d
- swift_cscf: SWIFT.1.2, SWIFT.2.11A, SWIFT.5.1
- cbb_tm: TM-6
- cbuae: CR-4
- nca_ecc: 2-2
- qatar_nia: AC
- sama_csf: 3.1
- uae_ia: T9
- bog_cisd: CISD-IX, CISD-VIII
- bom_ctrm: 3.3
- cbe_csf: CD-1, CTO-1
- cbn_csf: Part3.2
- popia: s19
- sa_js2: JS2-7.1
- bcbs_239: Principle 11
- bot_cyber: Ch2.2, Ch8.2
- cpmi_pfmi: CG.PR, PFMI.P17
- eba_ict: 3.4.2
- ecb_croe: CROE.2.3.1
- ffiec_is: II.C.7, II.C.7(b), II.C.15
- hipaa_sr: §164.308(a)(3)(i), §164.308(a)(3)(ii)(A), §164.308(a)(3)(ii)(B), §164.308(a)(3)(ii)(C), §164.308(a)(4)(i), §164.308(a)(4)(ii)(B), §164.308(a)(4)(ii)(C), §164.312(a)(1), §164.312(a)(2)(i), §164.312(a)(2)(ii)
- iosco_cyber: PROT-1
- nydfs_500: 500.7
- sebi_cscrf: PR.AA
- cmmc_2: AC
- nerc_cip: CIP-004-7, CIP-007-6
- nrc_73_54: RG5.71-A-AC
- tsa_psd: SD-2 Sec B
- ieee_1686: 5.1
- ferc_cip: Order 850
- doe_c2m2: ACCESS
- api_1164: Sec 6
- awia: AWWA Sec 3
- iaea_nss: Sec 5.2, Sec 5.3
- fips_140: FIPS 140-3 §7.4
- common_criteria: CC Part 2 — FMT
- isae_3402: Clause 4
- fca_sysc_13: SYSC 13.7.3
- fda_21_cfr_11: §11.10(d), §11.10(g), §11.100(a), §11.200(a)(2), §11.300(a), §11.300(b), §11.300(c)
- fda_cyber: SA-1
- hitrust_csf: 01.a, 02.c
- iso_27799: 7.3, 9.1, 9.2, 9.3
- lloyds_ms: MS8.3
- naic_ds: 4-access, 4B
- nhs_dspt: NDG-4.1, NDG-4.2
- pra_ss1_23: P2.4, P-IT.1
- solvency_ii: EIOPA-ICT-4.4
- csa_ccm_v4: IAM-03, IAM-05, IAM-06, IAM-07, IAM-08, IAM-10, IAM-11, IAM-13, LOG-12
- csa_aicm: IAM-03, IAM-05, IAM-06, IAM-07, IAM-08, IAM-10, IAM-11, IAM-13, IAM-17, IAM-18, LOG-12
- ccss_v9: 1.04.1, 1.04.2, 1.06.2
- mica: Art.67(1), Art.86(1)
- basel_sco60: SCO60.55, SCO60.62
- bssc: GSP-11, KMS-06, NOS-05
- sec_custody_digital: SEC-CD-02, SEC-CD-05, SEC-CD-16
- dpdpa: Rules.6(1)(b)
OSA's mapping for iso_27001_2022 and nist_csf_2 takes NIST's published crosswalk as its base. A clause not marked as OSA's own is in that crosswalk.

## More
- This control as JSON, with guidance and ATT&CK techniques: /api/v1/controls/AC-02
- Clauses only: /api/v1/controls/AC-02?fields=mappings
- Page for people: /controls/ac-02/