The Alerts queue shows a list of alerts that were flagged from devices in your network. By default, the queue displays alerts seen in the last 30 days in a grouped view. The most recent alerts are showed at the top of the list helping you see the most recent alerts first.
The alerts queue is significantly reduced with automated investigation and remediation, allowing security operations experts to focus on more sophisticated threats and other high value initiatives. When an alert contains a supported entity for automated investigation (for example, a file) in a device that has a supported operating system for it, an automated investigation and remediation can start. For more information on automated investigations, see Overview of Automated investigations.
There are several options you can choose from to customize the alerts queue view.
On the top navigation you can:
- Select grouped view or list view
- Customize columns to add or remove columns
- Select the items to show per page
- Navigate between pages
- Apply filters
Sort, filter, and group the alerts queue
You can apply the following filters to limit the list of alerts and get a more focused view the alerts.
|Alerts commonly seen associated with advanced persistent threats (APT). These alerts indicate a high risk because of the severity of damage they can inflict on devices. Some examples are: credential theft tools activities, ransomware activities not associated with any group, tampering with security sensors, or any malicious activities indicative of a human adversary.|
|Alerts from endpoint detection and response post-breach behaviors that might be a part of an advanced persistent threat (APT). This includes observed behaviors typical of attack stages, anomalous registry change, execution of suspicious files, and so forth. Although some might be part of internal security testing, it requires investigation as it might also be a part of an advanced attack.|
|Alerts on threats associated with prevalent malware. For example, hack-tools, non-malware hack tools, such as running exploration commands, clearing logs, etc., that often do not indicate an advanced threat targeting the organization. It could also come from an isolated security tool testing by a user in your organization.|
|Alerts that might not be considered harmful to the network but can drive organizational security awareness on potential security issues.|
Understanding alert severity
Microsoft Defender Antivirus (Microsoft Defender AV) and Defender for Endpoint alert severities are different because they represent different scopes.
The Microsoft Defender Antivirus threat severity represents the absolute severity of the detected threat (malware), and is assigned based on the potential risk to the individual device, if infected.
The Defender for Endpoint alert severity represents the severity of the detected behavior, the actual risk to the device but more importantly the potential risk to the organization.
So, for example:
- The severity of a Defender for Endpoint alert about a Microsoft Defender Antivirus detected threat that was completely prevented and did not infect the device is categorized as “Informational” because there was no actual damage.
- An alert about a commercial malware was detected while executing, but blocked and remediated by Microsoft Defender AV, is categorized as “Low” because it may have caused some damage to the individual device but poses no organizational threat.
- An alert about malware detected while executing which can pose a threat not only to the individual device but to the organization, regardless if it was eventually blocked, may be ranked as “Medium” or “High”.
- Suspicious behavioral alerts, which weren’t blocked or remediated will be ranked “Low”, “Medium” or “High” following the same organizational threat considerations.
Understanding alert categories
We’ve redefined the alert categories to align to the enterprise attack tactics in the MITRE ATT&CK matrix. New category names apply to all new alerts. Existing alerts will keep the previous category names.
The table below lists the current categories and how they generally map to previous categories.
|New category||API category name||Detected threat activity or component|
|Collection||Collection||Locating and collecting data for exfiltration.|
|Command and control||CommandAndControl||Connecting to attacker-controlled network infrastructure to relay data or receive commands.|
|Credential access||CredentialAccess||Obtaining valid credentials to extend control over devices and other resources in the network.|
|Defense evasion||DefenseEvasion||Avoiding security controls by, for example, turning off security apps, deleting implants, and running rootkits.|
|Discovery||Discovery||Gathering information about important devices and resources, such as administrator computers, domain controllers, and file servers.|
|Execution||Execution||Launching attacker tools and malicious code, including RATs and backdoors.|
|Exfiltration||Exfiltration||Extracting data from the network to an external, attacker-controlled location.|
|Exploit||Exploit||Exploit code and possible exploitation activity.|
|Initial access||InitialAccess||Gaining initial entry to the target network, usually involving password-guessing, exploits, or phishing emails.|
|Lateral movement||LateralMovement||Moving between devices in the target network to reach critical resources or gain network persistence.|
|Malware||Malware||Backdoors, trojans, and other types of malicious code.|
|Persistence||Persistence||Creating autostart extensibility points (ASEPs) to remain active and survive system restarts.|
|Privilege escalation||PrivilegeEscalation||Obtaining higher permission levels for code by running it in the context of a privileged process or account.|
|Ransomware||Ransomware||Malware that encrypts files and extorts payment to restore access.|
|Suspicious activity||SuspiciousActivity||Atypical activity that could be malware activity or part of an attack.|
|Unwanted software||UnwantedSoftware||Low-reputation apps and apps that impact productivity and the user experience; detected as potentially unwanted applications (PUAs).|
You can choose to limit the list of alerts based on their status.
Corresponds to the automated investigation state.
You can choose to filter the queue to display specific types of malicious activity.
You can choose between showing alerts that are assigned to you or automation.
Select the source that triggered the alert detection. Microsoft Threat Experts preview participants can now filter and see detections from the new threat experts-managed hunting service.
The Antivirus filter will only appear if devices are using Microsoft Defender Antivirus as the default real-time protection antimalware product.
|Detection source||API value|
|3rd party sensors||ThirdPartySensors|
|Microsoft 365 Defender||MTP|
|Microsoft Defender for Office 365||OfficeATP|
|Microsoft Threat Experts||ThreatExperts|
Limit the alerts queue view by selecting the OS platform that you’re interested in investigating.
If you have specific device groups that you’re interested in checking, you can select the groups to limit the alerts queue view.
Use this filter to focus on alerts that are related to high profile threats. You can see the full list of high-profile threats in Threat analytics.