Rules
Last updated
Last updated
The CUBE3 Engine uses rules to enable services like Risk Score and RASP and there are two default thresholds that determine risk scores as well as pass and blocking.
CUBE3 Engine uses three different ranges for risk score thresholds:
1 - 30 SAFE
31 - 69 Warning
70 - 100 Unsafe
These scores are automatically determined by the CUBE3 Engine via AI learning models.
Pass and block thresholds are determined by recommendations from CUBE3 based on the risk score thresholds and can be adjusted based on a customer business risk profile.
CUBE3 has unique capabilities to apply dynamic rules that implement policy against transactions on a global and per contract level. Global rules occur across all transactions and all smart contracts configured. Based on their configuration they can either raise the score or lower the score based on the applied rules. Each CUBE3 customer tenant has two pre-configured rules:
Block OFAC Sanctioned - This rule blocks by default all OFAC addresses detected in transactions by scoring the transaction at 100
High Score - This rule enables blocking for scores that are 70 - 100
Per contract rules enable fine grained rules on a per contract basis. These rules act as extensions of functions that smart contract use to execute commands. Example rules can be to enable limits or guardrails on transactions, or specify additional protections in a dynamic manner.
Allow and blocklists allow customers to specify addresses that should be allowed by default (ex: KYC addresses) and block list addresses that should never be allowed to interact with a customer platform. These addresses can be added both in bulk or individually with a API call.
