Changes for page eMagiz Security Guide

Summary

• Page properties (4 modified, 0 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 @@
1		-XWiki.ebakker
	1	+XWiki.marijn

Content

...	...	@@ -1,8 +1,19 @@
1		-{{container}}{{container layoutStyle="columns"}}(((
	1	+{{html wiki="true"}}
	2	+<div class="ez-academy">
	3	+ <div class="ez-academy_body">
	4	+<div class="doc">
	5	+
	6	+
	7	+
	8	+= eMagiz Security Guide =
	9	+
2	2	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.
3	3
4	4	Should you have any questions, please get in touch with academy@emagiz.com.
5	5
	14	+* Last update: February 17th, 2022
	15	+* Required reading time: 15 minutes
	16	+
6	6	== 1. Prerequisites ==
7	7
8	8	* Some context on cloud functionality will be helpful.
...	...	@@ -14,6 +14,8 @@
14	14	* Data in the Cloud is kept within your VPC
15	15	* Production data in the portal is behind an MFA check
16	16
	28	+
	29	+
17	17	== 3. eMagiz Security Guide ==
18	18
19	19	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 @@
35	35	* 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)
36	36	* 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.
37	37
38		-[[image:Main.Images.Fundamental.WebHome@fundamental-emagiz-security-guide--definition-emagiz-model.png]]
	51	+<p align="center">[[image:fundamental-emagiz-security-guide--definition-emagiz-model.png||]]</p>
39	39
40	40	=== 3.2 Security Guidelines * Cloud ===
41	41
...	...	@@ -46,7 +46,7 @@
46	46	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.
47	47	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.'
48	48
49		-[[image:Main.Images.Fundamental.WebHome@fundamental-emagiz-cloud-inner-workings--customer-level-overview-double-lane.png]]
	62	+<p align="center">[[image:fundamental-emagiz-cloud-inner-workings--customer-level-overview-double-lane.png||]]</p>
50	50
51	51	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.
52	52
...	...	@@ -135,7 +135,7 @@
135	135
136	136	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.
137	137
138		-[[image:Main.Images.Fundamental.WebHome@fundamental-emagiz-security-guide--data-orchestration.png]]
	151	+<p align="center">[[image:fundamental-emagiz-security-guide--data-orchestration.png||]]</p>
139	139
140	140	Data "in transit" is temporarily stored on an encrypted filesystem with the help of encryption algorithms.
141	141	For the Cloud, eMagiz uses the AES-256 encryption algorithm.
...	...	@@ -180,7 +180,7 @@
180	180
181	181	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
182	182
183		-[[image:Main.Images.Fundamental.WebHome@fundamental-emagiz-security-guide--api-gateway-portal-feedback.png]]
	196	+<p align="center">[[image:fundamental-emagiz-security-guide--api-gateway-portal-feedback.png||]]</p>
184	184
185	185	===== 3.5.2.2 External IDP =====
186	186
...	...	@@ -234,7 +234,7 @@
234	234	* Model owners are assigned to integration projects by eMagiz Administrators
235	235	* An audit trail is kept of the changes made in the project permission structure
236	236
237		-[[image:Main.Images.Fundamental.WebHome@fundamental-emagiz-security-guide--access-rights.png]]
	250	+<p align="center">[[image:fundamental-emagiz-security-guide--access-rights.png||]]</p>
238	238
239	239	===== 3.6.1.4 Partner user access to Client environments =====
240	240
...	...	@@ -255,9 +255,9 @@
255	255
256	256	* 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.
257	257
258		-[[image:Main.Images.Fundamental.WebHome@fundamental-emagiz-security-guide--create-new-version.png]]
	271	+<p align="center">[[image:fundamental-emagiz-security-guide--create-new-version.png||]]</p>
259	259
260		-[[image:Main.Images.Fundamental.WebHome@fundamental-emagiz-security-guide--history-pages.png]]
	273	+<p align="center">[[image:fundamental-emagiz-security-guide--history-pages.png||]]</p>
261	261
262	262	* 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.
263	263
...	...	@@ -313,6 +313,8 @@
313	313
314	314	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.
315	315
	329	+===== Practice =====
	330	+
316	316	== 4. Key takeaways ==
317	317
318	318	* Protecting your data is a joint responsibility between eMagiz and you
...	...	@@ -319,4 +319,9 @@
319	319	* The repository is read-only for clients
320	320	* Data in the Cloud is kept within your VPC
321	321	* Production data in the portal is behind an MFA check
322		-)))((({{toc/}}))){{/container}}{{/container}}
	337	+
	338	+</div>
	339	+</div>
	340	+</div>
	341	+
	342	+{{/html}}