Signals for CPaaS X

If you use CPaaS X applications and entities, Signals can protect each application and entity separately. This is useful when you send messages on behalf of many end customers. Each end customer gets its own fraud analysis, so an attack on one end customer does not affect how Signals handles traffic for the others.

How it works [#how-it-works]

Signals identifies traffic by its account, CPaaS X application, and entity.

For each application or entity that Signals protects, it analyzes traffic, calculates risk scores, and applies blocking thresholds separately.

Configure Signals for CPaaS X [#configure-signals-for-cpaas-x]

You decide which applications and entities Signals protects. Using the Signals API, you can configure the following for each of them:

• Blocking sensitivity: How aggressively Signals blocks suspicious traffic.
• Country overrides: A different blocking sensitivity for specific countries.
• Daily limits: The maximum number of messages per day. Signals blocks messages above the limit.
• Trusted numbers: Phone numbers that Signals never blocks.

Currently, you can manage trusted numbers for individual applications and entities only through the API.

Analytics [#analytics]

You can view blocked traffic for each CPaaS X application and entity in Analytics.