Security incident detection for WordPress

The incident engine watches your activity log for five attack patterns and assembles what happened into an incident with related events and remediation steps, not a wall of raw log lines.

5
attack patterns detected automatically
Hourly
scheduled analysis pass over recent events, plus event-triggered checks
De-duped
repeat detections fold into the open incident instead of spamming you
6
alert platforms: Slack, Discord, Teams, Telegram, PagerDuty, custom webhooks

What it does

A raw activity log tells you everything and therefore nothing. The incident engine correlates events inside a time window and recognizes the shapes that matter: brute-force attacks, privilege escalation, backdoor installation, plugin compromise, and the hostile-takeover sequence: an admin login followed by security-plugin deactivation and a suspicious file upload.

How it works

Detection runs two ways: significant events trigger an immediate check, and a scheduled pass analyzes the last hour of activity. When a pattern matches, the engine creates an incident that bundles the related events, de-duplicates against incidents already open for the same pattern, and attaches per-type remediation recommendations.

Alerts go where your team already is: email, Slack, Discord, Microsoft Teams, Telegram, PagerDuty or any custom webhook, with per-incident-type alert rules. There is a REST API for incidents and a WP-CLI surface for scripting.

  • Brute force, privilege escalation, backdoor installation, plugin compromise, hostile takeover
  • Event-triggered and hourly scheduled analysis
  • Incidents bundle related events with remediation recommendations
  • Per-type alert rules across 6 platforms
  • REST API and WP-CLI access

Documentation

Security incidents

Reading and resolving incidents.

Read the guide →

Alerts & notifications

Wire alerts into your team channels.

Read the guide →

Alert history

What fired, where and when.

Read the guide →

Incident detection questions

Will I get flooded with alerts during an attack?

No. Repeat detections of the same pattern fold into the already-open incident rather than creating new ones, and alert rules are configurable per incident type.

Does it depend on the activity log?

Yes. The engine correlates activity-log events, so incident detection and the full activity log ship together in Pro.

Can I integrate it with my own tooling?

Custom webhooks support bearer, basic and API-key auth, incidents are exposed over the REST API, and a WP-CLI surface exists for scripting.

Related features

Pro

Full activity log

Who did what, when. Exportable and filterable.

Learn more →
Pro

SIEM & webhooks

Forward logs to syslog, CloudWatch, Loggly and more.

Learn more →
Pro

Continuous file monitoring

Know when a monitored file changes, checked hourly.

Learn more →

All features →

Secure your site today

Install the free plugin from WordPress.org and set up real protection with the guided setup wizard. Upgrade to Pro whenever you need more.