Services / Messaging & Email Security
SEPPmail migration: on-premises and SEPPmail.cloud
SEPPmail is in use as an encryption gateway in many Swiss companies, and the appliance often runs longer than planned. We support the move to a new on-premises appliance or a new version as well as the switch to SEPPmail.cloud, including key material, GINA accounts and mail routing.
- SEPPmail
- SEPPmail.cloud
- Appliance Migration
- Cluster
- GINA
- S/MIME & OpenPGP
On-premises or cloud
In an on-premises migration the appliance changes: new hardware or VM, a new version, often a new cluster setup as well. Backup and restore transfer configuration and keys; network, certificates, licence and integrations still have to be checked individually. When switching to SEPPmail.cloud, the vendor takes over operation of the platform, but mail routing changes fundamentally: MX, connectors, SPF and submission from Microsoft 365 or Exchange are set up anew, and it must be clear which keys and GINA accounts are carried over.
Services
How an engagement runs
- 1 Inventory Version, licence, rules, keys, GINA accounts, integrations and submitting systems.
- 2 Target design On-premises or cloud, cluster or single system: a reasoned decision with a defined way back.
- 3 Parallel operation and cutover Test traffic on the new system, then routes switched one at a time and reversibly.
- 4 Acceptance and decommissioning Test encryption and decryption, signatures and GINA access, then remove the old appliance from routing and monitoring.
Further reading
Planning something similar?
In a first conversation, we'll look at where you stand, the risks and the most sensible next step.