Announcement: New Knowledge Base

4 June 2020: We are pleased to announce the launch of a new Knowledge Base, Changelogs for Business Security Products, where you can find more details, such as bugfixes or new features, about the most recent releases of our business-related products.

FSMSG Outlook plugin questions

Dear all

 

Have some questions regarding Outlook plugin for FSMSG since documentation seems to be scarce.

 

How Outlook plugin works?

 

1. Outlook plugin sends/uploads emails directly to FSMSG or send them via E-mail server, and injecting extended header?

2. How it is configured where to find FSMSG? For example, could it be used by a 'roaming' user connecting from an insecure network back to FSMSG to send email?

3. Need additional license? Where it is imported?

 

Thank you in advance

CI

Comments

  • Jari-PJari-P Posts: 79

    Hello Costas,

     

    The plug-in displays a Send Securely button in the Outlook interface that users can click to send secure messages. The Send Securely button adds a header to the message that triggers a F-Secure Protection Server rule to encrypt the message.

     

    All you need to do is enable the desktop_plugin_encrypt rule on the Email Firewall > Rules page and save your changes.

     

    F-Secure Encryption is based on the concept that encryption keys are managed separately from the content they encrypt. Keys are generated on the F-Secure Protection Server and stored on a centralized F-Secure key server.

    F-Secure Encryption provides the following benefits:

    Confidentiality - only intended recipients can read a message. Privacy and confidentiality are assured through authentication, authorization, and encryption.

    Integrity - messages cannot be altered while in transit from sender to recipient. Integrity is achieved by computing a hash, or mathematical computation of the text of the message. If one bit of a message is changed, a different hash is computed and the message is flagged as corrupt.

    Auditing and reporting - key access is recorded when recipients read messages. Timestamps are recorded when keys are retrieved by each recipient. Keys are associated with the sender's email address, the subject of the message, the timestamp of when the message was sent, and a list of the recipients for the message. Details include the number of times each recipient has read the message and the number of times each recipient has requested the key for the message.

    Authentication - users within your organization or outside your organization authenticate with the Authentication Source you configure on a user, domain group, or group level.

     

    License needs to be included with encryption, so if you don't have it contact our sales and we can release it to your license.

    Chrissy
This discussion has been closed.