Solutions
Real use cases, real signals
Each use case below references actual Sentriq capabilities — see the Product page for full detail on what each signal is and isn’t.
Account Takeover
When a login comes from an unrecognized device, or from an IP already implicated in credential abuse against other accounts, that context belongs in the decision — not just a raw "allow" flag.
Sentriq surfaces the mechanism, not a promised outcome: a new-device signal, a credential-abuse pattern, and a policy-engine decision your team configures the response to.
Sentriq signals that apply
- Device resolution — new vs. known device (Device Intelligence)
- Credential-abuse velocity signals — brute force, account attack (Network Intelligence)
- Risk engine decision — allow / monitor / challenge / block (Risk Engine)
Credential Abuse
Credential stuffing and brute-force attacks show up as request-velocity patterns before they show up as a successful takeover: one IP hitting many accounts, or one account being hit from many sources.
Sentriq’s velocity engine is built to distinguish that from ordinary shared-NAT traffic, so a login attempt event carries pattern context your policy can act on.
Sentriq signals that apply
- Brute-force and credential-stuffing pattern detection (Network Intelligence)
- IP-based velocity and account-attack signals (Network Intelligence)
- Risk engine decision on the login event (Risk Engine)
Multi-Account Abuse
Promo abuse, ban evasion, and fake-account rings often share one thing: the same device or IP touching an unusual number of distinct accounts.
Sentriq tracks that relationship directly — device-to-account and IP-to-account history — and turns it into a named signal your risk policy can weigh.
Sentriq signals that apply
- Multi-account-per-device detection (Account Security)
- Multi-account-per-IP detection, bounded 24-hour window (Network Intelligence)
- Risk engine decision (Risk Engine)
Bot Protection
Automated signups, scraping, and scripted login attempts often carry tell-tale coarse signals — a webdriver flag, a headless-browser pattern, an inconsistent viewport.
Sentriq scores those three heuristics into a basic automation confidence score you can feed into your own policy — it’s a starting signal, not a dedicated bot-detection suite.
Sentriq signals that apply
- Automation confidence score, 0-100 (Bot & Automation)
- Automation classification band (Bot & Automation)
- Risk engine incorporation of the automation signal (Risk Engine)
Fraud Prevention
Most fraud decisions need more than one signal to be defensible — a new device alone isn’t suspicious, but a new device plus a credential-abuse pattern plus an automation flag is worth a closer look.
The risk engine is where Sentriq’s signals come together: a deterministic, weighted score and a policy-engine decision your team can explain after the fact.
Sentriq signals that apply
- All named risk signals across device, network, account, and automation categories
- Deterministic weighted-sum scoring (Risk Engine)
- Configurable allow / monitor / challenge / block thresholds (Risk Engine)
Trusted Devices
Some devices — an admin’s laptop, a known internal test account’s browser — should carry less friction than a first-time device. Sentriq lets you mark a device trusted from the dashboard, and that status is audited.
Trust is device-wide, not account-scoped: it reflects a control-plane decision your team made, not something Sentriq inferred automatically.
Sentriq signals that apply
- Device trust flag, control-plane-only, audited (Device Intelligence)
- Trusted-device signal feeding into the risk score (Risk Engine)