Individual skill
analyzing-azure-activity-logs-for-threats
Queries Azure Monitor activity logs and sign-in logs via azure-monitor-query to detect suspicious administrative operations, impossible travel, privilege escalation, and resource modifications. Builds KQL queries for threat hunting in Azure environments. Use when investigating suspicious Azure tenant activity or building cloud SIEM detections.
internal/tools/skills/data/security-operations/analyzing-azure-activity-logs-for-threats/SKILL.md
Source commit d42f381ad34843e71a42658e5c57290c713e85af
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Instructions only
- Last checked
- Nov 9, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 1,323
- Repository last updated
- Nov 8, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- cybersecurity Repository topic
- security Repository topic
- bug-bounty Repository topic
- automation Repository topic
- autonomous-pentesting Repository topic
- ai-agent Repository topic
- ai-security Repository topic
- ethical-hacking Repository topic
- golang Repository topic
- penetration-testing Repository topic
- azure Declared skill tag
- cloud-security Declared skill tag
- azure-monitor Declared skill tag
- kql Declared skill tag
- threat-hunting Declared skill tag
- activity-logs Declared skill tag
- security Derived category
- operations Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Read excerpt
# Analyzing Azure Activity Logs for Threats
## When to Use
- When investigating security incidents that require analyzing azure activity logs for threats
- When building detection rules or threat hunting queries for this domain
- When SOC analysts need structured procedures for this analysis type
- When validating security monitoring coverage for related attack techniques
## Detection Gaps & Validation
- **`AzureActivity` ≠ `AuditLogs` ≠ `SigninLogs`:** role-assignment writes land in `AzureActivity` (`operationName` `MICROSOFT.AUTHORIZATION/ROLEASSIGNMENTS/WRITE`), but Azure AD directory-role grants (Global Admin) only appear in `AuditLogs` (`OperationName == "Add member to role"`). Querying one table misses the other entire escalation path.
- **Plane gap:** `AzureActivity` covers ARM control-plane only — data-plane actions (Key Vault secret *reads*, Storage blob GETs) require resource-specific diagnostic logs (`AzureDiagnostics`/`StorageRead`) to be explicitly enabled, or the access is invisible.