Skip to Content
Last modified by Erik Bakker on 2024/09/03 09:17
From version 10.1
edited by Erik Bakker
on 2022/10/03 14:49
Change comment: There is no comment for this version
To version 7.2
edited by Erik Bakker
on 2022/06/23 16:14
Change comment: Update document after refactoring.

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -Error Handling concerning GDPR
1 +advanced-understanding-error-handling-in-emagiz-error-handling-gdpr
Default language
... ... @@ -1,1 +1,0 @@
1 -en
Content
... ... @@ -1,8 +1,13 @@
1 1  {{container}}{{container layoutStyle="columns"}}(((
2 += Error Handling concerning GDPR =
3 +
2 2  In eMagiz, all errors are raised when a process fails, and you want to have some form of logging end up in the Manage phase of eMagiz. The Manage phase of eMagiz is primarily accessible to support employees, employees working on the project, and in some cases, even more, people have at least view rights. You can imagine that when many people have access to potentially sensitive data, you should consider countermeasures. This way, you can reduce the chances of sensitive data ending up in the wrong hands. Some of the potential countermeasures are available within the platform. Some of them are procedural in nature. In this microlearning, we will learn what you can do to keep your data safe within eMagiz.
3 3  
4 4  Should you have any questions, don't hesitate to get in touch with [[academy@emagiz.com>>mailto:academy@emagiz.com]].
5 5  
8 +* Last update: November 15th, 2021
9 +* Required reading time: 5 minutes
10 +
6 6  == 1. Prerequisites ==
7 7  
8 8  * Advanced knowledge of the eMagiz platform
... ... @@ -16,6 +16,8 @@
16 16  * eMagiz has various security measures in place to keep your data safe
17 17  * You also have a responsibility as a user how you use the data of the customer
18 18  
24 +
25 +
19 19  == 3. Error Handling regarding GDPR ==
20 20  
21 21  In eMagiz, all errors are raised when a process fails, and you want to have some form of logging end up in the Manage phase of eMagiz. The Manage phase of eMagiz is primarily accessible to support employees, employees working on the project, and in some cases, even more, people have at least view rights. You can imagine that when many people have access to potentially sensitive data, you should consider countermeasures. This way, you can reduce the chances of sensitive data ending up in the wrong hands. Some of the potential countermeasures are available within the platform. Some of them are procedural in nature. In this microlearning, we will learn what you can do to keep your data safe within eMagiz.
... ... @@ -28,6 +28,8 @@
28 28  
29 29  In terms of process, you should know which data is sensitive in terms of GDPR and **not** store that information in external tools such as Postman and SOAP UI. Furthermore, it would be best to consider how you want to shape the notifications to prevent sensitive information from being willingly distributed to the eMail boxes of recipients.
30 30  
38 +
39 +
31 31  == 4. Assignment ==
32 32  
33 33  Identify which attributes, if any, are sensitive in nature within your (Academy) project. This assignment can be completed within the (Academy) project you created/used in the previous assignment.
... ... @@ -38,6 +38,8 @@
38 38  * eMagiz has various security measures in place to keep your data safe
39 39  * You also have a responsibility as a user how you use the data of the customer
40 40  
50 +
51 +
41 41  == 6. Suggested Additional Readings ==
42 42  
43 43  There are no suggested additional readings on this topic.
advanced-understanding-error-handling-in-emagiz--store-component-gdpr-error-handling.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ebakker
Size
... ... @@ -1,0 +1,1 @@
1 +3.9 KB
Content