Short-lived authorization
Scoped tokens bound to a product, installation, audience, and short time window.
Security & privacy
Trust is not declared.
It is designed.
Every platform boundary minimizes privileges, transferred data, and the impact of an outage.
Protocol foundations
Small permissions. Verifiable messages.
Future cloud communication must fail safely and remain independent of the local protection core.
Signed responses
Entitlements, manifests, and future feeds with a key ID, schema version, expiry, and digest.
Replay protection
Timestamps, unique nonces, canonical requests, and idempotency keys for mutating operations.
Key rotation
Overlapping keysets, audited emergency revocation, and rollback without damaging the local core.
Minimum data
No form contents, raw IP addresses, WordPress users, or unnecessary personal data.
Safe fallback
An outage disables only the cloud extension; the last valid feed has a bounded stale window.
Failure mode
The cloud is not a single point of failure.
The plugin will verify the signature, schema, audience, expiry, and monotonic sequence. If the cloud is unavailable, local protection continues; only cloud extensions disconnect after expiry.
Sentinel Cloud has not launched.This is a binding design for a future implementation, not marketing for an active service.