How to stop incidents merging under new incident (MultiStage) in defender.
Dear All We are experiencing a challenge with the integration between Microsoft Sentinel and the Defender portal where multiple custom rule alerts and analytic rule incidents are being automatically merged into a single incident named "Multistage." This automatic incident merging affects the granularity and context of our investigations, especially for important custom use cases such as specific admin activities and differentiated analytic logic. Key concerns include: Custom rule alerts from Sentinel merging undesirably into a single "Multistage" incident in Defender, causing loss of incident-specific investigation value. Analytic rules arising from different data sources and detection logic are merged, although they represent distinct security events needing separate attention. Customers require and depend on distinct, non-merged incidents for custom use cases, and the current incident correlation and merging behavior undermines this requirement. We understand that Defender’s incident correlation engine merges incidents based on overlapping entities, timelines, and behaviors but would like guidance or configuration best practices to disable or minimize this automatic merging behavior for our custom and analytic rule incidents. Our goal is to maintain independent incidents corresponding exactly to our custom alerts so that hunting, triage, and response workflows remain precise and actionable. Any recommendations or advanced configuration options to achieve this separation would be greatly appreciated. Thank you for your assistance. Best regards
XDR advanced hunting region specific endpoints
Hi, I am exploring XDR advanced hunting API to fetch data specific to Microsoft Defender for Endpoint tenants. The official documentation (https://learn.microsoft.com/en-us/defender-xdr/api-advanced-hunting) mentions to switch to Microsoft Graph advanced hunting API. I had below questions related to it: 1. To fetch the region specific(US , China, Global) token and Microsoft Graph service root endpoints(https://learn.microsoft.com/en-us/graph/deployments#app-registration-and-token-service-root-endpoints ) , is the recommended way to fetch the OpenID configuration document (https://learn.microsoft.com/en-us/entra/identity-platform/v2-protocols-oidc#fetch-the-openid-configuration-document) for a tenant ID and based on the response, the region specific SERVICE/TOKEN endpoints could be fetched? Since using it, there is no need to maintain different end points for tenants in different regions. And do we use the global service URL https://login.microsoftonline.com to fetch OpenID config document for a tenantID in any region? 2. As per the documentation, Microsoft Graph Advanced hunting API is not supported in China region (https://learn.microsoft.com/en-us/graph/api/security-security-runhuntingquery?view=graph-rest-1.0&tabs=http). In this case, is it recommended to use Microsoft XDR Advanced hunting APIs(https://learn.microsoft.com/en-us/defender-xdr/api-advanced-hunting) to support all region tenants(China, US, Global)?Detecting browser anomalies to disrupt attacks early
Uncover the secrets of early attack disruption with browser anomaly detections! This blog post explores how Microsoft Defender XDR leverages advanced techniques to identify unusual browser activities and stop cyber threats in their tracks. Learn about the importance of monitoring unusual browser activities, session hijacking, Business Email Compromise (BEC), and other critical attack paths. With real-world examples and insights into the systematic approach used by Defender XDR, you'll gain a deeper understanding of how to enhance your organization's security posture. Don't miss out on this essential read for staying ahead of cyber threats!Introducing the new PowerShell Module for Microsoft Defender for Identity
Today, I am excited to introduce a new PowerShell module designed to help further simplify the deployment and configuration of Microsoft Defender for Identity. This tool will make it easier than ever to protect your organization from identity-based cyber-threats.
Unable to add Endpoints and Vulnerability management in XDR Permissions
Hi, I have defender for endpoint running on obver 400 devices. I have 10 with Bus Premium, 5 with E5, and the rest E3. I am getting incidents for DFE, and this is being sent to my SOAR platform for analysis, but when I pivot back using client-sync, I cannot see DFE incidents. I have gone into Settings > XDR > Workload settings, and can only see the below There does not appear to be the option to grant the roles I have provided for my SOAR user the ability to see Endpoint and Vulnerability management. Really scratching my head here. Help?
How to Connect MS Secure Scores to Power Query?
The Microsoft 365 Defender Portal (https://security.microsoft.com/) has a 'Secure Score' page, which contains the following: An overall secure score which is then broken down by Identity, Data, Device, and Application secure scores. I would like to be able to pull these four scores into a Power BI report; however, I have had some difficulty in putting together a solution. This data seems like it could be found in the Microsoft Graph API, but https://learn.microsoft.com/en-us/power-query/connecting-to-graph. I've tried other Defender APIs, but they all seem either outdated or out of scope for what I'm trying to pull. Can anyone advise? Thanks for reading.Automatic attack disruption: Enhanced containment for critical assets and shadow IT
Staying ahead of attackers is tough, as they constantly evolve and use advanced techniques like AI to exploit vulnerabilities. Protecting high-value assets is even harder, as these are prime targets. Security teams must constantly adapt to outpace attackers, balancing proactive measures with the need for speed and innovation. This is why Microsoft Defender XDR developed automatic attack disruption, a built-in self-defense capability that contains in-progress attacks to prevent further lateral movement & damage to an organization. We’re thrilled to introduce new, extended capabilities in automatic attack disruption, designed to further stop attackers and restrict them from moving laterally across the network by leveraging compromised devices. Specifically, within Microsoft Defender for Endpoint which disrupt ransomware on its own. With this expansion, we now offer: Granular containment of critical assets – Helping ensure essential infrastructure remains operational while blocking attacker activity. Containment of IP addresses linked to undiscovered devices – Helping to prevent attackers from exploiting shadow IT and unmanaged endpoints. Granular Containment of Critical Assets Critical assets—such as Domain Controllers, DNS, and DHCP servers—are prime targets for adversaries. These systems serve as strategic footholds for attackers to establish persistence, escalate privileges, and compromise further resources. However, containing these devices has traditionally been challenging, as full isolation could disrupt business operations. With this new capability, Defender for Endpoint applies intelligent, device role-based, granular containment to limit only specific network functionalities and interfaces used for malicious activity, while keeping essential functions running. This means: Attackers lose their ability to move laterally and escalate their attack. Key network functions are preserved, ensuring business continuity. Compromised critical assets remain operational while being protected. Containing IP addresses of undiscovered devices Shadow IT and unmanaged devices present a hidden security risk. Often unmonitored, these devices become easy targets for attackers to exploit for lateral movement. With the new IP address containment capability, Defender for Endpoint can now identify and incriminate malicious IP addresses linked to unmanaged or undiscovered devices and automatically contain those IPs, preventing attackers from getting their foot in the door through vulnerable, unmanaged devices before spreading to other non-compromised devices. Configuring IP containment Excluding assets from automatic attack disruption is not recommended as it can reduce the effectiveness of protecting your environment from sophisticated, high-impact attacks. If there is still a need to exclude an IP subnet or multiple IP addresses, this can be done within the Microsoft Defender XDR portal as follows: Under Automated responses, select Devices. In the IPs tab, select Exclude IP to exclude an IP address. In the flyout pane, enter the IP address/IP range/IP subnet you want to exclude. You can add multiple IP addresses and IP subnets by separating them with a comma. For full configuration options see the Defender XDR documentation. While security is undeniably challenging, security analysts should feel empowered by their tools to effectively combat against attacks. With continuous innovation and the ability to adapt to the latest threats, they can stay resilient and confident in their ability to protect valuable assets. The ever-evolving landscape of cybersecurity is demanding, but with the right resources, analysts are well-equipped to tackle it head-on. Get started Make sure your organization fulfills the Microsoft Defender XDR pre-requisites. Deploy Defender for Endpoint. A free trial is available here. Learn more Read our latest security blog on how we protect against ransomware attacks using domain controllers Read our latest Defender for Endpoint e-book Check out our documentation to learn more about Microsoft Defender XDR's attack disruption prerequisites, available controls, and indications. Learn more about our Device Containment capabilities. Learn more about other scenarios supported by automatic attack disruption.
