agentleFS
kaandgnshkaandgnsh/Claude-Blue/skills/azure-security/azure-activity-investigation/SKILL.md

azure-activity-investigation

Skill0 starsChanged 15 days agoMITView on GitHub

Investigate Azure control-plane and resource activity — Activity Log (AzureActivity), resource diagnostic logs (Key Vault, Storage, VM run-command), Defender for Cloud alerts — for privilege escalation, persistence, data access and defense evasion in subscriptions. Use when an Azure subscription or resource may be compromised, or a Defender for Cloud alert needs investigation.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Check data access: storage account keys listed → assume data access possible (storage logs only if diagnostics enabled), Key Vault secret …

    line 47

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Azure Activity Investigation

Key operations (AzureActivity.OperationNameValue)

TacticOperation
Privilege escalationMICROSOFT.AUTHORIZATION/ROLEASSIGNMENTS/WRITE, Microsoft.Authorization/elevateAccess/action
Execution on VMsMICROSOFT.COMPUTE/VIRTUALMACHINES/RUNCOMMAND/ACTION, .../EXTENSIONS/WRITE (CustomScriptExtension)
Credential accessMICROSOFT.KEYVAULT/VAULTS/WRITE (access policy changes), Key Vault data plane SecretGet (in AzureDiagnostics/KeyVault logs), MICROSOFT.STORAGE/STORAGEACCOUNTS/LISTKEYS/ACTION
Defense evasionMICROSOFT.INSIGHTS/DIAGNOSTICSETTINGS/DELETE, MICROSOFT.SECURITY/PRICINGS/WRITE (Defender plan disabled), NSG rule changes
ExfiltrationMICROSOFT.COMPUTE/DISKS/BEGINGETACCESS/ACTION (disk SAS export), MICROSOFT.COMPUTE/SNAPSHOTS/WRITE, storage SAS generation
ImpactMass DELETE operations, resource locks removed (MICROSOFT.AUTHORIZATION/LOCKS/DELETE)

KQL

AzureActivity
| where TimeGenerated > ago(14d)
| where OperationNameValue has_any ("ROLEASSIGNMENTS/WRITE", "RUNCOMMAND/ACTION", "LISTKEYS/ACTION", "DIAGNOSTICSETTINGS/DELETE",
                                    "BEGINGETACCESS/ACTION", "elevateAccess", "LOCKS/DELETE", "EXTENSIONS/WRITE")
| where ActivityStatusValue in ("Success", "Succeeded")
| project TimeGenerated, Caller, CallerIpAddress, OperationNameValue, ResourceGroup, _ResourceId, Properties_d
| order by TimeGenerated asc

Key Vault data plane:

AzureDiagnostics
| where ResourceProvider == "MICROSOFT.KEYVAULT" and OperationName in ("SecretGet", "KeyDecrypt", "SecretList")
| summarize count(), secrets=make_set(id_s, 50) by CallerIPAddress, identity_claim_upn_s, bin(TimeGenerated, 1h)

(Column names depend on whether resource-specific tables are used — e.g. AZKVAuditLogs.)

Workflow

  1. Identify the caller (user, service principal, managed identity) and correlate with Entra sign-ins (entra-signin-investigation, AADServicePrincipalSignInLogs).
  2. Build the change list; check Run Command/extension contents (az vm run-command list, extension settings) for executed scripts.
  3. Check data access: storage account keys listed → assume data access possible (storage logs only if diagnostics enabled), Key Vault secret reads.
  4. Review Defender for Cloud alerts (SecurityAlert | where ProductName has "Defender") for correlated detections.

Related skills

entra-audit-investigation, azure-rbac-review, cloud-incident-response, sentinel-kql-investigation

References

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.