SOC 2 · Questions answered
SOC 2 Questions Answered
Straight answers to the questions companies ask before, during, and after a SOC 2 examination, from InfoGuard’s senior cybersecurity practitioners.
Where we work. InfoGuard serves companies across California from offices in Silicon Valley and Irvine, including San Jose and Silicon Valley, San Francisco and the Bay Area, Los Angeles, Orange County and Irvine, and San Diego. We also support clients throughout the United States.
Section A
SOC 2 basics
1. What is SOC 2, and how do we know whether our organization needs it?
SOC 2 is an independent examination, defined by the AICPA, of how well your company protects customer data. You likely need it if you store or process customer data and sell to mid-market or enterprise buyers, or if prospects are sending you security questionnaires. A SOC 2 report answers those questionnaires once, so security reviews stop slowing your deals.
2. What is the difference between SOC 2 Type I and Type II?
A Type I report confirms your controls are suitably designed as of a single date. A Type II report confirms they operated effectively over an observation period, typically three to twelve months. Type I is a fast first milestone; Type II is the report most enterprise buyers expect. Many companies start with Type I and move to Type II.
3. What is the difference between readiness consulting and the independent examination, and who signs the final report?
Readiness consulting prepares you by identifying gaps, fixing them, and organizing evidence. The examination is the independent test of your controls, performed by a licensed CPA firm, which signs the final report. InfoGuard handles readiness and coordinates the examination with our independent audit partner, so you have one point of contact from the first assessment to the final report.
4. Which Trust Services Criteria should our SOC 2 report cover?
Security is required in every report. Add Availability, Processing Integrity, Confidentiality, or Privacy only when they match what you promise customers in contracts and service agreements. Covering criteria you don’t need adds cost without helping you win deals. If customers rely on output from your AI features, they may expect Processing Integrity. We help you pick the scope buyers expect.
5. What is the difference between a SOC 2 report and a SOC for Cybersecurity report?
A SOC 2 report covers a specific service and is shared only with customers and partners who need it. A SOC for Cybersecurity report covers your whole organization’s cybersecurity program and can be shared publicly with your board, investors, and regulators. Every InfoGuard SOC 2 engagement includes a SOC for Cybersecurity report at no additional fee.
Section B
Working with InfoGuard
6. Where does InfoGuard provide SOC 2 services in California?
InfoGuard provides SOC 2 readiness, remediation, and audit support across California from offices in Silicon Valley and Irvine. We work with companies in San Jose and Silicon Valley, San Francisco and the Bay Area, Los Angeles, Orange County, and San Diego. Most work is done remotely, with on-site sessions when your team prefers them, and we support clients throughout the United States.
7. Do you work with small and midsize businesses?
Yes. Small and midsize companies often face their first enterprise security questionnaire with limited resources, and that is where we help most. We scope the engagement to your size, so you meet buyer expectations without building a large compliance program you don’t need.
8. Which industries do you have SOC 2 experience in?
In more than 15 years of compliance work, InfoGuard has served clients across industries, including SaaS, AI, technology, healthcare technology, and financial services. Because we approach SOC 2 as cybersecurity practitioners, we understand the systems, data flows, and regulatory pressures specific to your industry, so your controls fit how your business actually runs.
9. What makes InfoGuard's approach different, and will we work directly with senior practitioners?
InfoGuard is a cybersecurity firm first, not a compliance-only shop. Senior practitioners work directly with your team from readiness through your final report, and do the hands-on work rather than handing it to junior staff. You get controls that improve your security and hold up through Type II testing, not just documentation that passes an audit.
10. What qualifications and experience should we look for in a SOC 2 provider?
Start with the firm itself: choose a cybersecurity company, where cybersecurity is the core function, not a compliance-only shop. A SOC 2 report built on real security expertise holds up under scrutiny and improves your protection. Then look for senior practitioners with recognized credentials such as CISSP, CISA, and CISM; hands-on technical depth in cloud and application security; and industry experience. Ask who will actually do the work, how they handle remediation, and whether they coordinate the examination with an independent CPA firm. InfoGuard is a cybersecurity firm first, and its engagements are led by practitioners holding these credentials, including former federal compliance assessors.
11. Can you help if we don't have a security team, or work alongside our IT provider or MSP?
Yes to both. If you have no security team, we act as your security function for the engagement, defining controls, writing policies and guiding implementation. If you have an IT provider, MSP, or internal team, we work alongside them, assigning clear roles, responsibilities, and accountability so nothing falls through the gaps.
Section C
Cost, timeline and proposal
12. How much does SOC 2 cost, what affects the price, and what is included in your fee?
There is no flat fee. Cost depends on your company’s size, the systems in scope, the Trust Services Criteria you choose, whether you choose Type I or Type II, and how much remediation is needed. After an initial gap assessment, we provide a firm quote that lists exactly what is included: readiness, policies, remediation support, a mock audit, the examination, and the included SOC 2 report for Cybersecurity, so there are no surprise charges.
13. How long does a SOC 2 Type I or Type II engagement take?
A Type I report can often be issued within weeks once your controls are in place. A Type II adds an observation period of three to twelve months. Most companies should plan for several months from first gap assessment to final report. The biggest variable is how quickly gaps are fixed, so starting readiness early shortens the whole timeline.
14. How much staff time should we budget?
Plan for one internal owner, usually an engineering, IT, or operations lead, spending a few hours a week, with heavier weeks while gaps are fixed and evidence is collected. Other staff contribute in short sessions for interviews and evidence requests. Because InfoGuard does much of the hands-on work, your team stays focused on running the business.
15. What should we prepare before requesting a proposal, and what should we look for when reviewing one?
Before requesting a proposal, gather a short description of your product or service, your cloud providers and key systems, approximate headcount, any customer deadline driving the request, and existing policies or compliance tools. When reviewing proposals, check who does the work, whether remediation and the examination are included, how scope is defined, and what happens if timelines slip.
16. How are responsibilities split between our team, your consultants and the auditor?
Your team owns and operates the controls and provides evidence. InfoGuard assesses gaps, designs controls, writes policies, guides remediation, and prepares you for the examination. The independent auditor tests your controls and issues the report. We define these roles, responsibilities, and accountability in writing at kickoff, so every task has an owner.
17. Who owns the policies and documents created during the engagement?
You do. Policies, procedures, and documentation created for your SOC 2 belong to your company, so you can keep using and updating them after the engagement ends. That protects your investment if your team, tools, or auditor change.
Section D
Readiness and preparation
18. How do we know we're ready to begin, and can you assess our gaps first?
You’re ready when your controls are in place, followed consistently and backed by evidence. The surest way to know is a readiness and gap assessment before the examination. InfoGuard tests your controls the way an auditor will, lists every gap with a fix, and confirms readiness with a mock audit, so problems are found while they are still inexpensive to fix.
19. What deliverables should we expect from a readiness engagement?
Expect a gap assessment report with prioritized fixes, a defined system boundary and scope, a control set mapped to the Trust Services Criteria, tailored policies and procedures, an evidence plan, and a mock audit result. Together they give you a clear path to the examination and documentation your team can keep using.
20. How do you help define scope, and can we limit it to a specific product or business unit?
Yes, we can limit scope to a specific product, service, or business unit, as long as it matches what you promise those customers. We map every application, vendor, and data flow inside the boundary, then set a scope that satisfies buyers without pulling in systems that add cost but no value.
21. Do you help implement controls and write policies tailored to our business?
Yes. We don’t stop at documentation. InfoGuard designs and helps implement technical and administrative controls, including access management, monitoring, encryption, vendor management, and incident response. We write policies that describe how your company actually operates, because generic templates are a leading cause of audit exceptions.
22. What evidence do we need to collect?
Auditors want proof that each control exists and works: system configurations, access lists and reviews, onboarding and offboarding records, training records, vulnerability scans, incident and change tickets, vendor reviews and signed policies. For a Type II, they sample evidence across the whole observation period. We give you an evidence plan that says what to collect, when, and by whom.
23. Do you work with compliance platforms such as Vanta and Drata?
Yes. InfoGuard is an official Vanta and Drata partner. These platforms automate evidence collection from your systems, but much of SOC 2, including scoping, gap analysis, policy writing, remediation, and audit preparation, still needs an experienced practitioner. We work alongside your platform so you get the most from it.
24. How should AI systems and third-party AI services be addressed in our SOC 2?
As of September 2026, AICPA guidance (Q&A Section 9561) expects your SOC 2 to address AI when it is part of your service or controls. That means describing the AI you use, assessing risks such as inaccuracy, bias, prompt injection, and data exposure, showing human oversight, and reviewing AI used by your vendors. InfoGuard builds these into your readiness work, so AI does not become a late audit finding.
25. Can SOC 2 and ISO 27001 readiness be coordinated to reduce duplicate work?
Yes. SOC 2 and ISO 27001 share most of their security controls, so one coordinated program can satisfy both. We map your controls once to both frameworks and reuse the same policies and evidence, which saves time and cost when you need U.S. and international customers to accept your security.
26. How do you assess controls in AWS, Azure and Google Cloud, including those our providers manage?
We assess the controls you configure in AWS, Azure and Google Cloud, such as identity and access, logging, encryption and network security. For controls the cloud provider manages, we review the provider’s own SOC report and confirm you have the complementary controls it expects of you. Your report then accurately reflects your shared responsibility.
27. Can you help assess our vendors and review their SOC reports?
Yes. We set up a vendor risk process that classifies vendors by risk, reviews their SOC reports and exceptions, and confirms you have the complementary controls they require. Vendor oversight is a common audit focus, and since 2026 it includes AI your vendors use on your behalf.
Section E
During the examination
28. How do we manage controls and evidence during the Type II observation period?
Every control must run consistently for the whole period, typically three to twelve months, and leave evidence each time it runs. Set a calendar of recurring tasks such as access reviews, scans and training, assign an owner to each, and check evidence monthly. InfoGuard monitors the period with you, so a missed control is caught and corrected before the auditor samples it.
29. Can you help us move from a Type I to a Type II report?
Yes. Moving to Type II means proving your Type I controls operate over time. We confirm which controls need recurring evidence, set up the schedule and tracking, close any design gaps the Type I surfaced, and support you through the observation period and examination.
30. What happens if the auditor finds deficiencies or exceptions?
Exceptions are noted in the report along with your management response. A few minor exceptions with sound explanations rarely stop a deal, but repeated ones raise buyer questions. We help you analyze the root cause, write a clear management response, and fix the control so it does not recur in the next period.
31. What if we can't finish fixing gaps before our planned exam date?
You have options: move the date, narrow the scope, start with a Type I while remediation finishes, or begin the Type II observation period after the fixes are in place. Starting an examination with known gaps usually costs more than a short delay. We help you pick the option that best protects your customer commitments.
32. How should we handle a security incident during the examination period?
Follow your documented incident response plan exactly, and record each step: detection, response, communication, and lessons learned. An incident does not automatically mean a failed audit; auditors look at whether your process worked. A well-handled incident can demonstrate that your controls are effective. We can support your response and the documentation.
33. What commonly delays SOC 2, and how do we avoid it?
The most common delays are unclear ownership, incomplete or scattered evidence, policies that don’t match practice, late remediation, and slow responses to auditor requests. Avoid them by naming an internal owner, fixing gaps before the observation period starts, and collecting evidence continuously instead of at the end.
34. How do you track progress and keep leadership informed?
We work from a shared plan with owners and target dates for every task, and send regular status updates covering progress, open items, risks, and decisions needed. Leadership sees where the engagement stands and what is needed from them, without having to manage the details.
35. How do we protect confidential information when sharing evidence?
Share only what each control requires, redact sensitive data such as customer records and secrets, and use encrypted, access-controlled channels instead of email attachments. InfoGuard is a cybersecurity firm and handles client evidence under strict confidentiality and need-to-know access.
36. Can we change auditors without starting over?
Yes. Your controls, policies, and evidence belong to you and carry over to a new audit firm. A new auditor will want to understand your system and prior reports, and coverage periods should continue without gaps. InfoGuard can help you plan the transition, including through our independent audit partner.
Section F
After the report
37. What does the final report include, who can we share it with, and how do we use it in customer security reviews?
The report includes the auditor’s opinion, your management assertion, a description of your system, and your controls with the auditor’s tests and results. Share it under NDA with customers, prospects, and partners who need it. Send it in place of long security questionnaires; when a customer questions scope or findings, we help you explain them clearly.
38. What is a bridge letter, and can customers rely on a report whose period ended months ago?
A bridge letter is a short statement from your management covering the gap between the end of your last report period and today, confirming no significant control changes. Customers generally accept a report whose period ended within the last twelve months, plus a bridge letter for the months since. Renewing annually keeps you covered.
39. How do we maintain controls between examinations, and what ongoing support do you offer?
Keep recurring controls running, update policies as your business changes, and collect evidence continuously so the next period is ready. InfoGuard offers ongoing support, including monitoring, evidence reviews, policy updates, vendor reviews, and annual renewal preparation, so your controls don’t drift between reports.
40. How do acquisitions, new products or infrastructure changes affect our scope?
Significant changes can bring new systems, vendors, or data flows into scope and must be reflected in your system description and controls. Tell your consultant and auditor early, before the next period starts. We assess the change, update scope and controls, and keep your report accurate, so customers aren’t surprised by what it covers.
41. Can SOC 2 preparation also strengthen our cybersecurity and reduce risk?
It should. Done well, SOC 2 tightens access control, monitoring, vendor oversight, and incident response, which reduces real risk, not just audit findings. InfoGuard approaches SOC 2 as cybersecurity practitioners: compliance should validate good security, not substitute for it, so your investment protects the business as well as closing deals.
42. How do we write an accurate public statement about our SOC 2 achievement?
State which report you completed (Type I or Type II), the period or date it covers, and that it was issued by an independent CPA firm. Avoid saying you are “SOC 2 certified”; SOC 2 is an attestation report, not a certification. We help you word website, sales, and trust-page statements that are accurate and hold up to customer scrutiny.
Also see: SOC 2 Control Requirements · SOC 2 Compliance services
Next step
Tell us where you stand
Tell us what you’re trying to accomplish. We’ll reply with clear next steps.
