Abusix | Help Center

Overview

Learn how AbuseHQ works

AbuseHQ provides automated and manual workflows that manage your network’s abuse reports.

Setting up AbuseHQ

Get started by forwarding your abuse reports

The most important step to starting AbuseHQ

Create user accounts

This article will walk you through creating AbuseHQ user accounts.

Enable 2FA at app.abusix.com

This article will walk you through enabling Two-factor authentication.

Configure your network settings

This article will walk you through configuring your network ranges within AbuseHQ.

Configure your mail settings

Learn how to configure AbuseHQ to send out reports using your SMTP servers.

Helpful configurations

Data Retention configuration

Data Retention configurations that meet your company’s requirements

SMTP configuration

SMTP Services must be configured if you use AbuseHQ to send out Email notifications to your subscribers.

Email templates configuration

Everything you need to know to configure your email notification templates.

XARF endpoint for report submission

Using API to send XARF reports to AbuseHQ

Event inbox

The Event Inbox is an intermediary step between Inbound Processing and case creation.

Network & abuse contact verification

Verified networks and abuse contacts are essential for ensuring that you receive the correct abuse reports from Abusix or other sources.

API Resolver Caching

We strongly recommend using the timestamp/date in your resolver config attributes because there is no guarantee that events always come in "real-time."

Create and manage your workflows

Configure Inbound Processing

Learn about Inbound Processing and how it fits into your workflows

Configure Case Groups

Here we will walk you through everything you need to know to configure your case groups.

Configure Playbooks

Learn why it’s important and how to configure your playbooks.

Integrate AbuseHQ with other systems

Subscriber resolving via an API and target system (like a CRM or Radius Server)

Integrating AbuseHQ with your systems using API calls during the inbound processing.

Subscriber resolving with Ubersmith

The Ubersmith integration resolves client/subscriber information during inbound processing.

Subscriber resolving via X-Header

Subscriber resolving is a very important step while setting AbuseHQ up as your Abuse Desk Automation

Integrate with upstream systems using Webhooks

Webhooks lets you integrate AbuseHQ into other systems and call their API endpoints.

Using API Keys to access data in AbuseHQ

You can create and manage API Keys in AbuseHQ. (Settings - API Keys) Those API keys can be used to access the HTTP resources of AbuseHQ.