Preparation decides how useful the audit is
A security audit compares what your controls should do with what they actually do, using evidence. When the objective, scope and evidence are clear before fieldwork starts, the audit takes less of your team’s time and the findings are easier to act on.
These ten steps apply to an internal security audit, a cyber insurance review or a compliance assessment such as HIPAA or PCI DSS. They are the same steps we ask clients to take before an OC Security Audit engagement.

Ten steps to prepare
Name a sponsor and get written authorization
Choose one senior person who owns the audit, approves its scope and receives the report. Put the authorization in writing, including what the auditor may and may not access.
Agree the objective
Write one sentence on why the audit is happening: an insurance renewal, a board request, a new compliance obligation, an acquisition or a change of IT provider. The objective decides how deep the audit goes.
Define the scope
List the sites, systems, cloud services, data and time period in scope, and anything excluded. A clear exclusion is better than an assumed one.
Choose the criteria
Pick what the controls will be measured against: your own policies, NIST CSF 2.0, CIS Controls v8, the HIPAA Security Rule or PCI DSS. Use one main framework and map the others to it.
Gather the core documents
Security policies, a network diagram, an asset inventory, a list of systems that hold sensitive data, the incident response plan, and contracts with key IT and cloud providers.
Collect evidence that controls run
Records from the audit period, not just settings: access reviews, leaver account reports, patch reports, backup restore tests, training completion and incident tickets. Note who produced each record and when.
Assign a control owner for each area
One named person for identity, endpoints, network, backups and policies, who can answer questions and provide evidence within a few days.
Prepare read-only access
Create audit accounts with read-only rights for the auditor, and never share an administrator password. Remove the accounts when the audit ends.
Tell the people who need to know
Let your IT provider, help desk and the staff being interviewed know the dates, so a new sign-in or an evidence request is not mistaken for an attack.
Plan for the findings
Set aside time and some budget for remediation, and agree who can accept a risk that will not be fixed. An audit is only useful if its findings are acted on.
What slows an audit down
Screenshots instead of records
A screenshot of a setting shows it today. An auditor also needs proof it worked during the period, such as reports or logs.
No list of who left
Without an HR list of leavers for the period, the auditor cannot test whether accounts were disabled on time.
Backups never restored
Backup job reports show copies were made. Only a restore test shows the business can recover.
Scope that grows mid-audit
Adding a site or system halfway through delays the report. Agree the scope first and audit additions separately.
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.

Led by Ali Hassani, CISO
Ali Hassani has prepared organizations for security audits, insurance reviews and compliance assessments for more than 25 years. If you would rather have the audit run for you, that is the fixed-price internal security audit.
- Certified CISO (C|CISO) and CISSP
- 25+ years in IT, networking and cybersecurity
- Microsoft and Cisco certifications, including CCNP, CCNA, MCSE, MCITP and MCSA Security
- Headquarters in Irvine; on-site across Southern California; remote audits nationwide
Questions about preparing
How long does preparation take?
It depends on how organized your records are. Most of the time goes into steps 5 and 6, gathering documents and evidence.
Do we need a framework to be audited?
No, but it helps. Your own policies can be the criteria. A framework such as NIST CSF 2.0 or CIS Controls v8 makes the results easier to compare and to share with insurers.
Should we fix things before the audit?
Fix anything you already know is urgent. Otherwise, let the audit show where you stand, so the roadmap reflects real risk rather than last-minute changes.

Ready for an independent audit?
Schedule a consultation. The internal security audit is a fixed $3,500 for the scope agreed in writing.
Read-only audit. Fixed price $3,500. Irvine, Orange County and Southern California on-site; remote nationwide.


