Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
mukul975 avatar

Analyzing Office365 Audit Logs For Compromise

  • 254 installs
  • 27.3k repo stars
  • Updated August 2, 2026
  • mukul975/anthropic-cybersecurity-skills

Analyzing Office365 Audit Logs For Compromise is an agent skill that guides structured Microsoft 365 audit-log review to detect and scope tenant compromise.

About

Analyzing Office365 Audit Logs For Compromise is an agent skill aimed at solo builders and small teams who run on Microsoft 365 and need a repeatable way to read audit logs when something looks wrong. Instead of ad-hoc searching in the compliance center, the skill frames how to pull relevant Unified Audit Log activity, correlate risky patterns such as impossible travel, privilege escalation, suspicious inbox rules, and mass downloads, and turn raw events into a short incident narrative you can act on. It fits the Operate phase when you are responding to alerts, validating a phishing aftermath, or doing periodic tenant hygiene—not when you are shipping application code. Expect procedural security knowledge rather than a turnkey SIEM integration; you still need appropriate Microsoft admin roles and export access. Use it when cloud identity compromise is plausible and you want structured questions and interpretation steps rather than guessing which cmdlet or portal view to open first.

  • Structured approach to Office 365 / Microsoft 365 Unified Audit Log review for breach indicators
  • Maps common compromise TTPs to observable sign-in, mailbox, and admin-action events
  • Supports incident scoping and timeline reconstruction from cloud audit exports
  • Oriented to security operators and solo builders defending their own Microsoft tenant
  • Pairs with broader cybersecurity skill packs from the same repository family

Analyzing Office365 Audit Logs For Compromise by the numbers

  • 254 all-time installs (skills.sh)
  • +17 installs in the week ending Aug 4, 2026 (Skillselion tracking)
  • Ranked #680 of 2,203 Security skills by installs in the Skillselion catalog
  • Security screen: LOW risk (skills.sh audit)
  • Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/mukul975/anthropic-cybersecurity-skills --skill analyzing-office365-audit-logs-for-compromise

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs254
repo stars27.3k
Security audit3 / 3 scanners passed
Last updatedAugust 2, 2026
Repositorymukul975/anthropic-cybersecurity-skills

What it does

Investigate suspected Microsoft 365 tenant compromise by querying and interpreting Unified Audit Log signals with an agent-guided workflow.

Who is it for?

Best when you administer your own Microsoft 365 tenant and need guided log interpretation after an alert or account takeover worry.

Skip if: Skip if you're without Microsoft audit-log access, pure app-level OWASP reviews, or organizations that already run a mature SOC with standardized playbooks and do not need agent-assisted triage.

When should I use this skill?

When Microsoft 365 audit activity suggests account takeover, suspicious admin actions, or you need structured compromise analysis on Unified Audit Log data.

What you get

After the skill runs you have a prioritized timeline of suspicious audit events, likely attack paths, and concrete next checks to contain and remediate the tenant.

  • Prioritized list of suspicious audit events with rationale
  • Incident timeline draft and recommended containment checks

Files

SKILL.mdMarkdownGitHub ↗

Analyzing Office 365 Audit Logs for Compromise

Overview

Business Email Compromise (BEC) attacks often leave traces in Office 365 audit logs: suspicious inbox rule creation, email forwarding to external addresses, mailbox delegation changes, and unauthorized OAuth application consent grants. This skill uses the Microsoft Graph API to query the Unified Audit Log, enumerate inbox rules across mailboxes, detect forwarding configurations, and identify compromised account indicators.

When to Use

  • When investigating security incidents that require analyzing office365 audit logs for compromise
  • 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

Prerequisites

  • Azure AD app registration with AuditLog.Read.All, MailboxSettings.Read, Mail.Read (application permissions)
  • Python 3.9+ with msal, requests
  • Client secret or certificate for authentication
  • Global Reader or Security Reader role

Steps

1. Authenticate to Microsoft Graph using MSAL client credentials flow 2. Query Unified Audit Log for suspicious operations (Set-Mailbox, New-InboxRule) 3. Enumerate inbox rules across mailboxes and flag forwarding rules 4. Detect mailbox delegation changes (Add-MailboxPermission) 5. Identify OAuth consent grants to suspicious applications 6. Check for suspicious sign-in patterns from audit logs 7. Generate compromise indicator report with timeline

Expected Output

  • JSON report listing forwarding rules, delegation changes, OAuth grants, and suspicious audit events with risk scores
  • Timeline of compromise indicators with affected mailboxes

Related skills

How it compares

Use for cloud identity audit triage instead of generic “debug my API” or frontend-focused agent skills.

FAQ

Who is analyzing-office365-audit-logs-for-compromise for?

Microsoft 365 administrators, SaaS operators, and security-conscious developers who must investigate tenant audit data without a full-time analyst.

When should I use analyzing-office365-audit-logs-for-compromise?

Use it in Operate when monitoring surfaces odd sign-ins, inbox rules, or admin changes; also after ship-phase security incidents when you pivot to production identity forensics.

Is analyzing-office365-audit-logs-for-compromise safe to install?

Treat it like any third-party security skill: review the Security Audits panel on this Prism page, confirm the repo source, and avoid pasting production secrets into the agent beyond what your investigation requires.

Securityauditcomplianceappsec

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.