Which would be the BEST approach to prevent successful brute forcing of the account?

A mission-critical system has been identified as having an administrative system account with
attributes that prevent locking and change of privileges and name. Which would be the BEST
approach to prevent successful brute forcing of the account?

A mission-critical system has been identified as having an administrative system account with
attributes that prevent locking and change of privileges and name. Which would be the BEST
approach to prevent successful brute forcing of the account?

A.
Prevent the system from being accessed remotely

B.
Create a strong random password

C.
Ask for a vendor patch

D.
Track usage of the account by audit trails

Explanation:

Creating a strong random password reduces the risk of a successful brute force attack by

exponentially increasing the time required. Preventing the system from being accessed remotely is
not always an option in mission-critical systems and still leaves local access risks. Vendor patches
are not always available, tracking usage is a detective control and will not prevent an attack.



Leave a Reply 0

Your email address will not be published. Required fields are marked *