Glossary

Brute-force attack

brute forcing

Definition

A brute-force attack repeatedly tries possible passwords or other secret values in an attempt to find one that works.

Attempts may target a live service or a stolen password database. Controls that slow online attempts do not protect stolen data in the same way.

A customer may include “Brute-force attack” in a supplier security questionnaire or spreadsheet. They want to understand whether this topic affects the service you provide and what safeguards or evidence support your answer.

A brute-force attack repeatedly tests possible values to find a secret, commonly a password. The attacker relies on many attempts rather than already knowing the correct value. They may try every combination within a range or begin with likely choices.

There is a useful distinction between online and offline attacks. Online attempts go through a service's sign-in process, where controls can slow or block them. Offline attempts work against stolen password data on the attacker's own systems, beyond the service's sign-in rate limits.

Hypothetical example: a small company's remote-access service receives repeated failed sign-ins against one administrator account. A rate limit reduces the attempts, while the IT provider checks whether any succeeded. The same limit would not stop an attacker testing a stolen password database elsewhere.

Use unique passwords and MFA, and apply rate limits to online sign-ins. These controls do not limit an attacker testing stolen password data offline, and aggressive lockouts can disrupt legitimate staff. Repeated failures are a signal to investigate, not proof that an account was taken over.

Sources: MITRE password guessing; MITRE brute force overview.