Changes for page eMagiz Security Guide
Last modified by Waria on 2026/07/23 09:35
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -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"]] 134 +For the Cloud, eMagiz uses the AES-256 encryption algorithm. 135 +For on-premise runtime installations, eMagiz uses the AES-128 encryption algorithm. 136 +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. 137 +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 ... ... @@ -172,6 +172,7 @@ 172 172 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. 173 173 174 174 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"]]. 177 + 175 175 ==== 3.5.3 Event Streaming ==== 176 176 177 177 Within the Event Streaming solution, eMagiz provides Event Streaming users, and topics can be created.