Changes for page eMagiz Security Guide

Last modified by Erik Bakker on 2023/01/02 10:25

From 12.1 to 13.1 From 14.1 to 15.1

From version 13.1

edited by eMagiz
on 2022/06/13 09:34

Change comment: There is no comment for this version

To version 14.1

edited by Erik Bakker
on 2022/06/13 12:37

Change comment: Imported from XAR

Raw
Rendered

Summary

Page properties (2 modified, 0 added, 0 removed)

Details

Page properties

Author

@@ -1,1 +1,1 @@
--XWiki.marijn
++XWiki.ebakker

Content

@@ -1,7 +1,4 @@
--{{html wiki="true"}}
--<div class="ez-academy">
--    <div class="ez-academy_body">
--<div class="doc">
++{{container}}{{container layoutStyle="columns"}}(((
@@ -11,9 +11,6 @@
  Should you have any questions, please get in touch with academy@emagiz.com.
--* Last update: February 17th, 2022
--* Required reading time: 15 minutes
--
  == 1. Prerequisites ==
  * Some context on cloud functionality will be helpful.
@@ -48,7 +48,7 @@
  * A bitbucket pipeline will be created soon to enable automatic updates. This data pipeline will also need a unique username/password combination along with the fact that the connection itself is a one-way SSL connection (encrypted)
  * The repository is read-only for clients. This means that even if someone gets their hands on a username/password combination, they do not have sufficient rights to alter anything in the repository. They can only read the data that is kept in the repository.
--<p align="center">[[image:fundamental-emagiz-security-guide--definition-emagiz-model.png||]]</p>
++[[image:Main.Images.Fundamental.WebHome@fundamental-emagiz-security-guide--definition-emagiz-model.png]]
  === 3.2 Security Guidelines * Cloud ===
@@ -59,7 +59,7 @@
  The picture below shows a standard double-lane setup of an eMagiz instance within the eMagiz Cloud. A single-lane design looks similar but only consists of one core machine.
  This gives insight into how messages flow through the Cloud, which measures are taken for monitoring and auto-healing, and where data is temporarily stored 'in transit.'
--<p align="center">[[image:fundamental-emagiz-cloud-inner-workings--customer-level-overview-double-lane.png||]]</p>
++[[image:Main.Images.Fundamental.WebHome@fundamental-emagiz-cloud-inner-workings--customer-level-overview-double-lane.png]]
  We want to use this picture to explain specific components within the Cloud from a security perspective. We will start at the outside and work our way inwards.
@@ -148,7 +148,7 @@
  Let us first look at the data "in transit." This is the process phase where data is interchanged between flows within the eMagiz platform. This data interchange goes (i.e., from entry to onramp or offramp to exit) via the orchestration of the JMS server on the messaging layer. This is nicely shown in the picture below.
--<p align="center">[[image:fundamental-emagiz-security-guide--data-orchestration.png||]]</p>
++[[image:Main.Images.Fundamental.WebHome@fundamental-emagiz-security-guide--data-orchestration.png]]
  Data "in transit" is temporarily stored on an encrypted filesystem with the help of encryption algorithms.
  For the Cloud, eMagiz uses the AES-256 encryption algorithm.
@@ -193,7 +193,7 @@
  As you can see in the picture shown below, the roles are defined so that the Read role can only access two integrations available for this specific API Gateway. If a client has insufficient rights, they will receive a 401 Unauthorized
--<p align="center">[[image:fundamental-emagiz-security-guide--api-gateway-portal-feedback.png||]]</p>
++[[image:Main.Images.Fundamental.WebHome@fundamental-emagiz-security-guide--api-gateway-portal-feedback.png]]
  ===== 3.5.2.2 External IDP =====
@@ -247,7 +247,7 @@
  * Model owners are assigned to integration projects by eMagiz Administrators
  * An audit trail is kept of the changes made in the project permission structure
--<p align="center">[[image:fundamental-emagiz-security-guide--access-rights.png||]]</p>
++[[image:Main.Images.Fundamental.WebHome@fundamental-emagiz-security-guide--access-rights.png]]
  ===== 3.6.1.4 Partner user access to Client environments =====
@@ -268,9 +268,9 @@
  * In all the relevant parts of the integration project, developers can version the changes made. The type (major, minor, or patch) can be indicated and commented on to describe the change. Once the version is created, that particular version will be available for Deployment and is then kept in the history of changes on a low level. Both are illustrated in the pictures below.
--<p align="center">[[image:fundamental-emagiz-security-guide--create-new-version.png||]]</p>
++[[image:Main.Images.Fundamental.WebHome@fundamental-emagiz-security-guide--create-new-version.png]]
--<p align="center">[[image:fundamental-emagiz-security-guide--history-pages.png||]]</p>
++[[image:Main.Images.Fundamental.WebHome@fundamental-emagiz-security-guide--history-pages.png]]
  * On a CDM level, the same functionality exists to indicate the version type incl. comments. All changes to the CDM model are logged in an audit trail that can help understand what changes are made by who in case of error resolution. The CDM is also protected by the permission structure of the Integration project.
@@ -326,8 +326,8 @@
  During these tests, the pentester will try to achieve goals (penetration of the target system on various levels) by undertaking various means. Such a test can help determine whether a system is vulnerable to attack if the defenses were sufficient and which defenses (if any) the test defeated. In addition, eventual findings from those tests are dealt with conforming to the corrective action processes in our ISMS.
--===== Practice =====
++
  == 4. Key takeaways ==
  * Protecting your data is a joint responsibility between eMagiz and you
@@ -334,9 +334,4 @@
  * The repository is read-only for clients
  * Data in the Cloud is kept within your VPC
  * Production data in the portal is behind an MFA check
--
--</div>
--</div>
--</div>
--
--{{/html}}
++)))((({{toc/}}))){{/container}}{{/container}}

Changes for page eMagiz Security Guide

Summary

Details

Navigation