The 443id-cli has been deprecated due to naming changes and is replaced
with verosint. The former repository is no longer maintained and may be removed in the future.

The new tool is available from the Verosint CLI repository.

Users of the 443id-cli migrating to the new tool should note the following
changes:

  • The default configuration file name has changed to .verosint.yaml.
  • The environment variable for holding the API key has changed from
    CLI_APIKEY to VEROSINT_APIKEY.

๐Ÿš€ Big releases this week!

  • Automated Signals bring you closer to automated fraud detection (no humans required ๐Ÿ˜‰). Multiple Accounts, Account Sharing, Impossible Travel, and New Print are automatically generated and applied to account activity in your SignalPrint graph. You can filter on these automated signals too.
  • Tags are labels you can create and apply to your SignalPrint graph.
    • Creating a tag automatically adds it to an account node.
    • Tags only exist when theyโ€™re associated with account nodes. Once the last tag is removed, the tag is deleted from the SignalPrint graph altogether.
  • We've made it super easy to find your API Key so you can quickly get started!
  • The SignalPrint Graph in the UI has been updated and decorated with OSINT risk information! You'll see:
    • Email metadata and risk info (e.g., is this Email a Spam account? Breached in the last year? )
    • IP address location, metadata, and risk info (e.g., is this a Bot? VPN?)
    • Phone number metadata and risk info (e.g., is this phone number a DNO?)
  • You can also filter what you see in your SignalPrint Graph view by selecting signals in the Filter View module. For example, do you want to only see accounts and IP's that are bots? Select "Bot" from the Filter View.
  • Now you can create rules using our SignalPrint(TM) signals! Use these signals to create rules based on your customers' SignalPrint history in the UI
  • Added Account ID as a new field to the SignalPrint API events endpoint. This allows you to assign a unique identifier to each customer account. If none is provided, the Account ID defaults to an email or phone number provided. You can use this field to test out specific rules on an Account ID in the Evaluate tab of a rules set.

We added more rules templates! Check out the IP Geofencing or Duration since an Email was Found in a Breach templates.

Happy new year! We've added new functions that you can use in rules.

  • With Geofencing, you can see if a user is located within N miles of a specific location (e.g., signals.ip.geo.isWithin(latitude,longitude, radius in miles))
  • With Duration, you can write rules based on time using daysSince(timestamp) and yearsSince(timestamp) (e.g., Email has been in more than 3 breaches in the last 180 days --> size(signals.email.breachInfo.breaches.filter(breach, daysSince(breach.date) < 180)) > 3)
  • We launched Rules Templates so you don't have to create a rules set from scratch
  • We updated how rules are applied. Each rule in a rule set will now be applied one after another. And if none of the rules apply, then a default outcome will be applied.
  • We've redesigned the UI for app.443id.com to showcase all of our products.
  • Share your rules with other users! To import rules sets, select the (+) button and choose the "Import" option. To export rules, click the "Export Rules Set" button for the rules set you want to share.
  • See out how your rules will work in the UI! Create your rules, then go to the "Evaluate" tab to apply them to a single user.