• We cut down the API response time by nearly half - so your calls to the Verosint Risk API are nearly twice as fast! ⚡
• Improvements to your API Usage page:
  • Your available API calls reset each month based on the date you signed up for an account, not per calendar month.
  • We also added a data refresh field, which tells you how often the OSINT data that is aggregated to score your users is updated. For Free plan customers, this defaults to monthly. It's more frequenty for paid plans.
• When you set all signals to 100 in the policy tuner, the category automatically sets to 100.
• Bug fix: We added error handling so that if you try to edit a policy and it doesn't load, you're not left in the dark. 🐛

• We've now added a Settings page in the Account menu so you can easily edit your account information.
• To adjust your risk score to best suit your business needs, you can now customize the numerical score cut-offs for High, Medium, and Low Risk! You can find these on your Settings page.
• Don't like the breakdown of High, Medium, and Low Risk users when testing out policies in Evaluator? Now you can easily adjust the score cut-offs in the Policy Results chart, making it easy to see how many users should be High, Medium, or Low Risk.
• We moved the Policy Tuner in the Signal Playground from the right to the left side of the page. UI testing revealed that when the Policy Tuner was on the right, some people interpreted it as the outcome of the risk score results - not the input to getting a risk score.
• When you go to the Policy Evaluator, you now land on Multiple User mode first (instead of Single User mode). This brings you one step closer to testing out policies against multiple users so that you can choose the right one for your business.
• Evaluator: We organized the CSV download of risk results so that signals flagged for a user are separated into individual columns, making it easier for you to create graphs and charts that explain why your users are risky!

• We made it super fast to sign up for Verosint: 1) Set your email and password, and 2) complete your profile. You're in! ⚡
• Bug Fix: Previously it was possible to type in a value > 100 when tuning a signal. As my 2-year old likes to say, "That's silly!" Fixed! 🐛

• Our sign-up and login pages have a new look and feel! 🎉
• Bug Fix: If you set your signals to the same weight, they should equally impact the risk score. But some signals check more data sources than others, impacting the risk score more than signals checking fewer data sources. We updated the scoring algorithm to account for this. 🐛
• Bug Fix: Previously if I tuned a policy and scored users again, the delta (aka change in score) remained zero. This is fixed so now you can determine if delta changed because users became more (or less) risky, or because of a policy change. 🐛

• Updated the policy tuner to automatically set all signals in a category to zero when you set that category to zero
• Added the ability to delete policies that you don’t need anymore
• Now when calculating scores, only data breaches that have occurred within the last 2 years will be considered
• app.verosint.com/sign-up will now take you directly to the sign up flow
• New policy results chart – now with a curve to better highlight where most of your scores are when comparing policies
• Added an empty state design when you don’t have any policies on your policies page
• Updated the descriptions of the starter policies (Strict, Moderate, and Permissive) based on customer feedback so you know what scores to expect when using them
• The delta value will no longer show up on the score response in Signal Playground
• Am I Risky? now shows better explanations of what caused each scenario to happen
• Am I Risky? now has prefilled emails and passwords for the example flows

Launched Am I Risky? app to give examples of possible UI workflows that could be enabled by 443ID

Launched new signal processor infrastructure for fetching data from signal providers for risk scoring.

Launched Signal Playground to allow customers to explore our available signals and tuning while immediately seeing the impact to their score results

API Usage page now automatically updates to show your current remaining calls.

• Get fewer Unknowns when getting risk scores on a single user in Evaluator.
• If customers get Unknown, they’ll see an improved message: “Still gathering enough information. Please try again.”
• Bug Fix: Disabled the policy selector in Evaluator after you hit “Get Results”, preventing half-baked info from showing up in Policy Results 🐛
• Bug Fix: Identifier headers in the csv template matches the parameters for the API request: email, ip, and phone-number, promoting consistency and cognitive recognition of our identifiers 🐛
• Bug Fix: The designed input validation errors show up in single user mode in Evaluator, minimizing the chances of a frustrated customer not knowing why their identifier is invalid 🐛
• Bug Fix: Some IP addresses were getting processed in Evaluator, but not showing up in the csv download of the results. Squashed! 🐛