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 62.1
edited by Waria
on 2026/06/23 12:59
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  
... ... @@ -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.