All users must be assigned a unique ID before granting them access to cardholder data |
This Action1 query verifies that generic “admin” credentials are not used to login to user workstations and makes sure that all users logon using their own unique domain credentials. It looks at all local user profiles (associated with both domain and local users) as well as all non-disabled local user accounts. The output of this query mark each endpoint as either compliant or non-compliant with section 8.1.1 with an explanation of what needs to be changed (such as removal of user profile or disabling of all local users).
Sign-up for Action1 Free Edition to streamline compliance efforts for your network of endpoints. Such as you can simplify assessments of 8.1.1: Assign Unique User IDs for your internal or external auditors, create instant or regular compliance reports that prove your compliance while reducing the costs. Action1 Endpoint Security Platform is entirely SaaS, with online web interface (no management tools to install) and it has zero cost for basic functionality. Running in the Cloud, Action1 discovers all of your endpoints within seconds and allows you to pass compliance audits and maintain continuous compliance with ease.
Respond to Threatsin Real-Time
Ask questions in plain English such as "list of installed software" or "all running processes".
Get answers instantly from live systems or subscribe to real-time alerts.
Related Alerts and Reports:
8.1.2: Management of User IDs
Control addition, deletion, and modification of user ID, credentials and other identifier objects
8.1.3: Revoke Access for Terminated Employees
Ensure that any terminated users lose their access to corporate systems
8.1.4: Inactive User Accounts
Remove or disable user accounts that have been inactive for over 90 days
8.1.5: Third Party Accounts
Enable third-party vendor accounts only when needed and monitor when in use
8.1.6: Account Lockouts
Limit multiple invalid login attempts by locking out the user ID after 6 attempts
8.1.7: Account Lockout Duration
The lockout duration must be at least 30 minutes or until re-enabled by administrator
8.1.8: Idle Sessions
Require user re-authentication after a session has been idle for more than 15 minutes
Keywords: All users must be assigned a unique ID before granting them access to cardholder data,Action1 8.1.1: Assign Unique User IDs.
Find more information on 8.1.1: Assign Unique User IDs at Microsoft TechNet.