This isn't completely true, but it is the current standard.
A website can detect and block many user/password attempts from the same IP and block IPs that are suspicious.
Websites can detect elivated login fails across many IPs are react accordingly (It may be reasonable to block all logins for a time if they detect an attack like this)
I'm sure there are other strategies, I don't know how often they are actually employed, but I wish companies would start taking this sort of attack more seriously (even if it's not at all hacking)
CGNAT would throw a wrench in that when you have thousands of users using mobile data and they appear to be coming from the same ip.
You look for trends, not raw numbers. If an ip increase 500%in 10 minutes... throttle it a bit... insert wait times. If it's trust worthy then allow new value to become normal... otherwise keep the ip throttled.
Nooooo, people keep telling me IPv6 will be insecure because of no longer having NAT.
Mostly people who don't know what a subnet is, but people.
It may be reasonable to block all logins for a time if they detect an attack like this
That would be a P1 incident and probably violate SLAs depending on the duration.
Inserting a literally meaningless delay like 5 seconds is sufficient to make your service virtually impenetrable to mass bruteforce/stuffing attacks. Credential stuffing become untenable when your trying to stuff 1million creds with a 5 second cooldown. Most normal users who would hit it would just think their wifi or cell service hicupped.
This isn't completely true, but it is the current standard.
A website can detect and block many user/password attempts from the same IP and block IPs that are suspicious.
Websites can detect elivated login fails across many IPs are react accordingly (It may be reasonable to block all logins for a time if they detect an attack like this)
I'm sure there are other strategies, I don't know how often they are actually employed, but I wish companies would start taking this sort of attack more seriously (even if it's not at all hacking)
CGNAT would throw a wrench in that when you have thousands of users using mobile data and they appear to be coming from the same ip.
You look for trends, not raw numbers. If an ip increase 500%in 10 minutes... throttle it a bit... insert wait times. If it's trust worthy then allow new value to become normal... otherwise keep the ip throttled.
Nooooo, people keep telling me IPv6 will be insecure because of no longer having NAT.
Mostly people who don't know what a subnet is, but people.
That would be a P1 incident and probably violate SLAs depending on the duration.
Inserting a literally meaningless delay like 5 seconds is sufficient to make your service virtually impenetrable to mass bruteforce/stuffing attacks. Credential stuffing become untenable when your trying to stuff 1million creds with a 5 second cooldown. Most normal users who would hit it would just think their wifi or cell service hicupped.