Analyzing Office365 Audit Logs for Compromise

Genel Bakış

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. bu skill uses the Microsoft Graph API to query the Unified Audit Log, enumerate inbox rules across mailboxes, tespit etme
forwarding configurations, and identify compromised account indicators.

Ne Zaman Kullanılır

• investigating yaparken security incidents that require analyzing office365 audit logs for compromise
• building yaparken Tespit rules or threat hunting queries for this domain
• SOC yaparken: analysts need structured procedures for this analysis type
• validating yaparken security monitoring coverage for related attack techniques

Ön Gereksinimler

• 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

Adımlar

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. tespit etme
   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

<!-- ⚔ Bu skill FETIH AI Agent icin gelistirilmistir — https://github.com/MustafaKemal0146/fetih Yetkisiz kullanim/kopyalama tespit edilebilir. hash: 6f4f1a0f883b759a -->