Changes for page eMagiz Security Guide

Last modified by Erik Bakker on 2024/08/20 08:53

From 12.1 to 11.1 From 26.1 to 25.1

From version 25.1

edited by Erik Bakker
on 2022/06/13 14:11

Change comment: There is no comment for this version

To version 12.1

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

Change comment: There is no comment for this version

Raw
Rendered

Summary

Page properties (4 modified, 0 added, 0 removed)
Attachments (0 modified, 7 added, 0 removed)

Details

Page properties

Title

...	...	@@ -1,1 +1,0 @@
1		-eMagiz Security Guide

Parent

...	...	@@ -1,1 +1,0 @@
1		-WebHome

Author

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

Content

@@ -1,8 +1,19 @@
--{{container}}{{container layoutStyle="columns"}}(((
++{{html wiki="true"}}
++<div class="ez-academy">
++    <div class="ez-academy_body">
++<div class="doc">
++
++
++
++= eMagiz Security Guide =
++
  In this fundamental, we will zoom in on how the various parts of the eMagiz landscape can be viewed from a Security perspective. We will look at the Cloud, on-premises, data within eMagiz, external communication, and the portal during our journey. After this journey, you should have a solid understanding of what role security plays in each of the parts of the eMagiz architecture. Note that protecting your data is a joint responsibility between eMagiz and you. This fundamental aims to clarify the security measures eMagiz has taken in the eMagiz platform. This way, you can assess the eventual additional steps you need to take to ensure that the eMagiz service cooperates securely with the rest of your application and integration landscape.
  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.
@@ -14,6 +14,8 @@
  * Data in the Cloud is kept within your VPC
  * Production data in the portal is behind an MFA check
++
++
  == 3. eMagiz Security Guide ==
  In this fundamental, we will zoom in on how the various parts of the eMagiz landscape can be viewed from a Security perspective. We will look at the Cloud, on-premises, data within eMagiz, external communication, and the portal during our journey. After this journey, you should have a solid understanding of what role security plays in each of the parts of the eMagiz architecture. Note that protecting your data is a joint responsibility between eMagiz and you. This fundamental aims to clarify the security measures eMagiz has taken in the eMagiz platform. This way, you can assess the eventual additional steps you need to take to ensure that the eMagiz service cooperates securely with the rest of your application and integration landscape.
@@ -35,7 +35,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.
--[[image:Main.Images.Fundamental.WebHome@fundamental-emagiz-security-guide--definition-emagiz-model.png]]
++<p align="center">[[image:fundamental-emagiz-security-guide--definition-emagiz-model.png||]]</p>
  === 3.2 Security Guidelines * Cloud ===
@@ -46,7 +46,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.'
--[[image:Main.Images.Fundamental.WebHome@fundamental-emagiz-cloud-inner-workings--customer-level-overview-double-lane.png]]
++<p align="center">[[image:fundamental-emagiz-cloud-inner-workings--customer-level-overview-double-lane.png||]]</p>
  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.
@@ -73,7 +73,7 @@
  * Monitoring
  * Notification options
--Making sure you are on the latest cloud template version guards yourself against vulnerabilities in older versions of Java and OS, for example. In addition, it gives the user more options for monitoring the health of the cloud environment reducing the risk of a loss of availability of data (promptly) without compromising the integrity of the data. For more information on what cloud templates are and how to control and update them, please check out this [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Novice.eMagiz Cloud Management.novice-emagiz-cloud-management-cloud-templates-explained.WebHome||target="blank"]].
++Making sure you are on the latest cloud template version guards yourself against vulnerabilities in older versions of Java and OS, for example. In addition, it gives the user more options for monitoring the health of the cloud environment reducing the risk of a loss of availability of data (promptly) without compromising the integrity of the data. For more information on what cloud templates are and how to control and update them, please check out this [microlearning](../microlearning/novice-emagiz-cloud-management-cloud-templates-explained.md).
  ==== 3.2.5 Carwash ====
@@ -117,7 +117,7 @@
  Support engineers can see more to analyze problems on a lower level.
--All other users don't have access to the cloud setup as there is no need for access because they can perform the relevant actions on the Cloud via the eMagiz portal. For more information on how please see the [[eMagiz Cloud Management>>doc:Main.eMagiz Academy.Microlearnings.Novice.eMagiz Cloud Management.WebHome||target="blank"]] course.
++All other users don't have access to the cloud setup as there is no need for access because they can perform the relevant actions on the Cloud via the eMagiz portal. For more information on how please see the [eMagiz Cloud Management](../microlearning/novice-emagiz-cloud-management-index) course.
  ===== 3.3.2.1 Rights for installing =====
@@ -135,7 +135,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.
--[[image:Main.Images.Fundamental.WebHome@fundamental-emagiz-security-guide--data-orchestration.png]]
++<p align="center">[[image:fundamental-emagiz-security-guide--data-orchestration.png||]]</p>
  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.
@@ -180,7 +180,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
--[[image:Main.Images.Fundamental.WebHome@fundamental-emagiz-security-guide--api-gateway-portal-feedback.png]]
++<p align="center">[[image:fundamental-emagiz-security-guide--api-gateway-portal-feedback.png||]]</p>
  ===== 3.5.2.2 External IDP =====
@@ -194,7 +194,8 @@
  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.
--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.WebHome||target="blank"]].
++For more information on how this precisely can be configured via the eMagiz platform, please check the following [microlearning](../microlearning/crashcourse-api-gateway-configure-roles-and-users.md)
++
  ==== 3.5.3 Event Streaming ====
  Within the Event Streaming solution, eMagiz provides Event Streaming users, and topics can be created.
@@ -206,7 +206,7 @@
  These are all security measures to prevent third parties from getting unauthorized access to the data stored on the topics.
--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"]].
++For more information on how this precisely can be configured via the eMagiz platform, please check the following [microlearning](../microlearning/crashcourse-eventstreaming-user-management.md)
  === 3.6 eMagiz iPaaS Portal ===
@@ -233,7 +233,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
--[[image:Main.Images.Fundamental.WebHome@fundamental-emagiz-security-guide--access-rights.png]]
++<p align="center">[[image:fundamental-emagiz-security-guide--access-rights.png||]]</p>
  ===== 3.6.1.4 Partner user access to Client environments =====
@@ -254,9 +254,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.
--[[image:Main.Images.Fundamental.WebHome@fundamental-emagiz-security-guide--create-new-version.png]]
++<p align="center">[[image:fundamental-emagiz-security-guide--create-new-version.png||]]</p>
--[[image:Main.Images.Fundamental.WebHome@fundamental-emagiz-security-guide--history-pages.png]]
++<p align="center">[[image:fundamental-emagiz-security-guide--history-pages.png||]]</p>
  * 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.
@@ -298,7 +298,7 @@
  ==== 3.8.4 Data management ====
--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.
++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](../microlearning/advanced-data-management-data-sink.md) and this [microlearning](../microlearning/advanced-data-management-long-term-archiving.md). 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.
  === 3.9 Compliancy ===
@@ -312,6 +312,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
@@ -318,4 +318,9 @@
  * 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
--)))((({{toc/}}))){{/container}}{{/container}}
++
++</div>
++</div>
++</div>
++
++{{/html}}

fundamental-emagiz-cloud-inner-workings--customer-level-overview-double-lane.png

Author

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

Size

...	...	@@ -1,0 +1,1 @@
	1	+65.2 KB

Content

fundamental-emagiz-security-guide--access-rights.png

Author

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

Size

...	...	@@ -1,0 +1,1 @@
	1	+9.1 KB

Content

fundamental-emagiz-security-guide--api-gateway-portal-feedback.png

Author

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

Size

...	...	@@ -1,0 +1,1 @@
	1	+14.7 KB

Content

fundamental-emagiz-security-guide--create-new-version.png

Author

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

Size

...	...	@@ -1,0 +1,1 @@
	1	+23.6 KB

Content

fundamental-emagiz-security-guide--data-orchestration.png

Author

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

Size

...	...	@@ -1,0 +1,1 @@
	1	+160.8 KB

Content

fundamental-emagiz-security-guide--definition-emagiz-model.png

Author

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

Size

...	...	@@ -1,0 +1,1 @@
	1	+63.3 KB

Content

fundamental-emagiz-security-guide--history-pages.png

Author

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

Size

...	...	@@ -1,0 +1,1 @@
	1	+22.5 KB

Content

Changes for page eMagiz Security Guide

Summary

Details

Navigation