Zix to Cloud-Native: Top Bank’s Blueprint for Migration

Read the Story

Challenge

  • Legacy system was rigid: Couldn’t enforce 2FA or work with Proofpoint.
  • User friction: Complex steps slowed people down.
  • Compliance gaps: Missed key authentication standards.

Solution

  • Moved to cloud: Switched to Echoworx on AWS for full key control.
  • Proofpoint in sync: Rolled out encryption with their Proofpoint migration.
  • Made it simple: Enabled web-based Outlook add-in for easy use.

Result

  • Stronger security: 2FA required for all contacts.
  • Better oversight: Real-time tracking with Splunk.
  • Less manual effort: Automated certificate management.

If you’ve been through a lengthy security migration, you know the challenges. In this session, we’ll walk through the technical steps a Top 5 Canadian bank took to move from a legacy Zix solution to Echoworx’s cloud-native encryption platform. The team managed this shift without business disruption, drawing on a focused technical approach.

This session looks at the technical strategy behind migrating from a legacy system to a cloud-native architecture. We’ll outline the key steps the bank took to build a flexible, integrated encryption platform designed to meet the realities of financial sector operations.


What you’ll learn:

  • The Migration Playbook: See how the bank leveraged deep Proofpoint synergy and a “Big Bang” cutover to ensure zero downtime and a seamless user transition.
  • Achieving Key Sovereignty: Explore the technical integration with AWS CloudHSM, which provided the bank with absolute, hardware-backed control over their encryption keys.
  • Solving Real-World Challenges: Learn how they enforced mandatory 2FA, solved the S/MIME certificate nightmare, and enabled real-time auditability with a direct Splunk API integration.

If you’re considering a similar move, this session offers a practical look at how the migration was handled—what worked and what you can take away for your own planning.