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. # last -R If users log directly onto accounts, rather than using the switch user (su) command from their own named account to access them, this is a finding (such as logging directly on to oracle). Verify with the SA or the IAO on documentation for users/administrators to log into their own accounts first and then switch user (su) to the account to be shared has been maintained including requirements and procedures. If no such documentation exists, this is a finding.

Fix Text

Use the switch user (su) command from a named account login to access shared accounts. Maintain audit trails to 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 account to be shared.

Additional Identifiers

Rule ID: SV-44791r1_rule

Vulnerability ID: V-760

Group Title: GEN000280

Expert Comments

CCIs tied to check.

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