Changes for page eMagiz Security Guide

Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -131,10 +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		-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.
	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.
138	138
139	139	Above, we mentioned that data "in transit" is temporarily stored. This can happen in two places:
140	140
...	...	@@ -174,7 +174,6 @@
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	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"]].
177		-
178	178	==== 3.5.3 Event Streaming ====
179	179
180	180	Within the Event Streaming solution, eMagiz provides Event Streaming users, and topics can be created.
...	...	@@ -246,7 +246,7 @@
246	246
247	247	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.
248	248
249		-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.
250	250
251	251	=== 3.7 GDPR compliancy ===
252	252