|
| 1 | +--- |
| 2 | +title: Release notes for Azure Security Center |
| 3 | +description: A description of what's new and changed in Azure Security Center. |
| 4 | +services: security-center |
| 5 | +documentationcenter: na |
| 6 | +author: memildin |
| 7 | +manager: rkarlin |
| 8 | +ms.service: security-center |
| 9 | +ms.devlang: na |
| 10 | +ms.topic: conceptual |
| 11 | +ms.tgt_pltfrm: na |
| 12 | +ms.workload: na |
| 13 | +ms.date: 05/11/2020 |
| 14 | +ms.author: memildin |
| 15 | + |
| 16 | +--- |
| 17 | + |
| 18 | +# What's new in Azure Security Center? |
| 19 | + |
| 20 | +Azure Security is in active development and receives improvements on an ongoing basis. To stay up to date with the most recent developments, this page provides you with information about: |
| 21 | + |
| 22 | +- New features |
| 23 | +- Bug fixes |
| 24 | +- Deprecated functionality |
| 25 | + |
| 26 | +This page is updated regularly, so revisit it often. If you're looking for items that are older than six months, you can find them in the [Archive for What's new in Azure Security Center](release-notes-archive.md). |
| 27 | + |
| 28 | + |
| 29 | +## May 2020 |
| 30 | + |
| 31 | +### Changes to just-in-time (JIT) virtual machine (VM) access |
| 32 | + |
| 33 | +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. |
| 34 | + |
| 35 | +This update brings the following changes to this feature: |
| 36 | + |
| 37 | +- The recommendation that advises you to enable JIT on a VM has been renamed. Formerly, "Just-in-time network access control should be applied on virtual machines" it's now: |
| 38 | +"**Management ports should be protected with just-in-time network access control**" |
| 39 | + |
| 40 | +- The recommendation has been set to be triggered only if there are open management ports. |
| 41 | + |
| 42 | +[Learn more about the JIT access feature](security-center-just-in-time.md). |
| 43 | + |
| 44 | + |
| 45 | +### Alert suppression rules (preview) |
| 46 | + |
| 47 | +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. |
| 48 | + |
| 49 | +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. |
| 50 | + |
| 51 | +Suppression rules define the criteria for which alerts should be automatically dismissed. Typically, you'd use a suppression rule to: |
| 52 | + |
| 53 | +- suppress alerts that you've identified as false positives |
| 54 | + |
| 55 | +- suppress alerts that are being triggered too often to be useful |
| 56 | + |
| 57 | +[Learn more about suppressing alerts from Azure Security Center's threat protection](alerts-suppression-rules.md). |
| 58 | + |
| 59 | + |
| 60 | +### Custom recommendations have been moved to a separate security control |
| 61 | + |
| 62 | +One of the security controls introduced with the enhanced secure score was "Implement security best practices". Any custom recommendations created for your subscriptions were automatically placed in that control. |
| 63 | + |
| 64 | +To make it easier to find your custom recommendations, we have moved them into a dedicated security control, "Custom recommendations". This control has no impact on your secure score. |
| 65 | + |
| 66 | +Learn more about security controls in [Enhanced secure score (preview) in Azure Security Center](secure-score-security-controls.md). |
| 67 | + |
| 68 | + |
| 69 | +### Toggle added to view recommendations in controls or as a flat list |
| 70 | + |
| 71 | +Security controls are logical groups of related security recommendations. They reflect your vulnerable attack surfaces. A control is a set of security recommendations, with instructions that help you implement those recommendations. |
| 72 | + |
| 73 | +To immediately see how well your organization is securing each individual attack surface, review the scores for each security control. |
| 74 | + |
| 75 | +By default, your recommendations are shown in the security controls, but from this update you can display them as a list. To view them as simple list sorted by the health status of the affected resources, use the new toggle 'Group by controls' at the top of the list in the portal. |
| 76 | + |
| 77 | +Learn more about security controls in [Enhanced secure score (preview) in Azure Security Center](secure-score-security-controls.md). |
0 commit comments