Best practice for layering Attack Protection against credential stuffing on a public login page?

Hi all,

I’m reviewing the login flow for a web app using Universal Login and
want to harden it against credential stuffing and bot traffic.

What we have enabled so far:

  • Brute-force protection
  • Breached password detection
  • Suspicious IP throttling

What I’m unsure about:

  1. Is Bot Detection (CAPTCHA) worth enabling for all logins, or only
    after a risk threshold is hit?
  2. How are others tuning thresholds to avoid locking out legitimate
    users on shared IPs (offices, mobile carriers)?
  3. Are you using Actions to add custom risk checks on top of the
    built-in protections? If so, what signals have worked well?

Would love to hear what has worked in production. Thanks!

The Cyber Seal