An organization notices that a shared account used by multiple automated processes is being locked frequently. Logs show repeated login attempts with an outdated password from an unidentified location. Which action is the BEST way to address this situation?
Force a password reset on every user account in the environment
Re-enable the account and modify multi-factor configurations
Lower the lockout threshold to quickly identify suspicious activity
Update all services to use the current password, including scripts and jobs
It is important to eliminate attempts from automated jobs or scripts that still use invalid credentials. Updating the shared account credentials in the relevant applications removes the root cause, because those processes will no longer attempt old passwords. Lowering the lockout threshold might attract more disruptions by increasing the chance of lockouts. Forcing password changes on a broad scale diverts resources and is not targeted to the failing scripts. Re-enabling the account or adjusting multi-factor settings does not address the out-of-date password attempts.
Ask Bash
Bash is our AI bot, trained to help you pass your exam. AI Generated Content may display inaccurate information, always double-check anything important.
Why is updating the credentials for automated processes the best solution for account lockouts?
Open an interactive chat with Bash
What risks are associated with lowering the lockout threshold for accounts?
Open an interactive chat with Bash
How does forcing password resets for all users fail to address the issue of automated account lockouts?