# How to respond to security and compliance questions on LinkedIn
> Handle prospect requests for security docs and SOC2 on LinkedIn without slowing down your sales momentum or losing the deal to a spreadsheet.
- HTML: https://getkinlead.com/handle-prospect-asking-for-security-documentation
- Markdown: https://getkinlead.com/handle-prospect-asking-for-security-documentation.md

**Short answer:** When a prospect asks for security docs on LinkedIn, provide the answer in the chat immediately. Use a tiered response: answer the specific concern, provide a link to a public security page, and offer a technical call only if the deal size justifies the time.

## Identify the type of security request

Most security requests aren't technical audits. They're checkboxes a buyer needs to tick to move you to the next stage. If you treat every request like a full audit, you'll waste hours on spreadsheets for deals that aren't even qualified.

Decide if the person is a buyer or a gatekeeper. A buyer asks if you're secure so they can buy. A gatekeeper asks for specific documentation to ensure you don't violate company policy. You handle them differently to keep the deal moving.

Look at the wording. A buyer might say 'Is our data safe with you?' or 'Do you have a security page?' A gatekeeper will ask for a SOC2 report, a completed questionnaire, or specific encryption standards. The gatekeeper has a checklist from their IT or legal team. Your job is to give them the exact item on that checklist, not to educate them on security.

If you're unsure, ask: 'Is this for your team's review, or do you have a specific checklist from IT?' That one question tells you how much detail to provide. For a buyer, a simple link is enough. For a gatekeeper, you might need to fill out their form or provide a specific document.

**The checkbox**

- They ask for a general security overview.
- They want to know if you have a SOC2.
- They just need to confirm you aren't a high risk.

**The gatekeeper**

- They ask about specific data residency (e.g., EU only).
- They cite specific GDPR articles.
- They demand encryption standards before a demo.

## The first response: acknowledge and provide

Don't say, 'I'll check with my CTO and email you.' That kills the momentum and moves the deal into a crowded inbox where it can die. Provide the answer in the chat so the prospect stays engaged.

If you have the document, send the link. If you don't have a formal document, describe your process in plain English. Always end with a question that puts the burden of the next step back on the prospect.

If you need a minute to find the link, say so. 'I have our security overview. Let me grab the link.' Then send it in the next message. If the question is complex and you genuinely need a technical person, say: 'That's a good question. I want to give you an accurate answer, so let me check with our engineering lead and get back to you by tomorrow.' Then actually do it.

Here's a simple template you can adapt: 'Yes, we have a security overview that covers encryption and data handling. Here's the link: [link]. Does that answer your question, or is there a specific requirement I should look into?' If the prospect goes silent after you send the link, follow up in two days with a simple question: 'Did your team have any questions about the security overview?'

- **them:** This looks interesting. Do you have a security whitepaper or SOC2 we can review?
- **you:** Yes, we do. I've attached our security overview here (link). It covers our encryption and data handling. Does that cover what your team needs, or is there a specific requirement I should look into?
- **them:** This is perfect. I'll send it to our IT lead and let you know if they have questions.

## Creating a security hub for fast sharing

Sending individual PDFs is slow and hard to update. Build a single source of truth instead. This lets you drop one link in a LinkedIn message that satisfies most compliance officers.

A security hub doesn't need to be a complex portal. A simple, hidden page on your website works. This keeps the prospect on your domain and lets you track when the security review is actually happening.

Include the documents most prospects ask for: your SOC2 report (or a summary if you don't have one), a standard security questionnaire you've already filled out, your data processing agreement, and a plain-English description of how you handle data. Add a note about where data is stored and who can access it.

Keep the page updated. When you get a new certification or change your infrastructure, update the page. A stale security page is worse than no page because it makes you look careless. Use a simple analytics tool to see when the page is viewed. That tells you when the security review is active and when to follow up.

1. **Create a trust page.** Build a page at yoursite.com/security or /trust. Keep it clean and easy to scan.
2. **List certifications.** Place SOC2, ISO, or GDPR compliance badges at the top of the page. If you don't have a certification, say what you do have.
3. **Host the documents.** Upload your standard security questionnaire or whitepaper as downloadable PDFs. Keep the file names clear.
4. **Add a direct contact.** Include a calendar link or a specific email address for security inquiries. This shows you're responsive.

## Handling the security questionnaire trap

A 50-page security spreadsheet can kill a deal. It takes days to fill out and weeks for the prospect to review. Often, 80% of the questions don't even apply to your software architecture.

Minimize the manual work while appearing cooperative. Never refuse to fill out a questionnaire, but negotiate the scope of the work.

Ask for the document first. Tell the prospect you'll fill out the parts that apply to your specific setup to save their team time reviewing irrelevant data. Most gatekeepers will agree because they don't want to read answers about systems you don't use.

Keep a library of standard answers. When you answer a question once, save it. Next time a similar questionnaire comes in, you can copy and paste instead of starting from scratch. This library becomes your security playbook. If the questionnaire is huge, offer to do a 15-minute call to walk through the key sections. That often satisfies the gatekeeper and saves you hours of writing. During the call, you can answer the most important questions verbally and then fill out only the sections that still matter.

| | Scenario | Wrong approach | Right approach |
| --- | --- | --- | --- |
| Massive spreadsheet | Spend three days filling every cell. | Fill the core 20% and offer a 15-minute call for the rest. |
| Missing certification | Apologize and say you don't have it. | Explain the equivalent controls you have in place. |
| Technical question | Guess the answer to keep momentum. | Acknowledge the question and promise a technical answer by tomorrow. |

> Ask for the document first. Tell the prospect you'll fill out the parts that apply to your specific setup to save their team time reviewing irrelevant data.

## What to do when you don't have the certification

Not having a SOC2 is not a dealbreaker for most small and mid-size deals. What matters is that you can show you take security seriously. Be honest about what you don't have, then explain what you do have.

If you're pursuing a certification, say so and give a rough timeline. 'We're in the audit process for SOC2 and expect to have the report by Q3.' That tells the prospect you're moving in the right direction.

Focus on the controls you have in place. Do you encrypt data at rest and in transit? Do you use a reputable cloud provider? Do you have access controls and logging? These answers often satisfy a gatekeeper who is just trying to check a box.

If the prospect insists on a certification you don't have, ask if there's an alternative. Sometimes a security questionnaire or a call with your technical lead is enough. If not, it's better to know early. Don't apologize for not having a certification. Just state the facts and move on. Apologizing makes it sound like you're hiding something. If they still insist, ask if you can start with a pilot or a limited scope while you work on the certification.

**Weak response**

- We don't have SOC2. Sorry.
- I'm not sure about our encryption. I can ask.
- We're a small company, so we don't have formal security docs.

**Strong response**

- We don't have SOC2 yet, but we're in the audit process and expect it by Q3. In the meantime, here's our security overview that covers encryption and access controls.
- We encrypt data at rest and in transit. Our infrastructure runs on AWS with strict access controls. I can send you our full security questionnaire.
- We're a small team, so we don't have a formal certification. But we follow best practices and can fill out your questionnaire to show exactly how we handle data.

## When to escalate to a technical call

Not every security question needs a technical call. But some do. Escalate when the prospect asks about specific architecture, custom integrations, or compliance requirements that you can't answer confidently.

Use deal size as a filter. If the deal is small and the question is simple, handle it yourself. If the deal is large or the prospect is a gatekeeper with a long checklist, bring in your CTO or security lead.

Set up the call quickly. Don't make the prospect wait a week. Offer two specific times in the next 48 hours. Include your technical person on the invite and send a brief summary of the question beforehand so they can prepare.

After the call, send a follow-up message with any documents or answers you promised. Keep the thread on LinkedIn or move to email if the prospect prefers. If you don't have a technical person, consider hiring a fractional security consultant for these calls. It's cheaper than losing a deal over a question you can't answer.

> If you don't know the answer, say so and give a specific time when you will. 'I'll check with our engineering lead and get back to you by tomorrow at noon.' Then do it.

## Doing this with Kinlead

You can automate these compliance conversations by using a sales playbook in Kinlead. Put your security hub link and standard answers for things like SOC2 status in your playbook.

Set the AI to reply until there is real interest or a meeting is booked. The AI handles basic certification questions using your scripts. When a prospect asks a complex technical question, use hand-off mode to take over personally.

You can learn more at [book a demo](/demo).

## Related

- [Book a demo](https://getkinlead.com/demo.md)
- [AI outreach features](https://getkinlead.com/features/ai-linkedin-outreach.md)
- [Unified inbox](https://getkinlead.com/features/unified-inbox.md)

## Common questions

**What if I don't have a SOC2 yet?**

Be honest and focus on what you do have. Explain your current security measures, like encrypted databases or your cloud provider's security, and mention if you are pursuing the certification.

**Should I send security docs in the first message?**

No. Only send them when the prospect asks or when compliance becomes a requirement. Sending them too early can make you look like a commodity.

**How do I handle GDPR requests from EU prospects on LinkedIn?**

Provide a link to your Data Processing Agreement (DPA) and your privacy policy. Confirm you store data in the required regions and offer to sign their standard DPA if needed.

[Create a Kinlead account](https://getkinlead.com/signup) or [book a call](https://getkinlead.com/demo) to talk through pricing and setup.
