Aegis
  • Introduction
    • Who is Aegis for?
    • How to start using Aegis?
    • How does Aegis work?
      • Supported networks
      • Findings
      • Categorizing your monitored address
      • Backtesting
        • Performing a backtest
      • Smart contract analysis
      • Allowances
  • Add a monitored address
    • Bulk import addresses
  • Add a notification channel
    • Add an email notification channel
    • Add a Slack notification channel
      • Anatomy of your Slack notification
    • Add a Telegram notification channel
      • Anatomy of your Telegram notification
    • Add an SMS notification channel
    • Add a Discord notification channel
      • Anatomy of your Discord notification
    • Webhooks
  • Triggers
    • Trigger Types compatibility matrix
    • Potential Risks
      • Risk Types
      • Risk Levels
      • Retention of Aegis Findings
    • Events
      • Event Listening: Use cases
    • Function Calls
      • Function Call Monitoring: Use Cases
    • The difference between Events and Function Calls
    • Value triggers
      • Transfer Threshold Monitoring: Use Cases
      • Total-Value-Locked (TVL) Monitoring: Use Cases
      • Token Mint Monitoring: Use Cases
    • Wallet Activity
  • Add an alert
    • Alert management
    • Notification limits solutions
  • Panic Button
    • Add a Panic Button
    • How does the Panic Button work?
  • Interact with your smart contract
  • Teams
  • API
  • Aegis dApp
    • Token risk analysis
  • Firewall
  • Pricing
    • LSS Boost
    • Aegis Limitless
    • Aegis Pulse
  • Glossary
  • Release notes
Powered by GitBook
On this page
  1. Triggers
  2. Potential Risks

Risk Levels

If one or more of the risk types are detected, our AI-powered system will compute a risk score based on the identified patterns of malicious activity.

  • Low risk score suggests a threat of minimal severity. Typically, this means Aegis has pinpointed a single risk factor with a reduced likelihood of being a significant threat. If low-risk alerts keep appearing, consider refining the alert parameters to reduce noise.

  • Medium risk score indicates that several risk factors have been identified. While this alert severity is primarily helpful in troubleshooting smart contract issues, a medium risk score may occasionally provide early warning of an imminent exploit.

  • High risk score signals that Aegis has picked up a high-severity pattern of malicious activity. The alert indicates a likely threat vector has been detected and should be reviewed immediately.

  • Critical risk score is reserved for the highest-severity threats, signaling an imminent or ongoing attack that warrants immediate attention.

Notifications based on the risk score may be configured by setting the baseline risk tolerance level. For instance, opting for "High Risk" notifications will also include alerts for "Critical Risks".

PreviousRisk TypesNextRetention of Aegis Findings

Last updated 1 year ago