v0.21

📖 Translations and 💾 S3, Azure support

In this latest release, french translations arrive for the application !
French will be used by default if it is your browser's default language, otherwise you can select your language by clicking on the "Marble" icon at the top left corner of the app. Please let us know if some translations are misleading or unclear.

Other than this, this weeks release includes some security and performance improvements, and the option to use a document storage backend other than GCP cloud storage for file storing in the case manager and for batch CSV uploads.

It is easy to set up, and you will find an explanation in the .env.example file on how to set environment variables to select you bucket provider of choice.

⚠️ Warning ⚠️

This release is a breaking release from the point of view of required environment variables, as the following variables have been renamed:

• GCS_INGESTION_BUCKET => INGESTION_BUCKET_URL
• GCS_CASE_MANAGER_BUCKET => CASE_MANAGER_BUCKET_URL

If you were already using a GCS storage backend, you now also need to inject a service account json key: see explanation in the .env.example file. Automatic credentials discovery will no longer work, because it is not compatible (at least, not convenient to make compatible) with URL signing for the case manager file storage.

The FAKE_GCS and FAKE_S3 environment variables have also been deprecated.

Blocking reviews

New feature : soft block & hard block

When managing transaction monitoring, you might want to set up two different type of checks :

• Post transaction checks, or soft block, where an analyst review the event after it was processed. Useful for low risk AML, it's a good way to optimise your resources
• Pre transaction checks, or hard block, where your system stops the transaction until an analyst validates or cancels it. Perfect for some type of fraud and high risk AML

With this release, you can now set your scenario output to enforce a pre transaction review.
In this case, the decision is put on hold until an analyst checks it, the provides you with a webhook to cancel or release the underlying event in your system.

To deploy on your Marble setup, follow the guide

Rule snoozing & case manager design

We've delivered another major release with the following improvements :

Rule snoozing : One of your rule keeps matching a user and you can't circumvent it by updating the scenario? you can now safely add a temporary whitelisting directly within Marble. When an alerts needs matching a pivot value and a specific rule is displayed in the case manager, you now have the option to temporarily deactivate the rule only for this pivot (account, user...), for a predetermined duration (max 1 year) and keep track of this decision.
Complete documentation available here

Another major update for this release : we delivered a new interface for the case manager : clearer, more condensed design, improved flexibility and more complete, it paves the way for the next improvements on the product. Let us know what you think of it !

Other improvements include :

Front :

• fix rule display on decision
• better display of CSV import status

Backend:

• Several fix / improvements on ingestion management
• Fix webhook delivery

Webhooks !

In this release, webhooks are finally joining the Marble offering ! (available under license)

Be notified automatically by Marble when a decision is created, or something happens in a case. More event types will be covered shortly, so let us know of your business needs and how you want to use the feature.
You can refer to our documentation page to learn how to set up your webhooks endpoint and how to consume webhooks.

Also includes some technical book keeping:

fixed a bug where unnecessary duplicate indexes on ingested data were created when publishing certain scenarios
many dependency version upgrades

v0.17

This week, we focused on releasing some preliminary work on not yet released features.
The release also contains various bug fixes and logging and tracing improvements.

v0.16 - handle license keys

In this release, we focused on background work, mostly not visible directly to the end user.

• We made some improvements to API error codes, scenario display
• We now handle license keys for access to premium features on-premise
• We updated multiple dependencies

v0.15 - Scenario page revamp

This week, we improved the scenario page to make it easier to understand and use. We introduced the possibility to define "rule group" identifiers on rules, to better order and search them.

We also fixed some bugs (among others, allowing files uploads in the case manager that were wrongly refused and an error that could happen while editing tags and posting a comment on a case).

Finally, we have been working on some data enrichment features on IP addresses, in private preview but which we hope to release soon 👀

v0.14 - Documentation

In this release, we mostly focused on improving and expanding our functional and technical documentation, on https://docs.checkmarble.com and with links in the product where relevant.

If you have not started using Marble for real yet, you can get started with our basic tutorial, or you can deep dive into one of the following sections to explore in detail how to setup your data, model, your first scenario, etc.
We hope it helps your integrate and use Marble, please let us know if you have questions that are not covered by it!

Also includes some minor improvements to ordering and searching of inboxes, scenarios etc in the application, as well as some minor bug fixes.

V0.13 - Pivot values and workflows

This new release allows you to fully leverage the Pivot added recently, by introducing the core bricks to build workflows

• New workflow tab added
• Create scenario by scenario workflows, based on decision outcomes
• Automatically route decisions to a specific case manager inbox
• Add to an existing case with the same pivot or systematically create a new case.

v0.12 - Pivot

v0.12 is a major release, providing the foundations of a key new feature : pivot.

You can now define a pivot in your datamodel. The pivot will allow you to group decisions (and in the near future, other features) by identical pivot to get global view on related alerts. For ex, you can set the user ID as a pivot => all future decisions can then be grouped by user ID, providing a bird eye view on the risk associated with him/her.

Backend :

• Feat : Creation of the pivot and storage of the pivot for each decision

Frontend :

• Feat : Create a pivot in the data model page
• Feat : Group decisions by pivot
• Feat : filter rules within a scenario
• Feat : Explore data model with a new view (available in "your data" tab)
• Fix : dropdown when selecting the field for a date