Skip to Content

Changes for page eMagiz Security Guide

Last modified by Waria on 2026/07/23 09:35
From version 61.1
edited by Waria
on 2026/06/23 12:57
Change comment: There is no comment for this version
To version 55.1
edited by Waria
on 2026/06/23 11:43
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -22,10 +22,10 @@
22 22  
23 23  eMagiz consists of various components communicating to develop the process layer and subsequently run the message layer as secure and stable as possible for our customers.
24 24  
25 -* In the eMagiz integration project, various flows are created that work together to realize the integration. The different types are shown on the top of the picture below.
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 -* 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  
26 +1. In the eMagiz integration project, various flows are created that work together to realize the integration. The different types are shown on the top of the picture below.
27 +2. 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).
28 +3. 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).
29 29  
30 30  [[image:Main.Images.Fundamental.WebHome@fundamental-emagiz-security-guide--emagiz-architecture.png]]
31 31  
... ... @@ -40,6 +40,7 @@
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 +
43 43  === 3.2 Security Guidelines - Cloud ===
44 44  
45 45  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.
... ... @@ -131,8 +131,10 @@
131 131  [[image:Main.Images.Fundamental.WebHome@fundamental-emagiz-security-guide--data-orchestration.png]]
132 132  
133 133  Data "in transit" is temporarily stored on an encrypted filesystem with the help of encryption algorithms.
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.
135 -The runtime image release notes mention the currently enabled cipher suites in case they have changed: [[Runtime Images release notes>>doc:Main.Release Information.Runtime Images.WebHome||target="blank"]]
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.
136 136  
137 137  Above, we mentioned that data "in transit" is temporarily stored. This can happen in two places:
138 138  
... ... @@ -164,6 +164,7 @@
164 164  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.
165 165  
166 166  ==== 3.5.2 API Gateway ====
170 +
167 167  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.
168 168  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.
169 169  
... ... @@ -185,6 +185,7 @@
185 185  
186 186  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"]].
187 187  
192 +
188 188  === 3.6 eMagiz iPaaS Portal ===
189 189  
190 190  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.