8.8 KiB
| implementation-status | control-origination | |||||
|---|---|---|---|---|---|---|
|
|
ac-2 - [catalog] Account Management
Control Statement
-
[a] Define and document the types of accounts allowed and specifically prohibited for use within the system;
-
[b] Assign account managers;
-
[c] Require 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 attributes (as required) for each account;
-
[e] Require approvals by personnel or roles for requests to create accounts;
-
[f] Create, enable, modify, disable, and remove accounts in accordance with policy, procedures, prerequisites, and criteria;
-
[g] Monitor the use of accounts;
-
[h] Notify account managers and personnel or roles within:
- [1] time period when accounts are no longer required;
- [2] time period when users are terminated or transferred; and
- [3] 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] attributes (as required);
-
[j] Review accounts for compliance with account management requirements 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.
Control 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.
Control assessment-objective
account types allowed for use within the system are defined and documented; account types specifically prohibited for use within the system are defined and documented; account managers are assigned; prerequisites and criteria for group and role membership are required; authorized users of the system are specified; group and role membership are specified; access authorizations (i.e., privileges) are specified for each account; attributes (as required) are specified for each account; approvals are required by personnel or roles for requests to create accounts; accounts are created in accordance with policy, procedures, prerequisites, and criteria; accounts are enabled in accordance with policy, procedures, prerequisites, and criteria; accounts are modified in accordance with policy, procedures, prerequisites, and criteria; accounts are disabled in accordance with policy, procedures, prerequisites, and criteria; accounts are removed in accordance with policy, procedures, prerequisites, and criteria; the use of accounts is monitored; account managers and personnel or roles are notified within time period when accounts are no longer required; account managers and personnel or roles are notified within time period when users are terminated or transferred; account managers and personnel or roles are notified within time period when system usage or the need to know changes for an individual; access to the system is authorized based on a valid access authorization; access to the system is authorized based on intended system usage; access to the system is authorized based on attributes (as required); accounts are reviewed for compliance with account management requirements frequency; a process is established for changing shared or group account authenticators (if deployed) when individuals are removed from the group; a process is implemented for changing shared or group account authenticators (if deployed) when individuals are removed from the group; account management processes are aligned with personnel termination processes; account management processes are aligned with personnel transfer processes.
What is the solution and how is it implemented?
Implementation a.
Add control implementation description here for item ac-2_smt.a
Implementation b.
Add control implementation description here for item ac-2_smt.b
Implementation c.
Add control implementation description here for item ac-2_smt.c
Implementation d.
Add control implementation description here for item ac-2_smt.d
Implementation e.
Add control implementation description here for item ac-2_smt.e
Implementation f.
Add control implementation description here for item ac-2_smt.f
Implementation g.
Add control implementation description here for item ac-2_smt.g
Implementation h.
Add control implementation description here for item ac-2_smt.h
Implementation i.
Add control implementation description here for item ac-2_smt.i
Implementation j.
Add control implementation description here for item ac-2_smt.j
Implementation k.
Add control implementation description here for item ac-2_smt.k
Implementation l.
Add control implementation description here for item ac-2_smt.l