Skip to main content
Connect Azion (Edge Firewall and Web Application Firewall, API v4) so Myrmex can review your WAF rule sets and sensitivity, manage false-positive exceptions, bind the WAF to traffic, work with IOC network lists, and analyze WAF events. Myrmex reaches the Azion API (api.azion.com) over HTTPS through a Collector on your network, querying it in real time.

​
What Myrmex Can Do

WAF rule sets

Review WAF rule sets and tune sensitivity for your traffic.

False-positive exceptions

Add and manage exceptions to cut false positives.

Network lists & binding

Work with IOC network lists and bind the WAF to Edge Firewalls and domains.

Real-time events

Analyze real-time WAF events during investigations.

​
Before You Start

  • A Collector that can reach the Azion API (api.azion.com) over HTTPS. See Deploying the agent.
  • An Azion personal token. The token itself scopes the whole account — no separate account or zone ID is needed.

​
Step 1 — Create the Personal Token in Azion

The credential Myrmex needs is an Azion personal token, sent as Authorization: Token.
1

Open Personal Tokens

In the Azion Console, open the Account Menu → Personal Tokens.
2

Create the token

Create a new personal token and set an expiration that fits your policy.
3

Copy the token

Copy the token now — it is shown only once. It scopes the whole account.
Optionally note a default Edge Firewall ID and WAF Rule Set ID to prefill in Myrmex — both can also be passed per action.

​
Step 2 — Add the Integration in Myrmex

From the Directory, choose Add Integration → Azion, then fill in:

​
Connect

Click Connect to validate the token and finish. Azion then appears under Environment → Integrations, and you can start asking Hydra about it in the Workspace.
Your personal token is stored securely and resolved server-side — it never passes through the AI, and Myrmex queries Azion on demand rather than storing its data.