Implementation Guidelines: Message Content

 

1. Encryption Settings

Encryption protocol for message content is set via the Administrative Web console on the Default Security Rules page shown below.  

 

After installing NotifyLink Enterprise Server components and before adding user accounts, access the Administrative Web console to set these Security parameters:

-Select IT Policy Management > select a policy and click the Edit IT Policy button > Security Rules

•  Enable encryption settings for new users

•  Select the encryption algorithm type (AES or TDES)

An encryption key will be automatically generated for each new user added to the system.  Keep in mind that the global encryption type you choose will only apply if a user’s device supports the protocol. The setting can be individualized for a user whose device does not support the global encryption type.  (From the admin web, select User Administration > select a user and click the Edit User Policy button > Security Rules.)

 

 

AES vs. TDES  Triple DES was the standard FIPS compliant encryption algorithm until 2001. Then the AES encryption algorithm became the standard.  NotifyLink supports both protocols and each is an effective encryption method for protecting information in transit.  Government grade security is available, however, by implementing the National Institute of Standards and Technology (NIST) FIPS compliant AES encryption algorithm.

 

2. Enabling SSL

Enable SSL for device to HTTP/Web server communication.

 

-Select Server Administration

•  Check the Use Device-Server SSL box.

-Install an SSL certificate on your HTTP/Web server and enable SSL in IIS/Apache.

-Instruct users, whose device O/S supports SSL, to enable it. 

•  On the device:  NotifyLink Preferences > Account Settings