EvoHub

Wazuh alerts, routed to the right on-call engineer

Receive Wazuh security alerts through a ready-made integratord custom integration script. EvoHub turns each Wazuh alert into an on-call alert, runs it through your escalation policy, and pages people by voice call, mobile push and email.

How the Wazuh integration works

  1. Create a Wazuh integration in EvoHub On-Call and pick the escalation policy it should notify.
  2. EvoHub gives the integration its own URL (or inbound address) with a unique key — paste it into Wazuh using the steps below.
  3. Each Wazuh alert opens an EvoHub alert, and your escalation policy pages the on-call person — then the next step if nobody acknowledges.
  4. No — Wazuh alerts are security events with no recovery; resolve in EvoHub.

Set up Wazuh

Create the integration in EvoHub first — it shows your personal integration URL to paste below.

# On the Wazuh manager (as root):

# 1. Save this script as /var/ossec/integrations/custom-evohub
#    — paste as-is (Python 3 standard library only; the first
#    line is the Python Wazuh ships with):
#!/var/ossec/framework/python/bin/python3
# EvoHub On-Call — Wazuh custom integration.
# Install as /var/ossec/integrations/custom-evohub (root:wazuh, mode 750).
# integratord runs it as: custom-evohub <alert file> <api key> <hook url>
# Test by hand:           custom-evohub --test <hook url>
import json
import sys
import urllib.error
import urllib.request


def post(url, payload):
    req = urllib.request.Request(
        url,
        data=json.dumps(payload).encode("utf-8"),
        method="POST",
        headers={"Content-Type": "application/json", "User-Agent": "evohub-wazuh/1"},
    )
    try:
        with urllib.request.urlopen(req, timeout=10) as resp:
            resp.read()
        return 0
    except urllib.error.HTTPError as e:
        sys.stderr.write("evohub: EvoHub answered HTTP %d\n" % e.code)
    except (urllib.error.URLError, OSError) as e:
        sys.stderr.write("evohub: could not reach EvoHub: %s\n" % getattr(e, "reason", e))
    return 1


def main(argv):
    if len(argv) == 3 and argv[1] == "--test":
        return post(argv[2], {"evohub_test": True})
    if len(argv) < 4:
        sys.stderr.write("usage: custom-evohub <alert file> <api key> <hook url>\n")
        return 2
    with open(argv[1], encoding="utf-8") as f:
        alert = json.load(f)
    return post(argv[3], alert)


if __name__ == "__main__":
    sys.exit(main(sys.argv))
chmod 750 /var/ossec/integrations/custom-evohub
chown root:wazuh /var/ossec/integrations/custom-evohub

# 2. Check the connection — EvoHub answers OK, opens no alert:
/var/ossec/integrations/custom-evohub --test '<your EvoHub integration URL>'

# 3. Add to /var/ossec/etc/ossec.conf, inside <ossec_config>:
<integration>
  <name>custom-evohub</name>
  <hook_url><your EvoHub integration URL></hook_url>
  <level>10</level>
  <alert_format>json</alert_format>
</integration>

# 4. systemctl restart wazuh-manager

# Every alert at level 10+ is sent. One EvoHub alert per rule and
# agent; repeats retrigger it. Level 12+ → critical, 10–11 → high,
# 7–9 → medium, 4–6 → low. Wazuh sends no recovery — resolve in
# EvoHub. Lower <level> or add <group>/<rule_id> to narrow it.

Wazuh + EvoHub — FAQ

How do I connect Wazuh to EvoHub?

In EvoHub, go to On-Call → Integrations, add Wazuh, and choose an escalation policy. Then configure Wazuh with the integration URL EvoHub shows you — the exact steps are on this page.

Do Wazuh alerts resolve automatically in EvoHub?

No — Wazuh alerts are security events with no recovery; resolve in EvoHub.

How is the Wazuh integration priced?

Integrations are included. EvoHub bills on usage, not per seat: an ingested alert costs 1 EvoHub token (about $0.015), push and webhook notifications are free, and every account gets 200 free tokens each month.

Start free — 200 EvoHub tokens every month. See pricing.

Last updated: · EvoHub is built and operated by EvoSync Teknoloji A.Ş.