Secure e-mail communication

An unencrypted e-mail is like a postcard: unauthorised persons can also read it while it is being transmitted and the sender or the content of the message can be modified. This guide will show you how you can protect yourself when sending e-mails to Helaba as a client or business partner.

Encrypting and signing e-mails - why is it important?


Quite simply because it ensures that only the sender and recipient of an e-mail can read the message. A digital signature guarantees the authenticity of the sender and the content for you as the recipient.

Helaba provides you with several options for secure e-mail communication:

Options for secure e-mail communication with Helaba

1. Encryption using PGP or S/MIME

If your company supports PGP or S/MIME encryption, we need either a PGP key or an S/MIME certificate from you or your domain.

You can transmit this information to us in the following way:

  • Start the registration process (see section 2 "Encrypted communication using the Secure E-Mail Webinterface") by asking a Helaba employee to send you a confidential e-mail. You will then receive an e-mail from Krypto-gateway-administrator@helaba.de. If you use S/MIME, please reply to this e-mail with a signed e-mail. If you use PGP, please send the key as a file attachment.

    Your key or certificate will then be automatically stored in our Secure E-Mail system, and future e-mail communication with any Helaba sender will be encrypted if the sender marks it as "confidential". The original e-mail from the sender that was used to initiate the registration process will now be sent to you directly.

  • If you already have a personal certificate or your personal key, please proceed as follows:

    Send us the certificate or the PGP key in an e-mail. If you use S/MIME, simply send a signed e-mail and if you use PGP, please send the key as a file attachment. Your key will then be automatically stored in our Secure E-Mail system and associated with your e-mail address. Subsequently, all e-mails from Helaba marked as confidential will be sent to you in an encrypted format.

  • You can also upload your S/MIME certificate or your PGP key into our system through the Secure E-Mail Webinterface if you are registered on https://secure-mail.helaba.de. The registration process is described in section 2.

If your company has a domain certificate and we do not already have it, please send it in an unencrypted zip file to scrmlhlbd.

If you would like to send encrypted e-mails to Helaba yourself, you either need the certificate or the key of the recipient at Helaba or, alternatively, our domain certificate.

The certificates or keys of specific Helaba e-mail addresses can be obtained on the Secure E-Mail Webinterface at https://secure-mail.helaba.de.

2. Encrypted communication using the Secure E-Mail Webinterface


If your company does not support either of the two encryption methods mentioned above, you can communicate securely with Helaba using our Secure E-Mail Webinterface. In order to do this, you only need to be registered.

The registration process is initiated when your contact person at Helaba sends you a confidential e-mail. You will then receive an e-mail from "Krypto-gateway-administrator@helaba.de" containing further information about the registration process.

You can now log in on the Secure E-Mail Webinterface at https://secure-mail.helaba.de. Your contact person at Helaba will have received the initial password and can give it you over the phone.

On the Secure E-Mail Webinterface, you will be able to read or reply to e-mails or download them to your computer. You can also change your Secure E-Mail password or upload your certificate or key here.


Secure Mail Webinterface 

Ensure your e-mail communication with us is safe - in order to register please get in touch with your contact person at Helaba.

FAQs on secure e-mail communication with Helaba

Your choice

When we make our website available to you, we use cookies. 

Some are necessary to help our website work properly, and can't be switched off. And some are optional, but support us in order to improve your experience during your visit.

Are you happy to accept cookies to improve our website?

Details

cookie [publisher]purposestorage period
_et_coid [etracker]statistic: cookie detection2 years
allowLoadExternRessources [helaba]statistic: Saves the user decision that external components may be loaded automatically.30 days
allowTracking [helaba]statistic: Saves the user decision that visitor behavior may be tracked.30 days
BT_ctst [etracker]statistic: Is used to detect whether cookies are activated in the visitor's browser or not.session
BT_pdc [etracker]statistic: Contains Base64-coded visitor history data (is customer, newsletter recipient, visitor ID, displayed smart messages) for personalization.2 years
BT_sdc [etracker]statistic: Contains Base64-encoded data of the current visitor session (referrer, number of pages, number of seconds since the beginning of the session), which is used for personalization purposes.session
disclaimer_disclosureRequirements [helaba]necessary: Verification when accessing certain (sub) areas of the websitesession
disclaimer_residenceGermany [helaba]necessary: Verification when accessing certain (sub) areas of the websitesession
hideCookieNotice [helaba]necessary: Saves that the cookie or data protection notice will not be requested every time you visit.30 days
isSdEnabled [etracker]statistic: Detection of whether the visitor's scroll depth is measured.1 hour
WSESSIONID [helaba]necessary: Standard cookie to use with PHP session data.session

You can find out more in our data policy.