Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages

Help for owners

A customer wants a security questionnaire or a SOC 2 report from my small company

Short answer

Most requests start as a questionnaire, not a certificate. Answer it honestly from what you really do, attach proof where you have it, and say plainly what you do not do yet. SOC 2 is a report by a licensed CPA firm, so it is a separate project, and you can often agree a smaller step with the customer first.

  • Written for business owners
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Does this sound like your situation?

  • A prospect's procurement team sent a spreadsheet with hundreds of security questions.
  • A deal is on hold until I show a SOC 2 report or something like it.
  • I do not know what half the questions mean.
  • Nobody in the company owns security, so the form keeps going back and forth.
  • I am afraid to answer yes where it is only partly true.

Why does this happen?

  1. The customer is managing their own risk

    A larger company that gives you its data or relies on your service has to show its own auditors that it checked its suppliers. The questionnaire is their paper trail, not a personal test of you.

  2. SOC 2 is an independent report, not a form you fill in

    The AICPA, which sets the professional standards for SOC engagements, describes SOC as a suite of services that CPAs may provide on system-level controls of a service organisation. It lists the areas covered by a SOC 2 report as security, availability, processing integrity, confidentiality and privacy. A CPA firm carries out the work.

  3. Not every provider is equal

    The AICPA says service organisations and CPA firms should thoroughly evaluate SOC services, and that it acts against members who do not follow professional standards or are unlicensed. A cheap-looking offer needs checking before you pay for it.

  4. Small teams lack the written records

    Questionnaires ask for things like who has access, how access is removed when someone leaves, how backups are tested and what happens during an incident. A small company often does these things informally and has nothing written to show.

  5. Answers become promises

    A yes in a questionnaire can end up in a contract. Rounding a partial control up to a yes is the quickest way to create a problem later.

What can I do about it today?

  1. Ask the customer what they actually needReply with a short, friendly question: is a completed questionnaire enough, or is a SOC 2 report a hard requirement? Often it is the first.
  2. Ask for the deadline and the formatFind out whether they require their own spreadsheet and when it is due.
  3. Answer only what is true todayUse yes, no, partly and planned, with one honest sentence each. Do not borrow wording from a larger vendor.
  4. Gather the evidence you already haveScreenshots of multi-factor authentication settings, a backup schedule, a list of who has access, your privacy policy. They answer many questions at once.
  5. Keep one master copy of your answersThe next customer will ask the same things. A saved set of answers saves hours.
  6. Do not agree to a date for SOC 2 until you have spoken to a CPA firmA report needs time, records and a firm to do it. Ask your customer whether a written plan with milestones is acceptable.

When should I bring someone in?

  • Questions about your code, servers, backups or access are ones nobody on your team can answer.
  • A signed contract will quote your answers.
  • The customer insists on SOC 2 and you need to decide whether it is worth it.

How do I handle it?

  1. Read the questionnaire with youI mark each question as technical, process or legal, and answer the technical ones from how the systems really are.
  2. Check the answers against realityI look at the actual settings: access lists, backups, logging, encryption. I do not write an answer I cannot show.
  3. Fix cheap gaps before answeringMissing multi-factor authentication or an unused admin account is fixed first, so the honest answer is better.
  4. Write the missing recordsA one-page note for access, backups and incident steps is written in plain words and kept up to date.
  5. Be clear about where I stopI prepare the technical side. The report itself comes from a licensed CPA firm, and legal questions go to a lawyer.

The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.

What do owners ask about this?

Do I need SOC 2 to sell to big customers?

Some require it, many accept a completed questionnaire first. Ask before you assume.

Can you give me a SOC 2 report?

No. It comes from an independent CPA firm. I can prepare the technical side.

Can I tell a customer the company is compliant?

Do not, unless an independent report says so. Say what you do, and what is planned.

What if the honest answer is no?

A clear no with a plan usually reads better than a vague yes that falls apart in review.

Sources

How was this page made?

I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.

Next step

Want this off your desk?

Send me a few lines on where things stand. I reply within 24 hours.