Skip to Content

Changes for page eMagiz Security Guide

Last modified by Erik Bakker on 2024/08/20 08:53
From version 30.1
edited by Erik Bakker
on 2023/01/02 10:10
Change comment: There is no comment for this version
To version 32.1
edited by Erik Bakker
on 2023/01/02 10:24
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -12,7 +12,7 @@
12 12  * Protecting your data is a joint responsibility between eMagiz and you
13 13  * The repository is read-only for clients
14 14  * Data in the Cloud is kept within your VPC
15 -* Production data in the portal is behind an MFA check
15 +* The portal is behind an MFA check
16 16  
17 17  == 3. eMagiz Security Guide ==
18 18  
... ... @@ -204,7 +204,7 @@
204 204  
205 205  These are all security measures to prevent third parties from getting unauthorized access to the data stored on the topics.
206 206  
207 -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.WebHome||target="blank"]].
207 +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"]].
208 208  
209 209  === 3.6 eMagiz iPaaS Portal ===
210 210  
... ... @@ -214,8 +214,8 @@
214 214  
215 215  ===== 3.6.1.1 User access to https://my.emagiz.com =====
216 216  
217 -Users can be added with their email address by the eMagiz Partner Manager, upon which the user gets an email to sign in. A temporary password is created and emailed, which has to be changed at the first login to the iPaaS portal. In addition, users are connected to organizations in eMagiz.
218 -In the administration section of the user, an MFA token can be used to enable the Multifactor Authentication on a user level. Typical authenticators on a smartphone can be used, such as Google Authenticator. An MFA response is required for model owners to manage the permissions on a project level and any Edit activity in Production environments. See the following sections for more details on these functions.
217 +Users can be added with their email address by the eMagiz Partner Manager or by their company contact, upon which the user gets an email to sign in. A temporary password is created and emailed, which has to be changed at the first login to the iPaaS portal. In addition, users are connected to organizations in eMagiz.
218 +In the administration section of the user, upon first login an MFA configuration needs to be executed by the user so they can access models to which they have been granted rights. Typical authenticators on a smartphone can be used, such as Google Authenticator. For more information, check out this [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-security-add-mfa||target="blank"]]. An MFA response is required for model owners to manage the permissions on a model level. See the following sections for more details on these functions.
219 219  
220 220  ===== 3.6.1.2 Users access to Integration Projects =====
221 221  
... ... @@ -296,11 +296,12 @@
296 296  
297 297  ==== 3.8.4 Data management ====
298 298  
299 -For more information on the conceptual ideas behind data management within the eMagiz platform, you can look at this [fundamental](fundamental-traceability-in-emagiz.md). For more concrete information on how to implement it within an eMagiz flow you could check out this [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Advanced Level.Data Management.advanced-data-management-data-sink.WebHome||target="blank"]] and this [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Advanced Level.Data Management.advanced-data-management-long-term-archiving.WebHome||target="blank"]]. All the information within the data sink and the long-term archiving solution is kept within the same VPC in the Cloud and can only be accessed by authorized parties.
299 +For more information on the conceptual ideas behind data management within the eMagiz platform, you can look at this [fundamental](fundamental-traceability-in-emagiz.md). For more concrete information on how to implement it within an eMagiz flow you could check out this [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Advanced Level.Data Management.advanced-data-management-data-sink||target="blank"]] and this [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Advanced Level.Data Management.advanced-data-management-long-term-archiving||target="blank"]]. All the information within the data sink and the long-term archiving solution is kept within the same VPC in the Cloud and can only be accessed by authorized parties.
300 300  
301 301  === 3.9 Compliancy ===
302 302  
303 -* eMagiz has the ISO-27001 certification at this moment.
303 +* eMagiz is currentlty ISO-27001 certified.
304 +* eMagiz is currently SOC2 Type 2 certified.
304 304  
305 305  === 3.10 Other ===
306 306