Actions
An action is the user-initiated event you ask Rupt to judge. Every evaluation is bound to exactly one action, and Rupt tunes its checks and risks to the threats most relevant to that flow.
The reserved actions
V3 supports the following reserved actions:
login
A user authenticates to an existing account. Rupt prioritizes the following risks for this action:
Rupt infers those risks from the following checks:
- new fingerprint
- new IP
- impossible travel
- anonymizing network
- concurrent sessions
- device count
- velocity
- shared fingerprint
signup
A new user is created. Rupt prioritizes the following risks for this action:
Rupt infers those risks from the following checks:
access
A page view or app open. Rupt prioritizes the following risks for this action:
Rupt infers those risks from the following checks:
custom actions (coming soon)
A custom action is one that you define. You can use this to protect any user-facing flow that doesn't fit into the reserved actions. Each risk contains checks that are derived from signals. In the dashboard, you can create a custom risk, define the checks and signals that contribute to it as well as the weight of each check based on the outcome as well as the level of severity based on the score.
Choosing the right action
Pick the action that matches the user-facing flow you are protecting. The underlying signals and checks are shared across all actions; the difference is which combinations Rupt weights most heavily and which risks get scored.
V3 grew out of the v2 account-sharing focus (access) but now covers more of the fraud surface: ATO via login, fake accounts via signup, and sharing via access. There will be more actions in the future.
- Need help? Contact support.
- Want to see Rupt in action? Request a demo.
- Questions? Talk to sales.
- Check out our changelog.
- Check our status page.
- LLM? Read llms.txt.