What's new in Microsoft Defender for Identity

This article is updated frequently to let you know what's new in the latest releases of Microsoft Defender for Identity (formerly Azure Advanced Threat Protection, also known as Azure ATP).

For details of earlier Defender for Identity releases until (and including) release 2.55, see the Defender for Identity release reference.

RSS feed: Get notified when this page is updated by copying and pasting the following URL into your feed reader: https://docs.microsoft.com/api/search/rss?search=%22This+article+is+updated+frequently+to+let+you+know+what%27s+new+in+the+latest+release+of+Azure+ATP%22&locale=en-us

Important

Threat protection product names from Microsoft are changing. Read more about this and other updates here. We'll be using the new names from release 2.129 onwards.

Defender for Identity release 2.132

Released November 17, 2020

  • Version includes improvements and bug fixes for internal sensor infrastructure.

Defender for Identity release 2.131

Released November 8, 2020

  • New security alert:  Suspected Kerberos SPN exposure (external ID 2410)
    Defender for Identity's Suspected Kerberos SPN exposure (external ID 2410) security alert is now available. In this detection, a Defender for Identity security alert is triggered when an attacker enumerates service accounts and their respective SPNs, and then requests Kerberos TGS tickets for the services. The attackers intent may be to extract the hashes from the tickets and save them for later use in offline brute force attacks. For more information, see Kerberos SPN exposure.
  • Version includes improvements and bug fixes for internal sensor infrastructure.

Defender for Identity release 2.130

Released October 25, 2020

  • Version includes improvements and bug fixes for internal sensor infrastructure.

Azure ATP release 2.129

Released October 18, 2020

  • Version includes improvements and bug fixes for internal sensor infrastructure.

Azure ATP release 2.128

Released September 27, 2020

  • Modified email notifications configuration
    We are removing the Mail notification toggles for turning on email notifications. To receive email notifications, simply add an address. For more information, see Set notifications.
  • Version includes improvements and bug fixes for internal sensor infrastructure.

Azure ATP release 2.127

Released September 20, 2020

  • New security alert: Suspected Netlogon privilege elevation attempt (external ID 2411)
    Azure ATP's Suspected Netlogon privilege elevation attempt (CVE-2020-1472 exploitation) (external ID 2411) security alert is now available. In this detection, an Azure ATP security alert is triggered when an attacker establishes a vulnerable Netlogon secure channel connection to a domain controller, using the Netlogon Remote Protocol (MS-NRPC), also known as Netlogon Elevation of Privilege Vulnerability. For more information, see Suspected Netlogon privilege elevation attempt.
  • Version includes improvements and bug fixes for internal sensor infrastructure.

Azure ATP release 2.126

Released September 13, 2020

  • Version includes improvements and bug fixes for internal sensor infrastructure.

Azure ATP release 2.125

Released September 6, 2020

  • Version includes improvements and bug fixes for internal sensor infrastructure.

Azure ATP release 2.124

Released August 30, 2020

  • New security alerts
    Azure ATP security alerts now includes the following new detections:
    • Active Directory attributes reconnaissance (LDAP) (external ID 2210)
      In this detection, an Azure ATP security alert is triggered when an attacker is suspected of successfully gaining critical information about the domain for use in their attack kill chain. For more information, see Active Directory attributes reconnaissance.
    • Suspected rogue Kerberos certificate usage (external ID 2047)
      In this detection, an Azure ATP security alert is triggered when an attacker that has gained control over the organization by compromising the certificate authority server is suspected of generating certificates that can be used as backdoor accounts in future attacks, such as moving laterally in your network. For more information, see Suspected rogue Kerberos certificate usage.
    • Suspected golden ticket usage (ticket anomaly using RBCD) (external ID 2040)
      Attackers with domain admin rights can compromise the KRBTGT account. Using the KRBTGT account, they can create a Kerberos ticket-granting ticket (TGT) that provides authorization to any resource.
      This forged TGT is called a "Golden Ticket" because it allows attackers to achieve lasting network persistence using Resource Based Constrained Delegation (RBCD). Forged Golden Tickets of this type have unique characteristics this new detection is designed to identify. For more information, see Suspected golden ticket usage (ticket anomaly using RBCD).
  • Version includes improvements and bug fixes for internal sensor infrastructure.

Azure ATP release 2.123

Released August 23, 2020

  • Version includes improvements and bug fixes for internal sensor infrastructure.

Azure ATP release 2.122

Released August 16, 2020

  • Version includes improvements and bug fixes for internal sensor infrastructure.

Azure ATP release 2.121

Released August 2, 2020

  • Version includes improvements and bug fixes for internal sensor infrastructure.

Azure ATP release 2.120

Released July 26, 2020

  • Version includes improvements and bug fixes for internal sensor infrastructure.

Azure ATP release 2.119

Released July 5, 2020

  • Feature enhancement: New Excluded domain controllers tab in Excel report
    To improve the accuracy of our domain controller coverage calculation, we will be excluding domain controllers with external trusts from the calculation toward achieving 100% coverage. Excluded domain controllers will be surfaced in the new excluded domain controllers tab in the domain coverage Excel report download. For information about downloading the report, see Domain controller status.
  • Version includes improvements and bug fixes for internal sensor infrastructure.

Azure ATP release 2.118

Released June 28, 2020

  • New security assessments
    Azure ATP security assessments now includes the following new assessments:

    • Riskiest lateral movement paths
      This assessment continuously monitors your environment to identify sensitive accounts with the riskiest lateral movement paths that expose a security risk, and reports on these accounts to assist you in managing your environment. Paths are considered risky if they have three or more non-sensitive accounts that can expose the sensitive account to credential theft by malicious actors. For more information, see Security assessment: Riskiest lateral movement paths (LMP).
    • Unsecure account attributes
      This assessment Azure ATP continuously monitors your environment to identify accounts with attribute values that expose a security risk, and reports on these accounts to assist you in protecting your environment. For more information, see Security assessment: Unsecure account attributes.
  • Updated sensitivity definition
    We are expanding our sensitivity definition for on-premises accounts to include entities that are allowed to use Active Directory replication.

Azure ATP release 2.117

Released June 14, 2020

  • Feature enhancement: Additional activity details available in the unified SecOps experience
    We've extended the device information we send to Cloud App Security including device names, IP addresses, account UPNs and used port. For more information about our integration with Cloud App Security, see Using Azure ATP with Cloud App Security.

  • Version includes improvements and bug fixes for internal sensor infrastructure.

Azure ATP release 2.116

Released June 7, 2020

  • Version includes improvements and bug fixes for internal sensor infrastructure.

Azure ATP release 2.115

Released May 31, 2020

  • New security assessments
    Azure ATP security assessments now includes the following new assessments:

    • Unsecure SID History attributes
      This assessment reports on SID History attributes that can be used by malicious attackers to gain access to your environment. For more information, see Security assessment: Unsecure SID History attributes.
    • Microsoft LAPS usage
      This assessment reports on local administrator accounts not using Microsoft's "Local Administrator Password Solution" (LAPS) to secure their passwords. Using LAPS simplifies password management and also helps defend against cyberattacks. For more information, see Security assessment: Microsoft LAPS usage.
  • Version includes improvements and bug fixes for internal sensor infrastructure.

Azure ATP release 2.114

Released May 17, 2020

  • Version includes improvements and bug fixes for internal sensor infrastructure.

Azure ATP release 2.113

Released May 5, 2020

  • Feature enhancement: Enriched Resource Access Activity with NTLMv1
    Starting from this version, Azure ATP now provides information for resource access activities showing whether the resource uses NTLMv1 authentication. This resource configuration is unsecure and poses a risk that malicious actors can force the application to their advantage. For more information about the risk, see Legacy protocols usage.

  • Feature enhancement: Suspected Brute Force attack (Kerberos, NTLM) alert
    Brute Force attack is used by attackers to gain a foothold into your organization and is a key method for threat and risk discovery in Azure ATP. To help you focus on the critical risks to your users, this update makes it easier and faster to analyze and remediate risks, by limiting and prioritizing the volume of alerts.

Azure ATP release 2.112

Released Mar 15, 2020

  • New Azure ATP instances automatically integrate with Microsoft Cloud App Security
    When creating an Azure ATP instance (formerly workspace), the integration with Microsoft Cloud App Security is enabled by default. For more information about the integration, see Using Azure ATP with Microsoft Cloud App Security.

  • New monitored activities
    The following activity monitors are now available:

  • Feature enhancement: Enriched Resource Access Activity
    Starting from this version, Azure ATP now provides information for resource access activities showing whether the resource is trusted for unconstrained delegation. This resource configuration is unsecure and poses a risk that malicious actors can force the application to their advantage. For more information about the risk, see Security assessment: Unsecure Kerberos delegation.

  • Suspected SMB packet manipulation (CVE-2020-0796 exploitation) - (preview)
    Azure ATP's Suspected SMB packet manipulation security alert is now in public preview. In this detection, an Azure ATP security alert is triggered when SMBv3 packet suspected of exploiting the CVE-2020-0796 security vulnerability are made against a domain controller in the network.

Azure ATP release 2.111

Released Mar 1, 2020

  • Version includes improvements and bug fixes for internal sensor infrastructure.

Azure ATP release 2.110

Released Feb 23, 2020

  • New security assessment: Unmonitored domain controllers
    Azure ATP security assessments now includes a report on unmonitored domain controllers, servers without a sensor, to help you in managing full coverage of your environment. For more information, see Unmonitored domain controllers.

Azure ATP release 2.109

Released Feb 16, 2020

  • Feature enhancement: Sensitive entities
    Starting from this version (2.109), machines identified as Certificate Authority, DHCP, or DNS Servers by Azure ATP are now automatically tagged as Sensitive.

Azure ATP release 2.108

Released Feb 9, 2020

  • New feature: Support for group Managed Service Accounts
    Azure ATP now supports using group Managed Service Accounts (gMSA) for improved security when connecting Azure ATP sensors to your Azure Active Directory (AD) forests. For more information about using gMSA with Azure ATP sensors, see Connect to your Active Directory Forest.

  • Feature enhancement: Scheduled report with too much data
    When a scheduled report has too much data, the email now informs you of the fact by displaying the following text: There was too much data during the specified period to generate a report. This replaces the previous behavior of only discovering the fact after clicking the report link in the email.

  • Feature enhancement: Updated domain controller coverage logic
    We've updated our domain controller coverage report logic to include additional information from Azure AD, resulting in a more accurate view of domain controllers without sensors on them. This new logic should also have a positive affect on the corresponding Microsoft Secure Score.

Azure ATP release 2.107

Released Feb 3, 2020

  • New monitored activity: SID history change
    SID history change is now a monitored and filterable activity. Learn more about which activities Azure ATP monitors, and how to filter and search monitored activities in the portal.

  • Feature enhancement: Closed or suppressed alerts are no longer reopened
    Once an alert is closed or suppressed in the Azure ATP portal, if the same activity is detected again within a short period of time, a new alert is opened. Previously, under the same conditions, the alert was reopened.

  • TLS 1.2 required for portal access and sensors
    TLS 1.2 is now required to use Azure ATP sensors and the cloud service. Access to the Azure ATP portal will no longer be possible using browsers that do not support TLS 1.2.

Azure ATP release 2.106

Released Jan 19, 2020

  • Version includes improvements and bug fixes for internal sensor infrastructure.

Azure ATP release 2.105

Released Jan 12, 2020

  • Version includes improvements and bug fixes for internal sensor infrastructure.

Azure ATP release 2.104

Released Dec 23, 2019

  • Sensor version expirations eliminated
    Azure ATP sensor deployment and sensor installation packages no longer expire after a number of versions and now only update themselves once. The result of this feature is that previously downloaded sensor installation packages can now be installed even if they are older than our max number of lapsed versions.

  • Confirm compromise
    You can now confirm compromise of specific Microsoft 365 users and set their risk level to high. This workflow allows your security operations teams another response capability to reduce their security incidents Time-To-Resolve thresholds. Learn more about how to confirm compromise using Azure ATP and Cloud App Security.

  • New experience banner
    On Azure ATP portal pages where a new experience is available in the Cloud App Security portal, new banners are displayed describing what's available with access links.

  • This version also includes improvements and bug fixes for internal sensor infrastructure.

Azure ATP release 2.103

Released Dec 15, 2019

  • Version includes improvements and bug fixes for internal sensor infrastructure.

Azure ATP release 2.102

Released Dec 8, 2019

  • Version includes improvements and bug fixes for internal sensor infrastructure.

Azure ATP release 2.101

Released Nov 24, 2019

  • Version includes improvements and bug fixes for internal sensor infrastructure.

Azure ATP release 2.100

Released Nov 17, 2019

  • Version includes improvements and bug fixes for internal sensor infrastructure.

Azure ATP release 2.99

Released November 3, 2019

  • Feature enhancement: Added user interface notification of Cloud App Security portal availability to the Azure ATP portal
    Ensuring all users are aware of the availability of the enhanced features available using the Cloud App Security portal, notification was added for the portal from the existing Azure ATP alert timeline.

  • Version includes improvements and bug fixes for internal sensor infrastructure.

Azure ATP release 2.98

Released October 27, 2019

  • Feature enhancement: Suspected brute force attack alert
    Improved the Suspected brute force attack (SMB) alert using additional analysis, and improved detection logic to reduce benign true positive (B-TP) and false positive (FP) alert results.

  • Version includes improvements and bug fixes for internal sensor infrastructure.

Azure ATP release 2.97

Released October 6, 2019

  • Version includes improvements and bug fixes for internal sensor infrastructure.

Azure ATP release 2.96

Released September 22, 2019

  • Enriched NTLM authentication data using Windows Event 8004
    Azure ATP sensors are now able to automatically read and enrich the NTLM authentications activities with your accessed server data when NTLM auditing is enabled, and Windows Event 8004 is turned on. Azure ATP parses Windows Event 8004 for NTLM authentications in order to enrich the NTLM authentication data used for Azure ATP threat analysis and alerts. This enhanced capability provides resource access activity over NTLM data as well as enriched failed logon activities including the destination computer which the user attempted but failed to access.

    Learn more about NTLM authentication activities using Windows Event 8004.

  • Version also includes improvements and bug fixes for internal sensor infrastructure.

Azure ATP release 2.95

Released September 15, 2019

  • Version includes improvements and bug fixes for internal sensor infrastructure.

Azure ATP release 2.94

Released September 8, 2019

  • Version includes improvements and bug fixes for internal sensor infrastructure.

Azure ATP release 2.93

Released September 1, 2019

  • ersion includes improvements and bug fixes for internal sensor infrastructure.

Azure ATP release 2.92

Released August 25, 2019

  • ersion includes improvements and bug fixes for internal sensor infrastructure.

Azure ATP release 2.91

Released August 18, 2019

  • Version includes improvements and bug fixes for internal sensor infrastructure.

Azure ATP release 2.90

Released August 11, 2019

  • Version includes improvements and bug fixes for internal sensor infrastructure.

Azure ATP release 2.89

Released August 4, 2019

  • Sensor method improvements
    To avoid excess NTLM traffic generation in creation of accurate Lateral Movement Path (LMP) assessments, improvements have been made to Azure ATP sensor methods to rely less on NTLM usage and make more significant use of Kerberos.

  • Alert enhancement: Suspected Golden Ticket usage (nonexistent account)
    SAM name changes have been added to the supporting evidence types listed in this type of alert. To learn more about the alert, including how to prevent this type of activity and remediate, see Suspected Golden Ticket usage (nonexistent account).

  • General availability: Suspected NTLM authentication tampering
    The Suspected NTLM authentication tampering alert is no longer in preview mode and is now generally available.

  • Version includes improvements and bug fixes for internal sensor infrastructure.

Azure ATP release 2.88

Released July 28, 2019

  • This version includes improvements and bug fixes for internal sensor infrastructure.

Azure ATP release 2.87

Released July 21, 2019

  • Feature enhancement: Automated Syslog event collection for Azure ATP standalone sensors
    Incoming Syslog connections for Azure ATP standalone sensors are now fully automated, while removing the toggle option from the configuration screen. These changes have no effect on outgoing Syslog connections.

  • This version includes improvements and bug fixes for internal sensor infrastructure.

Azure ATP release 2.86

Released July 14, 2019

  • New security alert: Suspected NTLM authentication tampering (external ID 2039)
    Azure ATP's new Suspected NTLM authentication tampering security alert is now in public preview. In this detection, an Azure ATP security alert is triggered when use of "man-in-the-middle" attack is suspected of successfully bypassing NTLM Message Integrity Check (MIC), a security vulnerability detailed in Microsoft CVE-2019-040. These types of attacks attempt to downgrade NTLM security features and successfully authenticate, with the ultimate goal of making successful lateral movements.

  • Feature enhancement: Enriched device operating system identification
    Until now, Azure ATP provided entity device operating system information based on the available attribute in Active Directory. Previously, if operating system information was unavailable in Active Directory, the information was also unavailable on Azure ATP entity pages. Starting from this version, Azure ATP now provides this information for devices where Active Directory doesn't have the information, or are not registered in Active Directory, by using enriched device operating system identification methods.

    The addition of enriched device operating system identification data helps identify unregistered and non-Windows devices, while simultaneously aiding in your investigation process. For learn more about Network Name Resolution in Azure ATP, see Understanding Network Name Resolution (NNR).

  • New feature: Authenticated proxy - preview
    Azure ATP now supports authenticated proxy. Specify the proxy URL using the sensor command line and specify Username/Password to use proxies that require authentication. For more information about how to use authenticated proxy, see Configure the proxy.

  • Feature enhancement: Automated domain synchronizer process
    The process of designating and tagging domain controllers as domain synchronizer candidates during setup and ongoing configuration is now fully automated. The toggle option to manually select domain controllers as domain synchronizer candidates is removed.

  • This version also includes improvements and bug fixes for internal sensor infrastructure.

Azure ATP release 2.85

Released July 7, 2019

  • This version includes improvements and bug fixes for internal sensor infrastructure.

Azure ATP release 2.84

Released July 1, 2019

  • New location support: Azure UK data center
    Azure ATP instances are now supported in the Azure UK data center. To learn more about creating Azure ATP instances and their corresponding data center locations, see Step 1 of Azure ATP installation.

  • Feature enhancement: New name and features for the Suspicious additions to sensitive groups alert (external ID 2024)
    The Suspicious additions to sensitive groups alert was previously named the Suspicious modifications to sensitive groups alert. The external ID of the alert (ID 2024) remains the same. The descriptive name change more accurately reflects the purpose of alerting on additions to your sensitive groups. The enhanced alert also features new evidence and improved descriptions. For more information, see Suspicious additions to sensitive groups.

  • New documentation feature: Guide for moving from Advanced Threat Analytics to Azure ATP
    This new article includes prerequisites, planning guidance, as well as configuration and verification steps for moving from ATA to Azure ATP service. For more information, see Move from ATA to Azure ATP.

  • This version also includes improvements and bug fixes for internal sensor infrastructure.

Azure ATP release 2.83

Released June 23, 2019

  • Feature enhancement: Suspicious service creation alert (external ID 2026)
    This alert now features an improved alert page with additional evidence and a new description. For more information, see Suspicious service creation security alert.

  • Instance naming support: Support added for digit only domain prefix
    Support added for Azure ATP instance creation using initial domain prefixes that only contain digits. For example, use of digit only initial domain prefixes such as 123456.contoso.com are now supported.

  • This version also includes improvements and bug fixes for internal sensor infrastructure.

Azure ATP release 2.82

Released June 18, 2019

  • New public preview
    Azure ATP's identity threat investigation experience is now in Public Preview, and available to all Azure ATP protected tenants. See Azure ATP Microsoft Cloud App Security investigation experience to learn more.

  • General availability
    Azure ATP support for untrusted forests is now in general availability. See Azure ATP multi-forest to learn more.

  • This version includes improvements and bug fixes for internal sensor infrastructure.

Azure ATP release 2.81

Released June 10, 2019

  • This version includes improvements and bug fixes for internal sensor infrastructure.

Azure ATP release 2.80

Released June 2, 2019

  • Feature enhancement: Suspicious VPN connection alert
    This alert now includes enhanced evidence and texts for better usability. For more information about alert features, and suggested remediation steps and prevention, see the Suspicious VPN connection alert description.

  • This version also includes improvements and bug fixes for internal sensor infrastructure.

Azure ATP release 2.79

Released May 26, 2019

  • General availability: Security principal reconnaissance (LDAP) (external ID 2038)

    This alert is now in GA (general availability). For more information about the alert, alert features and suggested remediation and prevention, see the Security principal reconnaissance (LDAP) alert description

  • This version also includes improvements and bug fixes for internal sensor infrastructure.

Azure ATP release 2.78

Released May 19, 2019

  • Feature enhancement: Sensitive entities
    Manual Sensitive tagging for Exchange Servers

    You can now manually tag entities as Exchange Servers during configuration.

    To manually tag an entity as an Exchange Server:

    1. In the Azure ATP portal, select Configuration.
    2. Under Detection, select Entity tags, then select Sensitive.
    3. Select Exchange Servers and then add the entity you wish to tag.

    After tagging a computer as an Exchange Server, it will be tagged as Sensitive and display that it was tagged as an Exchange Server. The Sensitive tag will appear in the computer's entity profile, and the computer will be considered in all detections that are based on Sensitive accounts and Lateral Movement Paths.

  • This version also includes improvements and bug fixes for internal sensor infrastructure.

Azure ATP release 2.77

Released May 12, 2019

  • This version includes improvements and bug fixes for internal sensor infrastructure.

Azure ATP release 2.76

Released May 6, 2019

  • This version includes improvements and bug fixes for internal sensor infrastructure.

Azure ATP release 2.75

Released April 28, 2019

  • Feature enhancement: Sensitive entities
    Starting from this version (2.75), machines identified as Exchange Servers by Azure ATP are now automatically tagged as Sensitive.

    Entities that are automatically tagged as Sensitive because they function as Exchange Servers list this classification as the reason they are tagged.

  • This version includes improvements and bug fixes for internal sensor infrastructure.

Azure ATP release 2.74

Releasing April 14, 2019

  • This version includes improvements and bug fixes for internal sensor infrastructure.

Azure ATP release 2.73

Released April 10, 2019

  • This version includes improvements and bug fixes for internal sensor infrastructure.

Azure ATP release 2.72

Released March 31, 2019

  • Feature enhancement: Lateral Movement Path (LMP) scoped depth
    Lateral movement paths (LMPs) are a key method for threat and risk discovery in Azure ATP. To help keep focus on the critical risks to your most sensitive users, this update makes it easier and faster to analyze and remediate risks to the sensitive users on each LMP, by limiting the scope and depth of each graph displayed.

    See Lateral Movement Paths to learn more about how Azure ATP uses LMPs to surface access risks to each entity in your environment.

  • This version also includes improvements and bug fixes for internal sensor infrastructure.

Azure ATP release 2.71

Released March 24, 2019

  • Feature enhancement: Network Name Resolution (NNR) health alerts
    Health alerts were added for confidence levels associated with Azure ATP security alerts that are based on NNR. Each health alert includes actionable and detailed recommendations to help resolve low NNR success rates.

    See What is Network Name Resolution to learn more about how Azure ATP uses NNR and why it's important for alert accuracy.

  • Server support: Support added for Server 2019 with use of KB4487044
    Support added for use of Windows Server 2019, with a patch level of KB4487044. Use of Server 2019 without the patch is not supported, and is blocked starting from this update.

  • Feature enhancement: User-based alert exclusion
    Extended alert exclusion options now allow for excluding specific users from specific alerts. Exclusions can help avoid situations where use or configuration of certain types of internal software repeatedly triggered benign security alerts.

  • This version also includes improvements and bug fixes for internal sensor infrastructure.

Azure ATP release 2.70

Released March 17, 2019

Azure ATP release 2.69

Released March 10, 2019

  • Feature enhancement: Suspected identity theft (pass-the-ticket) alert This alert now features new evidence showing the details of connections made by using remote desktop protocol (RDP). The added evidence makes it easy to remediate the known issue of (B-TP) Benign-True Positive alerts caused by use of Remote Credential Guard over RDP connections.

  • Feature enhancement: Remote code execution over DNS alert
    This alert now features new evidence showing your domain controller security update status, informing you when updates are required.

  • New documentation feature: Azure ATP Security alert MITRE ATT&CK Matrix™
    To explain and make it easier to map the relationship between Azure ATP security alerts and the familiar MITRE ATT&CK Matrix, we've added the relevant MITRE techniques to Azure ATP security alert listings. This additional reference makes it easier to understand the suspected attack technique potentially in use when an Azure ATP security alert is triggered. Learn more about the Azure ATP security alert guide.

  • This version also includes improvements and bug fixes for internal sensor infrastructure.

Azure ATP release 2.68

Released March 3, 2019

  • Feature enhancement: Suspected brute force attack (LDAP) alert
    Significant usability improvements were made to this security alert including a revised description, provision of additional source information, and guess attempt details for faster remediation.
    Learn more about Suspected brute force attack (LDAP) security alerts.

  • New documentation feature: Security alert lab
    To explain the power of Azure ATP in detecting the real threats to your working environment, we've added a new Security alert lab to this documentation. The Security alert lab helps you quickly set up a lab or testing environment, and explains the best defensive posturing against common, real-world threats and attacks.

    The step-by-step lab is designed to ensure you spend minimal time building, and more time learning about your threat landscape and available Azure ATP alerts and protection. We're excited to hear your feedback.

  • This version also includes improvements and bug fixes for internal sensor infrastructure.

Azure ATP release 2.67

Released February 24, 2019

  • New security alert: Security principal reconnaissance (LDAP) – (preview)
    Azure ATP's Security principal reconnaissance (LDAP) - preview security alert is now in public preview. In this detection, an Azure ATP security alert is triggered when security principal reconnaissance is used by attackers to gain critical information about the domain environment. This information helps attackers map the domain structure, as well as identify privileged accounts for use in later steps in their attack kill chain.

    Lightweight Directory Access Protocol (LDAP) is one the most popular methods used for both legitimate and malicious purposes to query Active Directory. LDAP focused security principal reconnaissance is commonly used as the first phase of a Kerberoasting attack. Kerberoasting attacks are used to get a target list of Security Principal Names (SPNs), which attackers then attempt to get Ticket Granting Server (TGS) tickets for.

  • Feature enhancement: Account enumeration reconnaissance (NTLM) alert
    Improved Account enumeration reconnaissance (NTLM) alert using additional analysis, and improved detection logic to reduce B-TP and FP alert results.

  • Feature enhancement: Network mapping reconnaissance (DNS) alert
    New types of detections added to Network mapping reconnaissance (DNS) alerts. In addition to detecting suspicious AXFR requests, Azure ATP now detects suspicious types of requests originating from non-DNS servers using an excessive number of requests.

  • This version also includes improvements and bug fixes for internal sensor infrastructure.

Azure ATP release 2.66

Released February 17, 2019

  • Feature enhancement: Suspected DCSync attack (replication of directory services) alert
    Usability improvements were made to this security alert including a revised description, provision of additional source information, new infographic, and more evidence. Learn more about Suspected DCSync attack (replication of directory services) security alerts.

  • This version also includes improvements and bug fixes for internal sensor infrastructure.

Azure ATP release 2.65

Released February 10, 2019

  • New security alert: Suspected NTLM relay attack (Exchange account) – (preview)
    Azure ATP's Suspected NTLM relay attack (Exchange account) - preview security alert is now in public preview. In this detection, an Azure ATP security alert is triggered when use of Exchange account credentials from a suspicious source is identified. These types of attacks attempt to leverage NTLM relay techniques to gain domain controller exchange privileges and are known as ExchangePriv. Learn more about the ExchangePriv technique from the ADV190007 advisory first published January 31, 2019, and the Azure ATP alert response.

  • General availability: Remote code execution over DNS
    This alert is now in GA (general availability). For more information and alert features, see the Remote code execution over DNS alert description page.

  • General availability: Data exfiltration over SMB
    This alert is now in GA (general availability). For more information and alert features, see the Data exfiltration over SMB alert description page.

  • This version also includes improvements and bug fixes for internal sensor infrastructure.

Azure ATP release 2.64

Released February 4, 2019

Azure ATP release 2.63

Released January 27, 2019

  • New feature: Untrusted forest support – (preview)
    Azure ATP's support for sensors in untrusted forests is now in public preview. From the Azure ATP portal Directory services page, configure additional sets of credentials to enable Azure ATP sensors to connect to different Active Directory forests, and report back to the Azure ATP service. See Azure ATP multi-forest to learn more.

  • New feature: Domain controller coverage
    Azure ATP now provides coverage information for Azure ATP monitored domain controllers.
    From the Azure ATP portal Sensors page, view the number of the monitored and unmonitored domain controllers detected by Azure ATP in your environment. Download the monitored domain controller list for further analysis, and to build an action plan. See the Domain controller monitoring how-to guide to learn more.

  • Feature enhancement: Account enumeration reconnaissance
    The Azure ATP account enumeration reconnaissance detection now detects and issues alerts for enumeration attempts using Kerberos and NTLM. Previously, the detection only worked for attempts using Kerberos. See Azure ATP reconnaissance alerts to learn more.

  • Feature enhancement: Remote code execution attempt alert

    • All remote execution activities, such as service creation, WMI execution, and the new PowerShell execution, were added to the profile timeline of the destination machine. The destination machine is the domain controller the command was executed on.
    • PowerShell execution was added to the list of remote code execution activities listed in the entity profile alert timeline.
    • See Remote code execution attempt to learn more.
  • Windows Server 2019 LSASS issue and Azure ATP
    In response to customer feedback regarding Azure ATP usage with domain controllers running Windows Server 2019, this update includes additional logic to avoid triggering the reported behavior on Windows Server 2019 machines. Full support for Azure ATP sensor on Windows Server 2019 is planned for a future Azure ATP update, however installing and running Azure ATP on Windows Servers 2019 is not currently supported. See Azure ATP sensor requirements to learn more.

  • This version also includes improvements and bug fixes for internal sensor infrastructure.

Azure ATP release 2.62

Released January 20, 2019

  • New security alert: Remote code execution over DNS – (preview)
    Azure ATP's Remote code execution over DNS security alert is now in public preview. In this detection, an Azure ATP security alert is triggered when DNS queries suspected of exploiting security vulnerability CVE-2018-8626 are made against a domain controller in the network.

  • Feature Enhancement: 72 hour delayed sensor update
    Changed option to delay sensor updates on selected sensors to 72 hours (instead of the previous 24-hour delay) after each release update of Azure ATP. See Azure ATP sensor update for configuration instructions.

  • This version also includes improvements and bug fixes for internal sensor infrastructure.

Azure ATP release 2.61

Released January 13, 2019

  • New Security Alert: Data exfiltration over SMB - (preview)
    Azure ATP's Data exfiltration over SMB security alert is now in public preview. Attackers with domain admin rights can compromise the KRBTGT account. Using the KRBTGT account, attackers can create a Kerberos ticket granting ticket (TGT) that provide authorization to any resource.

  • Feature Enhancement: Remote code execution attempt security alert
    A new alert description and additional evidence were added to help make the alert easier to understand, and provide better investigation workflows.

  • Feature Enhancement: DNS query logical activities
    Additional query types were added to Azure ATP monitored activities including: TXT, MX, NS, SRV, ANY, DNSKEY.

  • Feature Enhancement: Suspected Golden Ticket usage (ticket anomaly) and Suspected Golden Ticket usage (nonexistent account)
    Improved detection logic has been applied to both alerts to reduce the number of FP alerts, and deliver more accurate results.

  • Feature Enhancement: Azure ATP Security Alert documentation
    Azure ATP security alert documentation has been enhanced and expanded to include better alert descriptions, more accurate alert classifications, and explanations of evidence, remediation, and prevention. Get familiar with the new security alert documentation design using the following links:

  • This version also includes improvements and bug fixes for internal sensor infrastructure.

Azure ATP release 2.60

Released January 6, 2019

  • This version includes improvements and bug fixes for internal sensor infrastructure.

Azure ATP release 2.59

Released December 16, 2018

  • This version includes improvements and bug fixes for internal sensor infrastructure.

Azure ATP release 2.58

Released December 9, 2018

  • Security Alert Enhancement: Unusual Protocol Implementation alert split
    Azure ATP's series of Unusual Protocol Implementation security alerts that previously shared 1 externalId (2002), are now split into four distinctive alerts, with a corresponding unique external ID.

New alert externalIds

New security alert name Previous security alert name Unique external ID
Suspected brute force attack (SMB) Unusual protocol implementation (potential use of malicious tools such as Hydra) 2033
Suspected overpass-the-hash attack (Kerberos) Unusual Kerberos protocol implementation (potential overpass-the-hash attack) 2002
Suspected use of Metasploit hacking framework Unusual protocol implementation (potential use of Metasploit hacking tools) 2034
Suspected WannaCry ransomware attack Unusual protocol implementation (potential WannaCry ransomware attack) 2035
  • New monitored activity: File copy through SMB
    Copying of files using SMB is now a monitored and filterable activity. Learn more about which activities Azure ATP monitors, and how to filter and search monitored activities in the portal.

  • Large Lateral Movement Path image enhancement
    When viewing large lateral movement paths, Azure ATP now highlights only the nodes connected to a selected entity, instead of blurring the other nodes. This change introduces a significant improvement in large LMP rendering speed.

  • This version includes improvements and bug fixes for internal sensor infrastructure.

Azure ATP release 2.57

Released December 2, 2018

  • New Security Alert: Suspected Golden ticket usage- ticket anomaly (preview)
    Azure ATP's Suspected Golden Ticket usage - ticket anomaly security alert is now in public preview. Attackers with domain admin rights can compromise the KRBTGT account. Using the KRBTGT account, attackers can create a Kerberos ticket granting ticket (TGT) that provides authorization to any resource.

    This forged TGT is called a "Golden Ticket" because it allows attackers to achieve lasting network persistence. Forged Golden Tickets of this type have unique characteristics this new detection is designed to identify.

  • Feature Enhancement: Automated Azure ATP instance (workspace) creation
    From today, Azure ATP workspaces are renamed Azure ATP instances. Azure ATP now supports one Azure ATP instance per Azure ATP account. Instances for new customers are created using the instance creation wizard in the Azure ATP portal. Existing Azure ATP workspaces are converted automatically to Azure ATP instances with this update.

    To learn more about Azure ATP instances, see Create your Azure ATP instance.

  • This version includes improvements and bug fixes for internal sensor infrastructure.

Azure ATP release 2.56

Released November 25, 2018

  • Feature Enhancement: Lateral Movement Paths (LMPs)
    Two additional features are added to enhance Azure ATP Lateral Movement Path (LMP) capabilities:

    • LMP history is now saved and discoverable per entity, and when using LMP reports.
    • Follow an entity in an LMP via the activity timeline, and investigate using additional evidence provided for discovery of potential attack paths.

    See Azure ATP Lateral Movement Paths to learn more about how to use and investigate with enhanced LMPs.

  • Documentation enhancements: Lateral Movement Paths, Security Alert names
    Additions and updates were made to Azure ATP articles describing Lateral Movement Path descriptions and features, name mapping was added for all instances of old security alert names to new names and externalIds.

  • This version includes improvements and bug fixes for internal sensor infrastructure.

For details of each Defender for Identity release prior to (and including) release 2.55, see the Defender for Identity release reference.

See Also