Skip to Content

Changes for page eMagiz Security Guide

Last modified by Waria on 2026/07/23 09:35
From version 56.1
edited by Waria
on 2026/06/23 11:44
Change comment: There is no comment for this version
To version 64.1
edited by Waria
on 2026/07/16 10:01
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -40,7 +40,6 @@
40 40  * Connections to the registry are always one-way SSL (encrypted) and all access is secured with a unique username/password combination.
41 41  * As mentioned above, the registry is read-only for agents and client runtimes. This means that even if someone gets their hands on a username/password combination, they do not have sufficient rights to alter anything in the registry. They can only read the data that is kept in the registry.
42 42  
43 -
44 44  === 3.2 Security Guidelines - Cloud ===
45 45  
46 46  In this section, we take a closer look at the cloud setup in general. Here we will focus on high-level security measurements because we already specified security measurements at the data level.
... ... @@ -132,10 +132,7 @@
132 132  [[image:Main.Images.Fundamental.WebHome@fundamental-emagiz-security-guide--data-orchestration.png]]
133 133  
134 134  Data "in transit" is temporarily stored on an encrypted filesystem with the help of encryption algorithms.
135 -For the Cloud, eMagiz uses the AES-256 encryption algorithm.
136 -For on-premise runtime installations, eMagiz uses the AES-128 encryption algorithm.
137 -These algorithms ensure that even if third parties could get to the data on that encrypted filesystem, they won't be able to read the data.
138 -That way, the data is kept confidential.
134 +These algorithms ensure that even if third parties could get to the data on that encrypted filesystem, they won't be able to read the data. That way, the data is kept confidential. The [[runtime images release notes>>doc:Main.Release Information.Runtime Images.WebHome||target="blank"]] mention the currently enabled cipher suites in case they have changed.
139 139  
140 140  Above, we mentioned that data "in transit" is temporarily stored. This can happen in two places:
141 141  
... ... @@ -147,6 +147,9 @@
147 147  To ensure data integrity in the transport layer of eMagiz, it uses the TLS protocol. This means that all client-server communication is secured via TLS. In eMagiz, this is implemented as follows: The necessary certificates of the client(s) are trusted by the server, and the server is trusted by the client(s). The relevant information is stored in key stores and truststores that are unique per integration project (ll the integration configurations made to a single eMagiz instance spread across the ILM Phase from Capture to Manage). This ensures that data cannot be sent to other client projects or other environments within your project.
148 148  In other words, it prevents others from eavesdropping on your channels. eMagiz follows the standard guidelines when setting up TLS. Therefore, we ensure that the configured trusted certificate authority (CA) bundle that your messaging server uses to verify client connections is limited to only the CA used for your nodes, preferably an internally managed CA.
149 149  
146 +{{info}}Note: eMagiz is secure by design and, therefore, advises against the use of Deep Packet Inspection (DPI) and SSL bridging. These technologies intercept, inspect and re-encrypt encrypted traffic, which can interfere with the certificate-based trust chains used by eMagiz. As a result, connections may be identified as a man-in-the-middle attempt and rejected.
147 +In case DPI and SSL bridging is required by your organization, at least network traffic between your runtimes and the eMagiz backend must be excluded for your eMagiz model to work properly.{{/info}}
148 +
150 150  === 3.5 External data exchange ===
151 151  
152 152  Because eMagiz provides the integration between two or more applications via the eMagiz platform, the point at which the data is interchanged between application and integration is a critical part of the integration in terms of security.
... ... @@ -188,7 +188,6 @@
188 188  
189 189  For more information on how this precisely can be configured via the eMagiz platform, please check the following [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Event Streaming.crashcourse-eventstreaming-user-management||target="blank"]].
190 190  
191 -
192 192  === 3.6 eMagiz iPaaS Portal ===
193 193  
194 194  The eMagiz portal provides access to users to manage their eMagiz integration configurations. It provides access to all the features to develop, deploy and manage integrations across Test, Acceptance, and Production environments.
... ... @@ -247,7 +247,7 @@
247 247  
248 248  Monitoring your (Production) environment helps you monitor and detect deviations within your environment in near real-time. The ILM phase Manage provides access to errors logs generated in message processing by the platform and monitoring logs of the Cloud components and eMagiz runtimes. All errors and relevant logging is stored for a limited period (two weeks) within eMagiz for auditing or reporting purposes. Furthermore, notifications can be sent to people to alert them of a potential loss of data integrity. These alerts can contain a warning or the actual error that occurred.
249 249  
250 -If specific messages are processed but result in validation errors or other errors, the message is sent to the error stack. The developer can view the actual message, including the content, to understand the error reported adequately. For example, the eMagiz store holds a specific transformation (Mask XSLT) that can mask all the fields of the XML message sent to the error stack. It can mask all the fields or only specific fields that contain sensitive data. Clients are requested to make this assessment per integration advised by the eMagiz Partner. In future versions of eMagiz, particular attributes of entities in System Messages or CDM messages can be flagged, so the platform automatically takes care of this feature.
248 +If specific messages are processed but result in validation errors or other errors, the message is sent to the error stack. The developer can view the actual message, including the content, to understand the error reported adequately. For example, the eMagiz store holds a specific transformation (Mask XSLT) that can mask all the fields of the XML message sent to the error stack. It can mask all the fields or only specific fields that contain sensitive data. Clients are requested to make this assessment per integration advised by the eMagiz Partner.
251 251  
252 252  === 3.7 GDPR compliancy ===
253 253