Enterprise adds the controls security teams ask for. Each is off until an administrator turns it on, and each is checked on the server.

Tamper-evident log#

Sealing: every action log row is sealed into a SHA-256 hash chain within minutes, and a checkpoint signed with the site's Ed25519 key is recorded daily.
Checking: wp agentwarden log verify and Activity → Log integrity report edited, removed, or inserted rows, and changed checkpoints or keys.
Exports: exports include each row's hashes, so a SIEM can check the chain independently.

SIEM push#

Sealed rows and checkpoints are pushed every five minutes to syslog (TLS, TCP, or UDP), Splunk HTTP Event Collector, Datadog Logs, or Elasticsearch. Each event has a stable ID, so retries never duplicate. Configure destinations in Settings → SIEM push, and check them with Send test event.

Lockdown#

Settings → Lockdown can turn off the MCP adapter's default server, and stop application passwords from running abilities. Governed agents are then the only way AI clients run abilities on the site.

Retention and legal hold#

Retention: keep agent history for 30 days to 10 years (Settings → Data, or wp agentwarden retention set <days>).
Legal hold: a hold stops every deletion, including uninstall, until it is released. Placing and releasing a hold are recorded in the sealed log.

Compliance report#

Activity → Compliance report generates a quarterly summary of agents, activity, approvals, controls, and log integrity. It is signed with the site's checkpoint key, so an auditor can verify it offline. Generate one from WP-CLI with wp agentwarden compliance report --quarter=2026-Q3, and verify one with wp agentwarden compliance verify.