The first audit is the hardest one. Not because the controls are complicated, but because the vocabulary is unfamiliar, the timeline is unclear, and nobody on the team has done it before. Founders often discover they need a SOC 2 report or an ISO/IEC 27001 certificate only when a large customer asks for one in the middle of a deal.
This guide explains what these audits are, how the journey works from start to finish, and where first-timers lose time. It is written for founders and early leaders who need a plain-English map before they hire an auditor or commit budget.
Know what you are actually getting
The two most requested frameworks are different kinds of things, and the terms matter when you talk to customers.
- SOC 2 is an attestation report issued by an independent CPA firm. It covers controls relevant to the Trust Services Criteria: security (always included), and optionally availability, confidentiality, processing integrity and privacy. It is an attestation report, and the term "certification" does not apply to it.
- ISO/IEC 27001 is a certification. An accredited certification body audits your information security management system (ISMS) against the standard and, if it passes, issues a certificate that is typically valid for three years with surveillance audits in between.
Choose based on who is asking. US business customers most often ask for SOC 2. International buyers and some large enterprises often prefer ISO/IEC 27001. Some ask for both. Ask your top prospects which they will accept before you pick one.
Type 1 and Type 2, explained
SOC 2 reports come in two types. A Type 1 report describes whether your controls are suitably designed at a single point in time. A Type 2 report covers whether those controls operated effectively over a period, commonly several months or longer. Most customers eventually want Type 2, since it shows consistent operation rather than a snapshot. Some founders start with Type 1 to unblock early deals and move to Type 2 afterward. Ask your prospects whether a Type 1 will satisfy them before you spend on one.
The journey, phase by phase
1. Scope
Decide which product, systems, data and locations are in the audit. A narrower scope is cheaper and faster, but it must still cover what your customers care about. Document the system boundary, including the cloud services and key vendors you depend on. If personal data is in scope, bring in privacy consulting early so privacy commitments match your controls.
2. Gap assessment
Compare your current practices to the framework's requirements. This produces a list of missing policies, missing technical controls and missing evidence. It is the most valuable early step, because it turns "we have no idea" into a prioritized to-do list.
3. Remediation
Close the gaps. Typical work includes writing policies, enforcing multi-factor authentication, setting up logging and monitoring, formalizing access reviews and change management, running security awareness training, and assessing key vendors. This is where most of the calendar time goes.
4. Readiness check
Before engaging the auditor formally, do a dry run against your own evidence. Fix what a reviewer would flag. A readiness review is far cheaper than an audit finding.
5. The audit itself
The auditor requests evidence, interviews staff and tests samples of your controls. For a Type 2 SOC 2, this happens after an observation period during which your controls must run consistently. For ISO/IEC 27001, the process commonly has two stages: a documentation review, then an assessment of implementation.
6. Report or certificate, then maintenance
If you pass, you receive the report or certificate. If the auditor identifies exceptions, they are noted, and you remediate. Either way, the work does not end. Controls must keep running, and the audit repeats every year.
Common first-audit mistakes
- Treating it as a document exercise. Policies are only the starting point. Auditors test whether controls actually operate.
- Over-scoping. Including every system and every trust criterion on day one multiplies work. Start with what customers require.
- Buying tools before understanding requirements. Software can help with evidence collection, but it does not substitute for decisions about scope, policy and ownership.
- Writing policies you cannot follow. If your policy says quarterly access reviews and you will do them annually, the auditor will find the difference. Write what you will do and then do it.
- Starting evidence collection late. Many controls need proof across the whole observation period. Missing a month of evidence cannot be recreated afterward.
- No internal owner. Someone needs to drive the project weekly. Without a named lead, the work stalls.
Who does what
You will work with three kinds of people. Your own team owns the controls and produces the evidence. An independent auditor, which is a CPA firm for SOC 2 or an accredited certification body for ISO/IEC 27001, performs the audit and issues the report or certificate. An advisor may help you prepare. The preparation role and the audit role must stay separate: the firm that audits you should not be the one that built your controls. Velero prepares clients for audits and does not issue audit reports or certifications.
Budget your time honestly
Founders usually underestimate effort, not just on engineering but on coordination. Plan for realistic stretches of preparation before the audit begins, plus the observation period for a Type 2 report. Engineering, HR and IT each own pieces, and each will need protected time. Treat it as a project with a sponsor, a schedule and a weekly check-in. If a deal depends on the report, tell your sales team an honest timeline and do not promise dates before the auditor has confirmed a schedule.
Where to start
- Ask your top customers and prospects which framework and which report type they need.
- Define a narrow initial scope and write down the systems, data and vendors inside it.
- Run a gap assessment to get a prioritized remediation list and a realistic timeline.
- Name an internal owner and set a weekly cadence with engineering, IT and HR.
- Start collecting evidence early, even before you finish every control, so the observation period is not wasted.
If you want a guide through your first audit, our compliance advisory team can help, or get in touch.