Ylem documentation
  • 🗒️General information
    • Introduction to Ylem
    • Quick start guide
    • Release notes
  • 🔬Open-source edition
    • Installation
    • Usage of Apache Kafka
    • Task processing architecture
    • Configuring integrations with .env variables
  • 💡Integrations
    • Connecting an integration
    • Library of integrations
      • Amazon Redshift
      • Apache Kafka
      • APIs
      • Atlassian Jira
      • AWS Lambda
      • AWS RDS
      • AWS S3
      • ClickHouse
      • ElasticSearch
      • E-mail
      • Google Big Query
      • Google Cloud SQL
      • Google Pub/Sub
      • Google Sheets
      • Immuta
      • Incident.io
      • Jenkins
      • Hubspot
      • Microsoft Azure SQL
      • MySQL
      • OpenAI ChatGPT
      • Opsgenie
      • PostgreSQL
      • PlanetScale
      • RabbitMQ
      • Salesforce
      • Slack
      • Snowflake
      • Tableau
      • Twilio. SMS
      • WhatsApp (through Twilio)
    • Initial demo data source
  • 🚡Pipelines
    • Pipeline management
    • Tasks
      • Aggregator
      • API Call
      • Code
      • Condition
      • External trigger
      • Filter
      • For each
      • GPT
      • Merge
      • Notification
      • Query
      • Pipeline runner
      • Processor
      • Transformer
    • Running and scheduling pipelines
    • Library of templates
    • Environment variables
    • Mathematical functions and operations
    • Formatting of messages
  • 📈Statistics and profiling
    • Statistics of runs
    • Slow tasks
  • 📊Metrics
    • Metric management
    • Using previous values of a metric
  • 💼Use cases, patterns, templates, examples
    • Use cases
    • Messaging patterns
      • Datatype Channel
      • Message Dispatcher
      • Messaging Bridge
      • Message Bus
      • Message Filter
      • Message Router
      • Point-to-Point Channel
      • Publish-Subscribe Channel
      • Pull-Push
    • Functional use cases
      • Streaming from Apache Kafka and messaging queues
      • Streaming from APIs
      • Streaming from databases
      • Data orchestration, transformation and processing
      • Usage of Python and Pandas
      • KPI Monitoring
      • OKRs and custom metrics
      • Data Issues & Incidents
      • Reporting
      • Other functional use cases
    • Industry-specific use cases
      • Finance and Payments
      • E-commerce & Logistics
      • Customer Success
      • Security, Risk, and Anti-Fraud
      • Anti-Money Laundering (AML)
  • 🔌API
    • OAuth clients
    • API Reference
  • 👁️‍🗨️Other resources
    • FAQ
    • Our blog on Medium
Powered by GitBook
On this page
  • Monitoring of organizations with a high-risk score and streaming them to CRM
  • Streaming failed KYC reporting
  • Observing and streaming how many users created from the same IP
  • Technical real-time detection of XSS attempts
  • Anti-Money Laundering (AML) transaction streaming

Was this helpful?

Edit on GitHub
  1. Use cases, patterns, templates, examples
  2. Industry-specific use cases

Security, Risk, and Anti-Fraud

PreviousCustomer SuccessNextAnti-Money Laundering (AML)

Last updated 8 months ago

Was this helpful?

Monitoring of organizations with a high-risk score and streaming them to CRM

Customers who use their own scoring algorithms or rely on 3rd-party scoring providers can use the following pipeline or a modification of it to automate the monitoring of organizations with high-risk scores and call CRM API or send it as a report to the responsible departments.

Streaming failed KYC reporting

With this one, you can help your responsible department to automatically detect and take action for customers who failed the KYC procedure.

Observing and streaming how many users created from the same IP

Potential fraud.

Technical real-time detection of XSS attempts

Cross-site scripting (XSS) is a vulnerability that your application should prevent and be secured from. However, automatic XSS attempts can be monitored with Ylem by detecting the word "script" in the database items.

In case of detecting your data engineering teams need to block the attack and further improve the application and security to avoid such situations in the future.

Here is an example of a pipeline that will allow you to detect it:

Anti-Money Laundering (AML) transaction streaming

Anti-Money Laundering (AML) regulations require businesses to monitor transactions and report suspicious ones to authorities.

Ylem can help you with automating the following critical processes:

  • Unusual transaction amounts;

  • Unusual series of transactions (e.g., several cash credits);

  • Unusual geographic destination or origin of a payment;

  • Known threats or typologies.

Here is an example of the pipeline to monitor large transaction amounts

More examples of AML use cases are described on a .

💼
separate page
Possible pipeline
Possible data retrieval query
Potential pipeline
Potential pipeline
Potential SQL query to retrieve data
SQL query example
Query example to detect large transactions