For the complete documentation index, see llms.txt. This page is also available as Markdown.

Axora Arena

Overview

Axora Arena is the AI adversarial security validation platform of the Axora product line. Within an explicitly authorized and controlled environment, it validates the security boundary of AI systems, agents, and connected workflows against real adversarial scenarios, and turns what it finds into remediation and retest evidence.

Router manages access and AgentGuard protects action. Arena answers the question both of them depend on: does the boundary actually hold under attack?

The name describes the product. An arena is a bounded, controlled, repeatable space for adversarial testing. Arena keeps the professional meaning of red teaming while turning it from a one-off engagement into a platform that can be used continuously.

The Problem Arena Solves

Enterprises can usually see that policies have been configured. What they cannot easily answer is whether those policies are effective under a real attack:

  • Can prompt injection change an agent's instruction priority?

  • Can tool approvals and permission boundaries be bypassed?

  • Can RAG content, MCP servers, secrets, or customer data be leaked?

  • After a fix, has the original attack path actually been closed?

Agent environments also change constantly. New skills are installed, new tools are connected, new models are routed, and new attack techniques appear. A policy that was sufficient last month may have a gap today. Periodic, manual penetration testing designed for deterministic software cannot keep up with non-deterministic systems that speak in natural language.

How Arena Works

  1. Define the validation scope. Specify the target systems, agents, tools, data, permissions, and the attack paths that are permitted to be tested.

  2. Establish a controlled environment. Configure authorization, isolation, rate limits, dry-run mode, and emergency-stop conditions. Nothing runs until these are in place.

  3. Execute adversarial scenarios. Validate prompt injection and instruction-hierarchy bypass, tool misuse and approval bypass, RAG leakage, MCP escalation, secret exposure, data exfiltration, supply-chain risk, and Web3 contract risk such as wallet draining and unlimited approvals.

  4. Produce Findings. Each finding records severity, attack path, evidence, scope of impact, and owner.

  5. Support remediation and retest. Findings are converted into policy or engineering changes, and the affected attack paths are re-validated after the change.

Core Capabilities

Scenario-Based Adversarial Testing

Arena builds attack scenarios with an explicit scope against AI systems, agents, tools, and connected workflows, rather than stopping at static rule checks. Scenarios are aligned with public agent-threat taxonomies and with the detection rules and signed advisories that power AgentGuard's runtime defense, so validation always reflects the latest known attacks.

Reproducible Evidence

Every finding retains its validation conditions, key steps, results, and impact, so that security teams and engineering teams can confirm the problem together. Benign control cases are included so that teams see not only what is caught but what is wrongly blocked.

Linkage with Defensive Policy

Validation results feed AgentGuard's runtime policy and can be used to tighten Router's information-flow controls and approval conditions. A confirmed weakness becomes a proposed guard rule pushed to the fleet. Offensive results become defensive capability.

Continuous Retest

When a model, prompt, tool, permission, MCP server, or supply-chain component changes, or when the threat-intelligence network publishes a new advisory, Arena re-validates the affected attack paths and confirms coverage.

Open Benchmarks

Arena is the basis for GoPlus' open benchmarks for agent security tools, with labeled datasets across threat categories published so that detection rate, false-positive rate, precision, recall, and per-category coverage can be reproduced and compared. It also underpins the evaluation of autonomous trading systems developed with ecosystem partners.

Responsible Offensive Security

Arena is deliberately bounded. Every scenario is a dry run, declares its safety tier, and runs only inside an approved scope. Deny-first controls apply throughout:

  • Rules-of-engagement authorization. No scenario runs without an active, in-window customer authorization.

  • Isolated-runner attestation. Active validation executes only on runners attested to run in an isolated environment.

  • Blast-radius rate limits and an emergency-stop kill switch that halts all dispatch instantly and is visible in the audit record.

  • Evidence minimization. Findings record references and results, never raw credentials or customer data.

Arena is reserved for authorized validation of the customer's own systems. It is not a general-purpose attack framework.

Arena and the GoPlus Security Language Model

GoPlus plans to drive Arena with its own security-specialized language model, trained on the network's accumulated security data and red-team attack traces. The model will generate attack paths, run red-versus-blue adversarial exercises against agent environments, and evaluate whether defenses hold. Because the same model also powers detection across DeepScan, SafuSkill, GoPlus Intelligence, and AgentGuard, findings from the offensive side train the defensive side directly. This is where GoPlus' two directions, AI for Security and Security for AI, meet.

Arena and $GPS

Arena adversarial scenarios are metered security services. Each scenario run, retest, and benchmark evaluation is a discrete unit of security consumption settled in $GPS.

Arena also contributes to the supply side of the network. Verified attack findings submitted to the Security Data Layer are rewarded in $GPS, and security researchers who contribute attack scenarios and benchmark cases participate in the same staking and reward mechanisms as data contributors.

Who Arena Is For

  • Security teams that need to prove agent deployments are safe with evidence, and re-prove it after every change.

  • Agent platform operators that continuously test the environments their users run agents in.

  • Security researchers who contribute attack scenarios and benchmark cases and evaluate tools against open datasets.

  • Autonomous trading systems that must be validated against adversarial conditions before handling real assets.

Conclusion

Axora Arena validates the boundary. By continuously attacking AI systems and agents inside a controlled, authorized environment, producing reproducible findings, and feeding the results back into Router and AgentGuard, Arena turns one-off red-team projects into a continuous validation capability. It is the third control point in the Axora boundary, each exercise is a metered service settled in $GPS, and each verified finding strengthens the network for everyone.

Last updated