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/release-notes.md
+24-22Lines changed: 24 additions & 22 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -58,22 +58,6 @@ To deploy the solution, use the new security recommendation:
58
58
59
59
60
60
61
-
### Alert suppression rules (preview)
62
-
63
-
This new feature (currently in preview) helps reduce alert fatigue. Use rules to automatically hide alerts that are known to be innocuous or related to normal activities in your organization. This lets you focus on the most relevant threats.
64
-
65
-
Alerts that match your enabled suppression rules will still be generated, but their state will be set to dismissed. You can see the state in the Azure portal or however you access your Security Center security alerts.
66
-
67
-
Suppression rules define the criteria for which alerts should be automatically dismissed. Typically, you'd use a suppression rule to:
68
-
69
-
- suppress alerts that you've identified as false positives
70
-
71
-
- suppress alerts that are being triggered too often to be useful
72
-
73
-
[Learn more about suppressing alerts from Azure Security Center's threat protection](alerts-suppression-rules.md).
74
-
75
-
76
-
77
61
### Changes to just-in-time (JIT) virtual machine (VM) access
78
62
79
63
Security Center includes an optional feature to protect the management ports of your VMs. This provides a defense against the most common form of brute force attacks.
@@ -109,21 +93,39 @@ The security controls - and this toggle - are part of the new secure score exper
109
93
Learn more about security controls in [Enhanced secure score (preview) in Azure Security Center](secure-score-security-controls.md).
110
94
111
95
112
-
### Account security recommendations moved to "Security best practices" security control
96
+
### Expanded security control "Implement security best practices"
113
97
114
-
One of the security controls introduced with the enhanced secure score is "Security best practices". When a recommendation is in this control, it doesn't impact the secure score.
98
+
One of the security controls introduced with the enhanced secure score is "Implement security best practices". When a recommendation is in this control, it doesn't impact the secure score.
115
99
116
100
With this update, three recommendations have moved out of the controls in which they were originally placed, and into this best practices control. We've taken this step because we've determined that the risk of these three recommendations is lower than was initially thought.
117
101
118
-
The recommendations are:
102
+
In addition, two new recommendations have been introduced and added to this control.
103
+
104
+
The three recommendations that moved are:
105
+
106
+
-**MFA should be enabled on accounts with read permissions on your subscription** (originally in the "Enable MFA" control)
107
+
-**External accounts with read permissions should be removed from your subscription** (originally in the "Manage access and permissions" control)
108
+
-**A maximum of 3 owners should be designated for your subscription** (originally in the "Manage access and permissions" control)
109
+
110
+
The two new recommendations added the control are:
119
111
120
-
- MFA should be enabled on accounts with read permissions on your subscription (originally in the "Enable MFA" control)
121
-
- External accounts with read permissions should be removed from your subscription (originally in the "Manage access and permissions" control)
122
-
- A maximum of 3 owners should be designated for your subscription (originally in the "Manage access and permissions" control)
112
+
-**[Preview] Guest configuration agent should be installed** - Using [Azure Policy Guest Configuration](https://docs.microsoft.com/azure/governance/policy/concepts/guest-configuration) provides visibility inside virtual machines to server and application settings (Windows only).
113
+
114
+
-**[Preview] Windows exploit guard should be enabled** - Windows Defender Exploit Guard leverages the Azure Policy Guest Configuration agent. Exploit Guard has four components that are designed to lock down devices against a wide variety of attack vectors and block behaviors commonly used in malware attacks while enabling enterprises to balance their security risk and productivity requirements (Windows only).
115
+
116
+
Learn more about Windows Defender Exploit Guard in [Create and deploy an Exploit Guard policy](https://docs.microsoft.com/mem/configmgr/protect/deploy-use/create-deploy-exploit-guard-policy).
123
117
124
118
Learn more about security controls in [Enhanced secure score (preview) in Azure Security Center](secure-score-security-controls.md).
125
119
126
120
121
+
122
+
123
+
124
+
125
+
126
+
127
+
128
+
127
129
### Custom policies with custom metadata are now generally available
128
130
129
131
Custom policies are now part of the Security Center recommendations experience, secure score, and the regulatory compliance standards dashboard. This feature is now generally available and allows you to extend your organization's security assessment coverage in Security Center.
0 commit comments