Device Fingerprinting Protected Auth

Device Fingerprinting Protected Auth is a ready-made solution that enables you to focus solely on building auth flows with our frontend SDKs, while harnessing all the protective advantages of DFP.

One of the primary use cases for Stytch’s Device Fingerprinting product is to detect and stop fraud – which often involves the fraudulent traffic attempting to sign up or log in to the application. This often manifests as part of a credential stuffing attack to compromise the accounts of current users or to gain access to protected compute resources. Our Device Fingerprinting product is required to be queried from the customer’s backend to ensure that a bad actor cannot spoof a response.

Meanwhile, Stytch offers frontend SDKs that allow users to build auth without a backend. The SDKs outsource the backend implementation by providing pre-built components to start a login flow and methods that communicate with the Stytch API. These SDKs enable developers to get up and running faster through these pre-built components.

Stytch offers a feature called Device Fingerprinting Protected Auth that seamlessly integrates Device Fingerprinting with our frontend SDKs. When enabled, the SDKs automatically generate a telemetry ID before an API call and include the telemetry ID in the Stytch API request. The Stytch API will verify the fingerprint is a valid user before authenticating the request and handles the backend integration.

In the case of a credential stuffing attack, it would fail because the request doesn’t have a telemetry ID or the Device Fingerprinting product detects illegitimate requests like headless browser automation or a scripting language. The attacker would only see failed authentication attempts with no idea if the request failed due to a failed fingerprint request or an incorrect password.

Device Fingerprinting Protected Auth requires no code changes and is enabled from the Dashboard SDK configuration page under the Bot Protection section. Once enabled, there are two different modes for Device Fingerprinting Protected Auth: Observation mode and Decisioning mode.

The following frontend SDK methods are protected, meaning they will collect fingerprints and (when in Decisioning mode) prevent actions when a fingerprint receives a BLOCK verdict.

• stytch.biometrics.authenticate()
• stytch.cryptoWallets.authenticate()
• stytch.impersonation.authenticate()
• stytch.magicLinks.email.loginOrCreate()
• stytch.magicLinks.email.send()
• stytch.otps.authenticate()
• stytch.otps.email.loginOrCreate()
• stytch.otps.sms.loginOrCreate()
• stytch.otps.sms.send()
• stytch.otps.whatsapp.loginOrCreate()
• stytch.otps.whatsapp.send()
• stytch.passwords.authenticate()
• stytch.passwords.create()
• stytch.passwords.resetByEmail()
• stytch.passwords.resetByEmailStart()
• stytch.passwords.resetByExistingPassword()
• stytch.passwords.resetBySession()
• stytch.totps.authenticate()
• stytch.totps.recover()
• stytch.webauthn.authenticate()

• stytch.impersonation.authenticate()
• stytch.magicLinks.authenticate()
• stytch.magicLinks.discovery.authenticate()
• stytch.magicLinks.email.discovery.send()
• stytch.oauth.authenticate()
• stytch.oauth.discovery.authenticate()
• stytch.otps.email.authenticate()
• stytch.otps.email.discovery.authenticate()
• stytch.otps.email.discovery.send()
• stytch.otps.email.loginOrSignup()
• stytch.otps.sms.authenticate()
• stytch.otps.sms.send()
• stytch.passwords.authenticate()
• stytch.passwords.discovery.authenticate()
• stytch.passwords.discovery.resetByEmail()
• stytch.passwords.discovery.resetByEmailStart()
• stytch.passwords.resetByEmail()
• stytch.passwords.resetByEmailStart()
• stytch.passwords.resetByExistingPassword()
• stytch.passwords.resetBySession()
• stytch.recoveryCodes.recover()
• stytch.recoveryCodes.rotate()
• stytch.sso.authenticate()
• stytch.totp.authenticate()
• stytch.totp.create()

Learn how to set up Device Fingerprinting Protected Auth.