
A brute-force attack attempts to access an account by repeatedly guessing its password. Automated attempts can test many possibilities, making short or predictable passwords easier to guess.
Guessing is not the only way in.
Related attacks may try a common password against many accounts, or reuse login details exposed somewhere else. Reusing a password means trouble at one service can create a problem for another account.
For a business, the lesson is broader than asking staff to choose a complicated password. Account settings, authentication, monitoring, and recovery procedures all matter. No single measure prevents every kind of account compromise.
Make your own accounts harder to access.
Use a long, unique password for each account. A reputable password manager can help generate and keep track of them. Turn on two-factor authentication where available; an authenticator app or security key provides stronger options than some alternatives. Keep recovery information current and protect recovery codes.
Know what the provider controls.
Services can limit repeated attempts, introduce delays, and use additional verification. These measures need care: an overly simple lockout policy can also prevent legitimate people from accessing their accounts. For business systems, discuss the configuration with the person responsible for them.
Do not approve an unexpected login.
A verification prompt you did not initiate deserves attention. Go to the service through a known address, review available account activity, and follow its recovery instructions if something appears wrong. Do not share a code with someone who contacts you unexpectedly.
If your business needs help reviewing its approach, talk to us about business IT support.
