Professional seated at her desk in a bright office
How-to guide

How to Prepare for a Security Audit

Ten steps that make any security audit faster, cheaper and more useful, whether it is internal, for an insurer or for a compliance framework.

Analyst reviewing security dashboards on a large monitor
Evidence

Most delays come from missing evidence

Audits slow down when records are scattered or no one owns a control. Preparing the list first saves weeks.

Security consultant with a laptop beside a server rack
Ready?

Let a CISO run it for you

The internal security audit is a fixed $3,500 for the scope agreed in writing.

25+ yearsIT & cybersecurity experience
Certified expertsCISSP · C|CISO · Microsoft · Cisco
Southern CaliforniaLocal and on-site, based in Irvine
NationwideRemote audits & advisory
Before the auditor arrives

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.

IT team members reviewing laptops in a server room
The steps

Ten steps to prepare

01

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.

02

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.

03

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.

04

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.

05

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.

06

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.

07

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.

08

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.

09

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.

10

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.

Common mistakes

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.

Ali Hassani, CISO and founder of OC Security Audit
Who does the work

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

About Ali Hassani

FAQ

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.

Team of professionals reviewing documents together

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.