AbuseHQ
Overview
Learn how AbuseHQ works
AbuseHQ provides automated and manual workflows that manage your network’s abuse reports.
AbuseHQ Mailbox Sections Explained
An overview of what each mailbox section means.
AbuseHQ Event Inbox Explained
The Event Inbox is an intermediary step between Inbound Processing and case creation.
AbuseHQ Cases Page Explained
A breakdown of the components on the Case view page.
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 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.
Smartlinks configuration
Smartlinks enable you to access external tools with dynamically generated links easily.
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.
FAQ
Abusix Systems Status
Our Systems Status
Inbound Processing, Event Types
A list of the event types we classify during inbound processing
Resolver Reference
A list of definitions for the inbound resolver
Subscriber data model
The data structure of AbuseHQ is configurable. How you configure may impact your set-up and future workflows.
Outgoing IPs
These IP addresses make outgoing calls from AbuseHQ. Please configure your firewalls to allow calls from these addresses.
Email and report template variables
Here’s a collection of template variables you will find helpful while configuring email and report templates.
Parrot Querry Language PQL
PQL Queries are always executed in context, e.g., within a new incident or an existing case.
Browser support
These Web Browsers are compatible with Abusix products.