Convenings

alert-icon-red-11.png ATTENTION: This page has been migrated to the Tazama GitHub repository and is now located at: https://github.com/frmscoe/docs/blob/main/Product/04-Tazama-Rules-Life-Cycle.md https://github.com/frmscoe/docs/blob/main/Product/04-Taza

Configuration Arango requires a scrape configuration be added to the prometheus.yml. (https://www.arangodb.com/2020/03/monitoring-arangodb-prometheus-grafana/ https://www.arangodb.com/2020/03/monitoring-arangodb-prometheus-grafana/) - job_name: arangodb s

Setup Analyzer 1. In Lens, connect to the Shell of the ArangoDB pod 2. Type "arangosh" in the shell and hit Enter - this will connect to ArangoSH 3. To connect to the correct DB, type "db.useDatabase("transactionHistory");" 4. Then import analyzers: var a

The primary goal of pseudonymisation is to limit the linkability between a pseudonymised dataset and the holders of the pseudonyms and to thereby protect the identity of the data subjects. This type of protection is typically intended to counter the effor

alert-icon-red-11.png ATTENTION: This page has been migrated to the Tazama GitHub repository and is now located at: https://github.com/frmscoe/docs/blob/main/Product/06-Channel-Aggregation-And-Decisioning-Processor-Cadproc.md https://github.com/frmscoe/

Overview The Actio Financial Crime Risk Management Solution is designed to provide scalable and extensible financial crime risk monitoring and management functionality as a service to connected client systems. Channels can be implemented to allow for: Res

alert-icon-red-11.png ATTENTION: This page has been migrated to the Tazama GitHub repository and is now located at: https://github.com/frmscoe/docs/blob/main/Product/transaction-monitoring-service-api.md https://github.com/frmscoe/docs/blob/main/Product/t

{ "active": true, "cfg": "1.0.0", "messages": [ { "id": "004@1.0.0", "host": "NATS Server", "cfg": "1.0.0", "txTp": "pacs.002.001.12", "channels": [ { "id": "001@1.0.0", "host": "NATS Server", "cfg": "1.0.0", "typologies": [ { "id": "typology-processor@1.

A “banded” rule configuration: { "id": "006@1.0.0", "cfg": "1.0.0", "desc": "Outgoing transfer similarity - amounts", "config": { "parameters": { "maxQueryLimit": 3, "tolerance": 0.1 }, "exitConditions": [ { "subRuleRef": ".x00", "outcome": false, "reason

Building on the example rule configurations provided here: Complete example of a rule processor configuration Typology configuration for a typology with two rules { "desc": "Double-payment to a merchant.", "id": "typology-processor@1.0.0", "cfg": "001@1.0

TL;DR Introduction A transaction monitoring system is a key component of a Proof of Concept - Objectives Deployment Integration Ingress Egress Operation Detection Effectiveness Data requirements Approach Metrics Calibration Feature validation

alert-icon-red-11.png ATTENTION: This page has been migrated to the Tazama GitHub repository and is now located at: https://github.com/frmscoe/docs/blob/main/Product/configuration-management.md https://github.com/frmscoe/docs/blob/main/Product/configurati

alert-icon-red-11.png ATTENTION: This page has been migrated to the Tazama GitHub repository and is now located at: https://github.com/frmscoe/docs/blob/main/Product/07-Creating-And-Maintaining-Processors/04-Create-New-Channel.md https://github.com/frms

alert-icon-red-11.png ATTENTION: This page has been migrated to the Tazama GitHub repository and is now located at: https://github.com/frmscoe/docs/blob/main/Product/07-Creating-And-Maintaining-Processors/02-Create-New-Rule-Processor.md https://github.c

alert-icon-red-11.png ATTENTION: This page has been migrated to the Tazama GitHub repository and is now located at: https://github.com/frmscoe/docs/blob/main/Product/07-Creating-And-Maintaining-Processors/05-Create-New-Transaction.md https://github.com/

alert-icon-red-11.png ATTENTION: This page has been migrated to the Tazama GitHub repository and is now located at: https://github.com/frmscoe/docs/blob/main/Product/07-Creating-And-Maintaining-Processors/03-Create-New-Typology.md https://github.com/frm

alert-icon-red-11.png ATTENTION: This page has been migrated to the Tazama GitHub repository and is now located at: https://github.com/frmscoe/docs/blob/main/Product/07-Creating-And-Maintaining-Processors/00-Introduction.md https://github.com/frmscoe/do

alert-icon-red-11.png ATTENTION: This page has been migrated to the Tazama GitHub repository and is now located at: https://github.com/frmscoe/docs/blob/main/Product/transaction-monitoring-service-api.md https://github.com/frmscoe/docs/blob/main/Product/t

Configuration For DNS Monitoring we require a target to be configured on the Prometheus Config. - job_name: coredns scrape_interval: 5s metrics_path: /metrics static_configs: - targets: ['kube-dns.kube-system.svc:9153'] The default Metrics port is: 9153,

alert-icon-red-11.png ATTENTION: This page has been migrated to the Tazama GitHub repository and is now located at: https://github.com/frmscoe/docs/blob/main/Knowledge-Articles/01-Knowledge-Articles/18-Entity-Resolution-Explained.md https://github.com/f

Entity resolution Objective: To determine if the debtor (or creditor) in a transaction is the same person that had transacted previously, even if from a different account. Pre-requisites Account information from previous transactions have been independent

Introduction Scaling the FRMS Solution effectively means we will need to observe bottlenecks to scale effectively. Our monitoring Solution consists of Prometheus (https://prometheus.io/ https://prometheus.io/ ) for data collection and Grafana (https://gra

com.atlassian.ecosystem2729962a-bde6-4430-b9d6-d6483b89a1dd/5e7a22e6-909d-46ae-9ab3-35d134dfd821/static/poll-maker27239f3d-07d7-4586-9545-874a91c83575ari:cloud:ecosystem::extension/2729962a-bde6-4430-b9d6-d6483b89a1dd/5e7a22e6-909d-46ae-9ab3-35d134dfd821/

alert-icon-red-11.png ATTENTION: This page has been migrated to the Tazama GitHub repository and is now located at: https://github.com/frmscoe/docs/blob/main/Product/00-Glossary/00-Glossary.md https://github.com/frmscoe/docs/blob/main/Product/00-Glossar

alert-icon-red-11.png ATTENTION: This page has been migrated to the Tazama GitHub repository and is now located at: https://github.com/frmscoe/docs/blob/main/Knowledge-Articles/01-Knowledge-Articles/17-ISO20022-And-Tazama.md https://github.com/frmscoe/d

Introduction For our NATS monitoring we’re using the prometheus-nats exporter (https://github.com/nats-io/prometheus-nats-exporter https://github.com/nats-io/prometheus-nats-exporter ) Please note - on our NATS helm chart, this is automatically included w

SCENARIO 1: Pseudonymisation for internal use Data are collected directly from the data subjects and pseudonymised by the data controller, for subsequent internal processing. Actio will not collect data directly from data subjects. SCENARIO 2: Processor i

alert-icon-red-11.png ATTENTION: This page has been migrated to the Tazama GitHub repository and is now located at: https://github.com/frmscoe/docs/blob/main/Product/08-Processor-Results-Propagation.md https://github.com/frmscoe/docs/blob/main/Product/0

What is Tazama Tazama is an Open Source solution built to support any Digital Financial Services Provider (DFSP) that requires Transaction Monitoring. Whether that DFSP is a small provider running one or 2 transactions per day or a national payment switch

alert-icon-red-11.png ATTENTION: This page has been migrated to the Tazama GitHub repository and is now located at: https://github.com/frmscoe/docs/blob/main/Research-Articles/05-Pseudonymisation/01-Pseudonymisation-Of-Customer-Data.md https://github.co

Consider an identifier 𝐼𝑑 which appears several times in two datasets 𝐴 and 𝐵. After pseudonymisation, the identifier 𝐼𝑑 is substituted with respect to one of the following policies: Deterministic Pseudonymisation 𝐼𝑑 is universally replaced by the

Whichever technique is employed, pseudonymisation must be unambiguously reversible. Single-identifier Pseudonymisation Counter An identifier (the data that identifies a data subject) is substituted by a unique number chosen by a monotonic counter. First,

alert-icon-red-11.png ATTENTION: This page has been migrated to the Tazama GitHub repository and is now located at: https://github.com/frmscoe/docs/blob/main/Product/rule-processor-overview.md https://github.com/frmscoe/docs/blob/main/Product/rule-process

Tazama_Logo_Transparent.png 🕑 Recently updated You'll see the 5 most recently updated pages that you and your team create.

Change log 2022/03/17: Updated post-NiFi test files to include changes made in and Transformations Each ISO 20022 transaction message that is ingested into Actio flows through the following processes/processors which each may introduce some transformation

alert-icon-red-11.png ATTENTION: This page has been migrated to the Tazama GitHub repository and is now located at: https://github.com/frmscoe/transaction-aggregation-decisioning-processor/blob/main/README.md https://github.com/frmscoe/transaction-aggrega

alert-icon-red-11.png ATTENTION: This page has been migrated to the Tazama GitHub repository and is now located at: https://github.com/frmscoe/docs/blob/main/Product/transaction-monitoring-service-api.md https://github.com/frmscoe/docs/blob/main/Product/t

alert-icon-red-11.png ATTENTION: This page has been migrated to the Tazama GitHub repository and is now located at: https://github.com/frmscoe/docs/blob/main/Product/05-Typology-Processing.md https://github.com/frmscoe/docs/blob/main/Product/05-Typology