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.

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
Click the centre page to open it full size, then use Zoom in to read every line.
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)
Click the centre page to open it full size, then use Zoom in to read every line.
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
Click the centre page to open it full size, then use Zoom in to read every line.
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
Click the centre page to open it full size, then use Zoom in to read every line.
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
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.
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.
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.
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.
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.
| Area | Controls | Findings | Sample score | Examples of what is checked |
|---|---|---|---|---|
| Governance and management | 9 | 8 | Management groups, Azure Policy, RBAC, locks, regions, tagging, ownership | |
| Identity and access (Entra ID) | 12 | 10 | MFA, PIM, Conditional Access, guests, emergency accounts, service principals | |
| Network security | 10 | 8 | NSGs, Azure Firewall, private endpoints, DDoS, Bastion, segmentation, WAF | |
| Compute and VM security | 10 | 8 | Patching, EDR, vulnerability assessment, disk encryption, App Service | |
| Storage and data protection | 10 | 8 | Anonymous access, TLS, shared keys, Key Vault, Azure SQL, soft delete | |
| Logging and monitoring | 8 | 7 | Diagnostic settings, Sentinel, alerts, retention, flow logs, sign-in logs | |
| Security posture management | 6 | 4 | Defender for Cloud plans, secure score, compliance standards | |
| Backup, DR and resilience | 8 | 6 | Backup policies, Site Recovery, restore tests, vault protection |
Next steps
Related pages

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
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
Sample report packs for our other audits, including Microsoft 365, Entra ID, Intune, firewalls, HIPAA and PCI DSS.
Browse sample reports
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.

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.


