Skip to main content
AbuseProtect is an Axottle subsystem that monitors the use of subscriptions on nodes managed through Remnawave and helps the administrator respond to abuse.
  • Detection - detectors detect anomalies of use: traffic spikes, pressure on nodes, signs of subscription sharing, mail spam relays, signs of botnet activity.
  • Incidents with evidence - significant signals open an incident with a picture of evidence (evidence snapshot), statuses and full chronology.
  • Temporary Deceleration (QoS) is the only automatic measure of exposure: a time-limited bandwidth for a particular subscription that expires itself and is manually removed in one click.
The policy is the abusive policy, a single set of rules that the operator edits. No detector applies the actions itself: any impact passes through the policy, and anything more serious than what is allowed by the policy of temporary slowdown requires operator confirmation.
For whom: Panel Administrator, SRE. Required rights: Axottle Administrator (Bearer-Session Token).

Tough principles

These rules are sewn into the product and are not turned off by settings:

No automatic destructive actions

The user never shuts down automatically. Disabling the user and canceling the subscription are prohibited by default, and automation can not even offer them - such actions do not have automatic “writing” in the rules.

No fictitious signals

If the source of the data for the detector is not available, the signal is not generated. The pass is recorded in the audit log with a stable code.

Slowdown does not affect the base rate

QoS-override is a temporary record on top of a tariff that expires automatically, is manually removed, and the subscription rate never changes.

Infrastructure is not a user

Service accounts (transit credentials, health samples, monitoring) are registered as secure, detectors and exposure measures are checked against this registry, and when questioned, the system refuses to apply sanctions.

How the decision goes

Each signal passes through the same chain: Signal → Policy Mode → Rule Action → Safety Checks → Incident + Evidence → Offer to Operator or Self-Deceleration → Entry to AuditPossible outcomes alerted, suggested, applied, denied, skipped - and every one of them gets into logbookThis includes cases where “nothing has happened.”
The fresh setup is conservative: the default policy can’t accidentally slow down or shut down anyone. Auto slowdown needs to be activated consciously.

Where is it in the panel?

Page Security in the panel: summary-verdict, tabs Incidents, Slowdowns, Signals., The infrastructure, Policy, ApplicationDetails by nodes - in the section NodesNotifications - in notification settings.

Section map

Detection

What anomalies are recognized and how the system reports the state of the detectors.

Abuse policy

Modes from “notify only” to self-deceleration, rules, security restrictions.

Temporary deceleration (QoS)

How QoS overrides are applied, expired and removed.

Incidents and evidence

Incident life cycle, evidence snapshot, operator actions and audit.

Privacy.

What is stored, what is aggregated and hashed, the shelf life.