Blog / Cybersecurity

The Security Questionnaire Your First Enterprise Customer Will Send

DevOpsSaaSSMESOC2
Aviram Galim5 min read

A small software company finally secures a meeting with a major client. The demo goes well, and the price is agreed upon. Then, an email arrives with a spreadsheet attached. The spreadsheet has 150 to 300 questions about how the company handles security, and the deal won’t move forward until the spreadsheet is filled out.

For many startups, this is the first time they’ve been asked hard questions about their infrastructure. Good deals often stall for weeks at this stage, not because the answers are terrible, but because nobody knows them.

This is what to expect and how to prepare before the email arrives.

What it is

A security questionnaire is a list of questions that a customer’s security or procurement team sends to determine whether it is safe to do business with you. Some use a standard format, such as the Security, Information, and Risk Assessment (SIRA) from Shared Assessments or the Cloud Audit Information Questionnaire (CAIQ) from the Cloud Security Alliance. Many are custom spreadsheets, and many of those borrow questions from the standards.

Most questions are answered with a simple “yes” or “no,” and there is a comment box for additional information. The comment box is where the real answers live.

What they actually ask

The wording changes, but the topics remain the same.

  • Sign in and access. Is multi-factor authentication required? Who has access to production, and how is that access reviewed?
  • Data protection. Is the data encrypted in transit and at rest? Where is the data stored, and which third parties have access to it?
  • Backups and recovery: Are backups automated and tested? What happens on a bad day, and how quickly can you recover?
  • Monitoring and incidents: Do you log activity? Do you have an incident response plan, and who is responsible for it?
  • Updates and testing: How quickly do you patch? Has anyone tested the system for weaknesses, and when was the last time this was done?
  • People: How do new employees get access, and how is access removed when they leave?
  • Proof. Do you have certifications such as SOC 2 or ISO 27001?

Notice how much of this is ordinary infrastructure hygiene. As I’ve written before, it’s important to have tested backups, monitoring that catches problems early, and to keep secrets out of the wrong places. A questionnaire asks about those topics from a stranger.

How to answer without hurting yourself

The worst answers are the ones you can’t back up. A confident “yes” without substance can result in a failed review or, worse, a contract clause you can’t meet.

A good answer has three parts: an honest assessment of your current status, the steps you’re taking to mitigate the risk, and a date by which you plan to implement the control. For example: “We don’t yet run a formal quarterly access review. We review access whenever someone joins or leaves, and a scheduled quarterly review will start next quarter.”

“We take security very seriously” is not an answer. Neither is a blank cell. If a question doesn’t apply to you, explain why and say so.

Keep every answer you write in one place. The first questionnaire takes days to complete. The next ones will go much faster when you can reuse what you’ve already written.

Do you need SOC 2?

Often, not yet. Many early deals close based on a well-answered questionnaire alone. SOC 2 becomes worth considering when the same request keeps coming back or when deals stall because you don’t have it.

It is not cheap. Published estimates from auditors and compliance vendors, who have a stake in the matter, put the cost of an audit for a small company at around $5,000 to $20,000 for a Type 1 report, and more for a Type 2 report. The total cost for the first year, including tooling, testing, and preparation, is around $20,000 to $50,000. A Type 1 audit usually takes a few months. Type 2 requires an observation period, so plan for at least a year. Treat these estimates as ranges and get real quotes.

One more honest point: The audit itself must be performed by a licensed auditor. I can help prepare the technical side, but I can’t certify you.

What to do before the email arrives

None of this requires a security department. For a small team, it typically takes a few days to a couple of weeks of focused work. That is my estimate, not a measured figure.

  • Enable multi-factor authentication for email, the cloud console, code hosting, and every admin tool.
  • List your systems and who owns each one. Include where data is stored and which outside services access it.
  • Confirm that backups are running and that a restore has actually been tested.
  • Set up basic logging and alerts to notify you of a problem.
  • Write short, plain documents for access, incident response, and backups. One page each is sufficient.
  • Familiarize yourself with the off-boarding steps so that you can remove access when someone leaves.
  • Begin an answer library containing your honest responses to the aforementioned questions.

What to avoid

Don’t claim a certification you don’t have or list something as “in progress” if you haven’t even started yet. Don’t copy and paste generic answers that don’t reflect your actual work style. Don’t promise a deadline that you can’t meet.

Customers usually forgive a delay if there’s a plan in place. However, they rarely forgive an untrue answer.

Questions worth asking now

  • Is multi-factor authentication required for all important data?
  • Do we know where our data is stored and who else has access to it?
  • Can we demonstrate a recent, successful backup restore?
  • Do we have a written incident plan, even a short one?
  • If a questionnaire arrived tomorrow, who would answer it?

If you can’t answer the last question, start there.

If you’d like help getting your infrastructure ready for a first security review, get in touch.
I reply within 24 hours.
Contact Me

Keep reading