Castle signals are a great way to spot and filter out specific behaviors that could be related to the fraud you’re looking to discover. Today, we’re launching a new signal that indicates that the data collected by the Castle client side agents has been reused. When this happens, it could be an indication that someone is trying to spoof device data or run a script.
Up until now, Castle has provided a general Risk Score designed to make it easy to find and stop all sorts of fraud or abuse. Under the hood, this risk score is actually the combination of several independent risk factors. One of these risk factors is the likelihood that the request is initiated from a bot or script.
This week, we're happy to announce support for Single sign-on (SSO) for the Castle Dashboard, available for all customers on the Enterprise plan. We're offering SSO via OpenID connect, which means that you can use any compatible service like e.g. Okta.
One of the more powerful features of Castle is the ability to configure policies that allow you to control the inline action returned in the API response for the risk and filter endpoints. These actions can then be used to kick off workflows such as e.g. triggering a CAPTCHA at signup or prompting for two factor verification at login. All in real time.
With Castle's APIs you've been able to pass user profile data, such as email and prone number, via the user object (See reference for more details) for quite some time now. These traits can provide great help when chasing down fraudsters, especially in combination with Policies where you can use them to trigger custom workflows, such as additional verification.
Tracking the right data to Castle is crucial to finding fraudsters. By tracking user and/or event details that represent important business aspects, such as amount and account balance in case you're dealing with transactions, you're more likely to be able to spot suspicious behaviors.
The Castle Explore view makes it easy to find fraudulent activity, going from haystack to needle with a few clicks. It is also a great place to start your daily routine for inspecting new activity. In order to make this routine even easier and more streamlined, we've now launched saved searches which allows you to persist the most interesting behaviors that frequently needs to be inspected. Like "Logins from outside the US" or "Transactions by multi accounters".
Back in July last year, we introduced the Explore view in the Castle Dashboard as a way for you to quickly sift through and hone in on fraudulent behavior on a per event level. Today, we're launching a subtle but big improvement to quickly being able to assess the impact of a search result: the ability to see the distinct users matching it. This is particularly helpful when your search generates a lot of activity which can sometimes make it hard to get an overview of which users that are involved.
We're really excited about this one. Part of our mission here at Castle is to make it super easy for anyone to discover and stop fraud, and our goal is to provide unparalleled visibility that allows you to see every step the fraudsters make.
Today, we're releasing the ability to see information about Caste SDK versions in the event data. You're now able to visualize and filter events based on both client and server SDK name and version in the Explore view. Together with the top list chart feature, this provides a great way to monitor adoption of an SDK version upgrade.
