Changes for page eMagiz Security Guide

Last modified by Erik Bakker on 2023/01/02 10:25
From version 32.1
edited by Erik Bakker
on 2023/01/02 10:24
Change comment: There is no comment for this version
To version 33.1
edited by Erik Bakker
on 2023/01/02 10:25
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -215,7 +215,7 @@
215 215  ===== 3.6.1.1 User access to https://my.emagiz.com =====
216 216  
217 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.
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.WebHome||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  
... ... @@ -223,7 +223,7 @@
223 223  
224 224  ===== 3.6.1.3 User authorizations to Integration projects. =====
225 225  
226 -Every integration project has a model owner who can distribute rights across functionalities and environments. The picture below shows the various options available across the Integration Life Cycle (ILM) Phases Capture through Manage. In addition, the model owner manages the user permissions and needs to have the MFA authentication level passed before making any changes.
226 +Every integration project has a model owner who can distribute rights across functionalities and environments. The picture below shows the various options available across the Integration Life Cycle (ILM) Phases Capture through Manage. In addition, the model owner manages the user permissions and needs to have the MFA authentication level passed before making any changes (which is asked of the model owner upon login).
227 227  
228 228  * When Edit permission is granted on an ILM phase, all the sub-options are configurable
229 229  * View rights mean that all options can be viewed only
... ... @@ -316,5 +316,5 @@
316 316  * Protecting your data is a joint responsibility between eMagiz and you
317 317  * The repository is read-only for clients
318 318  * Data in the Cloud is kept within your VPC
319 -* Production data in the portal is behind an MFA check
319 +* The portal is behind an MFA check
320 320  )))((({{toc/}}))){{/container}}{{/container}}