Communication Channel Security (SAP Library - SAP ERP Central Component Security Guide)

Communication Channel Security

Use

The following table contains the communication paths used by MIC, the protocol used for the connection, and the type of data transferred.

Communication paths

Communication Path	Protocol Used	Type of Data Transferred	Data Requiring Special Protection
Front end client using SAP GUI for Windows to application server	DIAG	All application data	Passwords
Front end client using a Web browser to application server	HTTP/HTTPS	All application data	Passwords
Audit Information System (AIS) to application server	RFC for setting up AIS integration HTTP for displaying the AIS reports	AIS reports
External application via XI interface to application server	External application – XI: Various protocols possible (SAP standard) XI – application server: RFC	Structure data (such as central process catalog) Test logs
Application server to BI system	RFC	All application data

DIAG and RFC connections can be protected using Secure Network Communications (SNC). HTTPS connections are protected using the Secure Sockets Layer (SSL) protocol. For more information, see Transport Layer Security in the SAP NetWeaver Security Guide.

Note

For logon to the front end client (Web browser), Single Sign-On (SSO2) must be activated on the server side. For more information, see SAP Note 517860.

Navigation information is communicated between the start page and the Web applications via the URL.