SOC 2 Audit: What Type II Requires and Who Owns Each Control

A SOC 2 audit is an independent CPA examination of your controls against the AICPA criteria. Here is what a Type II report requires, who owns each control and what evidence to keep.

By the Total 360 Security team7 min read
Engineering meeting room in a Texas office with a whiteboard of boxes and arrows, illustrating control planning for a SOC 2 a

A SOC 2 audit is an independent examination by a licensed CPA firm of your controls against the AICPA Trust Services Criteria. For a Type II report, the controls have to operate over a period, typically six to twelve months, so control owners must be assigned and evidence collected as the work happens, not written up just before fieldwork. Running that program is the part we do for clients; the CPA firm performs the audit itself.

If a buyer is waiting on your report, confirm exactly what they need before committing to a date. The controls must operate throughout that period, and the auditor still needs time to test them and issue the report.

What does the buyer's report request actually need?

What does the buyer's report request actually need?, Total 360 Security

Start with the deal team and the buyer's vendor review requirements. Ask which report they need and what dates it must cover. Get the actual questionnaire or contract language rather than working from a sales note that says “needs SOC 2.” A Type I report will not automatically satisfy a request for Type II.

SOC 2 produces an attestation report, not a certificate. The auditor issues one of four opinions: Unqualified, Qualified, Adverse or Disclaimer. An unqualified opinion is the clean result. A qualified opinion identifies a qualification affecting the auditor's conclusion; have the auditor explain its significance rather than treating every exception as equivalent.

A Type I report evaluates control design at one point in time. A Type II report also evaluates whether controls operated effectively over a period. If the buyer requires Type II by a fixed date, work backward from report delivery, allowing time after the observation period for fieldwork and reporting.

Who sets the scope and the criteria the report covers?

Settle the scope before you buy any tooling. The program owner coordinates the scope with the internal team and the independent auditor. Start with the service the buyer uses, then identify everything required to deliver and secure it.

The system description explains that boundary. It covers the supporting infrastructure and the people who operate it, including relevant third-party dependencies. Describe how the service actually runs. A cloud host holding customer data and a contractor with administrator access both need consideration; neither disappears from scope discussions because they sit outside your payroll.

There are five Trust Services Criteria categories. Security is the one criterion every report includes. Add Availability, Processing Integrity, Confidentiality or Privacy where your service commitments and customer requirements justify them. Extra categories create extra obligations. Confirm the applicable criteria with the auditor before mapping controls.

Which department owns each control?

A policy cannot perform a control. Assign a named owner in the department that does the work, then define what evidence that person must retain. The vCISO coordinates the program; HR still owns hiring records, and engineering still owns change approvals.

Control areaEvidence produced byWho keeps it running
Background checks and confidentiality termsHR, through hiring records and signed agreementsHR lead
Change approval and security testingEngineering, through approval records and scan resultsEngineering lead
Device updates and endpoint managementIT, through management console reportsIT lead
Security trainingHR or training coordinator, through completion logsTraining coordinator
Vendor risk reviewsFinance or operations, through review recordsOperations or finance lead
Software and AI tool approvalsRequesting team, through approval recordsSecurity and legal reviewers

A common readiness failure is a documented control that produces no evidence because nobody owns the task. Put the required frequency and storage location in the control matrix. An owner should know exactly what to save without asking security each month.

What do auditors read closely in policy wording and AI tools?

Make controls easy to find. If personal-device rules sit inside a Remote Access Policy, cross-reference them clearly in the control matrix. A reviewer should not need a meeting to discover where you documented the requirement.

Check the wording against what staff actually do. A policy promising approval before every production change creates an obligation to retain those approvals, including the process for emergency changes. Do not write a stricter process than you can operate.

Unreviewed AI tools create another evidence problem. Staff can disclose customer data before security knows the tool exists. Require security and legal review before adoption, and retain the decision. The approval record demonstrates that the review happened; it does not, by itself, prove the tool is safe.

What has to be running before the window opens?

Readiness means testing the process before relying on it for audit evidence. Walk through each control with its owner and check the output, not just the policy:

  1. Confirm the owner understands the required evidence and frequency.
  2. Test the process and verify that its output is retained. For annual or event-driven controls, agree with the auditor how timing and evidence will be handled.
  3. Check that the system description matches current operations.
  4. Assign remediation owners and deadlines to known gaps.
  5. Check the proposed reporting schedule against the buyer's deadline.

Paperwork cannot replace an observation period. Starting late does not turn a Type II engagement into Type I, but it can leave you unable to deliver the requested Type II report on time. Confirm a realistic schedule with the auditor before making a commitment to sales.

Who collects evidence through the observation window?

Who collects evidence through the observation window?, Total 360 Security

Department owners collect evidence at the frequency each control requires. The program owner checks for missing records on a defined review schedule. Use consistent file names and controlled access so reviewers can trace an artifact to the control and period it supports.

If a control fails, document what happened and retain evidence of remediation. A missed patch deadline should not vanish from the record once the device is updated. The auditor determines how the failure affects testing and the opinion; remediation does not erase the original exception.

Stop and reassess if an unlogged failure comes to light or a vendor holds regulated data outside the described boundary. Investigate the impact with the auditor before fieldwork progresses. Either issue can affect what must be tested.

Plan for the next reporting cycle while operating the current one. Annual reporting is customary, but confirm the coverage your buyers require. Keep controls running between audits rather than rebuilding the evidence process for each renewal.

How is the auditor relationship managed from scoping to read-out?

Give the auditor one coordinator who can route requests and resolve ownership questions. That can be the vCISO. The CPA firm remains independent and controls its examination and opinion.

  1. Agree the scope early. Confirm the system boundary and applicable criteria early. Discuss the observation period and how testing will work before committing to delivery dates.
  2. Keep evidence requests moving. Give each request a named owner and a due date. Flag delays before they block fieldwork.
  3. Answer each exception with facts. Provide the facts and supporting remediation records. Correct misunderstandings with evidence, not argument.
  4. Review the draft report. Check it for factual accuracy. Ask the auditor to explain findings and their implications without trying to negotiate away supported conclusions.

A current report can reduce repetitive procurement questions because the buyer's security team has independent testing to review. It does not guarantee acceptance. Buyers can still ask questions about exclusions or requirements their contracts impose.

What goes to the auditor, and what should the buyer hear from you?

Give the auditor the system description and control matrix, with access to requested evidence and exception records. Keep a record of what was supplied. Provide sensitive material through the agreed secure channel rather than opening an unrestricted evidence folder.

Give the buyer the issued report under the applicable distribution arrangements. Explain what service it covers and the dates examined. Do not assume the buyer needs your internal risk register or every remediation working paper; review additional requests for relevance and confidentiality.

A SOC 2 report does not guarantee that an attacker cannot cause harm. It communicates the auditor's opinion on the controls within the stated scope. Describe that limit plainly, especially when a buyer treats “SOC 2 compliant” as a promise of breach prevention.

We are based in Fort Worth, Texas, and serve Texas, California, Nevada and New Mexico. We are Texas DPS-licensed and CPP, CISSP, CISM credentialed. Our vCISO service focuses on framework selection, incident response planning and compliance program ownership. We run security programs; the independent CPA firm performs the audit.

If your buyer has set a deadline and nobody owns readiness, review our vCISO compliance program ownership service, or book a 30-minute risk discussion with the buyer's requirements in hand.

Frequently asked questions

What is SOC 2 compliance?

SOC 2 is a voluntary AICPA attestation framework for service organizations. An independent CPA firm examines controls against the applicable Trust Services Criteria and issues a report, not a certificate. It is not a general Texas legal mandate, though a customer can require a report as a condition of doing business.

What are the four possible SOC 2 audit outcomes?

The four opinion statuses are Unqualified, Qualified, Adverse and Disclaimer. An unqualified opinion is the clean result; a qualified opinion includes a qualification affecting the conclusion. An adverse opinion indicates an unfavorable conclusion, while a disclaimer means the auditor does not express an opinion. Read the explanation with the auditor rather than judging the report by its label alone.

How long is a Type II observation window?

A Type II observation period typically lasts six to twelve months. Confirm the period with the independent auditor and check that it meets the buyer's requirements. Report delivery also requires time for testing and reporting, so the observation period's end date is not the delivery date.

Can a vCISO help us through a buyer's vendor review?

A vCISO can coordinate readiness, assign control responsibilities and track evidence requests. Department owners still perform their controls, and only the independent CPA firm issues the SOC 2 opinion. Bring the buyer's questionnaire and deadline to a 30-minute risk discussion to identify who needs to own the work.

Does a SOC 2 report mean we cannot be breached?

A SOC 2 report does not mean you cannot be breached. It is an attestation about controls within a defined scope, not a guarantee against attack. For Type II, it addresses operating effectiveness during the examined period; it does not establish that every system is secure today.

Total 360 Security provides virtual Chief Security Officer, vCISO, and Enterprise Security Risk Management programs for mid-market organizations. They design, run, and report security programs covering all 13 risk domains rather than just offering advisory decks or point solutions. The firm is Texas DPS-licensed with CPP, CISSP, and CISM credentials.

Serving Texas, California, Nevada, New Mexico.