Skip to main content

Security

  • No shared secrets. The plugin generates a key pair per site. The private key never leaves your server and is encrypted with your site's own secret keys. Wigoh holds only the public key. There are no API tokens or stored Wigoh passwords.
  • Signed requests. Every request from the plugin to Wigoh is signed with the site key. A request with a bad or stale signature is refused.
  • Proof of control. During connection Wigoh fetches a one-time challenge from your site to prove the request really came from it.
  • Human approval twice. You approve the link in Wigoh with a matching code. An administrator approves every release in WordPress.
  • Verified packages. Releases and plugin updates are checked against a published checksum and a signature before they are applied or installed.
  • Rollback. Automatic on a failed health check; manual for 7 days.
  • Protected data. Users, comments and plugin runtime tables are never replaced by a release.
  • Private storage. Snapshots and releases live in a private bucket and move over short-lived private addresses.

Full details in the plugin's own description under External Services and Update security, reproduced in Data and retention.