Release Notes 1.20.000
Happy Holidays from the Fraud.net team!!
We've squashed a few bugs and made a few tweaks.
Also just in time for the holidays we've made optimized the performance of the portal so that you walk away with confidence that all is well (with the portal, I mean, we can't help with any gift ideas)
Your feedback helps to keep us going, please let us know about any problems or issues you may have by submitting them here to our support site.
Release Notes 1.19.188
This update includes fixes and performance improvements.
Your feedback helps to keep us going, please let us know about any problems or issues you may have by submitting them here to our support site.
Security Advisory
December 13th, 2021
Attention Fraud.net Users:
Fraud.net is aware of a high severity vulnerability (CVE-2021-44228) impacting multiple versions of the Apache Log4j 2 631 utility which was disclosed publicly via the project’s GitHub 1.1k on December 9, 2021. This security advisory summarizes any potential impacts to Fraud.net products and related steps towards mitigation to address the issue, if any.
Day Zero Vulnerability: Apache Log4j 2 versions 2.0 to 2.14.1.
Fraud.net impact: Only one software impacted i.e. Elasticsearch. No other impacts exist across the Fraud.net asset pool.
Impact assessment: No exploitable impact for Fraud.net products and services found as per security advisory made by impacted vendor, Elasticsearch. The product versions in use at Fraud.net are not at risk from this exploit due to the inherent mitigation method, Java Security Manager, in use by impacted software.
Fraud.net security and operations teams continue to actively monitor threats and vulnerabilities across all its products and services and customers will be notified of any impacts as it is learnt and becomes necessary for further escalations and notifications.
Should there be any further questions, please reach out to security@fraud.net, or our customer help line at +1-866-971-2030.
Source: Official response from impacted vendor: https://discuss.elastic.co/t/apache-log4j2-remote-code-execution-rce-vulnerability-cve-2021-44228-esa-2021-31/291476
Release Notes 1.19.170
This week we made some tweaks to existing rules including how monitor rules are displayed on the transaction details page. As well as adjustments to velocity rules that include the direction of funds for more accurate results.
For our Marketplace clients, you can now write rules around how your customers are interacting with specific counterparties or sellers.
Stay tuned next week as we will be releasing our Claim AI product, which helps tackle health insurance fraud.
Your feedback helps to keep us going, please let us know about any problems or issues you may have by submitting them here to our support site.
Release 1.19.160
We’ve optimized the portal for buttery smooth performance and squashed bugs in the process.
Your feedback helps keeps us going, please let us know about any problems or issues you may have and stay tuned for updates and enhancements to come.
As always if you have any feedback from please submit them here to our support site.
Release 1.9.157
We’ve tinkered with the internal workings and polished some rough edges (like bug fixes).
This includes some tweaks to the advanced settings in rules and optimizing the case management portal for a better experience.
We are regularly making updates to our service to make it even better.
As always if you have any feedback from please submit them here to our support site.
Release 1.9.101: Manage Teams, SLAs, Holidays, and Data Points
Whether you're managing hundreds of investigators in different countries and timezones or have various departments or brands utilizing Fraud.net, organization and efficiency are paramount to your success. For example, do your Swedish-based investigators need to see a German-based credit score? Should the SLA for the number of hours needed to review a transaction before shipment vary by the time of day it was received?
Fraud.net has added a new Admin section called Management. Here you can manage each team by the data points they can view, expiration settings based on the days of the week and hours worked in each time zone and holidays. These features give the admin the controls to effectively manage the nuances of each department or team.
Learn more about it here!
Release 1.9.97: New Rules for the Counterparty and MCC
Fraud.net has released a few new rules for to our Banking Case Management Portal. We received feedback that our users wanted to dig deeper into the relationship between their customers and the counterparties they transact with. As a result, we are now keeping track of your customers' counts and sums with each counterparty at a variety of levels.
Also, we have added the "Advanced Settings" feature to now includes few more fields and is enabled for MCC-related rules.
Furthermore, you can now see if your customer's name is contained in the payment reference or counterparty. This may be a sign of money laundering.
Read below for all the specifics!
Count with Counterparty
Limit for number of transactions for a Customer, Account or Payment ID with that specific Counterparty
- Count of transactions for [Dropdown with Customer ID/Account ID/Payment ID] with Counterparty [seller_id] is gte/lte x in a time period
Limit for value of transactions for a Customer, Account or Payment ID with that specific Counterparty
- Sum of transactions for [Dropdown with Customer ID/Account ID/Payment ID] with Counterparty [seller_id] is gte/lte x in a time period
Counterparty Contains Customer Name
- Counterparty Name [seller_name] is/is not/contains/starts with/ends Customer or Company Name [customer.first_name and customer.last_name OR customer.company]
Payment Reference Contains Customer or Company Name
- Payment Reference [transaction.reference] is/is not/contains/starts with/ends [customer.first_name and customer.last_name OR customer.company]
Velocity Advanced Settings Updates
- The Advanced Settings now includes the following filters: Card Present Flag (payment.card_present) and Cardholder Auth (payment.ch_auth).
- Advanced Settings has now been enabled for Count/Sum of MCC over time velocity rules
Version 1.9.95 Release Notes
We are excited to share with you the details of Fraud.net’s January 2021 Release Notes. We added advanced settings to rules, integrated with ComplyAdvantage, created an easier way to capture device information, and enabled new fields to allow and deny lists. Read below for more information.
Rule Enhancements
Advanced Velocity Rules: We’ve added advanced functionality to our most utilized banking industry velocity rules (including card transaction counts, card sums, account sums, and account counts). Select the Advanced Settings button and choose the Direction of Funds, Statuses, Payment Statuses, or Payment Methods to include or exclude in the rule logic. For example, exclude transactions with the payment status of ‘declined’ from counting towards the overall velocity sum.
Introducing ComplyAdvantage
Capture Device Fingerprints
Allow or Deny Banking Specific Data Points
------
Fraud.net's release schedule is every Tuesday and Thursday at 5pm EST. Generally, we release just once per week, but keep in mind, there are only two possible times each week that Fraud.net will release. You will continue to be notified of these releases with accompanying notes.
Every release is meant to make for a better user experience. We look forward to hearing your input.