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; and2. 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; andc. Review and update the current identification and authentication:1. Policy [Assignment: organization-defined frequency] and following [Assignment: organization-defined events]; and2. Procedures [Assignment: organization-defined frequency] and following [Assignment: organization-defined events].
Uniquely identify and authenticate organizational users and associate that unique identification with processes acting on behalf of those users.
Implement multi-factor authentication for access to privileged accounts.
Implement multi-factor authentication for access to non-privileged accounts.
[Withdrawn: Incorporated into IA-2(1).]
[Withdrawn: Incorporated into IA-2(2).]
When shared accounts or authenticators are employed, require users to be individually authenticated before granting access to the shared accounts or resources.
Implement multi-factor authentication for [Selection (one or more): local; network; remote] access to [Selection (one or more): privileged accounts; non-privileged accounts] such that:(a) One of the factors is provided by a device separate from the system gaining access; and(b) The device meets [Assignment: organization-defined strength of mechanism requirements].
[Withdrawn: Incorporated into IA-2(6).]
Implement replay-resistant authentication mechanisms for access to [Selection (one or more): privileged accounts; non-privileged accounts].
[Withdrawn: Incorporated into IA-2(8).]
Provide a single sign-on capability for [Assignment: organization-defined system accounts and services].
[Withdrawn: Incorporated into IA-2(6).]
Accept and electronically verify Personal Identity Verification-compliant credentials.
Implement the following out-of-band authentication mechanisms under [Assignment: organization-defined conditions]: [Assignment: organization-defined out-of-band authentication].
Uniquely identify and authenticate [Assignment: organization-defined devices and/or types of devices] before establishing a [Selection (one or more): local; remote; network] connection.
Authenticate [Assignment: organization-defined devices and/or types of devices] before establishing [Selection (one or more): local; remote; network] connection using bidirectional authentication that is cryptographically based.
[Withdrawn: Incorporated into IA-3(1).]
(a) Where addresses are allocated dynamically, standardize dynamic address allocation lease information and the lease duration assigned to devices in accordance with [Assignment: organization-defined lease information and lease duration]; and(b) Audit lease information when assigned to a device.
Handle device identification and authentication based on attestation by [Assignment: organization-defined configuration management process].
Manage system identifiers by:a. Receiving authorization from [Assignment: organization-defined personnel or roles] to assign an individual, group, role, service, or device identifier;b. Selecting an identifier that identifies an individual, group, role, service, or device;c. Assigning the identifier to the intended individual, group, role, service, or device; andd. Preventing reuse of identifiers for [Assignment: organization-defined time period].
Prohibit the use of system account identifiers that are the same as public identifiers for individual accounts.
[Withdrawn: Incorporated into IA-12(1).]
[Withdrawn: Incorporated into IA-12(2).]
Manage individual identifiers by uniquely identifying each individual as [Assignment: organization-defined characteristic identifying individual status].
Manage individual identifiers dynamically in accordance with [Assignment: organization-defined dynamic identifier policy].
Coordinate with the following external organizations for cross-organization management of identifiers: [Assignment: organization-defined external organizations].
[Withdrawn: Incorporated into IA-12(4).]
Generate pairwise pseudonymous identifiers.
Maintain the attributes for each uniquely identified individual, device, or service in [Assignment: organization-defined protected central storage].
Manage system authenticators by:a. Verifying, as part of the initial authenticator distribution, the identity of the individual, group, role, service, or device receiving the authenticator;b. Establishing initial authenticator content for any authenticators issued by the organization;c. Ensuring that authenticators have sufficient strength of mechanism for their intended use;d. Establishing and implementing administrative procedures for initial authenticator distribution, for lost or compromised or damaged authenticators, and for revoking authenticators;e. Changing default authenticators prior to first use;f. Changing or refreshing authenticators [Assignment: organization-defined time period by authenticator type] or when [Assignment: organization-defined events] occur;g. Protecting authenticator content from unauthorized disclosure and modification;h. Requiring individuals to take, and having devices implement, specific controls to protect authenticators; andi. Changing authenticators for group or role accounts when membership to those accounts changes.
For password-based authentication:(a) Maintain a list of commonly-used, expected, or compromised passwords and update the list [Assignment: organization-defined frequency] and when organizational passwords are suspected to have been compromised directly or indirectly;(b) Verify, when users create or update passwords, that the passwords are not found on the list of commonly-used, expected, or compromised passwords in IA-5(1)(a);(c) Transmit passwords only over cryptographically-protected channels;(d) Store passwords using an approved salted key derivation function, preferably using a keyed hash;(e) Require immediate selection of a new password upon account recovery;(f) Allow user selection of long passwords and passphrases, including spaces and all printable characters;(g) Employ automated tools to assist the user in selecting strong password authenticators; and(h) Enforce the following composition and complexity rules: [Assignment: organization-defined composition and complexity rules].
(a) For public key-based authentication:(1) Enforce authorized access to the corresponding private key; and(2) Map the authenticated identity to the account of the individual or group; and(b) When public key infrastructure (PKI) is used:(1) Validate certificates by constructing and verifying a certification path to an accepted trust anchor, including checking certificate status information; and(2) Implement a local cache of revocation data to support path discovery and validation.
[Withdrawn: Incorporated into IA-12(4).]
[Withdrawn: Incorporated into IA-5(1).]
Require developers and installers of system components to provide unique authenticators or change default authenticators prior to delivery and installation.
Protect authenticators commensurate with the security category of the information to which use of the authenticator permits access.
Ensure that unencrypted static authenticators are not embedded in applications or other forms of static storage.
Implement [Assignment: organization-defined security controls] to manage the risk of compromise due to individuals having accounts on multiple systems.
Use the following external organizations to federate credentials: [Assignment: organization-defined external organizations].
Bind identities and authenticators dynamically using the following rules: [Assignment: organization-defined binding rules].
[Withdrawn: Incorporated into IA-2(1) and IA-2(2).]
For biometric-based authentication, employ mechanisms that satisfy the following biometric quality requirements [Assignment: organization-defined biometric quality requirements].
Prohibit the use of cached authenticators after [Assignment: organization-defined time period].
For PKI-based authentication, employ an organization-wide methodology for managing the content of PKI trust stores installed across all platforms, including networks, operating systems, browsers, and applications.
Use only General Services Administration-approved products and services for identity, credential, and access management.
Require that the issuance of [Assignment: organization-defined types of and/or specific authenticators] be conducted [Selection: in person; by a trusted external party] before [Assignment: organization-defined registration authority] with authorization by [Assignment: organization-defined personnel or roles].
Employ presentation attack detection mechanisms for biometric-based authentication.
(a) Employ [Assignment: organization-defined password managers] to generate and manage passwords; and(b) Protect the passwords using [Assignment: organization-defined controls].
Obscure feedback of authentication information during the authentication process to protect the information from possible exploitation and use by unauthorized individuals.
Implement mechanisms for authentication to a cryptographic module that meet the requirements of applicable laws, executive orders, directives, policies, regulations, standards, and guidelines for such authentication.
Uniquely identify and authenticate non-organizational users or processes acting on behalf of non-organizational users.
Accept and electronically verify Personal Identity Verification-compliant credentials from other federal agencies.
(a) Accept only external authenticators that are NIST-compliant; and(b) Document and maintain a list of accepted external authenticators.
[Withdrawn: Incorporated into IA-8(2).]
Conform to the following profiles for identity management [Assignment: organization-defined identity management profiles].
Accept and verify federated or PKI credentials that meet [Assignment: organization-defined policy].
Implement the following measures to disassociate user attributes or identifier assertion relationships among individuals, credential service providers, and relying parties: [Assignment: organization-defined measures].
Uniquely identify and authenticate [Assignment: organization-defined system services and applications] before establishing communications with devices, users, or other services or applications.
[Withdrawn: Incorporated into IA-9.]
[Withdrawn: Incorporated into IA-9.]
Require individuals accessing the system to employ [Assignment: organization-defined supplemental authentication techniques or mechanisms] under specific [Assignment: organization-defined circumstances or situations].
Require users to re-authenticate when [Assignment: organization-defined circumstances or situations requiring re-authentication].
a. Identity proof users that require accounts for logical access to systems based on appropriate identity assurance level requirements as specified in applicable standards and guidelines;b. Resolve user identities to a unique individual; andc. Collect, validate, and verify identity evidence.
Require that the registration process to receive an account for logical access includes supervisor or sponsor authorization.
Require evidence of individual identification be presented to the registration authority.
Require that the presented identity evidence be validated and verified through [Assignment: organizational defined methods of validation and verification].
Require that the validation and verification of identity evidence be conducted in person before a designated registration authority.
Require that a [Selection: registration code; notice of proofing] be delivered through an out-of-band channel to verify the users address (physical or digital) of record.
Accept externally-proofed identities at [Assignment: organization-defined identity assurance level].