Title

Direct logins must not be permitted to shared, default, application, or utility accounts. (Cat II impact)

Discussion

Shared accounts (accounts where two or more people log in with the same user identification) do not provide identification and authentication. There is no way to provide for non-repudiation or individual accountability.

Check Content

Use the last command to check for multiple accesses to an account from different workstations/IP addresses. If users log directly onto accounts, rather than using the su command from their own named account to access them, this is a finding (such as logging directly on to Oracle). Also, ask the SA or the IAO if shared accounts are logged into directly or if users log on to an individual account and switch user to the shared account.

Fix Text

Use the switch user (su) command from a named account login to access shared accounts. Maintain audit trails that identify the actual user of the account name. Document requirements and procedures for users/administrators to log into their own accounts first and then switch user (su) to the shared account.

Additional Identifiers

Rule ID: SV-220020r603265_rule

Vulnerability ID: V-220020

Group Title: SRG-OS-000109

Expert Comments

CCIs tied to check.

Controls tied to check. These are derived from the CCIs shown above.