Webhook Security for Insurance Integrations: HMAC Signing, Replay Protection, and Why It's Non-Negotiable

Insurance webhooks carry PII. If your CRM's webhooks aren't signed, you're one leaked URL away from a breach.

Webhooks are the most overlooked attack surface in CRM integrations. The URL is public by necessity, the payload often contains PII, and most receivers blindly trust whatever arrives. That's a breach waiting to happen.

The Three Layers of Protection

1. HMAC-SHA256 Signing

Every payload includes a header like X-Signature: t=1714000000,v1=<hex>. Your endpoint computes HMAC-SHA256(timestamp + "." + raw_body, shared_secret) and constant-time compares. Forgery requires the secret.

2. Timestamp Freshness

Reject requests where the timestamp is more than 5 minutes old. This blocks replay attacks even if a payload is captured in transit.

3. Per-Subscription Secrets

Each webhook subscription has its own rotatable secret. Rotate immediately if any system that knew the secret is decommissioned.

What to Demand From Any CRM Vendor

  • Stripe-style HMAC signatures (or equivalent)
  • Documented timestamp tolerance and replay protection
  • Per-subscription secrets, dashboard-rotatable
  • Retry ladder with dead-letter queue and dashboard replay
  • Test/inspect tooling so you can verify signatures during development

The Compliance Angle

Under HIPAA and most state insurance privacy regimes, "reasonable security" is the standard. Unsigned webhooks carrying PII fail that test in any post-incident review.