Skip to main content

 Mapping Azure Security Threats: A MITRE ATT&CK Mind Map


The MITRE ATT&CK framework in Azure environments is pivotal for searching, detecting, investigating, and mitigating attacks. This cheat critically maps MITRE ATT&CK tactics to Azure services, enabling proactive threat hunting and precise incident response.


🛡️Key Insights:


⇨ Initial Access: Attackers may gain entry via Azure CLI or compromised web apps. SignInLogs and AADServicePrincipalSignInLogs are essential for identifying suspicious login events.


⇨ Execution: Attackers often exploit Automation Accounts and VM scripts to run malicious code. Monitoring for abnormal execution of operations like MicrosoftCompute/virtualMachines/runCommand/action is crucial.


⇨ Privilege Escalation: Changes to Entra ID users, groups, or roles (via operations like Microsoftdirectory/servicePrincipals/enable) should be closely monitored for abnormal permission escalations.


⇨ Credential Access: Focus on Azure Key Vault activity. Unauthorized access or changes to secrets, certificates, and keyscould indicate credential harvesting.


⇨ Exfiltration: Attackers often use SAS URIs or soft delete data to move data undetected. Investigate suspicious API calls like MicrosoftStorage/storageAccounts/listAccountSas/action.


By integrating the MITRE ATT&CK framework with Azure specific actions, you can uncover potential attack paths, identify risks, and map adversary behaviors to real time activities across Azure services.


🛡️ Tip: Always trace back suspicious activities to their root cause. Correlate logs, activity details, and authentication anomalies to identify early signs of compromise and pivoting.


Many thanks, Expel, for a great mind map.

Comments

Popular posts from this blog

Step-by-Step Explanation of Ballooning, Compression & Swapping in VMware

 🔹 Step-by-Step Explanation of Ballooning, Compression & Swapping in VMware ⸻ 1️⃣ Memory Ballooning (vmmemctl) Ballooning is the first memory reclamation technique used when ESXi detects memory pressure. ➤ Step-by-Step: How Ballooning Works  1. VMware Tools installs the balloon driver (vmmemctl) inside the guest OS.  2. ESXi detects low free memory on the host.  3. ESXi inflates the balloon in selected VMs.  4. Balloon driver occupies guest memory, making the OS think RAM is full.  5. Guest OS frees idle / unused pages (because it believes memory is needed).  6. ESXi reclaims those freed pages and makes them available to other VMs. Why Ballooning Happens?  • Host free memory is very low.  • ESXi wants the VM to release unused pages before resorting to swapping. Example  • Host memory: 64 GB  • VMs used: 62 GB  • Free: 2 GB → ESXi triggers ballooning  • VM1 (8 GB RAM): Balloon inflates to 2 GB → OS frees 2 GB → ESXi re...

ESXi Host Troubleshooting Checklist

  🛠️ ESXi Host Troubleshooting Checklist (With Complete Log Locations) ✅ 1. Host Status & Connectivity Check host state in vCenter (Connected / Not Responding / Disconnected) Review CPU, RAM, and datastore usage Validate HA/DRS recommendations ✅ 2. Hardware Health Monitor hardware sensors (CPU, DIMMs, fans, PSU, RAID) Check RAID controller logs via vendor tools View hardware status in: vCenter → Monitor → Hardware Health DCUI → Hardware Status ✅ 3. Network Validation Verify vSwitches, Port Groups, NIC teaming, VLAN tagging Check vmkernel ports (mgmt, vMotion, iSCSI, vSAN) Test reachability using: Shell vmkping < IP > Show more lines Validate physical NIC status and link speed ✅ 4. Storage & Datastore Checks Confirm datastore accessibility Rescan storage adapters (iSCSI/FC/NFS) Validate multipathing (Round Robin / Fixed / MRU) Check datastore latency with esxtop ✅ **5. Critical Logs & Their Locations (Full List) Here are key ESXi log files that every VMware adm...
  vCenter Troubleshooting Tips, Common Issues & Log Locations 🚀 1. General Troubleshooting Approach A. Check service health first For vCenter Server Appliance (VCSA): Shell https : / / < vcenter - FQDN > : 5480 Show more lines Go to Services → Health to verify: vCenter Server ESXi hosts vSphere Client DNS, NTP, DB connections vpxd, vpxd-svcs, vsphere-ui B. DNS & NTP checks vCenter is highly dependent on correct DNS & time sync. Check: Shell nslookup < vcenter - fqdn > nslookup < esxi - host - fqdn > Show more lines Time drift > 5 minutes causes: Login failures vpxd crashes PSC authentication issues C. Check storage/database health Slow DB/storage = UI slow, tasks hung. For VCSA: Shell df - h du - sh / storage / log / * / var / log Show more lines Free up space if partitions hit >80%. D. Restart critical services safely On VCSA: Shell service - control - - status service - control - - stop - - all service - control - - start - - all ...