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: articles/security-center/custom-security-policies.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,17 +7,17 @@ manager: rkarlin
7
7
8
8
ms.service: security-center
9
9
ms.topic: conceptual
10
-
ms.date: 11/04/2019
10
+
ms.date: 03/25/2020
11
11
ms.author: memildin
12
12
---
13
13
14
14
15
15
16
-
# Using custom security policies (Preview)
16
+
# Using custom security policies
17
17
18
18
To help secure your systems and environment, Azure Security Center generates security recommendations. These recommendations are based on industry best practices, which are incorporated into the generic, default security policy supplied to all customers. They can also come from Security Center's knowledge of industry and regulatory standards.
19
19
20
-
With this preview feature, you can add your own *custom* initiatives. You'll then receive recommendations if your environment doesn't follow the policies you create. Any custom initiatives you create will appear alongside the built-in initiatives in the regulatory compliance dashboard described in the tutorial [Improve your regulatory compliance](security-center-compliance-dashboard.md).
20
+
With this feature, you can add your own *custom* initiatives. You'll then receive recommendations if your environment doesn't follow the policies you create. Any custom initiatives you create will appear alongside the built-in initiatives in the regulatory compliance dashboard described in the tutorial [Improve your regulatory compliance](security-center-compliance-dashboard.md).
21
21
22
22
As discussed [here](https://docs.microsoft.com/azure/governance/policy/concepts/definition-structure#definition-location) in the Azure Policy documentation, when you specify a location for your custom initiative, it must be a management group or a subscription.
23
23
@@ -34,7 +34,7 @@ As discussed [here](https://docs.microsoft.com/azure/governance/policy/concepts/
34
34
>
35
35
> When you add a custom standard, it assigns an *initiative* to that scope. We therefore recommend that you select the widest scope required for that assignment.
36
36
37
-
1. In the Security policy page, under Your custom initiatives (Preview), click **Add a custom initiative**.
37
+
1. In the Security policy page, under Your custom initiatives, click **Add a custom initiative**.
38
38
39
39
[](media/custom-security-policies/custom-policy-add-initiative.png#lightbox)
40
40
@@ -63,7 +63,7 @@ As discussed [here](https://docs.microsoft.com/azure/governance/policy/concepts/
63
63
64
64
* You'll begin to receive recommendations if your environment doesn't follow the policies you've defined.
65
65
66
-
1. To see the resulting recommendations for your policy, click **Recommendations** from the sidebar to open the recommendations page. The recommendations will appear with a “Custom” label and be available within approximately one hour.
66
+
1. To see the resulting recommendations for your policy, click **Recommendations** from the sidebar to open the recommendations page. The recommendations will appear with a "Custom" label and be available within approximately one hour.
0 commit comments