IA-02 Identification and Authentication (Organizational Users)
Control statement
Uniquely identify and authenticate organizational users and associate that unique identification with processes acting on behalf of those users.
Guidance
Organizations can satisfy the identification and authentication requirements by complying with the requirements in HSPD 12. Organizational users include employees or individuals who organizations consider to have an equivalent status to employees (e.g., contractors and guest researchers). Unique identification and authentication of users applies to all accesses other than those that are explicitly identified in AC-14 and that occur through the authorized use of group authenticators without individual authentication. Since processes execute on behalf of groups and roles, organizations may require unique identification of individuals in group accounts or for detailed accountability of individual activity. Organizations employ passwords, physical authenticators, or biometrics to authenticate user identities or, in the case of multi-factor authentication, some combination thereof. Access to organizational systems is defined as either local access or network access. Local access is any access to organizational systems by users or processes acting on behalf of users, where access is obtained through direct connections without the use of networks. Network access is access to organizational systems by users (or processes acting on behalf of users) where access is obtained through network connections (i.e., nonlocal accesses). Remote access is a type of network access that involves communication through external networks. Internal networks include local area networks and wide area networks. The use of encrypted virtual private networks for network connections between organization-controlled endpoints and non-organization-controlled endpoints may be treated as internal networks with respect to protecting the confidentiality and integrity of information traversing the network. Identification and authentication requirements for non-organizational users are described in IA-8.
Implementation
Keycloak customer sign-in (canary)
Customer users are to be identified and authenticated by Keycloak, one realm per customer. Partial: the Keycloak instance runs on the canary (checked), but no customer realm is imported, so no user authenticates through it yet.
Status: partial.
Evidence:
All controls. Source: OSCAL component definition reti-platform and NIST SP 800-53 Rev 5 (public domain).