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
+13-18Lines changed: 13 additions & 18 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -29,24 +29,6 @@ This page is updated regularly, so revisit it often. If you're looking for items
29
29
## May 2020
30
30
31
31
32
-
### Crash dump analysis capabilities migrating to fileless attack detection
33
-
34
-
We are integrating the Windows crash dump analysis (CDA) detection capabilities into the [fileless attack detection](https://docs.microsoft.com/azure/security-center/threat-protection#windows-fileless) feature.
35
-
36
-
Some of the benefits of this transition:
37
-
38
-
-**Proactive and timely malware detection** - The CDA approach involved waiting for a crash to occur and then running analysis to find active malware. Using fileless attack detection brings proactive identification of in-memory threats while they are running.
39
-
40
-
-**Enriched alerts** - The security alerts from fileless attack detection include enrichments that aren't available from CDA, such as the active network connections information.
41
-
42
-
-**Alert aggregation** - All the attack patterns detected within the memory of an infected process are now aggregated into a single alert. This means that analysts no longer need to correlate multiple alerts for the same infection.
43
-
44
-
-**Reduces requirements on your Log Analytics workspace** - Crash dumps and associated potentially sensitive data will no longer be uploaded to your log analytics workspace.
45
-
46
-
Fileless attack detection analytics brings improved versions of the following security alerts for Windows machines: Code injection discovered, Masquerading Windows Module Detected, Shellcode discovered, and Suspicious code segment detected.
47
-
48
-
49
-
50
32
### Alert suppression rules (preview)
51
33
52
34
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.
@@ -136,6 +118,19 @@ Learn more about Windows Defender Exploit Guard in [Create and deploy an Exploit
136
118
Learn more about security controls in [Enhanced secure score (preview) in Azure Security Center](secure-score-security-controls.md).
137
119
138
120
121
+
### Crash dump analysis capabilities migrating to fileless attack detection
122
+
123
+
We are integrating the Windows crash dump analysis (CDA) detection capabilities into [fileless attack detection](https://docs.microsoft.com/azure/security-center/threat-protection#windows-fileless). Fileless attack detection analytics brings improved versions of the following security alerts for Windows machines: Code injection discovered, Masquerading Windows Module Detected, Shellcode discovered, and Suspicious code segment detected.
124
+
125
+
Some of the benefits of this transition:
126
+
127
+
-**Proactive and timely malware detection** - The CDA approach involved waiting for a crash to occur and then running analysis to find active malware. Using fileless attack detection brings proactive identification of in-memory threats while they are running.
128
+
129
+
-**Enriched alerts** - The security alerts from fileless attack detection include enrichments that aren't available from CDA, such as the active network connections information.
130
+
131
+
-**Alert aggregation** - All the attack patterns detected within the memory of an infected process are now aggregated into a single alert. This means that analysts no longer need to correlate multiple alerts for the same infected process.
132
+
133
+
-**Reduced requirements on your Log Analytics workspace** - Crash dumps containing potentially sensitive data will no longer be uploaded to your Log Analytics workspace.
0 commit comments