You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/en/docs/control-center/security/security.md
+15-13Lines changed: 15 additions & 13 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
title: "Security Settings in Control Center"
3
3
linktitle: "Settings"
4
4
url: /control-center/security-settings/
5
-
description: "Describes the Settings page in the Security categoryin Control Center."
5
+
description: "Describes the Settings page in the Security category in Control Center."
6
6
weight: 10
7
7
no_list: false
8
8
---
@@ -13,7 +13,7 @@ A member in Control Center means a user of the Mendix platform who participates
13
13
14
14
## Introduction
15
15
16
-
The **Settings** page in the **Security**catogry in Control Center allows you to configure the security settings, manage the single sign-on configurations, and view the security history of your company.
16
+
The **Settings** page in the **Security**category in Control Center allows you to configure the security settings, manage the single sign-on configurations, and view the security history of your company.
17
17
18
18
## Security Settings Tab
19
19
@@ -23,34 +23,36 @@ With the **Password Policy** setting, you can set the password expiration policy
The Mendix Platform digitally signs the content of emails from senders [no-reply@notifications.mendix.com](mailto:no-reply@notifications.mendix.com) and [no-reply@platform-mail.mendix.com](mailto:no-reply@platform-mail.mendix.com). By digitally signing the content of an email, Mendix provides assurance to the recipient of the email that the content of an email has not been altered in transit. For reasons of security, this feature is enabled by default. However, in case digitally signing the content of an email interferes with the delivery of that email to the recipient, a Mendix Admin can disable this feature for emails sent to receivers in the company domains. For more information, see the [Why Do You Want to Disable the Digital Signing of Email Content?](#why-disable-email-signing) section below.
26
+
The Mendix Platform digitally signs the content of emails from senders [no-reply@notifications.mendix.com](mailto:no-reply@notifications.mendix.com) and [no-reply@platform-mail.mendix.com](mailto:no-reply@platform-mail.mendix.com). By digitally signing the content of an email, Mendix provides assurance to the recipient of the email that the content of an email has not been altered in transit. For reasons of security, this feature is enabled by default. However, if digitally signing the content of an email interferes with the delivery of that email to the recipient, a Mendix Admin can disable this feature for emails sent to receivers in the company domains. For more information, see the [Why Would You Want to Disable the Digital Signing of Email Content?](#why-disable-email-signing) section below.
27
27
28
28
To disable the digital signing of emails, turn off the toggle. To enable the digital signing of emails, turn on the toggle. This setting has an effect on the emails sent to all the [email domains claimed by your company](/control-center/company-settings/#company-email-domains).
29
29
30
-
#### Why Do You Want to Disable the Digital Signing of Email Content? {#why-disable-email-signing}
30
+
#### Why Would You Want to Disable the Digital Signing of Email Content? {#why-disable-email-signing}
31
31
32
-
Digital signing of email content contributes to security, but why do you want to disable the digital signing of email content sometimes? Digital signing might interfere with other email safety measures like “External Email Warning”. This feature might add a customized HTML warning to the email. Since Mendix emails cannot be altered, some email servers will wrap the original message in a blank email and add the original email as an attachment. This is not beneficial for the experience of the user and will make the emails look suspicious, impacting user engagement. Also, it makes searching for emails with specific text content more difficult for users.
32
+
Digital signing of email content contributes to security, so why would you want to disable the digital signing of email content sometimes?
33
+
34
+
Digital signing might interfere with other email safety measures like “External Email Warning”. This feature might add a customized HTML warning to the email. Since Mendix emails cannot be altered, some email servers will wrap the original message in a blank email and add the original email as an attachment. This is not beneficial for the experience of the user and will make the emails look suspicious, impacting user engagement. Also, it makes searching for emails with specific text content more difficult for users.
33
35
34
36
### Application Data Replication {#application-data-replication}
35
37
36
38
{{% alert color="info" %}}
37
-
This feature is only available for [premium cutomers](/developerportal/deploy/mendix-cloud-deploy/#additional-resources).
39
+
The application data replication setting only affects apps and environments that have not been provisioned yet.
40
+
41
+
This feature is only available to [premium customers](/developerportal/deploy/mendix-cloud-deploy/#additional-resources).
38
42
{{% /alert %}}
39
43
40
-
For security and disaster recovery purposes, you may want to replicate application data in Mendix Cloud to another region. If that is the case, click **Activate** to activate application data replication. By default, application data replication is activated.
44
+
By default, Mendix provides premium customers with an SLA which includes high-availability and disaster recovery measures. This means that your application data (file storage and database backups) is replicated to other availability zones within the region and also to a secondary region so that you can still access your data in case of an outage in the primary region.
41
45
42
-
When application data application is activated, all data and backups of your application on Mendix Cloud are replicated to another region in the country. If there is only one region in the country, the data is replicated to a region in another country.
46
+
Secondary regions are, wherever possible, in the same political region as the primary region. However this is not always possible.You can find which secondary regions are used for each primary region in the [Data Location](/developerportal/operate/backups/#data-location) section of *Backups*.
43
47
44
-
If you want to keep your data always in the same region, click **Deactivate** to deactivate application data replication.
48
+
If you want your data to remain in the primary region and not be replicated to a secondary region, click **Deactivate** to deactivate application data replication. You will have to confirm that you accept the impact this has on the service level agreement you have with Mendix regarding disaster recovery and SOC2 compliance.
45
49
46
-
{{% alert color="info" %}}
47
-
When you activate or deactivate application data replication, this only affects apps and environments that have not been provisioned yet.
48
-
{{% /alert %}}
50
+
You can turn application data replication back on by clicking **Activate**.
49
51
50
52
## Single Sign-On Tab
51
53
52
54
On the **Single Sign-On** tab, you can set up an identity federation between the Mendix Platform and your corporate identity provider. We call this feature *Bring Your Own Identity Provider (BYOIDP)* and you can find more information in [How to Set Up an SSO (BYOIDP)](/control-center/security/set-up-sso-byoidp/).
53
55
54
56
## Security History Tab
55
57
56
-
On the **Security History** tab, you can view a detailed history of changes to application data replication settings, including when the changes were made and by whom.
58
+
On the **Security History** tab, you can view a detailed history of changes to application data replication settings, including when the changes were made and by whom.
0 commit comments