IT director reviewing an Azure security audit in his office

Azure Security Audit · sample report

Azure Security Audit Sample Report

See the five deliverables from a Microsoft Azure security audit, page by page: executive report, technical report, risk register, roadmap and Excel findings workbook for a fictional company.

25+ yearsIT and cybersecurity experience
Read-only auditNo changes to your Azure environment
$3,500 fixedScope confirmed in writing first
Southern California and nationwideBased in Irvine, remote anywhere

Our deliverables

Five deliverables from one Azure security audit

This Azure security audit sample report shows exactly what you receive when OC Security Audit reviews your Microsoft Azure environment. Every page below comes from a complete sample pack we built for a fictional engineering firm with four Azure subscriptions, 38 virtual machines and a customer portal.

An Azure audit is only useful if the results reach the right people in a form they can act on. That is why the same evidence is written five ways: a short executive report for leadership, a detailed technical report for engineers, a risk register for risk owners, a 180-day roadmap for planning, and an Excel workbook for tracking the work week by week. All five use the same finding and risk references, so a single issue can be followed from the boardroom summary to the line in the workbook.

The sample assesses 73 controls across eight areas (governance, identity, network, compute, storage and data, logging, posture management, and backup and recovery) against the CIS Microsoft Azure Foundations Benchmark and the Microsoft cloud security benchmark, together with the Microsoft Defender for Cloud secure score.

Sample notice. Contoso Engineering Group (fictional sample) is a fictional company. Every name, account, IP address and number in these reports is invented for illustration. We never publish client data.

Two engineers in a server aisle reviewing Azure audit results on a tablet
73controls assessed
59findings, each with a fix and a test
17business risks with owners
31roadmap actions in 4 phases
48%Defender for Cloud secure score
33.4configuration score out of 100
D1

Executive Security Report

PDF and Word, 10 pages

A short, plain-English report for the owner, the board and the leadership team. It turns 59 technical findings into 17 business risks, explains how an attacker could chain them, and asks leadership for seven specific decisions.

Who uses it: Owners, executives, board members and anyone who approves budget or accepts risk.

What is included

  • Configuration security score and rating
  • Four headline tiles and a bottom line
  • Eight key numbers leadership can track
  • Top business risks in plain language
  • Attack chain from internet to ransomware
  • Posture score for each of 8 areas
  • What is working well
  • Top 10 actions and decisions requested
Sample pages · fictional company, illustrative data1 / 8
Slide 1 of 8CoverExecutive Security Report cover with the author block, the report date and the sample notice for the fictional company.
Slide 2 of 8Executive summaryA two-paragraph summary, the configuration security score of 33.4 out of 100 (Poor), four headline tiles, the bottom line for leadership and eight key numbers.
Slide 3 of 8Top business risksThe four Critical risks in business language: ransomware entry through exposed remote access, public client files, ERP data reachable from the internet and standing administrator accounts.
Slide 4 of 8How an attacker could chain the weaknessesFive confirmed weaknesses linked into one path, from exposed remote desktop to ransomware and data leak, followed by the ten High risks.
Slide 5 of 8Security posture by areaWeighted scores for the eight areas against a target of 85, with a one-line assessment of each area.
Slide 6 of 8What is working wellTen strengths to build on, including the hub firewall, strong VPN cryptography, private endpoints and encryption at rest.
Slide 7 of 8Priority recommendationsThe first ten actions with the risk each one reduces and its timeframe, plus the 180-day roadmap chart.
Slide 8 of 8Decisions requested from leadershipSeven decisions for leadership, from approving the containment changes this week to agreeing recovery objectives for ERP and the customer portal.

Click the centre page to open it full size, then use Zoom in to read every line.

D2

Technical Security Report

PDF and Word, 74 pages

The working document for IT and security teams. Every finding has its own card with the observation, business impact, recommendation, affected objects, a validation test, framework mapping and an owner and target date.

Who uses it: IT managers, cloud and security engineers, your managed service provider and auditors who need the evidence.

What is included

  • Paginated contents page
  • Scope, approach and result definitions
  • Environment overview with counts
  • Control results and findings index
  • Secure score by control and subscription
  • Identity, VM, storage and logging evidence tables
  • 59 finding cards grouped by area
  • Framework appendix (NIST CSF, ISO 27001, SOC 2, MCSB)
Sample pages · fictional company, illustrative data1 / 16
Slide 1 of 16CoverTechnical Security Report cover for IT and security teams, with the sample notice.
Slide 2 of 16ContentsContents page with page numbers for every section, from the introduction to the framework appendix.
Slide 3 of 16Introduction and scopePurpose, the scope table and the definitions used for Pass, Partial, Fail and Not applicable.
Slide 4 of 16Environment overviewThe size of the Azure estate in a chart and a table: 4 subscriptions, 412 resources, 38 virtual machines, 22 storage accounts and more.
Slide 5 of 16Control results73 controls assessed: 13 pass, 32 partly in place, 27 fail and 1 not applicable.
Slide 6 of 16Findings by severity and area59 findings by severity, findings stacked by area, and the weighted security score for each area.
Slide 7 of 16Findings indexEvery finding with its reference, control ID, severity and the business risk it belongs to.
Slide 8 of 16Defender for Cloud secure scoreSecure score of 26.5 of 55 points (48%) by security control, its four-month trend and the score for each subscription.
Slide 9 of 16Identity and privileged accessMFA registration across 312 staff accounts and the privileged accounts with their roles, assignment type and MFA method.
Slide 10 of 16Virtual machinesProtection coverage for 38 VMs (EDR, update assessment, backup, Trusted Launch) and the VMs with missing updates or exposed ports.
Slide 11 of 16Storage, databases and Key VaultA protection matrix for 22 storage accounts, followed by the Azure SQL server and Key Vault settings.
Slide 12 of 16Logging coverageDiagnostic settings coverage by resource type: 11 of 42 log-capable resources send logs.
Slide 13 of 16Finding card: exposed management portsA Critical finding with the observation, business impact, recommendation, affected objects, validation test, framework mapping, owner and target date.
Slide 14 of 16Finding card: public client filesThe Critical finding for a storage container readable by anyone, with containment steps and the test that proves the fix.
Slide 15 of 16Controls meeting the benchmarkThe controls that passed, with the evidence behind each result.
Slide 16 of 16Framework referenceEach finding mapped to NIST CSF 2.0, ISO/IEC 27001:2022, SOC 2, the Microsoft cloud security benchmark and PCI DSS 4.0.1.

Click the centre page to open it full size, then use Zoom in to read every line.

D3

Risk Register

PDF and Word, 19 pages, landscape

The findings consolidated into business risks you can own and track. Each risk is scored as likelihood times impact, has a named owner, a treatment, a target date that matches its rating, and a target score after treatment.

Who uses it: Leadership, risk owners, compliance staff, insurers and anyone preparing for a customer security review.

What is included

  • Scoring method and rating bands
  • Risk profile with inherent and residual heat maps
  • Summary table with owners and target dates
  • One card per risk with linked findings
  • Treatment and target after treatment
  • Finding-to-risk traceability
  • Risk reduction chart for the top 12 risks
  • Windows that match the roadmap
Sample pages · fictional company, illustrative data1 / 8
Slide 1 of 8CoverRisk Register cover in landscape format, with the sample notice.
Slide 2 of 8Risk scoring methodLikelihood and impact definitions on a 1-5 scale and the rating bands with the expected response for each.
Slide 3 of 8Risk profile17 business risks (4 Critical, 10 High, 3 Medium) and side-by-side heat maps of inherent and residual risk.
Slide 4 of 8Risk summaryEvery risk with likelihood, impact, score, rating, owner, target date and target rating.
Slide 5 of 8Risk detail: ransomware entryThe R-01 risk card: statement, scoring, linked findings, treatment, target after treatment and owner.
Slide 6 of 8Risk detail: administrator and account takeoverRisk cards for R-04 (standing administrator accounts) and R-05 (incomplete MFA and Conditional Access).
Slide 7 of 8Risk detail: lateral movement and web attacksRisk cards for R-11 (development peered with production) and R-12 (web attacks against the customer portal).
Slide 8 of 8Finding-to-risk traceabilityEvery finding mapped to the risks it supports, so nothing in the technical report is left without an owner.

Click the centre page to open it full size, then use Zoom in to read every line.

D4

Next Steps & Security Roadmap

PDF and Word, 15 pages

A 180-day plan in four phases that starts with containment in the first week. The 31 actions are grouped into nine projects with objectives, success measures, duration and effort, so the work can be scheduled and funded.

Who uses it: IT leadership, project managers, your managed service provider and the people who will do the work.

What is included

  • Today vs 30-day and 180-day targets
  • Roadmap chart with four phases
  • Action tables with risk and due date
  • Nine prioritized security projects
  • Project cards with success measures
  • Expected risk reduction
  • Future goals for 6 to 18 months
  • Operating rhythm and licensing check
Sample pages · fictional company, illustrative data1 / 8
Slide 1 of 8CoverNext Steps and Security Roadmap cover, with the sample notice.
Slide 2 of 8Where you are and where you should beThirteen measures with today's value and the 30-day and 180-day targets.
Slide 3 of 8180-day roadmapThe roadmap chart and the actions for Phase 0 (days 0-7) and Phase 1 (days 7-30).
Slide 4 of 8Recommended security projectsNine projects in priority order with objective, risks addressed, duration and effort.
Slide 5 of 8Project cardsCards for P1 Exposure Lockdown and P2 Privileged Access Modernization: objective, key activities, risks addressed and success measures.
Slide 6 of 8Expected outcomeRisk scores before and after remediation for the top 12 risks and the residual heat map.
Slide 7 of 8Future goalsGoals for the next 6 to 18 months and the recommended follow-on assessment.
Slide 8 of 8Governance and operating rhythmDaily to annual security activities with owners, a licensing check and how OC Security Audit can help.

Click the centre page to open it full size, then use Zoom in to read every line.

D5

Technical Findings Workbook

Excel, 33 sheets

The Excel workbook behind the reports, built on our Azure checklist. It holds every finding, risk and action with input columns for status and owners, live summary formulas, the inventories behind each finding and a Power BI ready export.

Who uses it: IT teams tracking remediation week by week, project managers and anyone who wants the raw evidence in a sortable format.

What is included

  • Summary with live counts and charts
  • Findings with status and owner inputs
  • Risk Register with calculated scores
  • Remediation Plan with percent complete
  • Secure score tracking by subscription
  • Eight checklist domain tabs
  • Inventories: users, roles, VMs, storage, SQL, Key Vault
  • PowerBI_Export sheet and dashboard guide
Sample pages · fictional company, illustrative data1 / 9
Slide 1 of 9Summary sheetPosture figures, live tables of findings by severity and risks by rating, roadmap progress and two charts.
Slide 2 of 9Executive ScorecardChecklist KPIs calculated from the domain tabs, including risk bands and the Defender for Cloud secure score.
Slide 3 of 9Findings sheetFindings with area, severity, owner, target date and linked risks; status, owner and due date are tracked in input columns.
Slide 4 of 9Risk Register sheetRisks with likelihood and impact inputs, calculated scores and ratings, target ratings, status and decision.
Slide 5 of 9Remediation Plan sheetEvery roadmap action with its phase, finding, risk, owner and due date, plus status and percent complete.
Slide 6 of 9Secure Score Tracking sheetSecure score points per subscription with previous values, calculated percentage and change.
Slide 7 of 9Checklist domain tab: Network SecurityOne of the eight checklist tabs: answer, impact, likelihood, calculated risk score and status for each control.
Slide 8 of 9Virtual Machines inventoryThe VM inventory behind the compute findings: operating system, internet exposure, EDR sensor, update assessment, missing updates and backup.
Slide 9 of 9Storage Accounts inventoryStorage settings behind the data findings: network access, private endpoints, anonymous access, TLS, secure transfer and key age.

Click the centre page to open it full size, then use Zoom in to read every line.

Want the same five deliverables for your Azure environment?

We confirm scope, read-only access and timing in writing before any work starts. The Azure Cloud Security Audit is a fixed fee of $3,500.

How the documents connect

Follow one finding from the report to the workbook

Every finding carries the same reference in all five documents. Here is how one issue from the sample, remote desktop open to the internet, travels through the pack.

F-01

Technical finding

Six network security group rules allow remote desktop, SSH or WinRM from any internet address to five VMs, including two Windows Server 2012 R2 servers.

The card lists the exact rules, the fix and the test that proves the ports are closed.

R-01

Business risk

Ransomware entry through internet-exposed remote access, scored 5 x 5 = 25 (Critical), with an owner and a target of 5 (Low) after treatment.

Linked findings show why the risk is so high: missing patches, open alerts and no secure admin path.

Phase 0

Roadmap action

Delete or restrict the six rules within 7 days, then deploy Azure Bastion and just-in-time access in Phase 1, all inside the 30-day window for Critical risks.

The action belongs to project P1, Exposure Lockdown.

Workbook

Tracking

The same action appears in the Remediation Plan sheet with an owner, due date, status and percent complete, and the VM and NSG inventories list every object involved.

Summary tables update as items are closed.

What the sample covers

Eight Azure security areas in the sample audit

The table shows how the 73 controls in the sample are spread across the eight areas, how many findings each area produced and the area score out of 100. Your own audit follows the same structure, scored on your environment.

AreaControlsFindingsSample scoreExamples of what is checked
Governance and management98
32 / 100
Management groups, Azure Policy, RBAC, locks, regions, tagging, ownership
Identity and access (Entra ID)1210
31 / 100
MFA, PIM, Conditional Access, guests, emergency accounts, service principals
Network security108
31 / 100
NSGs, Azure Firewall, private endpoints, DDoS, Bastion, segmentation, WAF
Compute and VM security108
44 / 100
Patching, EDR, vulnerability assessment, disk encryption, App Service
Storage and data protection108
31 / 100
Anonymous access, TLS, shared keys, Key Vault, Azure SQL, soft delete
Logging and monitoring87
33 / 100
Diagnostic settings, Sentinel, alerts, retention, flow logs, sign-in logs
Security posture management64
44 / 100
Defender for Cloud plans, secure score, compliance standards
Backup, DR and resilience86
29 / 100
Backup policies, Site Recovery, restore tests, vault protection

Next steps

Related pages

Azure Cloud Security Audit

Azure Cloud Security Audit

The service page: what we review across identity, subscriptions, network, data, logging and recovery, and how the read-only engagement runs.

See the Azure audit
Azure audit pricing

Azure audit pricing

One fixed fee of $3,500 for the read-only Azure Cloud Security Audit, with scope, access and timing confirmed in writing first.

See pricing
All sample reports

All sample reports

Sample report packs for our other audits, including Microsoft 365, Entra ID, Intune, firewalls, HIPAA and PCI DSS.

Browse sample reports
Ali Hassani, CISO, CISSP, President of OC Security Audit

Who leads the audit

Ali Hassani, CISO, CISSP

Ali Hassani is President of OC Security Audit and brings more than 25 years of experience in information security, cybersecurity leadership and security assessment. He leads every Azure audit personally, from the scoping call to the readout with your leadership team.

The reports are written for the people who have to act on them: leadership gets decisions and business risk, engineers get exact settings and validation tests, and risk owners get a register they can maintain after the engagement ends.

Questions

Azure sample report FAQ

Is Contoso Engineering Group a real client?

No. Contoso Engineering Group is a fictional organization. Every name, account, address and number in these sample reports was invented for illustration. We never publish anything from a real client engagement, not even with names removed.

What do we receive from an Azure security audit?

Five deliverables: an Executive Security Report, a Technical Security Report, a Risk Register, a Next Steps and Security Roadmap, and a Technical Findings Workbook in Excel. The reports come as editable Word files and as PDFs. The sample on this page shows the format and depth of each one.

Does the audit change anything in our Azure environment?

No. The Azure Cloud Security Audit is read-only. We review configuration, Microsoft Defender for Cloud results and documentation, and we interview your team. Any change is made later by your staff or your provider, following the roadmap.

How much does the Azure audit cost?

The Azure Cloud Security Audit is a fixed fee of $3,500. Scope, access and timing are confirmed in writing before any work starts. See the Azure audit pricing page for what the fee covers.

Which benchmarks and frameworks do you use?

Controls are assessed against the CIS Microsoft Azure Foundations Benchmark and the Microsoft cloud security benchmark, and we review the Defender for Cloud secure score. Findings are mapped to NIST CSF 2.0, ISO/IEC 27001:2022 and SOC 2. Mappings help with audits and questionnaires; they do not certify compliance with any framework.

Can we track remediation in Power BI?

Yes. The workbook includes a PowerBI_Export sheet with one row per control and a short guide with the measures and visuals to build, so you can follow progress and secure score over time.

Do you work with organizations outside Orange County?

Yes. OC Security Audit is based in Irvine, works on site across Southern California and runs Azure audits remotely for organizations nationwide.

Security engineers reviewing servers in a data center

Ready when you are

Get an Azure security audit for your own subscriptions

A read-only review, a fixed fee of $3,500, and five deliverables your leadership and your engineers can both use. On site across Southern California and remote nationwide.