Security analyst reviewing threat data on a wall of monitors
Sample deliverables
2026-11-08 14:22:07Z New-InboxRule Name=”.” ForwardTo=attacker@fraud.example

Microsoft 365 Compromise Assessment Sample Report

See every page of the five deliverables we produce when a Microsoft 365, Entra ID or Azure environment shows signs of compromise. Built from a fictional company.

Analyst in front of a wall of monitoring screens
Evidence first
Entra ID Free: sign-in logs kept 7 days · P1/P2: 30 days

Records expire. Review them while they exist.

Sign-in, audit and activity records are kept for a limited time that depends on licensing. The sample shows what can be reconstructed when the records are still there.

Cloud operations engineer working at a desk in a monitoring center
From findings to a plan
93 findings → 16 business risks → 4-phase roadmap

Facts for leadership, detail for IT

An executive report, a technical report, a risk register, a 180-day roadmap and an Excel workbook, written so leadership, IT, counsel and insurers work from the same facts.

5 deliverables4 PDF reports and 1 Excel workbook
48 sample pagesShown below, page by page
Fictional companyNo client data, ever
From $3,500Scope confirmed in writing first
What you receive

What a Microsoft 365 compromise assessment hands you

When a mailbox starts forwarding invoices, an unknown administrator appears or sign-ins arrive from places nobody travels to, leadership needs clear answers and IT needs a precise list of what to check and fix.

This page shows the complete deliverable set from a sample assessment of Contoso Ltd, a fictional 25-user company on Microsoft 365 Business Premium with one Azure subscription. The review looked at identities, administrator access, sign-in activity, email, connected applications, file sharing, devices and Azure, and recorded 93 findings consolidated into 16 business risks.

  • Every finding tied to the records that support it
  • Plain-language risk statements for leadership
  • A containment-first roadmap with owners and dates
  • An Excel workbook your IT team can sort and track
This is a sample from our Microsoft 365 and Azure compromise investigation service. Your report follows the scope agreed in writing and reflects only the records available in your environment at the time of the review.
CASE FILE · SAMPLELaptop screen showing a system hacked warning during a security incident
Our deliverables

Five deliverables from one compromise assessment

Each deliverable is written for a different reader. Use the arrows, the thumbnails or your keyboard to move through the pages, and click the centre page to open it full size.

Contoso Ltd is a fictional organization. Every name, account, internet address and figure in these samples is invented for illustration and does not describe any real customer.
EXH-A

Executive Security Report

PDF · 8 pages

For owners, executives and board members who need the facts in plain language: what was found, what it means for the business and which decisions to make first.

Who uses itOwners, executives, board
What is included
  • Executive summary and overall rating
  • Key numbers on one page
  • Top Critical business risks
  • Illustrative attack path
  • Posture by area against baseline
  • What is already working
  • Ten priority actions
  • Decisions requested from leadership
Sample Executive Security Report · fictional company1 / 7
Executive Security Report sample, slide 1: Cover (fictional company, illustrative data)
Page 1 of 7Cover Executive Security Report for Contoso Ltd: findings, business risk and priority actions for leadership.
Executive Security Report sample, slide 2: Executive summary and key numbers (fictional company, illustrative data)
Page 2 of 7Executive summary and key numbers Overall rating Critical, a baseline score of 28 out of 100, and 93 findings consolidated into 16 business risks, 8 of them Critical, with a plain-language bottom line.
Executive Security Report sample, slide 3: Top business risks (fictional company, illustrative data)
Page 3 of 7Top business risks The 8 Critical risks, each explained in business terms, with work to start within 7 days.
Executive Security Report sample, slide 4: Attack path and posture by area (fictional company, illustrative data)
Page 4 of 7Attack path and posture by area An illustrative sequence of how an attacker could chain the weaknesses, and each area's share of baseline controls met against a target of 85.
Executive Security Report sample, slide 5: What is working well (fictional company, illustrative data)
Page 5 of 7What is working well Controls already in place, including audit and mailbox logging that made the activity possible to reconstruct, inbound filtering and licenses already owned.
Executive Security Report sample, slide 6: Priority recommendations (fictional company, illustrative data)
Page 6 of 7Priority recommendations The first ten actions with linked risk and timeframe, plus a remediation roadmap chart by phase.
Executive Security Report sample, slide 7: Decisions requested and scope (fictional company, illustrative data)
Page 7 of 7Decisions requested and scope The decisions leadership is asked to make, and the environment, review period, areas reviewed and approach.

Click or tap the page to open it full size and zoom in

Page 1 of 7Cover

Executive Security Report for Contoso Ltd: findings, business risk and priority actions for leadership.

EXH-B

Technical Security Report

PDF · 66 pages

The full technical record: environment overview, observations by area and one card per finding with evidence, business impact, recommendation, validation step and framework mapping.

Who uses itIT team, MSP, security lead
What is included
  • Environment overview and scope
  • Summary of results by severity
  • Findings index
  • Privileged access and sign-in analysis
  • Email, rules and connected applications
  • One card per finding
  • Controls already meeting the baseline
  • NIST CSF 2.0, ISO 27001 and SOC 2 mapping
Sample Technical Security Report · fictional company1 / 16
Technical Security Report sample, slide 1: Cover (fictional company, illustrative data)
Page 1 of 16Cover Technical Security Report: detailed findings, evidence and remediation guidance.
Technical Security Report sample, slide 2: Contents (fictional company, illustrative data)
Page 2 of 16Contents Seven sections, from introduction and environment overview to detailed findings and the framework appendix.
Technical Security Report sample, slide 3: Environment overview (fictional company, illustrative data)
Page 3 of 16Environment overview Licensing and counts of users, administrators, mailboxes, applications, policies, devices and Azure resources in the reviewed tenant.
Technical Security Report sample, slide 4: Summary of results (fictional company, illustrative data)
Page 4 of 16Summary of results 93 findings by severity (13 Critical, 30 High, 35 Medium, 15 Low), baseline control results and findings by area.
Technical Security Report sample, slide 5: Findings index (fictional company, illustrative data)
Page 5 of 16Findings index Baseline score by area and the start of the index that lists every finding with its area, severity and linked risk.
Technical Security Report sample, slide 6: Privileged access (fictional company, illustrative data)
Page 6 of 16Privileged access Who holds administrator roles, when each account was created and its MFA status, including an external guest and an application identity.
Technical Security Report sample, slide 7: Authentication and sign-in activity (fictional company, illustrative data)
Page 7 of 16Authentication and sign-in activity MFA registration, Conditional Access policy states and a daily sign-in chart in which the password attack stands out.
Technical Security Report sample, slide 8: Sign-in sources and security events (fictional company, illustrative data)
Page 8 of 16Sign-in sources and security events Addresses linked to suspicious activity, and the security-relevant events of the review period grouped by type.
Technical Security Report sample, slide 9: Email authentication and applications (fictional company, illustrative data)
Page 9 of 16Email authentication and applications SPF, DKIM, DMARC and MTA-STS status, and the connected applications that need immediate verification.
Technical Security Report sample, slide 10: Finding card: administrator without MFA (fictional company, illustrative data)
Page 10 of 16Finding card: administrator without MFA Each finding is a card with observation, business impact, recommendation, validation step, framework mapping, owner and target date.
Technical Security Report sample, slide 11: Finding: hidden inbox rule (fictional company, illustrative data)
Page 11 of 16Finding: hidden inbox rule An inbox rule named "." forwards invoice and payment mail to an outside address, marks it read and deletes it.
Technical Security Report sample, slide 12: Finding: content search for invoices (fictional company, illustrative data)
Page 12 of 16Finding: content search for invoices A content search for "invoice OR wire" matched 540 items; content searches can read mail across the tenant.
Technical Security Report sample, slide 13: Finding: bulk file download (fictional company, illustrative data)
Page 13 of 16Finding: bulk file download A document was downloaded on five days with a bulk synchronization client from one internet address.
Technical Security Report sample, slide 14: Finding: password attack with a successful sign-in (fictional company, illustrative data)
Page 14 of 16Finding: password attack with a successful sign-in 40 failed IMAP sign-ins against eight accounts from one address, which also completed one successful sign-in.
Technical Security Report sample, slide 15: Controls meeting the benchmark (fictional company, illustrative data)
Page 15 of 16Controls meeting the benchmark The 10 of 36 baseline controls already met, listed so they stay in place while remediation proceeds.
Technical Security Report sample, slide 16: Appendix: framework reference (fictional company, illustrative data)
Page 16 of 16Appendix: framework reference Findings mapped to NIST CSF 2.0, ISO/IEC 27001:2022 Annex A and the SOC 2 Trust Services Criteria.

Click or tap the page to open it full size and zoom in

Page 1 of 16Cover

Technical Security Report: detailed findings, evidence and remediation guidance.

EXH-C

Risk Register

PDF · 16 pages

Findings consolidated into business risks, each scored by likelihood and impact, with an owner, a target date and a target rating, and a trace back to every finding.

Who uses itLeadership, risk owners, insurer conversations
What is included
  • Risk scoring method
  • Risk profile today and after treatment
  • Risk summary table
  • Detail page per risk
  • Owner and target date
  • Finding-to-risk traceability
Sample Risk Register · fictional company1 / 7
Risk Register sample, slide 1: Cover (fictional company, illustrative data)
Page 1 of 7Cover Risk Register: business risks, scoring, ownership and treatment.
Risk Register sample, slide 2: Risk scoring method (fictional company, illustrative data)
Page 2 of 7Risk scoring method Each risk is scored as likelihood times impact on a 1 to 5 scale, with plain definitions for every level.
Risk Register sample, slide 3: Risk profile (fictional company, illustrative data)
Page 3 of 7Risk profile 16 business risks (8 Critical, 4 High, 4 Medium), with their positions today and after the recommended treatment.
Risk Register sample, slide 4: Risk summary table (fictional company, illustrative data)
Page 4 of 7Risk summary table Every risk with likelihood, impact, score, rating, owner, target date, target rating and status.
Risk Register sample, slide 5: Risk detail: account takeover (fictional company, illustrative data)
Page 5 of 7Risk detail: account takeover Risk R-01 with its statement, evidence, inherent and target scores and treatment.
Risk Register sample, slide 6: Risk detail: business email compromise (fictional company, illustrative data)
Page 6 of 7Risk detail: business email compromise Risk R-03: mail copied to outside parties through forwarding, a hidden inbox rule and a mail flow rule.
Risk Register sample, slide 7: Finding-to-risk traceability (fictional company, illustrative data)
Page 7 of 7Finding-to-risk traceability Every one of the 93 findings is linked to one risk, so each fix can be traced to the risk it reduces.

Click or tap the page to open it full size and zoom in

Page 1 of 7Cover

Risk Register: business risks, scoring, ownership and treatment.

EXH-D

Next Steps & Security Roadmap

PDF · 12 pages

A sequenced plan that starts with containment in the first seven days and moves through hardening to maturity over 180 days, grouped into projects with owners and a governance rhythm.

Who uses itIT leadership, project owners
What is included
  • Where you are and 30/180-day goals
  • Four phases from Contain to Mature
  • Numbered actions linked to risks
  • Six recommended projects
  • Expected outcome after remediation
  • Future goals for 6 to 18 months
  • Governance and meeting rhythm
Sample Next Steps & Security Roadmap · fictional company1 / 8
Next Steps & Security Roadmap sample, slide 1: Cover (fictional company, illustrative data)
Page 1 of 8Cover Next Steps & Security Roadmap: sequenced actions, projects and goals for the next 180 days.
Next Steps & Security Roadmap sample, slide 2: Where you are and where you should be (fictional company, illustrative data)
Page 2 of 8Where you are and where you should be Key measures today with 30-day and 180-day goals, such as administrators with confirmed MFA.
Next Steps & Security Roadmap sample, slide 3: Roadmap phases (fictional company, illustrative data)
Page 3 of 8Roadmap phases Four phases matched to risk rating, starting with Phase 0: Contain, in days 0 to 7.
Next Steps & Security Roadmap sample, slide 4: Action list (fictional company, illustrative data)
Page 4 of 8Action list Numbered actions with area and linked risk, such as reviewing a restricted mailbox and removing anonymous links.
Next Steps & Security Roadmap sample, slide 5: Recommended security projects (fictional company, illustrative data)
Page 5 of 8Recommended security projects Six projects in priority order, starting with incident containment and investigation.
Next Steps & Security Roadmap sample, slide 6: Expected outcome (fictional company, illustrative data)
Page 6 of 8Expected outcome Risk scores today and after remediation; completing the roadmap is expected to move the Critical risks to Medium or Low.
Next Steps & Security Roadmap sample, slide 7: Future goals (6 to 18 months) (fictional company, illustrative data)
Page 7 of 8Future goals (6 to 18 months) Longer-term goals such as passwordless administrators, device-based access, sensitivity labels and access reviews.
Next Steps & Security Roadmap sample, slide 8: Governance and operating rhythm (fictional company, illustrative data)
Page 8 of 8Governance and operating rhythm Who meets, how often and why, from weekly incident reviews to monthly risk register reviews.

Click or tap the page to open it full size and zoom in

Page 1 of 8Cover

Next Steps & Security Roadmap: sequenced actions, projects and goals for the next 180 days.

EXH-E

Technical Findings Workbook

Excel · 24 sheets

The working file behind the reports: every finding, risk and action in sortable sheets, plus the evidence tables for sign-ins, mail rules, applications, file sharing and the security timeline.

Who uses itIT team, MSP, auditors
What is included
  • Summary and findings sheets
  • Risk register with live scoring
  • Remediation tracker
  • Sign-ins and risk detections
  • Mail forwarding and inbox rules
  • App consent and file sharing
  • Security timeline in date order
  • Baseline controls and results
Sample Technical Findings Workbook · fictional company1 / 10
Technical Findings Workbook sample, slide 1: Summary sheet (fictional company, illustrative data)
Page 1 of 10Summary sheet Findings by severity and by area, with the scope and review period of the assessment.
Technical Findings Workbook sample, slide 2: Findings sheet (fictional company, illustrative data)
Page 2 of 10Findings sheet Every finding with area, severity, observation, business impact and recommendation; yellow columns are for your team's input.
Technical Findings Workbook sample, slide 3: Risk Register sheet (fictional company, illustrative data)
Page 3 of 10Risk Register sheet The 16 risks with risk statement, linked findings and owner; likelihood and impact are inputs and the score is calculated.
Technical Findings Workbook sample, slide 4: Remediation Plan sheet (fictional company, illustrative data)
Page 4 of 10Remediation Plan sheet Every roadmap action by phase, with columns to track status, owner, due date and percent complete.
Technical Findings Workbook sample, slide 5: Identity evidence sheets (fictional company, illustrative data)
Page 5 of 10Identity evidence sheets Privileged Access, Risk Detections and Conditional Access sheets: administrator accounts, flagged sign-ins and policy states.
Technical Findings Workbook sample, slide 6: Sign-ins sheet (fictional company, illustrative data)
Page 6 of 10Sign-ins sheet Each sign-in in the review period with account, application, address, country, result, client, authentication and risk level.
Technical Findings Workbook sample, slide 7: Security Timeline sheet (fictional company, illustrative data)
Page 7 of 10Security Timeline sheet Security-relevant events in date order, the base for the incident timeline.
Technical Findings Workbook sample, slide 8: Mailbox evidence sheets (fictional company, illustrative data)
Page 8 of 10Mailbox evidence sheets Mail Forwarding and Inbox Rules sheets: where mail is sent outside and which rules hide it.
Technical Findings Workbook sample, slide 9: Applications and file sharing sheets (fictional company, illustrative data)
Page 9 of 10Applications and file sharing sheets App Consent Grants and File Sharing sheets: delegated permissions and external sharing events.
Technical Findings Workbook sample, slide 10: Baseline Controls sheet (fictional company, illustrative data)
Page 10 of 10Baseline Controls sheet Each baseline control with its result (met, partial or not met) and observation.

Click or tap the page to open it full size and zoom in

Page 1 of 10Summary sheet

Findings by severity and by area, with the scope and review period of the assessment.

How they fit together

One set of facts, five ways to use it

EXH-A

Decide

Leadership reads the executive report and makes the decisions it asks for.

EXH-B

Verify

IT checks each finding card against the records and confirms what is still active.

EXH-C

Prioritize

The risk register turns findings into owned business risks with target dates.

EXH-D

Act

The roadmap starts with seven days of containment, then hardening.

EXH-E

Track

The workbook tracks status, owners and evidence until every action is closed.

What an assessment can answer

  • What the available records show about sign-ins, role changes, mail rules, applications and sharing in the review period
  • Which settings allowed the activity and how they compare with a security baseline
  • Which business risks follow from the findings and what to fix first
  • Which records were missing or expired, so gaps are stated rather than guessed

What no one can promise

  • That every unauthorized action was found, when records are limited or expired
  • Who was behind the activity, or where they are
  • Recovery of data, mail or funds
  • Legal conclusions, breach-notification decisions or insurance outcomes, which belong to your counsel and insurer
Business leaders and advisers meeting around a table to discuss a security incident
Who reads the reports

Written to be shared with the people who decide

A suspected compromise involves more people than IT. The reports are structured so each reader finds their part quickly.

  • Leadership uses the executive report and the decisions page.
  • IT and your MSP work from the technical report and the workbook.
  • Legal counsel can use the timeline and findings as technical input to their own assessment.
  • Your insurer may ask for the risk register and the remediation plan.
When legal matters are involved, we recommend engaging your counsel first and working at their direction. We provide technical findings, not legal advice.
Ali Hassani, CISO, OC Security Audit
CISO-led

Prepared under the direction of Ali Hassani, CISO

Certified CISO (C|CISO) and CISSP with 25+ years in IT and cybersecurity and dozens of Microsoft certifications. Every engagement is scoped in writing, uses read-only access and is reported in language both leadership and IT can act on.

We work with businesses in Irvine, across Orange County and Los Angeles County, and remotely nationwide.

FAQ

Microsoft 365 compromise assessment questions

Is this a real customer report?

No. Contoso Ltd is a fictional organization. Every name, account, address, internet address and figure in the sample reports is invented for illustration and does not describe any real customer. We never publish client data.

What does a Microsoft 365 compromise assessment review?

It reviews the records and settings available in your Microsoft 365, Entra ID and Azure environment for signs of unauthorized activity and for the weaknesses that allowed it: administrator accounts and role changes, sign-ins and risk detections, mailbox forwarding and inbox rules, mail flow rules, connected applications and consents, file sharing, devices and the Azure subscription.

Which deliverables do we receive?

Five: an Executive Security Report, a Technical Security Report with one card per finding, a Risk Register, a Next Steps and Security Roadmap, and a Technical Findings Workbook in Excel. The exact content follows the scope agreed in writing for your engagement.

How far back can the review look?

It depends on your licenses and settings at the time of the activity. Microsoft documents that Entra ID sign-in and audit logs are kept for 7 days on Entra ID Free and 30 days on P1 or P2, that Audit (Standard) records are kept for 180 days, and that the Azure Activity log is kept for 90 days unless it is exported. Records that have already expired cannot be reviewed, so contacting us early matters.

Can the assessment tell us who attacked us or recover lost money?

No. The assessment describes what the available records show. It does not identify or attribute attackers, recover data or funds, or confirm that every unauthorized action was found. For payment fraud, contact your bank and law enforcement directly.

Do you change anything in our tenant?

The review uses read-only access. Containment and remediation steps are written as recommendations for your team or IT provider. If you want hands-on help, our implementation partner IT Perfection can carry out changes under a separate written agreement.

Does this replace legal counsel, breach notification advice or our insurer?

No. OC Security Audit provides technical cybersecurity assessment and reporting. Legal, breach-notification, regulatory and insurance decisions belong to your legal counsel and insurer, and we can work alongside them when you ask us to.

How much does an investigation cost?

Microsoft 365 and Azure compromise investigations start at $3,500. The final scope and price depend on the size of the environment and the questions to answer, and are confirmed in writing before any work begins.

Log retention figures are from Microsoft documentation: Microsoft Entra data retention, Purview audit log retention and Azure Monitor activity log (Microsoft Learn, checked November 15, 2026). Retention can change; your licenses and settings decide what is available.

Important notes
  • This page and the sample reports are for illustration only. Contoso Ltd and all data in the samples are fictional.
  • OC Security Audit provides technical cybersecurity assessment, advisory and reporting services. We are not a law firm and do not provide legal advice, and we are not a private investigation agency.
  • An assessment reviews the records and settings available at the time of the review. Log retention, licensing and configuration limit what can be reconstructed, so no assessment can guarantee that every unauthorized action has been identified.
  • We do not identify or attribute attackers, recover data or funds, or make breach-notification, regulatory or insurance determinations. Those decisions belong to you, your legal counsel and your insurer.
  • Our reports are technical observations, not legal conclusions, and we make no representation that they are suitable as evidence in any legal proceeding.
  • Scope, timing, price and deliverables are confirmed in a written agreement before any work begins. Investigations start at $3,500.
Implementation partner

From findings to fixes

OC Security Audit stays independent and read-only. If you want hands-on containment or remediation, IT Perfection can implement the changes under a separate agreement.

Visit IT Perfection
Two engineers reviewing systems on laptops in a data center

Seeing signs of compromise in Microsoft 365?

Avoid deleting accounts, mailboxes or devices before the records are reviewed. Call 949-777-5567 or schedule a consultation, and we will discuss scope and timing with you.

Compromise investigations start at $3,500 · Headquarters in Irvine, California · Remote nationwide · Microsoft 365 and Azure compromise investigation