Five deliverables
Word and PDF reports, plus Excel files your team can track to closure. Findings map to NIST CSF 2.0 and CIS Controls v8, and to HIPAA or PCI DSS where they apply.
| Deliverable | What it contains | Who uses it |
|---|---|---|
| Executive report | Overall rating, top risks and business impact in plain language | Owners, leadership and the board |
| Technical findings report | Each finding with condition, criteria, cause, consequence, evidence and the fix | IT team or IT provider |
| Risk register | Findings rolled up into business risks, each with an owner and a date | Management, auditors and insurers |
| 30/60/90-day roadmap | The order to fix things, by risk and effort | Whoever owns remediation |
| Evidence and workpaper index (Excel) | Each test with population, sample, evidence reference, result and reviewer | Internal audit and compliance |
A fictional distributor with two sites
Every number on this page comes from a made-up company and shows the format only. Your report uses the evidence from your own systems.
- Company
- Northgate Supply Co. (fictional company), wholesale distributor, 2 sites, 120 employees
- Objective
- Leadership asked for an independent view of security controls before a cyber insurance renewal
- Scope
- Active Directory and Microsoft 365 accounts, 140 laptops and desktops, 12 servers, one firewall and VPN, backups, and security policies
- Criteria
- NIST CSF 2.0 and CIS Controls v8, plus the company’s own written policies
- Period
- Controls tested for the 6 months before fieldwork

Ratings by area
Weighted pass share of the tests: Critical 10, High 6, Medium 3, Low 1; an exception counts half. Below 50 critical exposure, 50 to 70 needs improvement, 70 to 85 fair, 85 and above good.
| Area | Score | Band | |
|---|---|---|---|
| Identity & access | 44 | Critical exposure | |
| Endpoint & server risk | 58 | Needs improvement | |
| Network & monitoring | 52 | Needs improvement | |
| Backup resilience | 49 | Critical exposure | |
| Compliance evidence & governance | 66 | Needs improvement | |
| Security awareness & incident readiness | 71 | Fair |
Sample findings
- Condition
- 9 of 25 sampled accounts of people who left the company were still enabled 30 or more days after their last day.
- Criteria
- Company access policy: disable accounts on the last working day. CIS Controls v8, Safeguard 6.2 (access revoking process).
- Cause
- HR sends leaver notices by email to one IT person; there is no ticket and no backup when that person is out.
- Consequence
- Former staff, or anyone with their password, can still sign in to email and files.
- Evidence
- Population: 61 leavers in the period (HR list). Sample: 25, random. Account status from Active Directory and Microsoft 365 exports, reference E-07.
- Fix
- Create a leaver ticket from HR that IT must close on the last day; review all enabled accounts against the HR list now. Owner: IT manager. Target: 30 days.
- Condition
- Backups complete every night, but no restore of a full server has been tested in the period.
- Criteria
- NIST CSF 2.0, PR.DS-11: backups are created, protected, maintained and tested. Company backup policy: quarterly restore test.
- Cause
- Restore testing is not on anyone’s calendar and has no owner.
- Consequence
- After ransomware, recovery time is unknown and may exceed what the business can tolerate.
- Evidence
- Backup job reports for 6 months, reference E-14; interview with the IT provider, reference I-03.
- Fix
- Restore one critical server to an isolated network within 30 days and record the time taken; then test quarterly. Owner: IT provider.
- Condition
- Firewall and server logs are kept for 7 days and no one is alerted to failed administrator sign-ins.
- Criteria
- CIS Controls v8, Safeguards 8.9 and 8.10 (centralize and retain audit logs).
- Cause
- Logging was left at default settings when the firewall was installed.
- Consequence
- An intrusion found after a week cannot be traced.
- Evidence
- Firewall log settings export, reference E-19.
- Fix
- Send logs to a central log service with at least 90 days’ retention and alerts for administrator sign-in failures. Owner: IT manager. Target: 90 days.
Findings rolled up into business risks
Score = likelihood × impact, each from 1 to 5. Each risk has an owner and a target date.
| Risk | Linked findings | Score | Owner |
|---|---|---|---|
| Slow or failed recovery after ransomware | BR-01, BR-02, ES-05 | 20 | Operations director |
| Unauthorized access through old or shared accounts | IA-01, IA-03, IA-06 | 16 | IT manager |
| Unpatched servers exploited from the network | ES-02, ES-03, NM-02 | 15 | IT provider |
| Intrusion not detected or traced | NM-04, NM-05 | 12 | IT manager |
| Insurer questionnaire answers not supported by evidence | CE-02, CE-04 | 9 | Controller |
The 30/60/90-day roadmap
The order follows each risk score and how much effort the fix takes.
| Window | Actions | Findings closed |
|---|---|---|
| First 30 days | Disable leaver accounts and start the HR ticket; remove shared admin accounts; restore-test one critical server | IA-01, IA-03, BR-02 |
| 60 days | Patch the three servers behind schedule; turn on MFA for every remote sign-in; document backup scope | ES-02, ES-03, IA-06, BR-01 |
| 90 days | Central logging with alerts; update the incident response plan and run a tabletop exercise | NM-04, NM-05, CE-04 |
| After 90 days | Quarterly access reviews; a retest of closed findings; yearly re-audit | CE-02 and ongoing |
Related pages
Internal Security Audit
The service, the six areas we review, the method and the 200-item checklist.
Open →How to conduct an internal security audit
The twelve stages from authorization to verified closure.
Open →Plan a safe, authorized audit
Sponsor, authority, objectives, safety limits and scope.
Open →Collect and protect audit evidence
Evidence requests, provenance and handling sensitive exports.
Open →Test control effectiveness
Design, implementation and operating effectiveness, with examples.
Open →Create defensible workpapers
Workpapers a reviewer can follow and reproduce.
Open →All sample companies, systems and findings shown on this page are fictional and used for illustration only. An internal security audit by OC Security Audit is an independent cybersecurity assessment; it is not a financial statement audit and does not replace legal advice.
Questions about the report
Is the sample based on a real client?
No. Northgate Supply Co. is fictional and every number is made up to show the format. We never publish client information.
Can we give the report to our insurer, auditor or board?
Yes. The executive report and risk register are written for that purpose. The technical findings report and workpaper index are for your IT and audit teams.
Does the report include a retest?
The roadmap recommends when to retest. A retest is scheduled and quoted when your team is ready.

Get this report for your own organization
Schedule a consultation. The internal security audit is a fixed $3,500 for the scope agreed at the scoping call.
Read-only audit. Fixed price $3,500. Irvine, Orange County and Southern California on-site; remote nationwide.


