> ## Documentation Index
> Fetch the complete documentation index at: https://docs.wirespeed.co/llms.txt
> Use this file to discover all available pages before exploring further.

# Abnormal Security

> Import email threat detections from the Abnormal Threat Log

The Abnormal Security integration reads the Abnormal Threat Log through the
[Abnormal REST API](https://app.swaggerhub.com/apis-docs/abnormal-security/abx)
and creates one Wirespeed detection per threat campaign.

## Supported data

Each detection summarizes one Abnormal threat campaign:

* Abnormal's judgement: attack or borderline
* Attack type, attack strategy, attack vector, attacked party, and
  impersonated party
* Sender address, sender name, sender domain, and sender IP addresses
* Recipient mailboxes, subject, internet message IDs, URLs, and attachment
  names
* Abnormal's summary insights, the highest attack score in the campaign, and a
  link to the threat in the Abnormal portal
* Remediation status. A campaign whose every message Abnormal removed from the
  mailboxes is marked as mitigated. Wirespeed checks up to 500 messages per
  campaign; a larger campaign is not marked as mitigated.

Abnormal returns the details of at most 10 messages per campaign, so the
senders, recipients, URLs, and attachments of a larger campaign come from 10 of
its messages. The detection's recipient and message counts still cover the
whole campaign.

Up to 50 recipients are added to the detection as users. External senders are not
matched to directory users. When Abnormal attributes the campaign to a
compromised internal mailbox (account takeover), the sender is added as a
user too, so you can contain it with your Microsoft 365 or Google Workspace
integration.

Wirespeed imports attacks and borderline threats. Abnormal flags borderline
threats as suspicious without confirming them as attacks, so their detection
title is labeled **(borderline)**. Wirespeed does not import spam.

## Prerequisites

An Abnormal Security tenant with access to the **Abnormal REST API**
integration in the Abnormal portal.

## Create an API token

1. Sign in to the [Abnormal portal](https://portal.abnormalsecurity.com/home/settings/integrations)
   and open **Settings → Integrations**.
2. Select **Abnormal REST API**.
3. Add the Wirespeed IP addresses to the token's IP allowlist. Abnormal rejects
   requests from any address that is not on it.
   * `34.214.73.253`
   * `52.42.160.100`
   * `34.211.242.42`
4. Copy the authentication token.

## Connect Abnormal Security

1. In Wirespeed, go to **Settings → Integrations → [Add Integration](https://app.wirespeed.co/settings/integrations?tab=browse) → Abnormal Security**.
2. Enter the **API Host** for your region:
   * `api.abnormalplatform.com` for US tenants (default)
   * `eu.rest.abnormalsecurity.com` for EU tenants
   * The host Abnormal provided, if your account uses a dedicated one on
     `abnormalplatform.com` or `abnormalsecurity.com`
3. Enter the **API Token**.
4. Save and enable the integration.

If the connection test returns HTTP 403, either the token is invalid or was
revoked, or the Wirespeed IP addresses are not on the token's IP allowlist.
Abnormal returns the same error for both. HTTP 401 also means the token is
invalid or was revoked.

## Synchronization behavior

Wirespeed lists attacks, then borderline threats, by delivery time and by
remediation time, so it also imports threats that Abnormal detects and removes after delivery. The first
sync looks back 24 hours. Each sync reads threats delivered or remediated up
to five minutes ago, which gives Abnormal's automatic remediation time to
complete before Wirespeed reads the threat.

Each sync reads up to 100 threat details, attacks first. When more threats are waiting, the
next sync continues where the previous one stopped. Sync progress only
advances after Wirespeed ingests the threats it read.

Abnormal Security detections use a non-escalating default category until
dedicated categorization rules are defined.

## Not included

* Cases from Abnormal's separate Account Takeover product, AI Security
  Mailbox (Abuse Mailbox) reports, and audit logs. Threat Log campaigns sent
  from a compromised mailbox are imported.
* Message bodies and attachments
* Remediating or restoring messages from Wirespeed. Abnormal remediates
  messages on its side; Wirespeed shows the result as the detection's
  remediation status.
* Remediation that Abnormal completes after Wirespeed imported the threat does
  not mark the detection as mitigated. Wirespeed refreshes the Abnormal threat
  data of open, escalated detections less than 14 days old.
* A borderline threat that Abnormal later confirms as an attack keeps its
  borderline label in Wirespeed.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.