|
| 1 | +--- |
| 2 | +title: "Policies" |
| 3 | +url: /control-center/policies/ |
| 4 | +description: "Describes the Policies page in the Mendix Control Center." |
| 5 | +weight: 30 |
| 6 | +--- |
| 7 | + |
| 8 | +## Introduction |
| 9 | + |
| 10 | +Policies help ensure that your app landscape is secure, compliant, and consistent. On the **Policies** page, you can define policies that your apps need to adhere to. If they do not, violations are automatically detected and reported in Software Composition, allowing you to react accordingly. For details on how policy violations are displayed in Software Composition, refer to [Policy Status](/control-center/policy-status/). |
| 11 | + |
| 12 | +The **Policies** page allows you to create new policies, lists all of your existing policies, and displays a **Help & Support** pane with useful information about creating policies. |
| 13 | + |
| 14 | +## Defining Policies |
| 15 | + |
| 16 | +You can define policies by either using a template or starting from scratch. The following sections describe the process for each scenario. |
| 17 | + |
| 18 | +### Creating a Policy From a Template |
| 19 | + |
| 20 | +You can use one of the existing templates to create your own policy. |
| 21 | + |
| 22 | +1. Click **Create from Template**. |
| 23 | + |
| 24 | +2. Select one of the available templates: |
| 25 | + |
| 26 | + * Only allow Marketplace components that are platform-supported |
| 27 | + * Only medium or low findings are allowed |
| 28 | + * Only Mendix runtime versions >= 9.24.43 are allowed |
| 29 | + |
| 30 | +3. In the **Policy Name** field, add a name for the new policy. |
| 31 | + |
| 32 | +4. Select one of these actions: |
| 33 | + |
| 34 | + * **Edit** – Make changes to the template, such as adjusting the Mendix runtime version. |
| 35 | + * **Save as Inactive** – Save the policy, but do not enforce it yet. |
| 36 | + * **Save & Activate** – Save the policy and enforce it. |
| 37 | + |
| 38 | +### Creating a Policy From Scratch |
| 39 | + |
| 40 | +You can create a policy by defining your own details. |
| 41 | + |
| 42 | +1. Click **Create from Scratch**. |
| 43 | + |
| 44 | +2. On the **Policy Definition** tab, fill in the following details: |
| 45 | + |
| 46 | +* **Policy Name** – A relevant name for your policy, such as one indicating what the policy checks. |
| 47 | +* **Description** – A description of the goal of the policy, which covers why it needs to be adhered to, and how to fix its violations. |
| 48 | +* **Policy Conditions** – Define the conditions under which the policy is considered violated. These are the available conditions and their values: |
| 49 | + |
| 50 | + * **Any finding severity is** – Choose which severity level violates the policy. You can select one or more of the following values: |
| 51 | + |
| 52 | + * **LOW** |
| 53 | + * **MEDIUM** |
| 54 | + * **HIGH** |
| 55 | + * **CRITICAL** |
| 56 | + |
| 57 | + For example, if you select **CRITICAL**, apps with critical findings violate this policy. |
| 58 | + |
| 59 | + * **Mendix runtime version is lower than** – Indicate which Mendix version is the minimum that your apps must use. |
| 60 | + |
| 61 | + * **Marketplace component license is not** – Select the licenses that are acceptable. If a Marketplace component has a license which is not one of the ones you select here, the policy is violated. These are the possible values: |
| 62 | + |
| 63 | + * MIT |
| 64 | + * BSD_2_0 |
| 65 | + * APACHE_V2 |
| 66 | + * APACHE_1_0 |
| 67 | + * MENDIX_EULA |
| 68 | + * PARTNER_LICENSES |
| 69 | + * CREATIVE_COMMONS_CC0 |
| 70 | + * GNU_GENERAL_PUBLIC_LICENSE_V3 |
| 71 | + * MENDIX_MARKETPLACE_CONTENT_TERMS |
| 72 | + |
| 73 | + * **Marketplace component support is not** – Select the support types that are acceptable. If a Marketplace component has a support type which is not one of the ones you select here, the policy is violated. These are the possible values: |
| 74 | + |
| 75 | + * PARTNER |
| 76 | + * SIEMENS |
| 77 | + * PLATFORM |
| 78 | + * COMMUNITY |
| 79 | + |
| 80 | +* **Checkpoints & Action(s)** – Select the trigger which causes the policy to be checked, and the action that is taken if the policy is violated. Currently, policy violations are checked at the time of package creation, and violations generate warnings. |
| 81 | + |
| 82 | +3. On the **Policy Scope** tab, select whether you want the policy to apply to all licensed apps, or only to specific apps in your environment. |
| 83 | + |
| 84 | +4. Select one of these actions: |
| 85 | + |
| 86 | + * **Cancel** – Discard the policy. |
| 87 | + * **Save as Inactive** – Save the policy, but do not enforce it yet. |
| 88 | + * **Save & Activate** – Save the policy and enforce it. |
| 89 | + |
| 90 | +## Policy Details |
| 91 | + |
| 92 | +These are the details you can see for every existing policy: |
| 93 | + |
| 94 | +* **Policy Name** – The policy's name. |
| 95 | +* **ID** – The policy's unique ID, which you can copy. |
| 96 | +* **Policy Scope** – The policy's app scope. |
| 97 | +* **Last Updated By** – The unique ID of the user who most recently updated the policy. |
| 98 | +* **Last Updated Date** – The date when the policy was most recently updated. |
| 99 | +* **Status** – Whether the policy is active or not. |
| 100 | +* Actions: |
| 101 | + |
| 102 | + * **Edit Policy** |
| 103 | + * **Deactivate Policy** |
| 104 | + * **Delete Policy** |
0 commit comments