Shared user accounts must not be permitted on the system.

From Windows 8/8.1 Security Technical Implementation Guide

Part of Shared User Accounts

Associated with: CCI-000764

SV-48015r2_rule Shared user accounts must not be permitted on the system.

Vulnerability discussion

Shared accounts (accounts where two or more people log on with the same user identification) do not provide adequate identification and authentication. There is no way to provide for non-repudiation or individual accountability for system access and resource usage. Documentation must include a list of personnel that have access to each shared account.

Check content

Determine if any shared accounts exist. If no shared accounts exist, this is NA. Any shared account must be documented with the ISSO. Documentation must include the reason for the account, who has access to this account, and how the risk of using a shared account (which provides no individual identification and accountability) is mitigated. If such documentation does not exist, or is not current, this is a finding. Note: As an example, a shared account may be permitted for a help desk or a site security personnel machine, if that machine is standalone and has no access to the network.

Fix text

Create or update shared accounts documentation that minimally contains the name of the shared account(s), the system(s) on which the accounts exist, and the individuals who have access to the accounts. Remove any shared accounts that do not meet the requirements.

Pro Tips

Lavender hyperlinks in small type off to the right (of CSS class id, if you view the page source) point to globally unique URIs for each document and item. Copy the link location and paste anywhere you need to talk unambiguously about these things.

You can obtain data about documents and items in other formats. Simply provide an HTTP header Accept: text/turtle or Accept: application/rdf+xml.

Powered by sagemincer