What Changed

Cyren Threat Intelligence solution v3.0.4 introduces conditional deployment for JWT tokens, allowing customers to install either or both feeds based on their specific subscription.

Security Impact (Visibility & Fidelity)

Prior to this fix, customers purchasing only one Cyren feed (IP Reputation OR Malware URL) faced deployment failures due to ARM template validation requiring both tokens. This created a deployment barrier preventing threat intelligence ingestion for single-subscription customers.

The conditional deployment logic ensures only purchased feeds are deployed and active, eliminating 403 authentication errors from dummy tokens and enabling proper threat intelligence coverage matching customer subscriptions.

Deployment Changes

ARM template modifications include:

  • JWT token parameters changed from minLength: 1 to minLength: 0
  • Conditional deployment logic for each connector based on token presence
  • UI labels updated to indicate Optional status with helper text

Affected Files

(packaging artefacts: 3.0.4.zip, ReleaseNotes.md, mainTemplate.json)