Azure Monitor Audit
CheckedHelps with Azure, monitoring, auditing as part of deploying and managing cloud infrastructure workflows.
Install on your platform
Showing Claude Code. One command installs this skill into any of the agents below.
- 1
Run this in your project
terminal$ npx skills add bagelhole/devops-security-agent-skills --skill azure-monitor-audit -a claude-code Uses the open-source
skillsCLI and needs Node.js. Add-gto install it for your user instead of this project.
What we know about this skill
Publisher
bagelhole
Taken from the source listing. We haven't verified who controls this account.
Install target
Live repository
Not pinned. Installing fetches whatever the repository holds at the time you run the command.
Automated safety checks
This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.
Declares what it does: passed
SKILL.md parses and declares a name and a description.
SKILL.md exists, its frontmatter parses, and it declares a name and a description.
No undeclared network calls: passed
Makes no network calls.
Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.
No obfuscated payloads: passed
No encoded or obfuscated payloads.
No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.
No credential access: passed
Reads no keys, tokens, keychains or credential files.
Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.
No pipe-to-shell installers: passed
No pipe-to-shell or download-and-run installers.
No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.
Pinned to a commit: passed
Scanned bagelhole/devops-security-agent-skills at 0365f57a07.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- 0365f57a07
- Scanned
- 1 file, 341 lines
About this skill
What it does
This skill allows an AI agent to query and interpret Azure Monitor Audit Logs. It can retrieve information about user activity, resource changes, and security events within an Azure environment. The agent can then summarize these logs or extract specific details based on provided criteria, aiding in compliance checks and incident investigation.
When to use it
- Compliance Auditing: Generate reports demonstrating adherence to regulatory requirements by extracting relevant audit log data.
- Security Incident Response: Quickly identify the root cause of a security event by analyzing user actions and resource modifications around the time of the incident.
- Resource Change Tracking: Determine who made changes to specific Azure resources (e.g., virtual machines, storage accounts) and when those changes occurred.
- User Activity Monitoring: Track user logins, access attempts, and other activities within an Azure tenant for security monitoring purposes.
Key capabilities
- Query Azure Monitor Audit Logs
- Filter logs by time range, resource type, or user identity
- Summarize audit log data
- Extract specific details from audit events
Example prompts
- "Show me all login attempts to the Azure portal in the last 24 hours."
- "What changes were made to the 'my-vm' virtual machine yesterday?"
- "Generate a report of user activity on storage accounts for compliance purposes."
Tips & gotchas
- Requires appropriate Azure permissions (e.g., Reader, Contributor) to access Audit Logs.
- Audit logs retention period is limited; ensure sufficient retention policies are in place if historical data is needed.