November 14, 2024
Microsoft Azure Incident Response Use cases and Playbooks – Sentinel
A large number of Enterprises today run on Microsoft technologies, Azure cloud platform and security logging platforms as Sentinel. Responding diligently to alerts triggered due to abnormality and intrusion detections is key to avoid major crisis like Ransomware attacks and Data exfiltrations followed by publish on dark web.
The below use cases are critical to identifying any of the early, middle, and end-stage operations of the threat actors. A small abnormal event can be a clue to a larger adversarial attack.
Azure Security Center and Azure Defender are now called Microsoft Defender for Cloud.
- VM Run Command operations executing a unique PowerShell script
- VM Run Command operation executed during suspicious login window
- Azure Portal Sign-in from another Azure Tenant
- VM Run Command executed from Azure IP address
- VM Run Command linked with MDE
- Dormant Service Principal Update Creds and Logs In
- Dormant User Update MFA and Logs In
- Suspicious Addition of an Exchange related App Role
- Activity from password-spray associated IP address
- Unusual addition of credentials to an OAuth app
- Unusual ISP for an OAuth app
- Suspicious Run Command invocation detected
Azure
- Active Directory Risky Sign-In
- AD Login Without MFA
- Firewall Threat Intelligence Alert
- Frontdoor WAF Blocked a Request
- Frontdoor WAF Logged a Request
- Login Explicitly Denied MFA
- Network Security Group Open to the World
- Network Security Groups or Rules Created, Modified, or Deleted
- New owner added for service principal
- New Owner added to Azure Active Directory application
- New Service Principal created
- Policy Assignment Created
- Portal brute force login
- SQL Server Firewall Rules Created or Modified
- User invited an external user
- User ran a command on virtual machine
- Credential Stuffing Attack on Azure
Security Defaults is enabled on Azure Active Directory
Detailed list of use case for which we can provide you the Playbooks.
| A logon from a malicious IP has been detected. [seen multiple times] | A successful remote authentication for the account [account] and process [process] occurred, however the logon IP address (x.x.x.x) has previously been reported as malicious or highly unusual. A successful attack has probably occurred. Files with the .scr extensions are screen saver files and are normally reside and execute from the Windows system directory. | – | High |
| A logon from a malicious IP has been detected (VM_ThreatIntelSuspectLogon) | A successful remote authentication for the account [account] and process [process] occurred, however the logon IP address (x.x.x.x) has previously been reported as malicious or highly unusual. A successful attack has probably occurred. | Initial access | High |
| Addition of Guest account to Local Administrators group | Analysis of host data has detected the addition of the built-in Guest account to the Local Administrators group on %{Compromised Host}, which is strongly associated with attacker activity. | – | Medium |
| An event log was cleared | Machine logs indicate a suspicious event log clearing operation by user: ‘%{user name}’ in Machine: ‘%{CompromisedEntity}’. The %{log channel} log was cleared. | – | Informational |
| Antimalware Action Failed | Microsoft Antimalware has encountered an error when taking an action on malware or other potentially unwanted software. | – | Medium |
| Antimalware Action Taken | Microsoft Antimalware for Azure has taken an action to protect this machine from malware or other potentially unwanted software. | – | Medium |
| Antimalware broad files exclusion in your virtual machine (VM_AmBroadFilesExclusion) | Files exclusion from antimalware extension with broad exclusion rule was detected in your virtual machine by analyzing the Azure Resource Manager operations in your subscription. Such exclusion practically disabling the Antimalware protection. Attackers might exclude files from the antimalware scan on your virtual machine to prevent detection while running arbitrary code or infecting the machine with malware. | – | Medium |
| Antimalware disabled and code execution in your virtual machine (VM_AmDisablementAndCodeExecution) | Antimalware disabled at the same time as code execution on your virtual machine. This was detected by analyzing Azure Resource Manager operations in your subscription. Attackers disable antimalware scanners to prevent detection while running unauthorized tools or infecting the machine with malware. | – | High |
| Antimalware disabled in your virtual machine (VM_AmDisablement) | Antimalware disabled in your virtual machine. This was detected by analyzing Azure Resource Manager operations in your subscription. Attackers might disable the antimalware on your virtual machine to prevent detection. | Defense Evasion | Medium |
| Antimalware file exclusion and code execution in your virtual machine (VM_AmFileExclusionAndCodeExecution) | File excluded from your antimalware scanner at the same time as code was executed via a custom script extension on your virtual machine. This was detected by analyzing Azure Resource Manager operations in your subscription. Attackers might exclude files from the antimalware scan on your virtual machine to prevent detection while running unauthorized tools or infecting the machine with malware. | Defense Evasion, Execution | High |
| Antimalware file exclusion and code execution in your virtual machine (VM_AmTempFileExclusionAndCodeExecution) | Temporary file exclusion from antimalware extension in parallel to execution of code via custom script extension was detected in your virtual machine by analyzing the Azure Resource Manager operations in your subscription. Attackers might exclude files from the antimalware scan on your virtual machine to prevent detection while running arbitrary code or infecting the machine with malware. | Defense Evasion, Execution | High |
| Antimalware file exclusion in your virtual machine (VM_AmTempFileExclusion) | File excluded from your antimalware scanner on your virtual machine. This was detected by analyzing Azure Resource Manager operations in your subscription. Attackers might exclude files from the antimalware scan on your virtual machine to prevent detection while running unauthorized tools or infecting the machine with malware. | Defense Evasion | Medium |
| Antimalware real-time protection was disabled in your virtual machine (VM_AmRealtimeProtectionDisabled) | Real-time protection disablement of the antimalware extension was detected in your virtual machine by analyzing the Azure Resource Manager operations in your subscription. Attackers might disable real-time protection from the antimalware scan on your virtual machine to avoid detection while running arbitrary code or infecting the machine with malware. | Defense Evasion | Medium |
| Antimalware real-time protection was disabled temporarily in your virtual machine (VM_AmTempRealtimeProtectionDisablement) | Real-time protection temporary disablement of the antimalware extension was detected in your virtual machine by analyzing the Azure Resource Manager operations in your subscription. Attackers might disable real-time protection from the antimalware scan on your virtual machine to avoid detection while running arbitrary code or infecting the machine with malware. | Defense Evasion | Medium |
| Antimalware real-time protection was disabled temporarily while code was executed in your virtual machine (VM_AmRealtimeProtectionDisablementAndCodeExec) | Real-time protection temporary disablement of the antimalware extension in parallel to code execution via custom script extension was detected in your virtual machine by analyzing the Azure Resource Manager operations in your subscription. Attackers might disable real-time protection from the antimalware scan on your virtual machine to avoid detection while running arbitrary code or infecting the machine with malware. | – | High |
| Antimalware scans blocked for files potentially related to malware campaigns on your virtual machine (Preview) (VM_AmMalwareCampaignRelatedExclusion) | An exclusion rule was detected in your virtual machine to prevent your antimalware extension scanning certain files that are suspected of being related to a malware campaign. The rule was detected by analyzing the Azure Resource Manager operations in your subscription. Attackers might exclude files from antimalware scans to prevent detection while running arbitrary code or infecting the machine with malware. | Defense Evasion | Medium |
| Antimalware temporarily disabled in your virtual machine (VM_AmTemporarilyDisablement) | Antimalware temporarily disabled in your virtual machine. This was detected by analyzing Azure Resource Manager operations in your subscription. Attackers might disable the antimalware on your virtual machine to prevent detection. | – | Medium |
| Antimalware unusual file exclusion in your virtual machine (VM_UnusualAmFileExclusion) | Unusual file exclusion from antimalware extension was detected in your virtual machine by analyzing the Azure Resource Manager operations in your subscription. Attackers might exclude files from the antimalware scan on your virtual machine to prevent detection while running arbitrary code or infecting the machine with malware. | Defense Evasion | Medium |
| Custom script extension with suspicious command in your virtual machine (VM_CustomScriptExtensionSuspiciousCmd) | Custom script extension with suspicious command was detected in your virtual machine by analyzing the Azure Resource Manager operations in your subscription. Attackers may use custom script extension to execute a malicious code on your virtual machine via the Azure Resource Manager. | Execution | Medium |
| Custom script extension with suspicious entry-point in your virtual machine (VM_CustomScriptExtensionSuspiciousEntryPoint) | Custom script extension with a suspicious entry-point was detected in your virtual machine by analyzing the Azure Resource Manager operations in your subscription. The entry-point refers to a suspicious GitHub repository. Attackers may use custom script extensions to execute malicious code on your virtual machines via the Azure Resource Manager. | Execution | Medium |
| Custom script extension with suspicious payload in your virtual machine (VM_CustomScriptExtensionSuspiciousPayload) | Custom script extension with a payload from a suspicious GitHub repository was detected in your virtual machine by analyzing the Azure Resource Manager operations in your subscription. Attackers may use custom script extensions to execute malicious code on your virtual machines via the Azure Resource Manager. | Execution | Medium |
| Detected actions indicative of disabling and deleting IIS log files | Analysis of host data detected actions that show IIS log files being disabled and/or deleted. | – | Medium |
| Detected anomalous mix of upper and lower case characters in command-line | Analysis of host data on %{Compromised Host} detected a command line with anomalous mix of upper and lower case characters. This kind of pattern, while possibly benign, is also typical of attackers trying to hide from case-sensitive or hash-based rule matching when performing administrative tasks on a compromised host. | – | Medium |
| Detected change to a registry key that can be abused to bypass UAC | Analysis of host data on %{Compromised Host} detected that a registry key that can be abused to bypass UAC (User Account Control) was changed. This kind of configuration, while possibly benign, is also typical of attacker activity when trying to move from unprivileged (standard user) to privileged (for example administrator) access on a compromised host. | – | Medium |
| Detected decoding of an executable using built-in certutil.exe tool | Analysis of host data on %{Compromised Host} detected that certutil.exe, a built-in administrator utility, was being used to decode an executable instead of its mainstream purpose that relates to manipulating certificates and certificate data. Attackers are known to abuse functionality of legitimate administrator tools to perform malicious actions, for example using a tool such as certutil.exe to decode a malicious executable that will then be subsequently executed. | – | High |
| Detected enabling of the WDigest UseLogonCredential registry key | Analysis of host data detected a change in the registry key HKLM\SYSTEM\CurrentControlSet\Control\SecurityProviders\WDigest\ “UseLogonCredential”. Specifically this key has been updated to allow logon credentials to be stored in clear text in LSA memory. Once enabled an attacker can dump clear text passwords from LSA memory with credential harvesting tools such as Mimikatz. | – | Medium |
| Detected encoded executable in command line data | Analysis of host data on %{Compromised Host} detected a base-64 encoded executable. This has previously been associated with attackers attempting to construct executables on-the-fly through a sequence of commands, and attempting to evade intrusion detection systems by ensuring that no individual command would trigger an alert. This could be legitimate activity, or an indication of a compromised host. | – | High |
| Detected obfuscated command line | Attackers use increasingly complex obfuscation techniques to evade detections that run against the underlying data. Analysis of host data on %{Compromised Host} detected suspicious indicators of obfuscation on the commandline. | – | Informational |
| Detected Petya ransomware indicators | Analysis of host data on %{Compromised Host} detected indicators associated with Petya ransomware. See https://blogs.technet.microsoft.com/mmpc/2017/06/27/new-ransomware-old-techniques-petya-adds-worm-capabilities/ for more information. Review the command line associated in this alert and escalate this alert to your security team. | – | High |
| Detected possible execution of keygen executable | Analysis of host data on %{Compromised Host} detected execution of a process whose name is indicative of a keygen tool; such tools are typically used to defeat software licensing mechanisms but their download is often bundled with other malicious software. Activity group GOLD has been known to make use of such keygens to covertly gain back door access to hosts that they compromise. | – | Medium |
| Detected possible execution of malware dropper | Analysis of host data on %{Compromised Host} detected a filename that has previously been associated with one of activity group GOLD’s methods of installing malware on a victim host. | – | High |
| Detected possible local reconnaissance activity | Analysis of host data on %{Compromised Host} detected a combination of systeminfo commands that has previously been associated with one of activity group GOLD’s methods of performing reconnaissance activity. While ‘systeminfo.exe’ is a legitimate Windows tool, executing it twice in succession in the way that has occurred here is rare. | – | |
| Detected potentially suspicious use of Telegram tool | Analysis of host data shows installation of Telegram, a free cloud-based instant messaging service that exists both for mobile and desktop system. Attackers are known to abuse this service to transfer malicious binaries to any other computer, phone, or tablet. | – | Medium |
| Detected suppression of legal notice displayed to users at logon | Analysis of host data on %{Compromised Host} detected changes to the registry key that controls whether a legal notice is displayed to users when they log on. Microsoft security analysis has determined that this is a common activity undertaken by attackers after having compromised a host. | – | Low |
| Detected suspicious combination of HTA and PowerShell | mshta.exe (Microsoft HTML Application Host) which is a signed Microsoft binary is being used by the attackers to launch malicious PowerShell commands. Attackers often resort to having an HTA file with inline VBScript. When a victim browses to the HTA file and chooses to run it, the PowerShell commands and scripts that it contains are executed. Analysis of host data on %{Compromised Host} detected mshta.exe launching PowerShell commands. | – | Medium |
| Detected suspicious commandline arguments | Analysis of host data on %{Compromised Host} detected suspicious commandline arguments that have been used in conjunction with a reverse shell used by activity group HYDROGEN. | – | High |
| Detected suspicious commandline used to start all executables in a directory | Analysis of host data has detected a suspicious process running on %{Compromised Host}. The commandline indicates an attempt to start all executables (*.exe) that may reside in a directory. This could be an indication of a compromised host. | – | Medium |
| Detected suspicious credentials in commandline | Analysis of host data on %{Compromised Host} detected a suspicious password being used to execute a file by activity group BORON. This activity group has been known to use this password to execute Pirpi malware on a victim host. | – | High |
| Detected suspicious document credentials | Analysis of host data on %{Compromised Host} detected a suspicious, common precomputed password hash used by malware being used to execute a file. Activity group HYDROGEN has been known to use this password to execute malware on a victim host. | – | High |
| Detected suspicious execution of VBScript.Encode command | Analysis of host data on %{Compromised Host} detected the execution of VBScript.Encode command. This encodes the scripts into unreadable text, making it more difficult for users to examine the code. Microsoft threat research shows that attackers often use encoded VBscript files as part of their attack to evade detection systems. This could be legitimate activity, or an indication of a compromised host. | – | Medium |
| Detected suspicious execution via rundll32.exe | Analysis of host data on %{Compromised Host} detected rundll32.exe being used to execute a process with an uncommon name, consistent with the process naming scheme previously seen used by activity group GOLD when installing their first stage implant on a compromised host. | – | High |
| Detected suspicious file cleanup commands | Analysis of host data on %{Compromised Host} detected a combination of systeminfo commands that has previously been associated with one of activity group GOLD’s methods of performing post-compromise self-cleanup activity. While ‘systeminfo.exe’ is a legitimate Windows tool, executing it twice in succession, followed by a delete command in the way that has occurred here is rare. | – | High |
| Detected suspicious file creation | Analysis of host data on %{Compromised Host} detected creation or execution of a process which has previously indicated post-compromise action taken on a victim host by activity group BARIUM. This activity group has been known to use this technique to download additional malware to a compromised host after an attachment in a phishing doc has been opened. | – | High |
| Detected suspicious named pipe communications | Analysis of host data on %{Compromised Host} detected data being written to a local named pipe from a Windows console command. Named pipes are known to be a channel used by attackers to task and communicate with a malicious implant. This could be legitimate activity, or an indication of a compromised host. | – | High |
| Detected suspicious network activity | Analysis of network traffic from %{Compromised Host} detected suspicious network activity. Such traffic, while possibly benign, is typically used by an attacker to communicate with malicious servers for downloading of tools, command-and-control and exfiltration of data. Typical related attacker activity includes copying remote administration tools to a compromised host and exfiltrating user data from it. | – | Low |
| Detected suspicious new firewall rule | Analysis of host data detected a new firewall rule has been added via netsh.exe to allow traffic from an executable in a suspicious location. | – | Medium |
| Detected suspicious use of Cacls to lower the security state of the system | Attackers use myriad ways like brute force, spear phishing etc. to achieve initial compromise and get a foothold on the network. Once initial compromise is achieved they often take steps to lower the security settings of a system. Cacls—short for change access control list is Microsoft Windows native command-line utility often used for modifying the security permission on folders and files. A lot of time the binary is used by the attackers to lower the security settings of a system. This is done by giving Everyone full access to some of the system binaries like ftp.exe, net.exe, wscript.exe etc. Analysis of host data on %{Compromised Host} detected suspicious use of Cacls to lower the security of a system. | – | Medium |
| Detected suspicious use of FTP -s Switch | Analysis of process creation data from the %{Compromised Host} detected the use of the FTP “-s:filename” switch. This switch is used to specify an FTP script file for the client to run. Malware or malicious processes are known to use this FTP switch (-s:filename) to point to a script file which is configured to connect to a remote FTP server and download additional malicious binaries. | – | Medium |
| Detected suspicious use of Pcalua.exe to launch executable code | Analysis of host data on %{Compromised Host} detected the use of pcalua.exe to launch executable code. Pcalua.exe is component of the Microsoft Windows “Program Compatibility Assistant” which detects compatibility issues during the installation or execution of a program. Attackers are known to abuse functionality of legitimate Windows system tools to perform malicious actions, for example using pcalua.exe with the -a switch to launch malicious executables either locally or from remote shares. | – | Medium |
| Detected the disabling of critical services | The analysis of host data on %{Compromised Host} detected execution of “net.exe stop” command being used to stop critical services like SharedAccess or the Windows Security app. The stopping of either of these services can be indication of a malicious behavior. | – | Medium |
| Digital currency mining related behavior detected | Analysis of host data on %{Compromised Host} detected the execution of a process or command normally associated with digital currency mining. | – | High |
| Dynamic PS script construction | Analysis of host data on %{Compromised Host} detected a PowerShell script being constructed dynamically. Attackers sometimes use this approach of progressively building up a script in order to evade IDS systems. This could be legitimate activity, or an indication that one of your machines has been compromised. | – | Medium |
| Executable found running from a suspicious location | Analysis of host data detected an executable file on %{Compromised Host} that is running from a location in common with known suspicious files. This executable could either be legitimate activity, or an indication of a compromised host. | – | High |
| Fileless attack behavior detected (VM_FilelessAttackBehavior.Windows) | The memory of the process specified contains behaviors commonly used by fileless attacks. Specific behaviors include: 1) Shellcode, which is a small piece of code typically used as the payload in the exploitation of a software vulnerability. 2) Active network connections. See NetworkConnections below for details. 3) Function calls to security sensitive operating system interfaces. See Capabilities below for referenced OS capabilities. 4) Contains a thread that was started in a dynamically allocated code segment. This is a common pattern for process injection attacks. | Defense Evasion | Low |
| Fileless attack technique detected (VM_FilelessAttackTechnique.Windows) | The memory of the process specified below contains evidence of a fileless attack technique. Fileless attacks are used by attackers to execute code while evading detection by security software. Specific behaviors include: 1) Shellcode, which is a small piece of code typically used as the payload in the exploitation of a software vulnerability. 2) Executable image injected into the process, such as in a code injection attack. 3) Active network connections. See NetworkConnections below for details. 4) Function calls to security sensitive operating system interfaces. See Capabilities below for referenced OS capabilities. 5) Process hollowing, which is a technique used by malware in which a legitimate process is loaded on the system to act as a container for hostile code. 6) Contains a thread that was started in a dynamically allocated code segment. This is a common pattern for process injection attacks. | Defense Evasion, Execution | High |
| Fileless attack toolkit detected (VM_FilelessAttackToolkit.Windows) | The memory of the process specified contains a fileless attack toolkit: [toolkit name]. Fileless attack toolkits use techniques that minimize or eliminate traces of malware on disk, and greatly reduce the chances of detection by disk-based malware scanning solutions. Specific behaviors include: 1) Well-known toolkits and crypto mining software. 2) Shellcode, which is a small piece of code typically used as the payload in the exploitation of a software vulnerability. 3) Injected malicious executable in process memory. | Defense Evasion, Execution | Medium |
| High risk software detected | Analysis of host data from %{Compromised Host} detected the usage of software that has been associated with the installation of malware in the past. A common technique utilized in the distribution of malicious software is to package it within otherwise benign tools such as the one seen in this alert. Upon using these tools, the malware can be silently installed in the background. | – | Medium |
| Local Administrators group members were enumerated | Machine logs indicate a successful enumeration on group %{Enumerated Group Domain Name}%{Enumerated Group Name}. Specifically, %{Enumerating User Domain Name}%{Enumerating User Name} remotely enumerated the members of the %{Enumerated Group Domain Name}%{Enumerated Group Name} group. This activity could either be legitimate activity, or an indication that a machine in your organization has been compromised and used to reconnaissance %{vmname}. | – | Informational |
| Malicious firewall rule created by ZINC server implant [seen multiple times] | A firewall rule was created using techniques that match a known actor, ZINC. The rule was possibly used to open a port on %{Compromised Host} to allow for Command & Control communications. This behavior was seen [x] times today on the following machines: [Machine names] | – | High |
| Malicious SQL activity | Machine logs indicate that ‘%{process name}’ was executed by account: %{user name}. This activity is considered malicious. | – | High |
| Multiple Domain Accounts Queried | Analysis of host data has determined that an unusual number of distinct domain accounts are being queried within a short time period from %{Compromised Host}. This kind of activity could be legitimate, but can also be an indication of compromise. | – | Medium |
| Possible credential dumping detected [seen multiple times] | Analysis of host data has detected use of native windows tool (e.g. sqldumper.exe) being used in a way that allows to extract credentials from memory. Attackers often use these techniques to extract credentials that they then further use for lateral movement and privilege escalation. This behavior was seen [x] times today on the following machines: [Machine names] | – | Medium |
| Potential attempt to bypass AppLocker detected | Analysis of host data on %{Compromised Host} detected a potential attempt to bypass AppLocker restrictions. AppLocker can be configured to implement a policy that limits what executables are allowed to run on a Windows system. The command-line pattern similar to that identified in this alert has been previously associated with attacker attempts to circumvent AppLocker policy by using trusted executables (allowed by AppLocker policy) to execute untrusted code. This could be legitimate activity, or an indication of a compromised host. | – | High |
| PsExec execution detected (VM_RunByPsExec) | Analysis of host data indicates that the process %{Process Name} was executed by PsExec utility. PsExec can be used for running processes remotely. This technique might be used for malicious purposes. | Lateral Movement, Execution | Informational |
| Ransomware indicators detected [seen multiple times] | Analysis of host data indicates suspicious activity traditionally associated with lock-screen and encryption ransomware. Lock screen ransomware displays a full-screen message preventing interactive use of the host and access to its files. Encryption ransomware prevents access by encrypting data files. In both cases a ransom message is typically displayed, requesting payment in order to restore file access. This behavior was seen [x] times today on the following machines: [Machine names] | – | High |
| Ransomware indicators detected | Analysis of host data indicates suspicious activity traditionally associated with lock-screen and encryption ransomware. Lock screen ransomware displays a full-screen message preventing interactive use of the host and access to its files. Encryption ransomware prevents access by encrypting data files. In both cases a ransom message is typically displayed, requesting payment in order to restore file access. | – | High |
| Rare SVCHOST service group executed (VM_SvcHostRunInRareServiceGroup) | The system process SVCHOST was observed running a rare service group. Malware often uses SVCHOST to masquerade its malicious activity. | Defense Evasion, Execution | Informational |
| Sticky keys attack detected | Analysis of host data indicates that an attacker may be subverting an accessibility binary (for example sticky keys, onscreen keyboard, narrator) in order to provide backdoor access to the host %{Compromised Host}. | – | Medium |
| Successful brute force attack (VM_LoginBruteForceSuccess) | Several sign in attempts were detected from the same source. Some successfully authenticated to the host. This resembles a burst attack, in which an attacker performs numerous authentication attempts to find valid account credentials. | Exploitation | Medium/High |
| Suspect integrity level indicative of RDP hijacking | Analysis of host data has detected the tscon.exe running with SYSTEM privileges – this can be indicative of an attacker abusing this binary in order to switch context to any other logged on user on this host; it is a known attacker technique to compromise additional user accounts and move laterally across a network. | – | Medium |
| Suspect service installation | Analysis of host data has detected the installation of tscon.exe as a service: this binary being started as a service potentially allows an attacker to trivially switch to any other logged on user on this host by hijacking RDP connections; it is a known attacker technique to compromise additional user accounts and move laterally across a network. | – | Medium |
| Suspected Kerberos Golden Ticket attack parameters observed | Analysis of host data detected commandline parameters consistent with a Kerberos Golden Ticket attack. | – | Medium |
| Suspicious Account Creation Detected | Analysis of host data on %{Compromised Host} detected creation or use of a local account %{Suspicious account name} : this account name closely resembles a standard Windows account or group name ‘%{Similar To Account Name}’. This is potentially a rogue account created by an attacker, so named in order to avoid being noticed by a human administrator. | – | Medium |
| Suspicious Activity Detected (VM_SuspiciousActivity) | Analysis of host data has detected a sequence of one or more processes running on %{machine name} that have historically been associated with malicious activity. While individual commands may appear benign the alert is scored based on an aggregation of these commands. This could either be legitimate activity, or an indication of a compromised host. | Execution | Medium |
| Suspicious authentication activity (VM_LoginBruteForceValidUserFailed) | Although none of them succeeded, some of them used accounts were recognized by the host. This resembles a dictionary attack, in which an attacker performs numerous authentication attempts using a dictionary of predefined account names and passwords in order to find valid credentials to access the host. This indicates that some of your host account names might exist in a well-known account name dictionary. | Probing | Medium |
| Suspicious code segment detected | Indicates that a code segment has been allocated by using non-standard methods, such as reflective injection and process hollowing. The alert provides additional characteristics of the code segment that have been processed to provide context for the capabilities and behaviors of the reported code segment. | – | Medium |
| Suspicious command execution (VM_SuspiciousCommandLineExecution) | Machine logs indicate a suspicious command-line execution by user %{user name}. | Execution | High |
| Suspicious double extension file executed | Analysis of host data indicates an execution of a process with a suspicious double extension. This extension may trick users into thinking files are safe to be opened and might indicate the presence of malware on the system. | – | High |
| Suspicious download using Certutil detected [seen multiple times] | Analysis of host data on %{Compromised Host} detected the use of certutil.exe, a built-in administrator utility, for the download of a binary instead of its mainstream purpose that relates to manipulating certificates and certificate data. Attackers are known to abuse functionality of legitimate administrator tools to perform malicious actions, for example using certutil.exe to download and decode a malicious executable that will then be subsequently executed. This behavior was seen [x] times today on the following machines: [Machine names] | – | Medium |
| Suspicious download using Certutil detected | Analysis of host data on %{Compromised Host} detected the use of certutil.exe, a built-in administrator utility, for the download of a binary instead of its mainstream purpose that relates to manipulating certificates and certificate data. Attackers are known to abuse functionality of legitimate administrator tools to perform malicious actions, for example using certutil.exe to download and decode a malicious executable that will then be subsequently executed. | – | Medium |
| Suspicious failed execution of custom script extension in your virtual machine (VM_CustomScriptExtensionSuspiciousFailure) | Suspicious failure of a custom script extension was detected in your virtual machine by analyzing the Azure Resource Manager operations in your subscription. Such failures may be associated with malicious scripts run by this extension. | Execution | Medium |
| Suspicious PowerShell Activity Detected | Analysis of host data detected a PowerShell script running on %{Compromised Host} that has features in common with known suspicious scripts. This script could either be legitimate activity, or an indication of a compromised host. | – | High |
| Suspicious PowerShell cmdlets executed | Analysis of host data indicates execution of known malicious PowerShell PowerSploit cmdlets. | – | Medium |
| Suspicious process executed [seen multiple times] | Machine logs indicate that the suspicious process: ‘%{Suspicious Process}’ was running on the machine, often associated with attacker attempts to access credentials. This behavior was seen [x] times today on the following machines: [Machine names] | – | High |
| Suspicious process executed | Machine logs indicate that the suspicious process: ‘%{Suspicious Process}’ was running on the machine, often associated with attacker attempts to access credentials. | – | High |
| Suspicious process name detected [seen multiple times] | Analysis of host data on %{Compromised Host} detected a process whose name is suspicious, for example corresponding to a known attacker tool or named in a way that is suggestive of attacker tools that try to hide in plain sight. This process could be legitimate activity, or an indication that one of your machines has been compromised. This behavior was seen [x] times today on the following machines: [Machine names] | – | Medium |
| Suspicious process name detected | Analysis of host data on %{Compromised Host} detected a process whose name is suspicious, for example corresponding to a known attacker tool or named in a way that is suggestive of attacker tools that try to hide in plain sight. This process could be legitimate activity, or an indication that one of your machines has been compromised. | – | Medium |
| Suspicious process termination burst (VM_TaskkillBurst) | Analysis of host data indicates a suspicious process termination burst in %{Machine Name}. Specifically, %{NumberOfCommands} processes were killed between %{Begin} and %{Ending}. | Defense Evasion | Low |
| Suspicious Screensaver process executed (VM_SuspiciousScreenSaverExecution) | The process ‘%{process name}’ was observed executing from an uncommon location. Files with the .scr extensions are screen saver files and are normally reside and execute from the Windows system directory. | Defense Evasion, Execution | Medium |
| Suspicious SQL activity | Machine logs indicate that ‘%{process name}’ was executed by account: %{user name}. This activity is uncommon with this account. | – | Medium |
| Suspicious SVCHOST process executed | The system process SVCHOST was observed running in an abnormal context. Malware often uses SVCHOST to masquerade its malicious activity. | – | High |
| Suspicious system process executed (VM_SystemProcessInAbnormalContext) | The system process %{process name} was observed running in an abnormal context. Malware often uses this process name to masquerade its malicious activity. | Defense Evasion, Execution | High |
| Suspicious Volume Shadow Copy Activity | Analysis of host data has detected a shadow copy deletion activity on the resource. Volume Shadow Copy (VSC) is an important artifact that stores data snapshots. Some malware and specifically Ransomware, targets VSC to sabotage backup strategies. | – | High |
| Suspicious WindowPosition registry value detected | Analysis of host data on %{Compromised Host} detected an attempted WindowPosition registry configuration change that could be indicative of hiding application windows in non-visible sections of the desktop. This could be legitimate activity, or an indication of a compromised machine: this type of activity has been previously associated with known adware (or unwanted software) such as Win32/OneSystemCare and Win32/SystemHealer and malware such as Win32/Creprote. When the WindowPosition value is set to 201329664, (Hex: 0x0c00 0c00, corresponding to X-axis=0c00 and the Y-axis=0c00) this places the console app’s window in a non-visible section of the user’s screen in an area that is hidden from view below the visible start menu/taskbar. Known suspect Hex value includes, but not limited to c000c000 | – | Low |
| Suspiciously named process detected | Analysis of host data on %{Compromised Host} detected a process whose name is very similar to but different from a very commonly run process (%{Similar To Process Name}). While this process could be benign attackers are known to sometimes hide in plain sight by naming their malicious tools to resemble legitimate process names. | – | Medium |
| Unusual config reset in your virtual machine (VM_VMAccessUnusualConfigReset) | An unusual config reset was detected in your virtual machine by analyzing the Azure Resource Manager operations in your subscription. While this action may be legitimate, attackers can try utilizing VM Access extension to reset the configuration in your virtual machine and compromise it. | Credential Access | Medium |
| Unusual deletion of custom script extension in your virtual machine (VM_CustomScriptExtensionUnusualDeletion) | Unusual deletion of a custom script extension was detected in your virtual machine by analyzing the Azure Resource Manager operations in your subscription. Attackers may use custom script extensions to execute malicious code on your virtual machines via the Azure Resource Manager. | Execution | Medium |
| Unusual execution of custom script extension in your virtual machine (VM_CustomScriptExtensionUnusualExecution) | Unusual execution of a custom script extension was detected in your virtual machine by analyzing the Azure Resource Manager operations in your subscription. Attackers may use custom script extensions to execute malicious code on your virtual machines via the Azure Resource Manager. | Execution | Medium |
| Unusual process execution detected | Analysis of host data on %{Compromised Host} detected the execution of a process by %{User Name} that was unusual. Accounts such as %{User Name} tend to perform a limited set of operations, this execution was determined to be out of character and may be suspicious. | – | High |
| Unusual user password reset in your virtual machine (VM_VMAccessUnusualPasswordReset) | An unusual user password reset was detected in your virtual machine by analyzing the Azure Resource Manager operations in your subscription. While this action may be legitimate, attackers can try utilizing the VM Access extension to reset the credentials of a local user in your virtual machine and compromise it. | Credential Access | Medium |
| Unusual user SSH key reset in your virtual machine (VM_VMAccessUnusualSSHReset) | An unusual user SSH key reset was detected in your virtual machine by analyzing the Azure Resource Manager operations in your subscription. While this action may be legitimate, attackers can try utilizing VM Access extension to reset SSH key of a user account in your virtual machine and compromise it. | Credential Access | Medium |
| VBScript HTTP object allocation detected | Creation of a VBScript file using Command Prompt has been detected. The following script contains HTTP object allocation command. This action can be used to download malicious files. | – | High |
| Windows registry persistence method detected (VM_RegistryPersistencyKey) | Analysis of host data has detected an attempt to persist an executable in the Windows registry. Malware often uses such a technique to survive a boot. | Persistence | Low |
| A history file has been cleared | Analysis of host data indicates that the command history log file has been cleared. Attackers may do this to cover their traces. The operation was performed by user: ‘%{user name}’. | – | Medium |
| Access of htaccess file detected (VM_SuspectHtaccessFileAccess) | Analysis of host data on %{Compromised Host} detected possible manipulation of a htaccess file. Htaccess is a powerful configuration file that allows you to make multiple changes to a web server running the Apache Web software including basic redirect functionality, or for more advanced functions such as basic password protection. Attackers will often modify htaccess files on machines they have compromised to gain persistence. | Persistence, Defense Evasion, Execution | Medium |
| Antimalware broad files exclusion in your virtual machine (VM_AmBroadFilesExclusion) | Files exclusion from antimalware extension with broad exclusion rule was detected in your virtual machine by analyzing the Azure Resource Manager operations in your subscription. Such exclusion practically disabling the Antimalware protection. Attackers might exclude files from the antimalware scan on your virtual machine to prevent detection while running arbitrary code or infecting the machine with malware. | – | Medium |
| Antimalware disabled and code execution in your virtual machine (VM_AmDisablementAndCodeExecution) | Antimalware disabled at the same time as code execution on your virtual machine. This was detected by analyzing Azure Resource Manager operations in your subscription. Attackers disable antimalware scanners to prevent detection while running unauthorized tools or infecting the machine with malware. | – | High |
| Antimalware disabled in your virtual machine (VM_AmDisablement) | Antimalware disabled in your virtual machine. This was detected by analyzing Azure Resource Manager operations in your subscription. Attackers might disable the antimalware on your virtual machine to prevent detection. | Defense Evasion | Medium |
| Antimalware file exclusion and code execution in your virtual machine (VM_AmFileExclusionAndCodeExecution) | File excluded from your antimalware scanner at the same time as code was executed via a custom script extension on your virtual machine. This was detected by analyzing Azure Resource Manager operations in your subscription. Attackers might exclude files from the antimalware scan on your virtual machine to prevent detection while running unauthorized tools or infecting the machine with malware. | Defense Evasion, Execution | High |
| Antimalware file exclusion and code execution in your virtual machine (VM_AmTempFileExclusionAndCodeExecution) | Temporary file exclusion from antimalware extension in parallel to execution of code via custom script extension was detected in your virtual machine by analyzing the Azure Resource Manager operations in your subscription. Attackers might exclude files from the antimalware scan on your virtual machine to prevent detection while running arbitrary code or infecting the machine with malware. | Defense Evasion, Execution | High |
| Antimalware file exclusion in your virtual machine (VM_AmTempFileExclusion) | File excluded from your antimalware scanner on your virtual machine. This was detected by analyzing Azure Resource Manager operations in your subscription. Attackers might exclude files from the antimalware scan on your virtual machine to prevent detection while running unauthorized tools or infecting the machine with malware. | Defense Evasion | Medium |
| Antimalware real-time protection was disabled in your virtual machine (VM_AmRealtimeProtectionDisabled) | Real-time protection disablement of the antimalware extension was detected in your virtual machine by analyzing the Azure Resource Manager operations in your subscription. Attackers might disable real-time protection from the antimalware scan on your virtual machine to avoid detection while running arbitrary code or infecting the machine with malware. | Defense Evasion | Medium |
| Antimalware real-time protection was disabled temporarily in your virtual machine (VM_AmTempRealtimeProtectionDisablement) | Real-time protection temporary disablement of the antimalware extension was detected in your virtual machine by analyzing the Azure Resource Manager operations in your subscription. Attackers might disable real-time protection from the antimalware scan on your virtual machine to avoid detection while running arbitrary code or infecting the machine with malware. | Defense Evasion | Medium |
| Antimalware real-time protection was disabled temporarily while code was executed in your virtual machine (VM_AmRealtimeProtectionDisablementAndCodeExec) | Real-time protection temporary disablement of the antimalware extension in parallel to code execution via custom script extension was detected in your virtual machine by analyzing the Azure Resource Manager operations in your subscription. Attackers might disable real-time protection from the antimalware scan on your virtual machine to avoid detection while running arbitrary code or infecting the machine with malware. | – | High |
| Antimalware scans blocked for files potentially related to malware campaigns on your virtual machine (Preview) (VM_AmMalwareCampaignRelatedExclusion) | An exclusion rule was detected in your virtual machine to prevent your antimalware extension scanning certain files that are suspected of being related to a malware campaign. The rule was detected by analyzing the Azure Resource Manager operations in your subscription. Attackers might exclude files from antimalware scans to prevent detection while running arbitrary code or infecting the machine with malware. | Defense Evasion | Medium |
| Antimalware temporarily disabled in your virtual machine (VM_AmTemporarilyDisablement) | Antimalware temporarily disabled in your virtual machine. This was detected by analyzing Azure Resource Manager operations in your subscription. Attackers might disable the antimalware on your virtual machine to prevent detection. | – | Medium |
| Antimalware unusual file exclusion in your virtual machine (VM_UnusualAmFileExclusion) | Unusual file exclusion from antimalware extension was detected in your virtual machine by analyzing the Azure Resource Manager operations in your subscription. Attackers might exclude files from the antimalware scan on your virtual machine to prevent detection while running arbitrary code or infecting the machine with malware. | Defense Evasion | Medium |
| Attempt to stop apt-daily-upgrade.timer service detected [seen multiple times] | Analysis of host data on %{Compromised Host} detected an attempt to stop apt-daily-upgrade.timer service. In some recent attacks, attackers have been observed stopping this service, to download malicious files and granting execution privileges for their attack. This behavior was seen [x] times today on the following machines: [Machine names] | – | Low |
| Attempt to stop apt-daily-upgrade.timer service detected (VM_TimerServiceDisabled) | Analysis of host data on %{Compromised Host} detected an attempt to stop apt-daily-upgrade.timer service. In some recent attacks, attackers have been observed stopping this service, to download malicious files and granting execution privileges for their attack. | Defense Evasion | Low |
| Behavior similar to common Linux bots detected [seen multiple times] | Analysis of host data on %{Compromised Host} detected the execution of a process normally associated with common Linux botnets. This behavior was seen [x] times today on the following machines: [Machine names] | – | Medium |
| Behavior similar to common Linux bots detected (VM_CommonBot) | Analysis of host data on %{Compromised Host} detected the execution of a process normally associated with common Linux botnets. | Execution, Collection, Command and Control | Medium |
| Behavior similar to Fairware ransomware detected [seen multiple times] | Analysis of host data on %{Compromised Host} detected the execution of rm -rf commands applied to suspicious locations. As rm -rf will recursively delete files, it is normally used on discrete folders. In this case, it is being used in a location that could remove a lot of data. Fairware ransomware is known to execute rm -rf commands in this folder. This behavior was seen [x] times today on the following machines: [Machine names] | – | Medium |
| Behavior similar to Fairware ransomware detected (VM_FairwareMalware) | Analysis of host data on %{Compromised Host} detected the execution of rm -rf commands applied to suspicious locations. As rm -rf will recursively delete files, it is normally used on discrete folders. In this case, it is being used in a location that could remove a lot of data. Fairware ransomware is known to execute rm -rf commands in this folder. | Execution | Medium |
| Behavior similar to ransomware detected [seen multiple times] | Analysis of host data on %{Compromised Host} detected the execution of files that have resemblance of known ransomware that can prevent users from accessing their system or personal files, and demands ransom payment in order to regain access. This behavior was seen [x] times today on the following machines: [Machine names] | – | High |
| Container with a miner image detected (VM_MinerInContainerImage) | Machine logs indicate execution of a Docker container that run an image associated with a digital currency mining. | Execution | High |
| Custom script extension with suspicious command in your virtual machine (VM_CustomScriptExtensionSuspiciousCmd) | Custom script extension with suspicious command was detected in your virtual machine by analyzing the Azure Resource Manager operations in your subscription. Attackers may use custom script extension to execute a malicious code on your virtual machine via the Azure Resource Manager. | Execution | Medium |
| Custom script extension with suspicious entry-point in your virtual machine (VM_CustomScriptExtensionSuspiciousEntryPoint) | Custom script extension with a suspicious entry-point was detected in your virtual machine by analyzing the Azure Resource Manager operations in your subscription. The entry-point refers to a suspicious GitHub repository. Attackers may use custom script extensions to execute malicious code on your virtual machines via the Azure Resource Manager. | Execution | Medium |
| Custom script extension with suspicious payload in your virtual machine (VM_CustomScriptExtensionSuspiciousPayload) | Custom script extension with a payload from a suspicious GitHub repository was detected in your virtual machine by analyzing the Azure Resource Manager operations in your subscription. Attackers may use custom script extensions to execute malicious code on your virtual machines via the Azure Resource Manager. | Execution | Medium |
| Detected anomalous mix of upper and lower case characters in command line | Analysis of host data on %{Compromised Host} detected a command line with anomalous mix of upper and lower case characters. This kind of pattern, while possibly benign, is also typical of attackers trying to hide from case-sensitive or hash-based rule matching when performing administrative tasks on a compromised host. | – | Medium |
| Detected file download from a known malicious source [seen multiple times] (VM_SuspectDownload) | Analysis of host data has detected the download of a file from a known malware source on %{Compromised Host}. This behavior was seen over [x] times today on the following machines: [Machine names] | Privilege Escalation, Execution, Exfiltration, Command and Control | Medium |
| Detected file download from a known malicious source | Analysis of host data has detected the download of a file from a known malware source on %{Compromised Host}. | – | Medium |
| Detected persistence attempt [seen multiple times] | Analysis of host data on %{Compromised Host} has detected installation of a startup script for single-user mode. It is extremely rare that any legitimate process needs to execute in that mode, so this may indicate that an attacker has added a malicious process to every run-level to guarantee persistence. This behavior was seen [x] times today on the following machines: [Machine names] | – | Medium |
| Detected persistence attempt (VM_NewSingleUserModeStartupScript) | Host data analysis has detected that a startup script for single-user mode has been installed. Because it’s rare that any legitimate process would be required to run in that mode, this might indicate that an attacker has added a malicious process to every run-level to guarantee persistence. | Persistence | Medium |
| Detected suspicious file download [seen multiple times] | Analysis of host data has detected suspicious download of remote file on %{Compromised Host}. This behavior was seen 10 times today on the following machines: [Machine name] | – | Low |
| Detected suspicious file download (VM_SuspectDownloadArtifacts) | Analysis of host data has detected suspicious download of remote file on %{Compromised Host}. | Persistence | Low |
| Detected suspicious network activity | Analysis of network traffic from %{Compromised Host} detected suspicious network activity. Such traffic, while possibly benign, is typically used by an attacker to communicate with malicious servers for downloading of tools, command-and-control and exfiltration of data. Typical related attacker activity includes copying remote administration tools to a compromised host and exfiltrating user data from it. | – | Low |
| Detected suspicious use of the useradd command [seen multiple times] | Analysis of host data has detected suspicious use of the useradd command on %{Compromised Host}. This behavior was seen [x] times today on the following machines: [Machine names] | – | Medium |
| Detected suspicious use of the useradd command (VM_SuspectUserAddition) | Analysis of host data has detected suspicious use of the useradd command on %{Compromised Host}. | Persistence | Medium |
| Digital currency mining related behavior detected | Analysis of host data on %{Compromised Host} detected the execution of a process or command normally associated with digital currency mining. | – | High |
| Disabling of auditd logging [seen multiple times] | The Linux Audit system provides a way to track security-relevant information on the system. It records as much information about the events that are happening on your system as possible. Disabling auditd logging could hamper discovering violations of security policies used on the system. This behavior was seen [x] times today on the following machines: [Machine names] | – | Low |
| Docker build operation detected on a Kubernetes node (VM_ImageBuildOnNode) | Machine logs indicate a build operation of a container image on a Kubernetes node. While this behavior might be legitimate, attackers might build their malicious images locally to avoid detection. | Defense Evasion | Low |
| Executable found running from a suspicious location (VM_SuspectExecutablePath) | Analysis of host data detected an executable file on %{Compromised Host} that is running from a location in common with known suspicious files. This executable could either be legitimate activity, or an indication of a compromised host. | Execution | High |
| Exploitation of Xorg vulnerability [seen multiple times] | Analysis of host data on %{Compromised Host} detected the user of Xorg with suspicious arguments. Attackers may use this technique in privilege escalation attempts. This behavior was seen [x] times today on the following machines: [Machine names] | – | Medium |
| Exposed Docker daemon on TCP socket (VM_ExposedDocker) | Machine logs indicate that your Docker daemon (dockerd) exposes a TCP socket. By default, Docker configuration, does not use encryption or authentication when a TCP socket is enabled. This enables full access to the Docker daemon, by anyone with access to the relevant port. | Execution, Exploitation | Medium |
| Failed SSH brute force attack (VM_SshBruteForceFailed) | Failed brute force attacks were detected from the following attackers: %{Attackers}. Attackers were trying to access the host with the following user names: %{Accounts used on failed sign in to host attempts}. | Probing | Medium |
| Fileless Attack Behavior Detected (VM_FilelessAttackBehavior.Linux) | The memory of the process specified below contains behaviors commonly used by fileless attacks. Specific behaviors include: {list of observed behaviors} | Execution | Low |
| Fileless Attack Technique Detected (VM_FilelessAttackTechnique.Linux) | The memory of the process specified below contains evidence of a fileless attack technique. Fileless attacks are used by attackers to execute code while evading detection by security software. Specific behaviors include: {list of observed behaviors} | Execution | High |
| Fileless Attack Toolkit Detected (VM_FilelessAttackToolkit.Linux) | The memory of the process specified below contains a fileless attack toolkit: {ToolKitName}. Fileless attack toolkits typically do not have a presence on the filesystem, making detection by traditional anti-virus software difficult. Specific behaviors include: {list of observed behaviors} | Defense Evasion, Execution | High |
| Hidden file execution detected | Analysis of host data indicates that a hidden file was executed by %{user name}. This activity could either be legitimate activity, or an indication of a compromised host. | – | Informational |
| Indicators associated with DDOS toolkit detected [seen multiple times] | Analysis of host data on %{Compromised Host} detected file names that are part of a toolkit associated with malware capable of launching DDoS attacks, opening ports and services and taking full control over the infected system. This could also possibly be legitimate activity. This behavior was seen [x] times today on the following machines: [Machine names] | – | Medium |
| Indicators associated with DDOS toolkit detected (VM_KnownLinuxDDoSToolkit) | Analysis of host data on %{Compromised Host} detected file names that are part of a toolkit associated with malware capable of launching DDoS attacks, opening ports and services and taking full control over the infected system. This could also possibly be legitimate activity. | Persistence, Lateral Movement, Execution, Exploitation | Medium |
| Local host reconnaissance detected [seen multiple times] | Analysis of host data on %{Compromised Host} detected the execution of a command normally associated with common Linux bot reconnaissance. This behavior was seen [x] times today on the following machines: [Machine names] | – | Medium |
| Local host reconnaissance detected (VM_LinuxReconnaissance) | Analysis of host data on %{Compromised Host} detected the execution of a command normally associated with common Linux bot reconnaissance. | Discovery | Medium |
| Manipulation of host firewall detected [seen multiple times] (VM_FirewallDisabled) | Analysis of host data on %{Compromised Host} detected possible manipulation of the on-host firewall. Attackers will often disable this to exfiltrate data. This behavior was seen [x] times today on the following machines: [Machine names] | Defense Evasion, Exfiltration | Medium |
| Manipulation of host firewall detected | Analysis of host data on %{Compromised Host} detected possible manipulation of the on-host firewall. Attackers will often disable this to exfiltrate data. | – | Medium |
| MITRE Caldera agent detected (VM_MitreCalderaTools) | Machine logs indicate that the suspicious process: ‘%{Suspicious Process}’ was running on %{Compromised Host}. This is often associated with the MITRE 54ndc47 agent which could be used maliciously to attack other machines in some way. | All | Medium |
| New SSH key added [seen multiple times] (VM_SshKeyAddition) | A new SSH key was added to the authorized keys file. This behavior was seen [x] times today on the following machines: [Machine names] | Persistence | Low |
| New SSH key added | A new SSH key was added to the authorized keys file | – | Low |
| Possible attack tool detected [seen multiple times] | Machine logs indicate that the suspicious process: ‘%{Suspicious Process}’ was running on %{Compromised Host}. This tool is often associated with malicious users attacking other machines in some way. This behavior was seen [x] times today on the following machines: [Machine names] | – | Medium |
| Possible attack tool detected (VM_KnownLinuxAttackTool) | Machine logs indicate that the suspicious process: ‘%{Suspicious Process}’ was running on %{Compromised Host}. This tool is often associated with malicious users attacking other machines in some way. | Execution, Collection, Command and Control, Probing | Medium |
| Possible backdoor detected [seen multiple times] | Analysis of host data has detected a suspicious file being downloaded then run on %{Compromised Host} in your subscription. This activity has previously been associated with installation of a backdoor. This behavior was seen [x] times today on the following machines: [Machine names] | – | Medium |
| Possible credential access tool detected [seen multiple times] | Machine logs indicate a possible known credential access tool was running on %{Compromised Host} launched by process: ‘%{Suspicious Process}’. This tool is often associated with attacker attempts to access credentials. This behavior was seen [x] times today on the following machines: [Machine names] | – | Medium |
| Possible credential access tool detected (VM_KnownLinuxCredentialAccessTool) | Machine logs indicate a possible known credential access tool was running on %{Compromised Host} launched by process: ‘%{Suspicious Process}’. This tool is often associated with attacker attempts to access credentials. | Credential Access | Medium |
| Possible exploitation of Hadoop Yarn (VM_HadoopYarnExploit) | Analysis of host data on %{Compromised Host} detected the possible exploitation of the Hadoop Yarn service. | Exploitation | Medium |
| Possible exploitation of the mailserver detected (VM_MailserverExploitation ) | Analysis of host data on %{Compromised Host} detected an unusual execution under the mail server account | Exploitation | Medium |
| Possible Log Tampering Activity Detected [seen multiple times] | Analysis of host data on %{Compromised Host} detected possible removal of files that tracks user’s activity during the course of its operation. Attackers often try to evade detection and leave no trace of malicious activities by deleting such log files. This behavior was seen [x] times today on the following machines: [Machine names] | – | Medium |
| Possible Log Tampering Activity Detected (VM_SystemLogRemoval) | Analysis of host data on %{Compromised Host} detected possible removal of files that tracks user’s activity during the course of its operation. Attackers often try to evade detection and leave no trace of malicious activities by deleting such log files. | Defense Evasion | Medium |
| Possible loss of data detected [seen multiple times] | Analysis of host data on %{Compromised Host} detected a possible data egress condition. Attackers will often egress data from machines they have compromised. This behavior was seen [x]] times today on the following machines: [Machine names] | – | Medium |
| Possible loss of data detected (VM_DataEgressArtifacts) | Analysis of host data on %{Compromised Host} detected a possible data egress condition. Attackers will often egress data from machines they have compromised. | Collection, Exfiltration | Medium |
| Possible malicious web shell detected [seen multiple times] (VM_Webshell) | Analysis of host data on %{Compromised Host} detected a possible web shell. Attackers will often upload a web shell to a machine they have compromised to gain persistence or for further exploitation. This behavior was seen [x] times today on the following machines: [Machine names] | Persistence, Exploitation | Medium |
| Possible malicious web shell detected | Analysis of host data on %{Compromised Host} detected a possible web shell. Attackers will often upload a web shell to a machine they have compromised to gain persistence or for further exploitation. | – | Medium |
| Possible password change using crypt-method detected [seen multiple times] | Analysis of host data on %{Compromised Host} detected password change using crypt method. Attackers can make this change to continue access and gaining persistence after compromise. This behavior was seen [x] times today on the following machines: [Machine names] | – | Medium |
| Potential overriding of common files [seen multiple times] | Analysis of host data has detected common executables being overwritten on %{Compromised Host}. Attackers will overwrite common files as a way to obfuscate their actions or for persistence. This behavior was seen [x] times today on the following machines: [Machine names] | – | Medium |
| Potential overriding of common files (VM_OverridingCommonFiles) | Analysis of host data has detected common executables being overwritten on %{Compromised Host}. Attackers will overwrite common files as a way to obfuscate their actions or for persistence. | Persistence | Medium |
| Potential port forwarding to external IP address [seen multiple times] | Analysis of host data on %{Compromised Host} detected the initiation of port forwarding to an external IP address. This behavior was seen [x] times today on the following machines: [Machine names] | – | Medium |
| Potential port forwarding to external IP address (VM_SuspectPortForwarding) | Host data analysis detected the initiation of port forwarding to an external IP address. | Exfiltration, Command and Control | Medium |
| Potential reverse shell detected [seen multiple times] | Analysis of host data on %{Compromised Host} detected a potential reverse shell. These are used to get a compromised machine to call back into a machine an attacker owns. This behavior was seen [x] times today on the following machines: [Machine names] | – | Medium |
| Potential reverse shell detected (VM_ReverseShell) | Analysis of host data on %{Compromised Host} detected a potential reverse shell. These are used to get a compromised machine to call back into a machine an attacker owns. | Exfiltration, Exploitation | Medium |
| Privileged command run in container (VM_PrivilegedExecutionInContainer) | Machine logs indicate that a privileged command was run in a Docker container. A privileged command has extended privileges on the host machine. | Privilege Escalation | Low |
| Privileged Container Detected (VM_PrivilegedContainerArtifacts) | Machine logs indicate that a privileged Docker container is running. A privileged container has a full access to the host’s resources. If compromised, an attacker can use the privileged container to gain access to the host machine. | Privilege Escalation, Execution | Low |
| Process associated with digital currency mining detected [seen multiple times] | Analysis of host data on %{Compromised Host} detected the execution of a process normally associated with digital currency mining. This behavior was seen over 100 times today on the following machines: [Machine name] | – | Medium |
| Process associated with digital currency mining detected | Host data analysis detected the execution of a process that is normally associated with digital currency mining. | Exploitation, Execution | Medium |
| Process seen accessing the SSH authorized keys file in an unusual way (VM_SshKeyAccess) | An SSH authorized keys file has been accessed in a method similar to known malware campaigns. This access can indicate that an attacker is attempting to gain persistent access to a machine. | – | Low |
| Python encoded downloader detected [seen multiple times] | Analysis of host data on %{Compromised Host} detected the execution of encoded Python that downloads and runs code from a remote location. This may be an indication of malicious activity. This behavior was seen [x] times today on the following machines: [Machine names] | – | Low |
| Screenshot taken on host [seen multiple times] | Analysis of host data on %{Compromised Host} detected the user of a screen capture tool. Attackers may use these tools to access private data. This behavior was seen [x] times today on the following machines: [Machine names] | – | Low |
| Script extension mismatch detected [seen multiple times] | Analysis of host data on %{Compromised Host} detected a mismatch between the script interpreter and the extension of the script file provided as input. This has frequently been associated with attacker script executions. This behavior was seen [x] times today on the following machines: [Machine names] | – | Medium |
| Script extension mismatch detected (VM_MismatchedScriptFeatures) | Analysis of host data on %{Compromised Host} detected a mismatch between the script interpreter and the extension of the script file provided as input. This has frequently been associated with attacker script executions. | Defense Evasion | Medium |
| Shellcode detected [seen multiple times] | Analysis of host data on %{Compromised Host} detected shellcode being generated from the command line. This process could be legitimate activity, or an indication that one of your machines has been compromised. This behavior was seen [x] times today on the following machines: [Machine names] | – | Medium |
| SSH server is running inside a container (VM_ContainerSSH) | Machine logs indicate that an SSH server is running inside a Docker container. While this behavior can be intentional, it frequently indicates that a container is misconfigured or breached. | Execution | Medium |
| Successful SSH brute force attack (VM_SshBruteForceSuccess) | Analysis of host data has detected a successful brute force attack. The IP %{Attacker source IP} was seen making multiple login attempts. Successful logins were made from that IP with the following user(s): %{Accounts used to successfully sign in to host}. This means that the host may be compromised and controlled by a malicious actor. | Exploitation | High |
| Suspicious Account Creation Detected | Analysis of host data on %{Compromised Host} detected creation or use of a local account %{Suspicious account name} : this account name closely resembles a standard Windows account or group name ‘%{Similar To Account Name}’. This is potentially a rogue account created by an attacker, so named in order to avoid being noticed by a human administrator. | – | Medium |
| Suspicious compilation detected [seen multiple times] | Analysis of host data on %{Compromised Host} detected suspicious compilation. Attackers will often compile exploits on a machine they have compromised to escalate privileges. This behavior was seen [x] times today on the following machines: [Machine names] | – | Medium |
| Suspicious compilation detected (VM_SuspectCompilation) | Analysis of host data on %{Compromised Host} detected suspicious compilation. Attackers will often compile exploits on a machine they have compromised to escalate privileges. | Privilege Escalation, Exploitation | Medium |
| Suspicious failed execution of custom script extension in your virtual machine (VM_CustomScriptExtensionSuspiciousFailure) | Suspicious failure of a custom script extension was detected in your virtual machine by analyzing the Azure Resource Manager operations in your subscription. Such failures may be associated with malicious scripts run by this extension. | Execution | Medium |
| Suspicious kernel module detected [seen multiple times] | Analysis of host data on %{Compromised Host} detected a shared object file being loaded as a kernel module. This could be legitimate activity, or an indication that one of your machines has been compromised. This behavior was seen [x] times today on the following machines: [Machine names] | – | Medium |
| Suspicious password access [seen multiple times] | Analysis of host data has detected suspicious access to encrypted user passwords on %{Compromised Host}. This behavior was seen [x] times today on the following machines: [Machine names] | – | Informational |
| Suspicious password access | Analysis of host data has detected suspicious access to encrypted user passwords on %{Compromised Host}. | – | Informational |
| Suspicious PHP execution detected (VM_SuspectPhp) | Machine logs indicate that a suspicious PHP process is running. The action included an attempt to run OS commands or PHP code from the command line using the PHP process. While this behavior can be legitimate, in web applications this behavior is also observed in malicious activities such as attempts to infect websites with web shells. | Execution | Medium |
| Suspicious request to Kubernetes API (VM_KubernetesAPI) | Machine logs indicate that a suspicious request was made to the Kubernetes API. The request was sent from a Kubernetes node, possibly from one of the containers running in the node. Although this behavior can be intentional, it might indicate that the node is running a compromised container. | Execution | Medium |
| Suspicious request to the Kubernetes Dashboard (VM_KubernetesDashboard) | Machine logs indicate that a suspicious request was made to the Kubernetes Dashboard. The request was sent from a Kubernetes node, possibly from one of the containers running in the node. Although this behavior can be intentional, it might indicate that the node is running a compromised container. | Lateral movement | Medium |
| Unusual config reset in your virtual machine (VM_VMAccessUnusualConfigReset) | An unusual config reset was detected in your virtual machine by analyzing the Azure Resource Manager operations in your subscription. While this action may be legitimate, attackers can try utilizing VM Access extension to reset the configuration in your virtual machine and compromise it. | Credential Access | Medium |
| Unusual deletion of custom script extension in your virtual machine (VM_CustomScriptExtensionUnusualDeletion) | Unusual deletion of a custom script extension was detected in your virtual machine by analyzing the Azure Resource Manager operations in your subscription. Attackers may use custom script extensions to execute malicious code on your virtual machines via the Azure Resource Manager. | Execution | Medium |
| Unusual execution of custom script extension in your virtual machine (VM_CustomScriptExtensionUnusualExecution) | Unusual execution of a custom script extension was detected in your virtual machine by analyzing the Azure Resource Manager operations in your subscription. Attackers may use custom script extensions to execute malicious code on your virtual machines via the Azure Resource Manager. | Execution | Medium |
| Unusual user password reset in your virtual machine (VM_VMAccessUnusualPasswordReset) | An unusual user password reset was detected in your virtual machine by analyzing the Azure Resource Manager operations in your subscription. While this action may be legitimate, attackers can try utilizing the VM Access extension to reset the credentials of a local user in your virtual machine and compromise it. | Credential Access | Medium |
| Unusual user SSH key reset in your virtual machine (VM_VMAccessUnusualSSHReset) | An unusual user SSH key reset was detected in your virtual machine by analyzing the Azure Resource Manager operations in your subscription. While this action may be legitimate, attackers can try utilizing VM Access extension to reset SSH key of a user account in your virtual machine and compromise it. | Credential Access | Medium |
| K8S API requests from proxy IP address detected (K8S_TI_Proxy) | Kubernetes audit log analysis detected API requests to your cluster from an IP address that is associated with proxy services, such as TOR. While this behavior can be legitimate, it’s often seen in malicious activities, when attackers try to hide their source IP. | Execution | Low |
| Container with a sensitive volume mount detected (K8S_SensitiveMount) | Kubernetes audit log analysis detected a new container with a sensitive volume mount. The volume that was detected is a hostPath type which mounts a sensitive file or folder from the node to the container. If the container gets compromised, the attacker can use this mount for gaining access to the node. | Privilege Escalation | Medium |
| CoreDNS modification in Kubernetes detected (K8S_CoreDnsModification) | Kubernetes audit log analysis detected a modification of the CoreDNS configuration. The configuration of CoreDNS can be modified by overriding its configmap. While this activity can be legitimate, if attackers have permissions to modify the configmap, they can change the behavior of the cluster’s DNS server and poison it. | Lateral Movement | Low |
| Creation of admission webhook configuration detected (K8S_AdmissionController) | Kubernetes audit log analysis detected a new admission webhook configuration. Kubernetes has two built-in generic admission controllers: MutatingAdmissionWebhook and ValidatingAdmissionWebhook. The behavior of these admission controllers is determined by an admission webhook that the user deploys to the cluster. The usage of such admission controllers can be legitimate, however attackers can use such webhooks for modifying the requests (in case of MutatingAdmissionWebhook) or inspecting the requests and gain sensitive information (in case of ValidatingAdmissionWebhook). | Credential Access, Persistence | Low |
| Digital currency mining container detected (K8S_MaliciousContainerImage) | Kubernetes audit log analysis detected a container that has an image associated with a digital currency mining tool. | Execution | High |
| Exposed Kubeflow dashboard detected (K8S_ExposedKubeflow) | The Kubernetes audit log analysis detected exposure of the Istio Ingress by a load balancer in a cluster that runs Kubeflow. This action might expose the Kubeflow dashboard to the internet. If the dashboard is exposed to the internet, attackers can access it and run malicious containers or code on the cluster. Find more details in the following article: https://www.microsoft.com/security/blog/2020/06/10/misconfigured-kubeflow-workloads-are-a-security-risk | Initial Access | Medium |
| Exposed Kubernetes dashboard detected (K8S_ExposedDashboard) | Kubernetes audit log analysis detected exposure of the Kubernetes Dashboard by a LoadBalancer service. Exposed dashboard allows an unauthenticated access to the cluster management and poses a security threat. | Initial Access | High |
| Exposed Kubernetes service detected (K8S_ExposedService) | The Kubernetes audit log analysis detected exposure of a service by a load balancer. This service is related to a sensitive application that allows high impact operations in the cluster such as running processes on the node or creating new containers. In some cases, this service doesn’t require authentication. If the service doesn’t require authentication, exposing it to the internet poses a security risk. | Initial Access | Medium |
| Exposed Redis service in AKS detected (K8S_ExposedRedis) | The Kubernetes audit log analysis detected exposure of a Redis service by a load balancer. If the service doesn’t require authentication, exposing it to the internet poses a security risk. | Initial Access | Low |
| Kubernetes events deleted (K8S_DeleteEvents) | Defender for Cloud detected that some Kubernetes events have been deleted. Kubernetes events are objects in Kubernetes which contain information about changes in the cluster. Attackers might delete those events for hiding their operations in the cluster. | Defense Evasion | Medium |
| Kubernetes penetration testing tool detected (K8S_PenTestToolsKubeHunter) | Kubernetes audit log analysis detected usage of Kubernetes penetration testing tool in the AKS cluster. While this behavior can be legitimate, attackers might use such public tools for malicious purposes. | Execution | Low |
| New container in the kube-system namespace detected (K8S_KubeSystemContainer) | Kubernetes audit log analysis detected a new container in the kube-system namespace that isn’t among the containers that normally run in this namespace. The kube-system namespaces should not contain user resources. Attackers can use this namespace for hiding malicious components. | Persistence | Low |
| New high privileges role detected (K8S_HighPrivilegesRole) | Kubernetes audit log analysis detected a new role with high privileges. A binding to a role with high privileges gives the user\group high privileges in the cluster. Unnecessary privileges might cause privilege escalation in the cluster. | Persistence | Low |
| Privileged container detected (K8S_PrivilegedContainer) | Kubernetes audit log analysis detected a new privileged container. A privileged container has access to the node’s resources and breaks the isolation between containers. If compromised, an attacker can use the privileged container to gain access to the node. | Privilege Escalation | Low |
| Role binding to the cluster-admin role detected (K8S_ClusterAdminBinding) | Kubernetes audit log analysis detected a new binding to the cluster-admin role which gives administrator privileges. Unnecessary administrator privileges might cause privilege escalation in the cluster. | Persistence | Low |
| Anomalous pod deployment (Preview) (K8S_AnomalousPodDeployment) | Kubernetes audit log analysis detected pod deployment which is anomalous based on previous pod deployment activity. This activity is considered an anomaly when taking into account how the different features seen in the deployment operation are in relations to one another. The features monitored by this analytics include the container image registry used, the account performing the deployment, day of the week, how often does this account performs pod deployments, user agent used in the operation, is this a namespace which is pod deployment occur to often, or other feature. Top contributing reasons for raising this alert as anomalous activity are detailed under the alert extended properties. | Execution | Medium |
| Excessive role permissions assigned in Kubernetes cluster (Preview) (K8S_ServiceAcountPermissionAnomaly) | Analysis of the Kubernetes audit logs detected an excessive permissions role assignment to your cluster. From examining role assignments, the listed permissions are uncommon to the specific service account. This detection considers previous role assignments to the same service account across clusters monitored by Azure, volume per permission, and the impact of the specific permission. The anomaly detection model used for this alert takes into account how this permission is used across all clusters monitored by Microsoft Defender for Cloud. | Privilege Escalation | Low |
| A possible vulnerability to SQL Injection (SQL.VM_VulnerabilityToSqlInjection SQL.DB_VulnerabilityToSqlInjection SQL.MI_VulnerabilityToSqlInjection SQL.DW_VulnerabilityToSqlInjection) | An application has generated a faulty SQL statement in the database. This can indicate a possible vulnerability to SQL injection attacks. There are two possible reasons for a faulty statement. A defect in application code might have constructed the faulty SQL statement. Or, application code or stored procedures didn’t sanitize user input when constructing the faulty SQL statement, which can be exploited for SQL injection. | PreAttack | Medium |
| Attempted logon by a potentially harmful application (SQL.DB_HarmfulApplication SQL.VM_HarmfulApplication SQL.MI_HarmfulApplication SQL.DW_HarmfulApplication) | A potentially harmful application attempted to access SQL server ‘{name}’. | PreAttack | High |
| Log on from an unusual Azure Data Center (SQL.DB_DataCenterAnomaly SQL.VM_DataCenterAnomaly SQL.DW_DataCenterAnomaly SQL.MI_DataCenterAnomaly) | There has been a change in the access pattern to an SQL Server, where someone has signed in to the server from an unusual Azure Data Center. In some cases, the alert detects a legitimate action (a new application or Azure service). In other cases, the alert detects a malicious action (attacker operating from breached resource in Azure). | Probing | Low |
| Log on from an unusual location (SQL.DB_GeoAnomaly SQL.VM_GeoAnomaly SQL.DW_GeoAnomaly SQL.MI_GeoAnomaly) | There has been a change in the access pattern to SQL Server, where someone has signed in to the server from an unusual geographical location. In some cases, the alert detects a legitimate action (a new application or developer maintenance). In other cases, the alert detects a malicious action (a former employee or external attacker). | Exploitation | Medium |
| Login from a principal user not seen in 60 days (SQL.DB_PrincipalAnomaly SQL.VM_PrincipalAnomaly SQL.DW_PrincipalAnomaly SQL.MI_PrincipalAnomaly) | A principal user not seen in the last 60 days has logged into your database. If this database is new or this is expected behavior caused by recent changes in the users accessing the database, Defender for Cloud will identify significant changes to the access patterns and attempt to prevent future false positives. | Exploitation | Medium |
| Login from a suspicious IP (SQL.VM_SuspiciousIpAnomaly) | Your resource has been accessed successfully from an IP address that Microsoft Threat Intelligence has associated with suspicious activity. | PreAttack | Medium |
| Potential SQL Brute Force attempt | An abnormally high number of failed sign in attempts with different credentials have occurred. In some cases, the alert detects penetration testing in action. In other cases, the alert detects a brute force attack. | Probing | High |
| Potential SQL injection (SQL.DB_PotentialSqlInjection SQL.VM_PotentialSqlInjection SQL.MI_PotentialSqlInjection SQL.DW_PotentialSqlInjection Synapse.SQLPool_PotentialSqlInjection) | An active exploit has occurred against an identified application vulnerable to SQL injection. This means an attacker is trying to inject malicious SQL statements by using the vulnerable application code or stored procedures. | PreAttack | High |
| Potentially Unsafe Action (SQL.DB_UnsafeCommands SQL.MI_UnsafeCommands SQL.DW_UnsafeCommands) | A potentially unsafe action was attempted on your database ‘{name}’ on server ‘{name}’. | – | High |
| Suspected brute force attack using a valid user | A potential brute force attack has been detected on your resource. The attacker is using the valid user sa, which has permissions to login. | PreAttack | High |
| Suspected brute force attack | A potential brute force attack has been detected on your SQL server ‘{name}’. | PreAttack | High |
| Suspected successful brute force attack (SQL.DB_BruteForce SQL.VM_BruteForce SQL.DW_BruteForce SQL.MI_BruteForce) | A successful login occurred after an apparent brute force attack on your resource | PreAttack | High |
| Unusual export location | Someone has extracted a massive amount of data from your SQL Server ‘{name}’ to an unusual location. | Exfiltration | High |
| Suspected brute force attack using a valid user (SQL.PostgreSQL_BruteForce SQL.MariaDB_BruteForce SQL.MySQL_BruteForce) | A potential brute force attack has been detected on your resource. The attacker is using the valid user (username), which has permissions to login. | PreAttack | High |
| Suspected successful brute force attack (SQL.PostgreSQL_BruteForce SQL.MySQL_BruteForce SQL.MariaDB_BruteForce) | A successful login occurred after an apparent brute force attack on your resource. | PreAttack | High |
| Suspected brute force attack (“SQL.MySQL_BruteForce”) | A potential brute force attack has been detected on your SQL server ‘{name}’. | PreAttack | High |
| Attempted logon by a potentially harmful application (SQL.PostgreSQL_HarmfulApplication SQL.MariaDB_HarmfulApplication SQL.MySQL_HarmfulApplication) | A potentially harmful application attempted to access your resource. | PreAttack | High |
| Login from a principal user not seen in 60 days (SQL.PostgreSQL_PrincipalAnomaly SQL.MariaDB_PrincipalAnomaly SQL.MySQL_PrincipalAnomaly) | A principal user not seen in the last 60 days has logged into your database. If this database is new or this is expected behavior caused by recent changes in the users accessing the database, Defender for Cloud will identify significant changes to the access patterns and attempt to prevent future false positives. | Exploitation | Medium |
| Login from a domain not seen in 60 days (SQL.MariaDB_DomainAnomaly SQL.PostgreSQL_DomainAnomaly SQL.MySQL_DomainAnomaly) | A user has logged in to your resource from a domain no other users have connected from in the last 60 days. If this resource is new or this is expected behavior caused by recent changes in the users accessing the resource, Defender for Cloud will identify significant changes to the access patterns and attempt to prevent future false positives. | Exploitation | Medium |
| Log on from an unusual Azure Data Center (SQL.PostgreSQL_DataCenterAnomaly SQL.MariaDB_DataCenterAnomaly SQL.MySQL_DataCenterAnomaly) | Someone logged on to your resource from an unusual Azure Data Center. | Probing | Low |
| Logon from an unusual cloud provider (SQL.PostgreSQL_CloudProviderAnomaly SQL.MariaDB_CloudProviderAnomaly SQL.MySQL_CloudProviderAnomaly) | Someone logged on to your resource from a cloud provider not seen in the last 60 days. It’s quick and easy for threat actors to obtain disposable compute power for use in their campaigns. If this is expected behavior caused by the recent adoption of a new cloud provider, Defender for Cloud will learn over time and attempt to prevent future false positives. | Exploitation | Medium |
| Log on from an unusual location (SQL.MariaDB_GeoAnomaly SQL.PostgreSQL_GeoAnomaly SQL.MySQL_GeoAnomaly) | Someone logged on to your resource from an unusual Azure Data Center. | Exploitation | Medium |
| Login from a suspicious IP (SQL.PostgreSQL_SuspiciousIpAnomaly SQL.MariaDB_SuspiciousIpAnomaly SQL.MySQL_SuspiciousIpAnomaly) | Your resource has been accessed successfully from an IP address that Microsoft Threat Intelligence has associated with suspicious activity. | PreAttack | Medium |
| Azure Resource Manager operation from suspicious IP address (Preview) (ARM_OperationFromSuspiciousIP) | Microsoft Defender for Resource Manager detected an operation from an IP address that has been marked as suspicious in threat intelligence feeds. | Execution | Medium |
| Azure Resource Manager operation from suspicious proxy IP address (Preview) (ARM_OperationFromSuspiciousProxyIP) | Microsoft Defender for Resource Manager detected a resource management operation from an IP address that is associated with proxy services, such as TOR. While this behavior can be legitimate, it’s often seen in malicious activities, when threat actors try to hide their source IP. | Defense Evasion | Medium |
| MicroBurst exploitation toolkit used to enumerate resources in your subscriptions (ARM_MicroBurst.AzDomainInfo) | MicroBurst’s Information Gathering module was run on your subscription. This tool can be used to discover resources, permissions and network structures. This was detected by analyzing the Azure Activity logs and resource management operations in your subscription | – | High |
| MicroBurst exploitation toolkit used to enumerate resources in your subscriptions (ARM_MicroBurst.AzureDomainInfo) | MicroBurst’s Information Gathering module was run on your subscription. This tool can be used to discover resources, permissions and network structures. This was detected by analyzing the Azure Activity logs and resource management operations in your subscription | – | High |
| MicroBurst exploitation toolkit used to execute code on your virtual machine (ARM_MicroBurst.AzVMBulkCMD) | MicroBurst’s exploitation toolkit was used to execute code on your virtual machines. This was detected by analyzing Azure Resource Manager operations in your subscription. | Execution | High |
| MicroBurst exploitation toolkit used to execute code on your virtual machine (RM_MicroBurst.AzureRmVMBulkCMD) | MicroBurst’s exploitation toolkit was used to execute code on your virtual machines. This was detected by analyzing Azure Resource Manager operations in your subscription. | – | High |
| MicroBurst exploitation toolkit used to extract keys from your Azure key vaults (ARM_MicroBurst.AzKeyVaultKeysREST) | MicroBurst’s exploitation toolkit was used to extract keys from your Azure key vaults. This was detected by analyzing Azure Activity logs and resource management operations in your subscription. | – | High |
| MicroBurst exploitation toolkit used to extract keys to your storage accounts (ARM_MicroBurst.AZStorageKeysREST) | MicroBurst’s exploitation toolkit was used to extract keys to your storage accounts. This was detected by analyzing Azure Activity logs and resource management operations in your subscription. | Collection | High |
| MicroBurst exploitation toolkit used to extract secrets from your Azure key vaults (ARM_MicroBurst.AzKeyVaultSecretsREST) | MicroBurst’s exploitation toolkit was used to extract secrets from your Azure key vaults. This was detected by analyzing Azure Activity logs and resource management operations in your subscription. | – | High |
| Permissions granted for an RBAC role in an unusual way for your Azure environment (Preview) (ARM_AnomalousRBACRoleAssignment) | Microsoft Defender for Resource Manager detected an RBAC role assignment that’s unusual when compared with other assignments performed by the same assigner / performed for the same assignee / in your tenant due to the following anomalies: assignment time, assigner location, assigner, authentication method, assigned entities, client software used, assignment extent. This operation might have been performed by a legitimate user in your organization. Alternatively, it might indicate that an account in your organization was breached, and that the threat actor is trying to grant permissions to an additional user account they own. | Lateral Movement, Defense Evasion | Medium |
| PowerZure exploitation toolkit used to elevate access from Azure AD to Azure (ARM_PowerZure.AzureElevatedPrivileges) | PowerZure exploitation toolkit was used to elevate access from AzureAD to Azure. This was detected by analyzing Azure Resource Manager operations in your tenant. | – | High |
| PowerZure exploitation toolkit used to enumerate resources (ARM_PowerZure.GetAzureTargets) | PowerZure exploitation toolkit was used to enumerate resources on behalf of a legitimate user account in your organization. This was detected by analyzing Azure Resource Manager operations in your subscription. | Collection | High |
| PowerZure exploitation toolkit used to enumerate storage containers, shares, and tables (ARM_PowerZure.ShowStorageContent) | PowerZure exploitation toolkit was used to enumerate storage shares, tables, and containers. This was detected by analyzing Azure Resource Manager operations in your subscription. | – | High |
| PowerZure exploitation toolkit used to execute a Runbook in your subscription (ARM_PowerZure.StartRunbook) | PowerZure exploitation toolkit was used to execute a Runbook. This was detected by analyzing Azure Resource Manager operations in your subscription. | – | High |
| PowerZure exploitation toolkit used to extract Runbooks content (ARM_PowerZure.AzureRunbookContent) | PowerZure exploitation toolkit was used to extract Runbook content. This was detected by analyzing Azure Resource Manager operations in your subscription. | Collection | High |
| PREVIEW – Activity from a risky IP address (ARM.MCAS_ActivityFromAnonymousIPAddresses) | Users activity from an IP address that has been identified as an anonymous proxy IP address has been detected. These proxies are used by people who want to hide their device’s IP address, and can be used for malicious intent. This detection uses a machine learning algorithm that reduces false positives, such as mis-tagged IP addresses that are widely used by users in the organization. Requires an active Microsoft Defender for Cloud Apps license. | – | Medium |
| PREVIEW – Activity from infrequent country (ARM.MCAS_ActivityFromInfrequentCountry) | Activity from a location that wasn’t recently or ever visited by any user in the organization has occurred. This detection considers past activity locations to determine new and infrequent locations. The anomaly detection engine stores information about previous locations used by users in the organization. Requires an active Microsoft Defender for Cloud Apps license. | – | Medium |
| PREVIEW – Azurite toolkit run detected (ARM_Azurite) | A known cloud-environment reconnaissance toolkit run has been detected in your environment. The tool Azurite can be used by an attacker (or penetration tester) to map your subscriptions’ resources and identify insecure configurations. | Collection | High |
| PREVIEW – Impossible travel activity (ARM.MCAS_ImpossibleTravelActivity) | Two user activities (in a single or multiple sessions) have occurred, originating from geographically distant locations. This occurs within a time period shorter than the time it would have taken the user to travel from the first location to the second. This indicates that a different user is using the same credentials. This detection uses a machine learning algorithm that ignores obvious false positives contributing to the impossible travel conditions, such as VPNs and locations regularly used by other users in the organization. The detection has an initial learning period of seven days, during which it learns a new user’s activity pattern. Requires an active Microsoft Defender for Cloud Apps license. | – | Medium |
| PREVIEW – Suspicious management session using an inactive account detected (ARM_UnusedAccountPersistence) | Subscription activity logs analysis has detected suspicious behavior. A principal not in use for a long period of time is now performing actions that can secure persistence for an attacker. | Persistence | Medium |
| PREVIEW – Suspicious management session using PowerShell detected (ARM_UnusedAppPowershellPersistence) | Subscription activity logs analysis has detected suspicious behavior. A principal that doesn’t regularly use PowerShell to manage the subscription environment is now using PowerShell, and performing actions that can secure persistence for an attacker. | Persistence | Medium |
| PREVIEW – Suspicious management session using Azure portal detected (ARM_UnusedAppIbizaPersistence) | Analysis of your subscription activity logs has detected a suspicious behavior. A principal that doesn’t regularly use the Azure portal (Ibiza) to manage the subscription environment (hasn’t used Azure portal to manage for the last 45 days, or a subscription that it is actively managing), is now using the Azure portal and performing actions that can secure persistence for an attacker. | Persistence | Medium |
| Privileged custom role created for your subscription in a suspicious way (Preview) (ARM_PrivilegedRoleDefinitionCreation) | Microsoft Defender for Resource Manager detected a suspicious creation of privileged custom role definition in your subscription. This operation might have been performed by a legitimate user in your organization. Alternatively, it might indicate that an account in your organization was breached, and that the threat actor is trying to create a privileged role to use in the future to evade detection. | Privilege Escalation, Defense Evasion | Low |
| Usage of MicroBurst exploitation toolkit to run an arbitrary code or exfiltrate Azure Automation account credentials (ARM_MicroBurst.RunCodeOnBehalf) | Usage of MicroBurst exploitation toolkit to run an arbitrary code or exfiltrate Azure Automation account credentials. This was detected by analyzing Azure Resource Manager operations in your subscription. | Persistence, Credential Access | High |
| Usage of NetSPI techniques to maintain persistence in your Azure environment (ARM_NetSPI.MaintainPersistence) | Usage of NetSPI persistence technique to create a webhook backdoor and maintain persistence in your Azure environment. This was detected by analyzing Azure Resource Manager operations in your subscription. | – | High |
| Usage of PowerZure exploitation toolkit to run an arbitrary code or exfiltrate Azure Automation account credentials (ARM_PowerZure.RunCodeOnBehalf) | PowerZure exploitation toolkit detected attempting to run code or exfiltrate Azure Automation account credentials. This was detected by analyzing Azure Resource Manager operations in your subscription. | – | High |
| Usage of PowerZure function to maintain persistence in your Azure environment (ARM_PowerZure.MaintainPersistence) | PowerZure exploitation toolkit detected creating a webhook backdoor to maintain persistence in your Azure environment. This was detected by analyzing Azure Resource Manager operations in your subscription. | – | High |
| Anomalous network protocol usage (AzureDNS_ProtocolAnomaly) | Analysis of DNS transactions from %{CompromisedEntity} detected anomalous protocol usage. Such traffic, while possibly benign, may indicate abuse of this common protocol to bypass network traffic filtering. Typical related attacker activity includes copying remote administration tools to a compromised host and exfiltrating user data from it. | Exfiltration | – |
| Anonymity network activity (AzureDNS_DarkWeb) | Analysis of DNS transactions from %{CompromisedEntity} detected anonymity network activity. Such activity, while possibly legitimate user behavior, is frequently employed by attackers to evade tracking and fingerprinting of network communications. Typical related attacker activity is likely to include the download and execution of malicious software or remote administration tools. | Exfiltration | – |
| Anonymity network activity using web proxy (AzureDNS_DarkWebProxy) | Analysis of DNS transactions from %{CompromisedEntity} detected anonymity network activity. Such activity, while possibly legitimate user behavior, is frequently employed by attackers to evade tracking and fingerprinting of network communications. Typical related attacker activity is likely to include the download and execution of malicious software or remote administration tools. | Exfiltration | – |
| Attempted communication with suspicious sinkholed domain (AzureDNS_SinkholedDomain) | Analysis of DNS transactions from %{CompromisedEntity} detected request for sinkholed domain. Such activity, while possibly legitimate user behavior, is frequently an indication of the download or execution of malicious software. Typical related attacker activity is likely to include the download and execution of further malicious software or remote administration tools. | Exfiltration | – |
| Communication with possible phishing domain (AzureDNS_PhishingDomain) | Analysis of DNS transactions from %{CompromisedEntity} detected a request for a possible phishing domain. Such activity, while possibly benign, is frequently performed by attackers to harvest credentials to remote services. Typical related attacker activity is likely to include the exploitation of any credentials on the legitimate service. | Exfiltration | – |
| Communication with suspicious algorithmically generated domain (AzureDNS_DomainGenerationAlgorithm) | Analysis of DNS transactions from %{CompromisedEntity} detected possible usage of a domain generation algorithm. Such activity, while possibly benign, is frequently performed by attackers to evade network monitoring and filtering. Typical related attacker activity is likely to include the download and execution of malicious software or remote administration tools. | Exfiltration | – |
| Communication with suspicious domain identified by threat intelligence (AzureDNS_ThreatIntelSuspectDomain) | Communication with suspicious domain was detected by analyzing DNS transactions from your resource and comparing against known malicious domains identified by threat intelligence feeds. Communication to malicious domains is frequently performed by attackers and could imply that your resource is compromised.” | Initial Access | Medium |
| Communication with suspicious random domain name (AzureDNS_RandomizedDomain) | Analysis of DNS transactions from %{CompromisedEntity} detected usage of a suspicious randomly generated domain name. Such activity, while possibly benign, is frequently performed by attackers to evade network monitoring and filtering. Typical related attacker activity is likely to include the download and execution of malicious software or remote administration tools. | Exfiltration | – |
| Digital currency mining activity (AzureDNS_CurrencyMining) | Analysis of DNS transactions from %{CompromisedEntity} detected digital currency mining activity. Such activity, while possibly legitimate user behavior, is frequently performed by attackers following compromise of resources. Typical related attacker activity is likely to include the download and execution of common mining tools. | Exfiltration | – |
| Network intrusion detection signature activation (AzureDNS_SuspiciousDomain) | Analysis of DNS transactions from %{CompromisedEntity} detected a known malicious network signature. Such activity, while possibly legitimate user behavior, is frequently an indication of the download or execution of malicious software. Typical related attacker activity is likely to include the download and execution of further malicious software or remote administration tools. | Exfiltration | – |
| Possible data download via DNS tunnel (AzureDNS_DataInfiltration) | Analysis of DNS transactions from %{CompromisedEntity} detected a possible DNS tunnel. Such activity, while possibly legitimate user behavior, is frequently performed by attackers to evade network monitoring and filtering. Typical related attacker activity is likely to include the download and execution of malicious software or remote administration tools. | Exfiltration | – |
| Possible data exfiltration via DNS tunnel (AzureDNS_DataExfiltration) | Analysis of DNS transactions from %{CompromisedEntity} detected a possible DNS tunnel. Such activity, while possibly legitimate user behavior, is frequently performed by attackers to evade network monitoring and filtering. Typical related attacker activity is likely to include the download and execution of malicious software or remote administration tools. | Exfiltration | – |
| Possible data transfer via DNS tunnel (AzureDNS_DataObfuscation) | Analysis of DNS transactions from %{CompromisedEntity} detected a possible DNS tunnel. Such activity, while possibly legitimate user behavior, is frequently performed by attackers to evade network monitoring and filtering. Typical related attacker activity is likely to include the download and execution of malicious software or remote administration tools. | Exfiltration | – |
| Access from a suspicious IP address (Storage.Blob_SuspiciousIp Storage.Files_SuspiciousIp) | Indicates that this storage account has been successfully accessed from an IP address that is considered suspicious. This alert is powered by Microsoft Threat Intelligence. Learn more about Microsoft’s threat intelligence capabilities. Applies to: Azure Blob Storage, Azure Files, Azure Data Lake Storage Gen2 | Initial Access | Medium |
| PREVIEW – Anonymous scan of public storage containers (Storage.Blob_ContainerAnonymousScan) | A series of attempts were made to anonymously identify public containers in your storage account. This might indicate a reconnaissance attack, where the attacker scans your storage account to identify publicly accessible containers and then tries to find sensitive data inside them. Applies to: Azure Blob Storage | PreAttack, Collection | Medium / High |
| PREVIEW – Phishing content hosted on a storage account (Storage.Blob_PhishingContent Storage.Files_PhishingContent) | A URL used in a phishing attack points to your Azure Storage account. This URL was part of a phishing attack affecting users of Microsoft 365. Typically, content hosted on such pages is designed to trick visitors into entering their corporate credentials or financial information into a web form that looks legitimate. This alert is powered by Microsoft Threat Intelligence. Learn more about Microsoft’s threat intelligence capabilities. Applies to: Azure Blob Storage, Azure Files | Collection | High |
| PREVIEW – Storage account identified as source for distribution of malware (Storage.Files_WidespreadeAm) | Antimalware alerts indicate that an infected file(s) is stored in an Azure file share that is mounted to multiple VMs. If attackers gain access to a VM with a mounted Azure file share, they can use it to spread malware to other VMs that mount the same share. Applies to: Azure Files | Lateral Movement, Execution | High |
| PREVIEW – Storage account with potentially sensitive data has been detected with a publicly exposed container (Storage.Blob_OpenACL) | The access policy of a container in your storage account was modified to allow anonymous access. This might lead to a data breach if the container holds any sensitive data. This alert is based on analysis of Azure activity log. Applies to: Azure Blob Storage, Azure Data Lake Storage Gen2 | Privilege Escalation | Medium |
| Access from a Tor exit node to a storage account (Storage.Blob_TorAnomaly Storage.Files_TorAnomaly) | Indicates that this account has been accessed successfully from an IP address that is known as an active exit node of Tor (an anonymizing proxy). The severity of this alert considers the authentication type used (if any), and whether this is the first case of such access. Potential causes can be an attacker who has accessed your storage account by using Tor, or a legitimate user who has accessed your storage account by using Tor. Applies to: Azure Blob Storage, Azure Files, Azure Data Lake Storage Gen2 | Probing, Exploitation | High |
| Access from an unusual location to a storage account (Storage.Blob_GeoAnomaly Storage.Files_GeoAnomaly) | Indicates that there was a change in the access pattern to an Azure Storage account. Someone has accessed this account from an IP address considered unfamiliar when compared with recent activity. Either an attacker has gained access to the account, or a legitimate user has connected from a new or unusual geographic location. An example of the latter is remote maintenance from a new application or developer. Applies to: Azure Blob Storage, Azure Files, Azure Data Lake Storage Gen2 | Exploitation | Low |
| Anonymous access to a storage account (Storage.Blob_AnonymousAccessAnomaly) | Indicates that there was a change in the access pattern to an Azure Storage account. Someone accessed a container in this storage account without authenticating. Access to this container is typically authenticated by SAS token, storage account key, or AAD. This might indicate that an attacker has exploited public read access to the storage account. Applies to: Azure Blob Storage | Exploitation | High |
| Potential malware uploaded to a storage account (Storage.Blob_MalwareHashReputation Storage.Files_MalwareHashReputation) | Indicates that a blob containing potential malware has been uploaded to a blob container or a file share in a storage account. This alert is based on hash reputation analysis leveraging the power of Microsoft threat intelligence, which includes hashes for viruses, trojans, spyware and ransomware. Potential causes may include an intentional malware upload by an attacker, or an unintentional upload of a potentially malicious blob by a legitimate user. Applies to: Azure Blob Storage, Azure Files (Only for transactions over REST API) Learn more about Azure’s hash reputation analysis for malware. Learn more about Microsoft’s threat intelligence capabilities. | Lateral Movement | High |
| Unusual access inspection in a storage account (Storage.Blob_AccessInspectionAnomaly Storage.Files_AccessInspectionAnomaly) | Indicates that the access permissions of a storage account have been inspected in an unusual way, compared to recent activity on this account. A potential cause is that an attacker has performed reconnaissance for a future attack. Applies to: Azure Blob Storage, Azure Files | Collection | Medium |
| Unusual amount of data extracted from a storage account (Storage.Blob_DataExfiltration.AmountOfDataAnomaly Storage.Blob_DataExfiltration.NumberOfBlobsAnomaly Storage.Files_DataExfiltration.AmountOfDataAnomaly Storage.Files_DataExfiltration.NumberOfFilesAnomaly) | Indicates that an unusually large amount of data has been extracted compared to recent activity on this storage container. A potential cause is that an attacker has extracted a large amount of data from a container that holds blob storage. Applies to: Azure Blob Storage, Azure Files, Azure Data Lake Storage Gen2 | Exfiltration | Medium |
| Unusual application accessed a storage account (Storage.Blob_ApplicationAnomaly Storage.Files_ApplicationAnomaly) | Indicates that an unusual application has accessed this storage account. A potential cause is that an attacker has accessed your storage account by using a new application. Applies to: Azure Blob Storage, Azure Files | Exploitation | Medium |
| Unusual change of access permissions in a storage account (Storage.Blob_PermissionsChangeAnomaly Storage.Files_PermissionsChangeAnomaly) | Indicates that the access permissions of this storage container have been changed in an unusual way. A potential cause is that an attacker has changed container permissions to weaken its security posture or to gain persistence. Applies to: Azure Blob Storage, Azure Files, Azure Data Lake Storage Gen2 | Persistence | Medium |
| Unusual data exploration in a storage account (Storage.Blob_DataExplorationAnomaly Storage.Files_DataExplorationAnomaly) | Indicates that blobs or containers in a storage account have been enumerated in an abnormal way, compared to recent activity on this account. A potential cause is that an attacker has performed reconnaissance for a future attack. Applies to: Azure Blob Storage, Azure Files | Collection | Medium |
| Unusual deletion in a storage account (Storage.Blob_DeletionAnomaly Storage.Files_DeletionAnomaly) | Indicates that one or more unexpected delete operations has occurred in a storage account, compared to recent activity on this account. A potential cause is that an attacker has deleted data from your storage account. Applies to: Azure Blob Storage, Azure Files, Azure Data Lake Storage Gen2 | Exfiltration | Medium |
| Unusual upload of .cspkg to a storage account (Storage.Blob_CspkgUploadAnomaly) | Indicates that an Azure Cloud Services package (.cspkg file) has been uploaded to a storage account in an unusual way, compared to recent activity on this account. A potential cause is that an attacker has been preparing to deploy malicious code from your storage account to an Azure cloud service. Applies to: Azure Blob Storage, Azure Data Lake Storage Gen2 | Lateral Movement, Execution | Medium |
| Unusual upload of .exe to a storage account (Storage.Blob_ExeUploadAnomaly Storage.Files_ExeUploadAnomaly) | Indicates that an .exe file has been uploaded to a storage account in an unusual way, compared to recent activity on this account. A potential cause is that an attacker has uploaded a malicious executable file to your storage account, or that a legitimate user has uploaded an executable file. Applies to: Azure Blob Storage, Azure Files, Azure Data Lake Storage Gen2 | Lateral Movement, Execution | Medium |
| Network communication with a malicious machine detected (Network_CommunicationWithC2) | Network traffic analysis indicates that your machine (IP %{Victim IP}) has communicated with what is possibly a Command and Control center. When the compromised resource is a load balancer or an application gateway, the suspected activity might indicate that one or more of the resources in the backend pool (of the load balancer or application gateway) has communicated with what is possibly a Command and Control center. | Command and Control | Medium |
| Possible compromised machine detected (Network_ResourceIpIndicatedAsMalicious) | Threat intelligence indicates that your machine (at IP %{Machine IP}) may have been compromised by a malware of type Conficker. Conficker was a computer worm that targets the Microsoft Windows operating system and was first detected in November 2008. Conficker infected millions of computers including government, business and home computers in over 200 countries/regions, making it the largest known computer worm infection since the 2003 Welchia worm. | Command and Control | Medium |
| Possible incoming %{Service Name} brute force attempts detected (Generic_Incoming_BF_OneToOne) | Network traffic analysis detected incoming %{Service Name} communication to %{Victim IP}, associated with your resource %{Compromised Host} from %{Attacker IP}. When the compromised resource is a load balancer or an application gateway, the suspected incoming traffic has been forwarded to one or more of the resources in the backend pool (of the load balancer or application gateway). Specifically, sampled network data shows suspicious activity between %{Start Time} and %{End Time} on port %{Victim Port}. This activity is consistent with brute force attempts against %{Service Name} servers. | PreAttack | Medium |
| Possible incoming SQL brute force attempts detected (SQL_Incoming_BF_OneToOne) | Network traffic analysis detected incoming SQL communication to %{Victim IP}, associated with your resource %{Compromised Host}, from %{Attacker IP}. When the compromised resource is a load balancer or an application gateway, the suspected incoming traffic has been forwarded to one or more of the resources in the backend pool (of the load balancer or application gateway). Specifically, sampled network data shows suspicious activity between %{Start Time} and %{End Time} on port %{Port Number} (%{SQL Service Type}). This activity is consistent with brute force attempts against SQL servers. | PreAttack | Medium |
| Possible outgoing denial-of-service attack detected (DDOS) | Network traffic analysis detected anomalous outgoing activity originating from %{Compromised Host}, a resource in your deployment. This activity may indicate that your resource was compromised and is now engaged in denial-of-service attacks against external endpoints. When the compromised resource is a load balancer or an application gateway, the suspected activity might indicate that one or more of the resources in the backend pool (of the load balancer or application gateway) was compromised. Based on the volume of connections, we believe that the following IPs are possibly the targets of the DOS attack: %{Possible Victims}. Note that it is possible that the communication to some of these IPs is legitimate. | Impact | Medium |
| Possible outgoing port scanning activity detected (PortSweeping) | Network traffic analysis detected suspicious outgoing traffic from %{Compromised Host}. This traffic may be a result of a port scanning activity. When the compromised resource is a load balancer or an application gateway, the suspected outgoing traffic has been originated from to one or more of the resources in the backend pool (of the load balancer or application gateway). If this behavior is intentional, please note that performing port scanning is against Azure Terms of service. If this behavior is unintentional, it may mean your resource has been compromised. | Discovery | Medium |
| Suspicious incoming RDP network activity from multiple sources (RDP_Incoming_BF_ManyToOne) | Network traffic analysis detected anomalous incoming Remote Desktop Protocol (RDP) communication to %{Victim IP}, associated with your resource %{Compromised Host}, from multiple sources. When the compromised resource is a load balancer or an application gateway, the suspected incoming traffic has been forwarded to one or more of the resources in the backend pool (of the load balancer or application gateway). Specifically, sampled network data shows %{Number of Attacking IPs} unique IPs connecting to your resource, which is considered abnormal for this environment. This activity may indicate an attempt to brute force your RDP end point from multiple hosts (Botnet) | PreAttack | Medium |
| Suspicious incoming RDP network activity (RDP_Incoming_BF_OneToOne) | Network traffic analysis detected anomalous incoming Remote Desktop Protocol (RDP) communication to %{Victim IP}, associated with your resource %{Compromised Host}, from %{Attacker IP}. When the compromised resource is a load balancer or an application gateway, the suspected incoming traffic has been forwarded to one or more of the resources in the backend pool (of the load balancer or application gateway). Specifically, sampled network data shows %{Number of Connections} incoming connections to your resource, which is considered abnormal for this environment. This activity may indicate an attempt to brute force your RDP end point | PreAttack | Medium |
| Suspicious incoming SSH network activity from multiple sources (SSH_Incoming_BF_ManyToOne) | Network traffic analysis detected anomalous incoming SSH communication to %{Victim IP}, associated with your resource %{Compromised Host}, from multiple sources. When the compromised resource is a load balancer or an application gateway, the suspected incoming traffic has been forwarded to one or more of the resources in the backend pool (of the load balancer or application gateway). Specifically, sampled network data shows %{Number of Attacking IPs} unique IPs connecting to your resource, which is considered abnormal for this environment. This activity may indicate an attempt to brute force your SSH end point from multiple hosts (Botnet) | PreAttack | Medium |
| Suspicious incoming SSH network activity (SSH_Incoming_BF_OneToOne) | Network traffic analysis detected anomalous incoming SSH communication to %{Victim IP}, associated with your resource %{Compromised Host}, from %{Attacker IP}. When the compromised resource is a load balancer or an application gateway, the suspected incoming traffic has been forwarded to one or more of the resources in the backend pool (of the load balancer or application gateway). Specifically, sampled network data shows %{Number of Connections} incoming connections to your resource, which is considered abnormal for this environment. This activity may indicate an attempt to brute force your SSH end point | PreAttack | Medium |
| Suspicious outgoing %{Attacked Protocol} traffic detected (PortScanning) | Network traffic analysis detected suspicious outgoing traffic from %{Compromised Host} to destination port %{Most Common Port}. When the compromised resource is a load balancer or an application gateway, the suspected outgoing traffic has been originated from to one or more of the resources in the backend pool (of the load balancer or application gateway). This behavior may indicate that your resource is taking part in %{Attacked Protocol} brute force attempts or port sweeping attacks. | Discovery | Medium |
| Suspicious outgoing RDP network activity to multiple destinations (RDP_Outgoing_BF_OneToMany) | Network traffic analysis detected anomalous outgoing Remote Desktop Protocol (RDP) communication to multiple destinations originating from %{Compromised Host} (%{Attacker IP}), a resource in your deployment. When the compromised resource is a load balancer or an application gateway, the suspected outgoing traffic has been originated from to one or more of the resources in the backend pool (of the load balancer or application gateway). Specifically, sampled network data shows your machine connecting to %{Number of Attacked IPs} unique IPs, which is considered abnormal for this environment. This activity may indicate that your resource was compromised and is now used to brute force external RDP end points. Note that this type of activity could possibly cause your IP to be flagged as malicious by external entities. | Discovery | High |
| Suspicious outgoing RDP network activity (RDP_Outgoing_BF_OneToOne) | Network traffic analysis detected anomalous outgoing Remote Desktop Protocol (RDP) communication to %{Victim IP} originating from %{Compromised Host} (%{Attacker IP}), a resource in your deployment. When the compromised resource is a load balancer or an application gateway, the suspected outgoing traffic has been originated from to one or more of the resources in the backend pool (of the load balancer or application gateway). Specifically, sampled network data shows %{Number of Connections} outgoing connections from your resource, which is considered abnormal for this environment. This activity may indicate that your machine was compromised and is now used to brute force external RDP end points. Note that this type of activity could possibly cause your IP to be flagged as malicious by external entities. | Lateral Movement | High |
| Suspicious outgoing SSH network activity to multiple destinations (SSH_Outgoing_BF_OneToMany) | Network traffic analysis detected anomalous outgoing SSH communication to multiple destinations originating from %{Compromised Host} (%{Attacker IP}), a resource in your deployment. When the compromised resource is a load balancer or an application gateway, the suspected outgoing traffic has been originated from to one or more of the resources in the backend pool (of the load balancer or application gateway). Specifically, sampled network data shows your resource connecting to %{Number of Attacked IPs} unique IPs, which is considered abnormal for this environment. This activity may indicate that your resource was compromised and is now used to brute force external SSH end points. Note that this type of activity could possibly cause your IP to be flagged as malicious by external entities. | Discovery | Medium |
| Suspicious outgoing SSH network activity (SSH_Outgoing_BF_OneToOne) | Network traffic analysis detected anomalous outgoing SSH communication to %{Victim IP} originating from %{Compromised Host} (%{Attacker IP}), a resource in your deployment. When the compromised resource is a load balancer or an application gateway, the suspected outgoing traffic has been originated from to one or more of the resources in the backend pool (of the load balancer or application gateway). Specifically, sampled network data shows %{Number of Connections} outgoing connections from your resource, which is considered abnormal for this environment. This activity may indicate that your resource was compromised and is now used to brute force external SSH end points. Note that this type of activity could possibly cause your IP to be flagged as malicious by external entities. | Lateral Movement | Medium |
| Traffic detected from IP addresses recommended for blocking | Microsoft Defender for Cloud detected inbound traffic from IP addresses that are recommended to be blocked. This typically occurs when this IP address doesn’t communicate regularly with this resource. Alternatively, the IP address has been flagged as malicious by Defender for Cloud’s threat intelligence sources. | Probing | Low |
| Access from a suspicious IP address to a key vault (KV_SuspiciousIPAccess) | A key vault has been successfully accessed by an IP that has been identified by Microsoft Threat Intelligence as a suspicious IP address. This may indicate that your infrastructure has been compromised. We recommend further investigation. Learn more about Microsoft’s threat intelligence capabilities. | Credential Access | Medium |
| Access from a TOR exit node to a key vault (KV_TORAccess) | A key vault has been accessed from a known TOR exit node. This could be an indication that a threat actor has accessed the key vault and is using the TOR network to hide their source location. We recommend further investigations. | Credential Access | Medium |
| High volume of operations in a key vault (KV_OperationVolumeAnomaly) | An anomalous number of key vault operations were performed by a user, service principal, and/or a specific key vault. This anomalous activity pattern may be legitimate, but it could be an indication that a threat actor has gained access to the key vault and the secrets contained within it. We recommend further investigations. | Credential Access | Medium |
| Suspicious policy change and secret query in a key vault (KV_PutGetAnomaly) | A user or service principal has performed an anomalous Vault Put policy change operation followed by one or more Secret Get operations. This pattern is not normally performed by the specified user or service principal. This may be legitimate activity, but it could be an indication that a threat actor has updated the key vault policy to access previously inaccessible secrets. We recommend further investigations. | Credential Access | Medium |
| Suspicious secret listing and query in a key vault (KV_ListGetAnomaly) | A user or service principal has performed an anomalous Secret List operation followed by one or more Secret Get operations. This pattern is not normally performed by the specified user or service principal and is typically associated with secret dumping. This may be legitimate activity, but it could be an indication that a threat actor has gained access to the key vault and is trying to discover secrets that can be used to move laterally through your network and/or gain access to sensitive resources. We recommend further investigations. | Credential Access | Medium |
| Unusual application accessed a key vault (KV_AppAnomaly) | A key vault has been accessed by a service principal that does not normally access it. This anomalous access pattern may be legitimate activity, but it could be an indication that a threat actor has gained access to the key vault in an attempt to access the secrets contained within it. We recommend further investigations. | Credential Access | Medium |
| Unusual operation pattern in a key vault KV_OperationPatternAnomaly) | An anomalous pattern of key vault operations was performed by a user, service principal, and/or a specific key vault. This anomalous activity pattern may be legitimate, but it could be an indication that a threat actor has gained access to the key vault and the secrets contained within it. We recommend further investigations. | Credential Access | Medium |
| Unusual user accessed a key vault (KV_UserAnomaly) | A key vault has been accessed by a user that does not normally access it. This anomalous access pattern may be legitimate activity, but it could be an indication that a threat actor has gained access to the key vault in an attempt to access the secrets contained within it. We recommend further investigations. | Credential Access | Medium |
| Unusual user-application pair accessed a key vault (KV_UserAppAnomaly) | A key vault has been accessed by a user-service principal pair that does not normally access it. This anomalous access pattern may be legitimate activity, but it could be an indication that a threat actor has gained access to the key vault in an attempt to access the secrets contained within it. We recommend further investigations. | Credential Access | Medium |
| User accessed high volume of key vaults (KV_AccountVolumeAnomaly) | A user or service principal has accessed an anomalously high volume of key vaults. This anomalous access pattern may be legitimate activity, but it could be an indication that a threat actor has gained access to multiple key vaults in an attempt to access the secrets contained within them. We recommend further investigations. | Credential Access | Medium |
| DDoS Attack detected for Public IP | DDoS Attack detected for Public IP (IP address) and being mitigated. | Probing | High |
| DDoS Attack mitigated for Public IP | DDoS Attack mitigated for Public IP (IP address). | Probing | Low |
Sentinel
https://github.com/reprise99/Sentinel-Queries
https://github.com/reprise99/Sentinel-Queries/blob/main
MCAS
https://www.cloudservus.com/microsoft-cloud-app-security/
Microsoft Defender
Office365
https://o365blog.com/aadkillchain/
References
- https://docs.datadoghq.com/security_platform/default_rules/
- https://learn.microsoft.com/en-us/azure/sentinel/fusion-scenario-reference#multiple-vm-creation-activities-following-suspicious-azure-active-directory-sign-in IMPORTANT
- How Azure Security Center helps reveal a Cyberattack | Microsoft Azure Blog
- Azure-Sentinel/Detections at master · Azure/Azure-Sentinel · GitHub
- LOLBAS
- Remove-AntiPhishRule (ExchangePowerShell) | Microsoft Learn
- Respond to web threats in Microsoft Defender for Endpoint – Microsoft Defender for Endpoint | Microsoft Learn
- Malicious web application requests linked with Microsoft Defender for Endpoint formerly Microsoft Defender ATP alerts | Microsoft Sentinel Analytic Rules – MITRE perspective ***
