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.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionanalyzing-azure-activity-logs-for-threatsExecute the skills CLI command in your project's root directory to begin installation:
Fetches analyzing-azure-activity-logs-for-threats from mukul975/Anthropic-Cybersecurity-Skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate analyzing-azure-activity-logs-for-threats. Access via /analyzing-azure-activity-logs-for-threats in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
0
total installs
0
this week
8.6K
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
8.6K
stars
| name | analyzing-azure-activity-logs-for-threats |
| description | '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. ' |
| domain | cybersecurity |
| subdomain | security-operations |
| tags | - azure - cloud-security - azure-monitor - kql - threat-hunting - activity-logs |
| version | '1.0' |
| author | mahipal |
| license | Apache-2.0 |
| nist_csf | - DE.CM-01 - RS.MA-01 - GV.OV-01 - DE.AE-02 |
Use azure-monitor-query to execute KQL queries against Azure Log Analytics workspaces, detecting suspicious admin operations and sign-in anomalies.
from azure.identity import DefaultAzureCredential
from azure.monitor.query import LogsQueryClient
from datetime import timedelta
credential = DefaultAzureCredential()
client = LogsQueryClient(credential)
response = client.query_workspace(
workspace_id="WORKSPACE_ID",
query="AzureActivity | where OperationNameValue has 'MICROSOFT.AUTHORIZATION/ROLEASSIGNMENTS/WRITE' | take 10",
timespan=timedelta(hours=24),
)
Key detection queries:
# Detect new Global Admin role assignments
query = '''
AuditLogs
| where OperationName == "Add member to role"
| where TargetResources[0].modifiedProperties[0].newValue has "Global Administrator"
'''
Prerequisites
Time Estimate
15-45 minutes depending on use case complexity
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
mukul975/Anthropic-Cybersecurity-Skills
mukul975/Anthropic-Cybersecurity-Skills
mukul975/Anthropic-Cybersecurity-Skills
mukul975/Anthropic-Cybersecurity-Skills
mukul975/Anthropic-Cybersecurity-Skills
mukul975/Anthropic-Cybersecurity-Skills
analyzing-azure-activity-logs-for-threats has been reliable in day-to-day use. Documentation quality is above average for community skills.
Registry listing for analyzing-azure-activity-logs-for-threats matched our evaluation — installs cleanly and behaves as described in the markdown.
We added analyzing-azure-activity-logs-for-threats from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Keeps context tight: analyzing-azure-activity-logs-for-threats is the kind of skill you can hand to a new teammate without a long onboarding doc.
Keeps context tight: analyzing-azure-activity-logs-for-threats is the kind of skill you can hand to a new teammate without a long onboarding doc.
Registry listing for analyzing-azure-activity-logs-for-threats matched our evaluation — installs cleanly and behaves as described in the markdown.
Solid pick for teams standardizing on skills: analyzing-azure-activity-logs-for-threats is focused, and the summary matches what you get after install.
We added analyzing-azure-activity-logs-for-threats from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
analyzing-azure-activity-logs-for-threats has been reliable in day-to-day use. Documentation quality is above average for community skills.
analyzing-azure-activity-logs-for-threats fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
showing 1-10 of 36