Securing Data in Motion Quick Start

In a mobile environment, data in motion refers to the transfer of data between the source repository (EIS or backend), and the copies of data from that source as it traverses the perimeter of your organization into mobile networks or the Internet.

To ensure data is protected along all communication channels, Sybase recommends that you use your existing PKI infrastructure to protect all Unwired Platform communications within and outside your corporate perimeter.

Securing Synchronization
Messaging data is automatically strongly encrypted over HTTP, using a private messaging payload protocol that is completely secure, once established. The message body is a JSON document. Therefore, only replication payloads require administrative intervention.
Securing DCNs
The most efficient way to update data from the back-end datasource is to allow the EIS to “push” data changes to Unwired Server. This is accomplished with data change notifications (DCN). DCN can operate over HTTP, however, for a secure communication, use HTTPS and ensure the EIS and Unwired Server use basic authentication.
Securing Unwired Platform Runtime Component Communications
There are two different ports that require encryption: the management port for Sybase Control Center (HTTPS), and the management ports used by Unwired Server (IIOPS).
Data in Motion Worksheet
Record security setup options for data that moves from one point to another. Refer to recorded information to streamline security tasks.

Parent topic: Security Task Flows, Checklists, and Worksheets