πŸ””New feature alert! Enterprise SSO is now available for Google Workspace, Okta Workforce, Ping Federate, OpenID Connect, SAML, and Microsoft Azure Active Directory (now Microsoft Entra ID), and Active Directory Federation Services (ADFS)! Learn more here.

πŸ’œ We're always looking to improve your experience.

When you sign up for Verosint, you can explore the Verosint Demo workspace. We added example use cases of suspicious activity and fraud to that workspace to demonstrate how you can you use Verosint to discover and prevent fraud.

Credential Stuffing Attack

A single IP successfully logging into multiple accounts (aka Credential Stuffing Attack)

A single IP successfully logging into multiple accounts (aka Credential Stuffing Attack)

Fraud "Ring"

A single IP accessing multiple accounts (e.g., bot network)

A single IP accessing multiple accounts (e.g., bot network)

Multiple Accounts

A Print with Multiple Accounts

A Print with Multiple Accounts

Account Sharing

An Account using multiple IPs and Prints (aka Account Sharing)

An Account using multiple IPs and Prints (aka Account Sharing)

πŸ”¨ We want to provide the best experience, so we're constantly fixing up the Verosint application.

  1. A SignalPrint is the unique identifier generated for a device based on IP & User Agent. In doing research to make Verosint signals more precise, we noticed and fixed a bug in which users signing up for multiple accounts (different emails) with the same IP and User Agent were generating separate Prints. Bug squashed! πŸ›
  2. πŸ“Ά We are always working to improve the quality of the Verosint signals so they are precise and enable real-time decision making. In doing so, we fixed a bug when searching for valid MX records for an email: if the search timed out, the signal would show invalidMXrecords. Not anymore! Bug squashed! 🐜

πŸ””New feature alert! We've made it easier for you to spot credential stuffing attacks.

  1. Spot credential stuffing attacks! When users attempt to access your platform by inputting a username and password that does not exist, you will see a 🚫 Login Failed attempt with no Account ID in Explorer.
The last two rows of this Events table shows :no-entry-sign: Login Failed attempts with no Account ID, signs of a potential credential stuffing attack

The last two rows of this Events table shows 🚫 Login Failed attempts with no Account ID, signs of a potential credential stuffing attack

⚠️ Note that if you open up the Events side panel and then try to see the Email in the SignalPrint graph, it will not display because there is no Account ID associated.

  1. Perhaps you want to learn more about an account while looking at Events in Explorer. Click on the Account cell in the Events table and see the Account side panel for more details.
Access the Account side panel from the Events table

Access the Account side panel from the Events table

πŸ’œ We're always looking to improve your experience.

  1. If you need more details on an event that occurred in your system, we added the raw event data at the bottom of the Events side panel.

πŸ”¨ We want to provide the best experience, so we're constantly fixing up the Verosint application.

  1. We did some tuning 🎻 of the Verosint AI that produces your AI insights. For example, it very briefly cited a Verosint risk signal that does not exist. πŸ˜…
  2. You can use keyboard shortcuts to create search filters in Explorer. We fixed a keyboard shortcut bug in which previously, you couldn't select values from the dropdown with the spacebar. Fixed! 🌟

πŸ”” New feature alert! You can now add signals (of type = string) to a list! In addition to listing out a specific group of users, this feature allows you to group users by a specific criteria (for example, ip.privacyProvider = NordVPN would impact any user whose IP is on NordVPN).

πŸ”” You can also add Payment Hashes to a list. πŸ’³ This if useful for say, putting payment methods on a "Banned Accounts" list if you see multiple accounts opened with the same payment information.


πŸ’œ We're always looking to improve your experience.

  1. When you sign up for Verosint, you can see how Verosint discovers and prevents fraud by exploring the Verosint Demo workspace. We added example payment events to that workspace to demonstrate how you can you use payments data to discover a multiple accounts problem.
    For example, you may have two accounts that seem unrelated until you realize they signed up with the same credit card.πŸ‘€
Payment Hash shows a multiple accounts problem

Payment Hash shows a multiple accounts problem

  1. ✨ There were some AI Insights cards where the title overflowed off the card. Womp womp. UI magic has been applied - and this is fixed!

πŸ””New feature alert! Verosint has added recommendations to your AI Insights! Our recommendations outline the next step you can take to act on an insight and prevent fraud on your platform.

Based on the bot activity detected in the workspace, Verosint recommends creating rules using our BOT signals

Based on the bot activity detected in the workspace, Verosint recommends creating rules using our BOT signals

This feature is the precursor to Recommended Actions: with your permission and one click of a button, Verosint will execute a preventative action for you (e.g., add to a list, create a rule, etc.).

πŸ””New feature alert! We're celebrating Valentine's Day with a feature that shows how much we love stopping account fraud. Now you can trust but verify your AI insights by seeing the supporting data in Explorer!

β™₯️ Happy Valentine's Day! β™₯️

πŸ””New feature alert! Verosint now supports Payment Hashes and added 8 new event types related to payments, so that you can track your users and their payment activity on your platform.

Event Type NameDescription
PAYMENT_ADDED_SUCCESSA payment method was added to an account successfully
PAYMENT_ADDED_FAILEDAn attempt to add a payment method to an account failed
PAYMENT_REMOVED_SUCCESSA payment method was successfully removed from an account
PAYMENT_REMOVED_FAILEDAn attempt to remove a payment method from an account failed
PAYMENT_SUCCESSA payment from an account was successfully processed
PAYMENT_FAILEDA payment from an account was attempted, but failed to be processed
CHANGE_PAYMENT_SUCCESSA payment method was successfully changed on an account
CHANGE_PAYMENT_FAILEDAn attempt to change a payment method on an account failed

πŸ’‘Pro Tip: Sending Verosint payment data will enable you to discover if users are creating multiple accounts with the same payment hash. You can see this in Explorer or in the SignalPrint Graph.

Suspicious Activity: The same Payment Hash (green circle) is connected to  
3 separate Accounts (navy circle)

Suspicious Activity: The same Payment Hash (green circle) is connected to
3 separate Accounts (navy circle)

You can also see payment activity and search for specific Payment Hashes in Explorer.

Payment activity in Explorer

Payment activity in Explorer

Also, February 13th: Happy Galentine's Day!

πŸ”” New feature alert! Verosint's AI Insights shows you where there might be fraud on your platform by pointing out unusual activity and workspace trends.

The process to determine if suspicious activity on your platform is actually fraud is like looking for a needle in a haystack. With AI Insights, Verosint highlights workspace trends and unusual activity -- so you don't have to look for it.

Verosint's AI Insights looks across your user activity and points out potential fraud, so you don't have to go digging for it

Verosint's AI Insights looks across your user activity and points out potential fraud, so you don't have to go digging for it