# Cybersecurity advisor data referral handoff | SourceX

Canonical: https://refer.sourcex.si/guides/a-cybersecurity-advisor-s-role-in-a-data-introduction
Last updated: 2026-11-05

Your privileged access exists because the client hired you to protect its systems, so it gives you no standing to export, sample, size or vouch for its records in a licensing deal. What security work does give you is timing: retention reviews, system retirements and data mapping put old records in view before anyone else notices them. Your part is narrow. Spot the moment, tell the person who would sponsor it that SourceX exists and that you could be paid, let the CEO decide, and stay out of grading the risk of a deal you have a stake in.

This page is for vCISOs, MSSP account leads and MSP engineers who run security work. Routing a CEO's security questions is covered in [handing off security questions](/guides/how-to-hand-off-security-questions-without-interpreting-the-answers), a security firm's own records in [cybersecurity services firms](/industries/refer-cybersecurity-services-firm-data-licensing) and the practice economics in [vCISO referrals](/for/vciso-additional-revenue). The subject here is your position: what you hold, what you may say and when you go quiet.

## Why a referral from the security advisor sounds like an endorsement

When the person who usually says "do not move that data" mentions a company that licenses data, the client hears a verdict: our security advisor thinks this is safe. You have not assessed SourceX, and while a reward is possible you are the wrong person to do so.

The client's own framework already expects roles like yours to be written down. Subcategory GV.SC-02 of NIST's Cybersecurity Framework 2.0 reads: "Cybersecurity roles and responsibilities for suppliers, customers, and partners are established, communicated, and coordinated internally and externally." Your service contract defines the security role. A referral sits outside it, so name it as a second role rather than slipping it into a status call.

Professional codes point the same way. ISACA's Code of Professional Ethics, at item 4, has members keep information obtained in the course of their activities private and confidential unless a legal authority requires disclosure, and says that information "shall not be used for personal benefit or released to inappropriate parties." A referral reward is a personal benefit. So every fact you pass toward SourceX has to come from the CEO or be confirmed by the CEO, never from what your consoles showed you.

| What your access shows you | Why the client granted it | What it must never turn into |
|---|---|---|
| Endpoint and SIEM telemetry | Detection and response | A measure of how busy or how large a system is, quoted to an outsider |
| Mailbox and file search rights | Investigating incidents | A sample, a keyword hit count or a volume figure for SourceX |
| Backup consoles and restore points | Recovery | Proof of how far back history goes, offered as a selling point |
| Classification and data-loss reports | Protecting sensitive data | A map of what might be licensable |
| Asset inventories and scan results | Reducing exposure | A system list sent outside the company |

## Security work that brings a licensing question into view

Finish the billable work item first, then decide whether the moment fits.

| Event in your engagement | What surfaces | Who might sponsor it inside the company | Hold off when |
|---|---|---|---|
| Retention schedule review | Years of records kept with no rule requiring them, and a plan to delete | Compliance lead or COO | A litigation hold, a regulator or an investigation is driving retention |
| Decommissioning a legacy application | An archive with a shutdown date | IT director or the system's owner | The archive holds customers' records rather than the company's own |
| Data mapping for a framework assessment or insurance renewal | Which systems hold the company's own work records and which hold customers' | COO or head of IT | The map was commissioned under terms that limit its use |
| Tenant consolidation after an acquisition | Two companies' histories landing in one place | The integration lead | The deal has not closed: until then the target's CEO decides for the target |
| Incident response or a breach investigation | Nothing you should act on | Nobody | Always: wait until the incident is closed and the retainer conversation is over |

A sponsor carries the question; the CEO answers it. A CISO, IT director or compliance lead can raise the idea internally, but the decision to discuss licensing, and the signature, are the CEO's. Once an acquisition closes, the acquirer's CEO decides for the business it bought.

## The security-role referral handoff

Read the table across: at every stage, each of the three parties has its own job, and the right-hand column is the sentence that hands the stage on.

| Stage | Technical custodian: your firm | Customer owner: the CEO and the company's staff | SourceX | Your handoff sentence |
|---|---|---|---|---|
| 1. Spot, during paid work | Notes the event privately, never in the client's ticket or report | Unaware | Not involved | None yet |
| 2. Mention, after the work item closes | Tells the sponsor SourceX exists, discloses the possible reward, sends the screening page | The sponsor chooses whether to take it to the CEO | Not involved | "I'm raising this as a SourceX referral partner, separately from our security work, and my firm could be paid if a deal closes." |
| 3. Decide | Answers questions about the company's own controls only | The CEO decides whether to talk | Not involved | "Whether to go ahead is your call; I'll stay out of judging the deal itself." |
| 4. Introduce | Submits through the partner link after a written yes, carrying only facts the CEO confirmed | The CEO expects SourceX's contact | Receives the introduction and checks its own records for an earlier relationship | "SourceX will contact you directly, and you don't need me on those calls." |
| 5. Review | No part; completes no questionnaire about the client's systems | Lists its own systems, years and what it can export; answers its own rights questions | Checks fit, completes the inventory with the company, runs the rights check, sets the processing route | "That question is for SourceX; I'm not the right source." |
| 6. If the company signs | No access for the deal; ordinary security work carries on | Signs its agreements and settles scope | Has data extracted, transferred and de-identified through approved processing routes after its go-ahead | "Preparation is arranged between you and SourceX, outside my role." |

Two rules hold through all six stages. Your line goes flat after stage 4: SourceX deals with the company directly, and section 2.2 of the unsigned partner agreement sample says the partner need not join every call, email or negotiation. And whenever the CEO asks whether the deal is safe, you disclose your stake before you say anything else, which the next sections turn into words.

**Method note.** The stages follow SourceX's own published process and its referral terms (Version 2026-10-22.2, since replaced by version 2026-11-04), the partner agreement's unsigned 2026-10-19 sample and the screening page, all read on 2026-10-27; GV.SC-02 and ISACA's item 4 frame the security role. It has not been tested in live engagements, and nothing has been published on how clients react when their security advisor raises a referral.

## What your admin roles were granted for, and what they were not

Hold three things apart, because a security engagement blurs them more than most IT work does.

| | Who holds it | Where it comes from | What it decides |
|---|---|---|---|
| Access | Your firm | Credentials and delegated roles the client grants for a defined service, revocable at will | How you protect, monitor and recover the client's systems |
| Service duty | Your firm, to the client | The service contract and its confidentiality terms | What you must do for the client, and what you must keep to yourself |
| Licensing authority | The company, through its CEO | Who created the records, the company's customer contracts and SourceX's rights check | Whether anything is licensed at all |

None of the three borrows from another. Your partner agreement adds nothing to your access either: section 4.2 of the sample withholds any authority to pass on a supplier's inventory, records, raw data or personal information, and any right to reach into extraction systems. When the company applies, it describes its own systems and confirms its own rights, including that its personal data was collected lawfully and that the records have never been licensed for AI training.

If you run a SOC or managed detection service, client telemetry you hold is the client's, and SourceX's screening guidance lists client-owned material among the things that rarely pass. Licensing your firm's own playbooks would make you a supplier, not a referrer.

## The conflict to name before the CEO asks you

Sooner or later the CEO says: "You're our security person. Is this safe?" You have three honest moves, in this order.

1. **Disclose.** "Before I answer: if you sign, SourceX may pay my firm a referral reward, so I have a stake."
2. **Answer only for the company's side.** Which systems exist, who administers them, what your contract covers, and what you would need in writing before touching anything.
3. **Send the rest elsewhere.** Questions about SourceX's handling go to SourceX, with its published process page. If the CEO wants an independent view of the deal itself, suggest someone with nothing to gain: the company's counsel, a board member or another adviser.

Never say the deal is secure, that nothing will leave the client's environment, that records will be de-identified to a particular standard or that the company will be accepted. SourceX publishes less than that: no records change hands when the company applies, and only after its go-ahead is data extracted, transferred and de-identified through approved processing routes. Send the page instead of retelling it; the wider list is in [what not to promise clients about data privacy](/guides/what-not-to-promise-clients-about-data-privacy).

## A vCISO, a retention review and a 260-person claims administrator (Illustrative)

Illustrative. A 260-person claims administrator retains a vCISO from an MSP. The facts and dates are invented and imply no outcome.

| Date | What happened | Role in play | Recorded where |
|---|---|---|---|
| Feb 4 | Quarterly retention review: claim files go back to 2009, and pre-2016 archives are due for deletion in the third quarter | Custodian, paid work | The client's review report |
| Feb 11 | After the review closes, the vCISO tells the COO that SourceX exists and that the MSP could earn a reward | Referrer | The MSP's own partner log |
| Feb 18 | The CEO asks the vCISO whether licensing is safe; the vCISO discloses the stake, describes only the company's own controls and points to SourceX | Referrer, stepping back | Partner log |
| Feb 20 | The CEO says yes in writing; the vCISO submits the introduction with the peak headcount and the claims system's start year, both as the CEO stated them | Referrer | Partner link |
| Mar 10 | The COO asks the vCISO to pull a count of claim files for SourceX; the vCISO declines and the company gives its own figure | Custodian, declining | Partner log |

The deletion plan stayed on the company's schedule. Retention advice is security work, and a possible referral never bends it; a documented deletion date is real urgency for the CEO's decision, not a reason for the advisor to delay a control.

Suppose SourceX later paid the company $400,000 under its Dataset Deal Confirmation. On the 2026 terms the MSP's reward would be USD 70,000: USD 50,000 plus 5% of the payout comes to USD 70,000, more than the 15% alternative of USD 60,000, and no cap limits it. SourceX would pay the MSP from its own funds once every payment condition is met, with nothing taken from the company's agreed compensation. SourceX does not publish how it prices offers.

## An introduction note with no security verdict in it

The note carries four kinds of fact and nothing your tools produced:

- That you write as a SourceX referral partner, separately from your security work.
- That your firm may be paid if a deal closes.
- The company's name and its CEO, who has said yes.
- Peak full-time headcount and the main systems and years, each as the CEO stated them.

Leave out risk ratings, anything measured from a console, statements about SourceX's controls, claims that the company qualifies, incident history and customer names. Section 4.6 of the agreement sample bars telling a referred company that an indicative estimate, positive interest, a signature or a data upload makes a purchase or reward certain, and a security advisor's "it's fine" weighs more than most such hints.

## Where the two roles collide anyway

- **You are the only security voice the CEO has.** A vCISO may be all the security function a company owns. Say so plainly and suggest the CEO bring in counsel or a board member for the deal-level call.
- **Regulated records.** Health, payment or government records carry their own rules; leave them to the company and SourceX's rights check.
- **An open investigation.** No mention until it is closed, whatever the retention calendar says.
- **Policies on both sides.** Your firm may restrict third-party payments, and the client may bar suppliers from earning them. Check both before the first mention.
- **Groups.** A parent and its subsidiaries count as one referred company, so the USD 50,000 floor applies once across the group. Whether a sister company's earlier contact with SourceX, or another partner's introduction of one, affects your credit is not set out in the terms; SourceX settles that in duplicate review.

## 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 a security engagement turns up a retention or retirement decision and the CEO wants the conversation, [register as a partner](/register); keep the [screening criteria](/who-qualifies) and the [program terms](/terms) open while you write the introduction note. Brokers working the same signals from the insurance side can compare [cyber renewal questionnaires](/guides/cyber-insurance-renewal-questionnaire).

## Sources

- https://refer.sourcex.si/terms
- https://sourcex.si/documents/partner/SourceX_Channel_Partner_Agreement_Sample.pdf
- https://sourcex.si/how-it-works
- https://refer.sourcex.si/who-qualifies
- https://nvlpubs.nist.gov/nistpubs/CSWP/NIST.CSWP.29.pdf
- https://www.isaca.org/code-of-professional-ethics
