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 63.1
edited by Waria
on 2026/06/23 13:06
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -131,8 +131,7 @@
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 +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.
136 136  
137 137  Above, we mentioned that data "in transit" is temporarily stored. This can happen in two places:
138 138  
... ... @@ -243,7 +243,7 @@
243 243  
244 244  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.
245 245  
246 -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.
245 +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.
247 247  
248 248  === 3.7 GDPR compliancy ===
249 249