# Referral security questionnaire handoff sheet | SourceX

Canonical: https://refer.sourcex.si/guides/how-to-hand-off-security-questions-without-interpreting-the-answers
Last updated: 2026-11-04

Forward the question exactly as it was asked and let the party who will be held to the answer write it. A question a CEO asks about SourceX goes to SourceX's security contact, with a link to its trust center; a question SourceX asks about the company's systems goes to the company's own security owner. The analyst logs who asked, who owns the reply and when it went out, and never rewords, grades or vouches for an answer in either direction.

There is one exception. When someone asks what the analyst or the fund will see, the analyst answers that one personally, because nobody else can.

## Why a forwarded answer is safer than a summarized one

A security answer is a statement someone is accountable for. A summary of it is a statement nobody is.

Security questionnaires are built that way on purpose. The Cloud Security Alliance describes its CAIQ as a set of yes/no questions that map to the controls in its Cloud Controls Matrix: each answer is an assertion about the answering party's own controls. Change "yes, encrypted at rest" to "they encrypt everything" and the assertion is now yours, with a scope the original never had.

The parties on both sides also treat supplier security as their own governance work. NIST's Cybersecurity Framework 2.0 places supply chain risk inside its Govern function, with outcomes for due diligence before a relationship starts, contract requirements, monitoring and what happens when a relationship ends. On the AI side, NIST's AI Risk Management Framework asks developers to document how they map the legal and technology risks of third-party data and software, including risks to other people's intellectual property. Those chains run from the company to SourceX and from SourceX to the Acquisition Partner. A referrer is not a link in either, and an answer that passes through one has left the chain.

A portfolio operations analyst has a particular reason for care: the fund often knows a good deal about a company's systems from board materials. That knowledge came in confidence, and using it to answer a security question on the company's behalf is the fastest way to misuse it.

## Four directions a security question travels

| Direction | Typical wording | Who answers | How it gets there |
|---|---|---|---|
| The company about SourceX | "Where does our data go, and who can see it?" | SourceX | The CEO or security lead writes to the security contact on SourceX's trust center |
| SourceX about the company | "How would records be exported, and who holds admin access?" | The company's security or IT owner, or its MSP on the company's written instruction | Directly to SourceX, once the company has applied |
| The company about the buyer | "Which AI company ends up with it, and how do they protect it?" | SourceX, as far as it can say | Through SourceX; the analyst never guesses at buyers |
| The company about the partner | "What will you, or the fund, see?" | The analyst | In the analyst's own words |

The third row has a reason behind it. SourceX's investor page lists Acquisition Partner anonymity as a feature, meaning labs can source data without revealing their identity or roadmap to the market. An analyst who names a likely buyer is guessing, and may be guessing about something SourceX has agreed not to disclose.

The fourth row is short. Under section 7 of the terms, partners never receive access to other partners' records, applicant documents or confidential buyer information, and SourceX's [description of the partner role](/how-it-works) says the introducer does not need to export, upload or describe confidential records. Say so, in one sentence.

## The security contact routing sheet

**Part 1, where each question family goes.**

| Question family | Answered by | What the analyst sends | What the analyst never says |
|---|---|---|---|
| What leaves the company, and when | SourceX | The question word for word, plus the trust center link | "Nothing leaves until you sign" |
| Storage, access controls and audit trail at SourceX | SourceX | The question word for word | "It's all encrypted" |
| De-identification and its limits | SourceX | The question word for word | "It's anonymous" |
| Certifications and audit reports | SourceX's trust center, which states its own status | The link, with no paraphrase | Any status from memory |
| Incident handling and notification | SourceX | The question word for word | "They'd tell you straight away" |
| Subprocessors and processing partners | SourceX | The question word for word | Names you heard somewhere |
| What happens to data if no deal closes | SourceX | The question word for word | A number of days |
| The company's export method, admin access and credential handling | The company's security or IT owner | SourceX's question, word for word | "Our IT looked, it's fine" |
| Security terms in the contract, such as a DPA, liability or insurance | Company counsel and SourceX, in the agreements | The question word for word | "It's standard paper" |

Several items in the last column are things SourceX does publish in some form. That is the point: when SourceX's own page says it, the CEO should read SourceX's words with their date, not the analyst's memory of them.

**Part 2, the forwarding log.** One row per question.

| Field | What to record |
|---|---|
| Date asked | The day the question reached you |
| Asked by | Name and role, such as the CEO or the IT director |
| Question | Verbatim, never summarized |
| Answer owner | SourceX, the company's security owner, counsel or you |
| Sent to, and when | The address used and the date |
| Direct thread? | Yes when the answer goes straight to the asker; aim for yes every time |
| What you keep | Only "answered on" and the date, not a copy of the answer |

## What SourceX publishes, and why you send the link instead of retelling it

SourceX's trust center, checked on 27 October 2026, lists the controls it says are in place today, names a security contact and states that requests are answered within two business days. It says security questionnaire responses, a business continuity overview, an incident escalation process, contract templates and a DPA where applicable are shared privately after review, and that its subprocessor list is available on request. It also lists three compliance initiatives as in progress and says none has been issued yet.

That last sentence is the best argument for this whole page. It is precise, it is SourceX's to state, and it is exactly the kind of line that turns into "they're certified" after two retellings. Send the link, with the date you sent it.

## One CEO, five questions, routed (Illustrative)

Illustrative. A generic company with invented facts; no outcome implied. A 260-person insurance claims administrator, founder-led, with the fund as a minority investor. After the analyst mentions SourceX, the IT director sends five questions.

| # | Question as asked | Routed to | Log entry |
|---|---|---|---|
| 1 | "Would SourceX need remote access to our claims system?" | SourceX, with the IT director copied | Day 1, direct thread opened |
| 2 | "Are they certified?" | Trust center link, and the question to SourceX's security contact | Day 1, link dated |
| 3 | "Which AI company gets our data in the end?" | SourceX | Day 1, buyer identity is SourceX's to disclose or not |
| 4 | "Will the fund see our claim files?" | Answered by the analyst | Day 1: no files, no credentials, no applicant documents |
| 5 | "What happens to anything we send if we walk away?" | SourceX | Day 1, direct thread |

The analyst's reply to the IT director, in full:

> I've sent your questions word for word to SourceX's security contact and copied you, so the answers come straight to you. The one about us: our firm never receives your files or credentials. I won't summarize their replies; if anything is unclear, ask them in the same thread.

Three sentences, one answered question, four forwarded ones, and no opinion anywhere.

## When the questions come from SourceX instead

Once the company applies, SourceX's review may ask how records would be exported and who controls access. Those questions belong to the company's named security or IT owner. If the analyst receives one, forward it to that person with SourceX copied and leave the thread. Where an MSP runs the company's systems, it acts only on the company's written instruction; [MSP client data licensing security](/guides/msp-client-data-licensing-security) covers that role, and [how data is secured in licensing](/proof/what-is-data-security-in-licensing) gives the contract-level picture.

## Where routing still goes wrong

- **The real question is underneath.** "Are they secure?" may mean "we had an incident last year". Pass that context on only if the CEO agrees to it.
- **Loops through the analyst.** Every hop adds days and invites paraphrase. Open the direct thread on the first forward.
- **The fund's own knowledge.** Board materials describe systems in detail. None of it becomes an answer.
- **Status changes.** SourceX's trust center lists planned items next to current ones, so a link sent today may describe a different state next quarter. Date every link.
- **Borrowed timelines.** The two-business-day reply is SourceX's stated aim. Do not promise it on SourceX's behalf.

**Methods note.** The routing sheet was assembled on 2026-10-27 from SourceX's trust center and investor page, section 7 of the program terms, CSA's description of the CAIQ, the Govern function of NIST CSF 2.0 and MAP 4.1 of the NIST AI RMF. It does not measure how often security questions slow an introduction or how quickly they are answered in practice; no such figures have been published. To test the sheet, log every security question for a quarter and count how many you answered yourself. The target is one family only: questions about what the partner sees.

## Next step

> **Refer a company. No cap on rewards.** Default reward on a company's first qualifying transaction: the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap; further qualifying transactions first agreed within 12 months of the first Closing pay 15%. Eligibility and payment conditions apply, including the USD 100,000 Minimum Transaction, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.

When the company's security owner has a direct thread with SourceX and the CEO still wants the conversation, [register](/register) and sign the partner agreement, look at the company against [the screening profile](/who-qualifies), and read [the terms](/terms) before submitting the introduction. Platform teams running this across a portfolio can start with the [overview for venture platform teams](/for/venture-platform-teams).

Routing security questions is referral work; deciding whether SourceX deserves a place in a portfolio is diligence of a different kind, and it starts at the [SourceX investor overview](https://sourcex.si/investors), where materials can be requested.

This article is for information only and is not an offer to sell or a solicitation of an offer to buy securities. Any offering by SourceX is made only to verified accredited investors through its offering documents.

## Sources

- https://refer.sourcex.si/terms
- https://refer.sourcex.si/how-it-works
- https://sourcex.si/trust
- https://cloudsecurityalliance.org/artifacts/cloud-controls-matrix-v4-1
- https://nvlpubs.nist.gov/nistpubs/CSWP/NIST.CSWP.29.pdf
- https://nvlpubs.nist.gov/nistpubs/ai/nist.ai.100-1.pdf
- https://sourcex.si/investors
