Understanding the High-risk AI tools in use risk

Understanding the High-risk AI tools in use risk

BarracudaONE displays this risk when it detects that one or more AI applications classified as high risk are being accessed within your environment.

High-risk AI tools can amplify errors and attacks, mishandle highly sensitive information, and operate in ways that can directly affect people’s safety or major outcomes. Failures while using these applications are harder to detect, control, and defend against.

Why this a risk

High-risk AI applications may expose sensitive data to exploits. Relying on manual policies instead of automated enforcement lags behind real-world use, so by the time you realize that a high-risk application has compromised your users' data, it may be too late.

Identifying this risk

To help you identify the tools affected, BarracudaONE displays:

  • The AI applications accessed

  • The level of risk

  • The number of times each application has been accessed

Resolving this risk

Resolving this risk involves enabling Barracuda SecureEdge to automatically implement and enforce automated AI application control in real time.

To resolve the High-risk AI tools in use risk
  1. In the left navigation menu, select Home Home.png.

  2. In the Risks section, do one of the following:

    • Select the High-risk AI tools in use risk.

    • Select another risk, then use the arrows to navigate to the High-risk AI tools in use risk.

  3. Click the Fix in SecureEdge button and follow the steps to resolve the risk.

Once you click the Fix in SecureEdge button, the risk goes into the Pending state for 24 hours. If you follow the steps to resolve the risk, when the risk is synced, it will go into the Resolved state. If you do not resolve the risk within 24 hours, it returns to the Unresolved state.

Once you have resolved this risk

Once you put a tool in place to view AI tool usage in real time and set up advanced block and allow policies to secure your environment, you can regulate and ensure AI is used in a way that is:

  • Safe - Doesn’t cause harm through errors or unsafe outputs

  • Secure - Doesn’t expose or leak sensitive data, or get exploited

  • Accountable - Ensures traceability for decisions and failures

  • Compliant - Meets privacy, security, and sector-specific rules

  • Reliable - Measures, documents, and continuously improves performance


We value your feedback.
If you have questions, suggestions, or feedback on our documentation, contact the Campus Product Documentation team.
For general product inquiries or technical support, please contact the global Barracuda Support team.