## 13.6.2.2.1  Network and Communication Channel Security
The information below shows the communication channels used, the protocol used for the connection, and the type of data transferred.
## Connection to a SAP FSCM System
For Global Trade Management, you have the option to use an external SAP FSCM system to create forward exchange transactions. If you install SAP FSCM on a separate system, you require an RFC connection. If you install SAP FSCM together with Global Trade Management on one system, no RFC connection is necessary.
| Communication Path                                                       | Protocol Used   | Type of Data Transferred   | Data Requiring Special Pro- tection   |
|--------------------------------------------------------------------------|-----------------|----------------------------|---------------------------------------|
| SAP S/4HANAsystem - SAP FSCMsystem (Financial Sup- ply Chain Management) | RFC             | Application data           | n/a                                   |
RFC connections can be protected using Secure Network Communications ( SNC ). For more information about setting up the RFC connection, and the prerequisites (authorizations), see Customizing for SAP S/4HANA under Logistics General Global Trade Management Currency Hedging Maintain RFC Destination of CFM System .
## Connection to an External Global Trade Services System
You can connect Global Trade Management to an external Global Trade Services (GTS) system in order to check whether the contract data for Global Trade Management adheres to the prevailing legal requirements (import/export controls, global trade data).
| Communication Path              | Protocol Used   | Type of Data Transferred   | Data Requiring Special Pro- tection   |
|---------------------------------|-----------------|----------------------------|---------------------------------------|
| SAP S/4HANA system - GTS system | RFC             | Application data           | n/a                                   |
All users in the SAP S/4HANA system can call the functions on the GTS server using an RFC entry. In this RFC entry, you specify a user that is used uniquely for communication with GTS. Assign this communication user to the following roles for SAP Compliance Management.
Roles for Compliance Management
| Role                    | Description                       |
|-------------------------|-----------------------------------|
| /SAPSLL/LEG_ARCH GTS    | Archiving                         |
| /SAPSLL/LEG_LCE_APP GTS | Legal Control Export: Specialist  |
| /SAPSLL/LEG_LCI_APP GTS | Legal Control Import: Specialist  |
| /SAPSLL/LEG_SPL_APP GTS | Sanctioned Party List: Specialist |
| /SAPSLL/LEG_SYS_COMM GTS   | (Technical) System Communication   |
|----------------------------|------------------------------------|
DIAG and RFC connections can be protected using Secure Network Communications (SNC). HTTP connections are protected using the Secure Sockets Layer (SSL) protocol. SOAP connections are protected with Web services security.
##  Note
We strongly recommend using secure protocols (SSL, SNC) whenever possible.
For more information, see Transport Layer Security and Web Services Security in the ABAP Platform Security Guide.