Skip to main content
Add browser, device and automation evidence to your existing authentication controls.

​
Where to integrate

Start identification when the login form is used and verify it before issuing the session. Start with the SDK for your stack and retrieve the result on your backend.

​
What to read

Combine the score and automation flags with your own failed-login and account counters. Use the current Risk Score and flags, plus High-Risk Events where relevant. Treat a missing or incomplete result as an explicit unverified state.

​
How to act

Slow repeated attempts and require verification for suspicious successful logins. Keep password validation and authentication rate limits active even when identification is unavailable.

​
Build the example

The runnable tutorial includes the starting app, the completed integration, and steps to test its behavior. Its application policy is stated separately from ShieldLabs detection. For implementation details, see Acting on results and Identification flow. Verify the expected domain, result age and account association, and consume protected actions atomically.