Limit multiple invalid login attempts by locking out the user ID after 6 attempts |
The purpose of this section of PCI is to prevent password guessing attacks via continuous manual or automated password cracking sequences. This Action1 query verifies that required account lockout settings are configured on each endpoint for both local and domain accounts.
Sign-up for Action1 Free Edition to receive real-time alerts and view instant data from your endpoints, such as alert on 8.1.6: Account Lockouts created, deleted or modified or run live or scheduled queries with the ability to export to CSV or Excel. 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 in seconds and you can query your entire network in plain English.
Endpoint configuration management in the Cloud
Manage endpoint configuration using plain English from the Cloud. Such as type 'Windows services' or 'reboot computer'.
Get results instantly from live systems and run automated actions.
Related Alerts and Reports:
8.1.1: Assign Unique User IDs
All users must be assigned a unique ID before granting them access to cardholder data
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.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
Find more information on 8.1.6: Account Lockouts at Microsoft TechNet.