Skip to Content

Changes for page eMagiz Security Guide

Last modified by Waria on 2026/07/23 09:35
From version 64.1
edited by Waria
on 2026/07/16 10:01
Change comment: There is no comment for this version
To version 64.2
edited by Waria
on 2026/07/23 09:32
Change comment: Renamed back-links.

Summary

Details

Page properties
Content
... ... @@ -1,4 +1,6 @@
1 -{{container}}{{container layoutStyle="columns"}}(((
1 +{{container}}
2 +{{container layoutStyle="columns"}}
3 +(((
2 2  In this fundamental, we will delve into the security perspective of the eMagiz landscape. We'll explore the cloud setup, data protection, and more to understand the role security plays in each part of the eMagiz architecture. Let's dive in!
3 3  
4 4  Should you have any questions, please get in touch with academy@emagiz.com.
... ... @@ -26,7 +26,6 @@
26 26  * Your customized flows are combined with a base image (which contains framework components to make the flows work) and are deployed into a runtime (java-based application container).
27 27  * These runtimes run on Cloud machines that contain Cloud templates (all required components to make the Cloud machine operational such as OS, Java runtime version, and more).
28 28  
29 -
30 30  [[image:Main.Images.Fundamental.WebHome@fundamental-emagiz-security-guide--emagiz-architecture.png]]
31 31  
32 32  Your flows are stored within a registry so deployments can be managed efficiently. To prevent unauthorized access to this repository, the following measures have been taken:
... ... @@ -143,8 +143,10 @@
143 143  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.
144 144  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.
145 145  
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}}
147 +{{info}}
148 +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.
149 +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.
150 +{{/info}}
148 148  
149 149  === 3.5 External data exchange ===
150 150  
... ... @@ -166,6 +166,7 @@
166 166  This way, each connection between the application and the integration (end-point) can be adequately secured and gives the flexibility to confer with the external application which method suits their needs the best.
167 167  
168 168  ==== 3.5.2 API Gateway ====
172 +
169 169  To secure the front end of the API Gateway in eMagiz rights can be assigned to users in User Management. Users are automatically created for systems integrated by the API pattern in the Portal. Next to that manual users can be added for external systems that interact with the eMagiz API Gateway. You can configure read and write rights per created operation in your model. If a user has insufficient rights for the requested action, they will receive a 401 Unauthorized.
170 170  For the backend of the API Gateway, the same logic applies as stated above for messaging, which means that eMagiz supports the industry standard. Therefore, you as a user should confer with the external party about the correct method.
171 171  
... ... @@ -173,7 +173,8 @@
173 173  
174 174  To prevent the error message if it occurs is sent straight back to the client, you can configure the front end of the API Gateway, so that correct HTTP Status codes are given back to the client, including a descriptive message.
175 175  
176 -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 API Gateway.crashcourse-api-gateway-configure-roles-and-users||target="blank"]].
180 +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 API Gateway.crashcourse-api-gateway-user-management||target="blank"]].
181 +
177 177  ==== 3.5.3 Event Streaming ====
178 178  
179 179  Within the Event Streaming solution, eMagiz provides Event Streaming users, and topics can be created.
... ... @@ -278,6 +278,7 @@
278 278  
279 279  For more information on the conceptual ideas behind data management within the eMagiz platform, you can look at this [[fundamental>>doc:Main.eMagiz Academy.Fundamentals.fundamental-traceability-in-emagiz||target="blank"]]. For more concrete information on how to implement it within an eMagiz flow you could check out this [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Advanced Level.Data Management.advanced-data-management-data-sink||target="blank"]] and this [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Advanced Level.Data Management.advanced-data-management-long-term-archiving||target="blank"]]. All the information within the data sink and the long-term archiving solution is kept within the same VPC in the Cloud and can only be accessed by authorized parties.
280 280  
286 +
281 281  === 3.9 Compliancy ===
282 282  
283 283  * eMagiz is currentlty ISO-27001 certified.
... ... @@ -298,6 +298,7 @@
298 298  * Data in the Cloud is kept within your VPC
299 299  * The portal is behind an MFA check
300 300  
307 +
301 301  == 5. Suggested additional readings ==
302 302  
303 303  * [[Fundamental (Navigation)>>doc:Main.eMagiz Academy.Fundamentals.WebHome||target="blank"]]
... ... @@ -308,7 +308,7 @@
308 308  *** [[Security - Add MFA (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-security-add-mfa.WebHome||target="blank"]]
309 309  *** [[Portal Security - Basic (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-manage-portal-security-basic||target="blank"]]
310 310  ** [[Crash Course API Gateway (Navigation)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course API Gateway.WebHome||target="blank"]]
311 -** [[Configure Roles and Users (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course API Gateway.crashcourse-api-gateway-configure-roles-and-users||target="blank"]]
318 +** [[Configure Roles and Users (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course API Gateway.crashcourse-api-gateway-user-management||target="blank"]]
312 312  ** [[Crash Course Event Streaming (Navigation)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Event Streaming.WebHome||target="blank"]]
313 313  ** [[User Management (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Event Streaming.crashcourse-eventstreaming-user-management||target="blank"]]
314 314  * [[Novice Level (Menu)>>doc:Main.eMagiz Academy.Microlearnings.Novice.WebHome||target="blank"]]
... ... @@ -318,4 +318,10 @@
318 318  ** [[Data Management (Navigation)>>doc:Main.eMagiz Academy.Microlearnings.Advanced Level.Data Management.WebHome||target="blank"]]
319 319  *** [[Data Sink (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Advanced Level.Data Management.advanced-data-management-data-sink||target="blank"]]
320 320  *** [[Long Term Archiving (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Advanced Level.Data Management.advanced-data-management-long-term-archiving||target="blank"]]
321 -)))((({{toc/}}))){{/container}}{{/container}}
328 +)))
329 +
330 +(((
331 +{{toc/}}
332 +)))
333 +{{/container}}
334 +{{/container}}