Skip to main content

LSEG (Reuters) Messenger Overview

This overview explains how LSEG Messenger capture works in MCO eComms, including the available log acquisition methods, how messages are brought into the archive, and why user mapping is required for retention and monitoring policies to apply.

What is LSEG Messenger capture?

LSEG Messenger capture brings supported LSEG Messenger communications into MCO eComms so they can be retained, monitored, and reviewed according to your organization’s electronic communications policy.

Overview

LSEG Messenger, previously known as Reuters Messenger and Eikon Messenger, is a messaging platform used by financial services professionals for business communications. These communications can include business records that compliance teams need to preserve and supervise.

MCO eComms supports LSEG Messenger capture through two log acquisition methods: direct connection with LSEG or client-managed Secure File Transfer Protocol (SFTP) transfer. In both methods, logs must be exported in the supported Reuters format before they can be imported into MCO eComms.

User mapping is required so MCO eComms can associate LSEG Messenger communications with the correct user profiles. When messages are mapped to users, the appropriate retention and detection policies apply to future communications.

Supported acquisition methods

Method

Description

Direct connect with LSEG

MCO acquires logs directly from LSEG and manages the import process with minimal client IT involvement.

Client-managed SFTP transfer

Your organization acquires the logs from LSEG in the supported format and places them in an MCO-managed SFTP location.

How it works

Step

Description

Confirm the acquisition method

Your organization chooses either direct connection with LSEG or client-managed SFTP transfer.

Confirm LSEG access

For direct connection, your organization confirms it has the required Reuters account access for granting permissions.

Exchange connection details

For direct connection, MCO provides the IP address, Pretty Good Privacy (PGP) key, and passphrase needed for secure log delivery.

Export logs

LSEG Messenger logs are exported in the supported Reuters format.

Transfer logs

Logs are either acquired directly by MCO from LSEG or placed by your organization in an MCO-managed SFTP location.

Import communications

MCO eComms imports the supported LSEG Messenger logs into the archive.

Map users

Admin users map LSEG Messenger identities to MCO eComms user profiles.

Apply policies

Once messages are mapped, configured retention and detection policies apply to future LSEG Messenger communications.

Review communications

Compliance users can search, monitor, and review captured LSEG Messenger communications in MCO eComms.

User mapping

LSEG Messenger users are mapped in MCO eComms by the email address or identity used to identify the user in LSEG Messenger. These identifiers can be mapped to the primary email address on the user profile or added as additional source mappings.

After a mapping is saved, newly arriving LSEG Messenger messages that match the mapped identifier are associated with that user. Once the messages are mapped, the user’s retention and detection policies apply to future LSEG Messenger communications.

IMPORTANT: New source mappings update existing messages and alerts for search and display reference purposes. They do not retroactively apply retention and detection policies to messages already in MCO eComms.

Did this answer your question?