A cybersecurity company sells its data to AI by licensing the full trail from alert to resolution, or its private security code, to a buyer like Mercor.
Mercor pays cybersecurity companies $20,000 to $750,000. It wants several years of cases from a company with 20 to 2,000 employees, anywhere.
Two things make this industry harder than most. Much of the data describes your customers, and some security code is export-controlled.
For the full process across every industry, start with our guide to how to sell your company’s data to AI companies.
Key takeaways
- Mercor’s cybersecurity listing pays $20,000 to $750,000 and wants alerts, triage decisions, investigation notes and case write-ups together, not raw logs.
- It rules out “logs without case context” and “customer data the company can’t share.”
- Threat intel you received under TLP can’t be passed on without the original source’s explicit permission.
- Intrusion-software tools and the technology to develop them are export-controlled under ECCNs 4D004 and 4E001.c.
- Giving a foreign national access to that technology counts as a deemed export, even if nothing leaves the country.
- The Cybersecurity Information Sharing Act of 2015 protects threat sharing, not commercial licensing, and it runs out on December 11, 2026.
What cybersecurity data do AI companies buy?
Mercor’s cybersecurity listing, read November 6, 2026, splits it up like this:
| Data | Mercor’s view | Main risk |
|---|---|---|
| Alerts and triage decisions | Core of the license | Customer names and asset inventories |
| Investigation notes and case write-ups | Core of the license | Named victims and unfixed weaknesses |
| Private security code | Core of the license | Export controls and hardcoded secrets |
| SOAR and containment logs | Adds to what you earn | Credentials and internal hostnames |
| Detection rules | Adds to what you earn | Vendor license terms on rule sets |
| Penetration test reports | Adds to what you earn | The client’s NDA and live vulnerabilities |
| Repositories scrubbed of secrets | Adds to what you earn | Keys in the commit history, not just the files |
| Logs without case context | Not a fit | Rejected outright |
Mercor names the companies it wants:
- Managed security and MDR providers
- Enterprises with an in-house SOC
- Security product companies with private code
- Penetration-testing firms
It works with exports from Splunk, Microsoft Sentinel, Google SecOps, CrowdStrike, Defender, SentinelOne, Okta and ServiceNow SecOps.
The questions it opens with tell you what matters. Do you keep case write-ups with the alerts behind them, and is the data yours or your customers’?
How much is cybersecurity data worth to AI companies?
That $20,000 floor is among the lowest on Mercor’s board, and the $750,000 top end sits in the bottom third of its 25 listings.
| Mercor listing | Company earns | Size bar |
|---|---|---|
| Manufacturing and industrial | $100,000 to $1.5 million | 20 to 2,000 employees |
| Law firm | $50,000 to $1.2 million | 5 to 300 attorneys and staff |
| Cybersecurity company | $20,000 to $750,000 | 20 to 2,000 employees |
| Software company | $50,000 to $500,000 | 15 to 500 employees |
Mercor also shows a $75,000 referral fee for cybersecurity companies. That’s paid to someone who refers a company, not to the company.
Our guide to how much company data is worth to AI compares published payouts across industries.
Can you license case data about your customers?
Sort your cases into three piles before you talk to a buyer.
- Your own environment: alerts and investigations on your own network and staff. These are yours to license.
- Customer environments: everything an MDR or MSSP sees for a client. Your MSA governs it, and most make you the processor, not the owner.
- Received intelligence: indicators and reports from vendors, ISACs or peers. Someone else set the terms.
Received intelligence is the pile people forget. The Traffic Light Protocol says a recipient who needs to share more widely than the original marking allows must get explicit permission from the source.
That makes TLP:AMBER and TLP:RED material unlicensable on your own. ISAC membership agreements usually say the same thing in contract form.
Pen test reports carry their own problem. They belong to the client under the engagement letter, and they describe weaknesses that may still be open.
If customer data is the only thing you have, go back to the customer first. An amendment or a written consent turns a dead pile into the most valuable one you own.
Do export controls apply to security tools and code?
15 CFR 740.22 sets out License Exception ACE. It authorizes exports, reexports and in-country transfers of cybersecurity items, subject to the restrictions in paragraph (c).
Those restrictions matter more than the exception. ACE doesn’t reach nationals of Country Group E:1 and E:2, and it limits government end users in Country Groups D:1 and D:5.
The regulation carves out “vulnerability disclosure” and “cyber incident response” from several of those limits. Most defensive work sits in that carve-out.
Deemed exports are the trap. Under 15 CFR 734.13(b), releasing controlled technology to a foreign national in the United States counts as an export to their country.
An AI buyer’s annotation team is global. If your license includes exploit development code or the technology behind it, the people reading it are the export question.
Ask three things before you sign. Who touches the data, in which countries, and will the buyer accept a clause excluding controlled technology from the license.
Manufacturers face the same structure with different rules. Our guide to selling manufacturing data to AI covers ITAR technical data and DFARS flowdowns.
What has to come out before you ship?
| Item | What to do |
|---|---|
| API keys, tokens and passwords | Remove from files and from the commit history, not just the current branch |
| Customer names, domains and asset inventories | Replace with consistent codes across every case |
| Usernames, email addresses and IP addresses | Pseudonymize; these are personal data under the GDPR and state privacy laws |
| Internal hostnames and network diagrams | Generalize, or cut |
| Open vulnerabilities in a named environment | Hold the case back until it’s remediated |
| Live malware samples | Scope separately, with the buyer’s handling terms in writing |
| Third-party detection rules and feeds | Check the vendor license before including them |
Keep the codes consistent across cases. A model learns more from “customer A appears in 40 incidents” than from 40 unlinked ones, and you give up nothing by keeping the link.
Mercor says it signs an NDA, runs the export and removes or protects personal information. A security engineer on your side should still read a sample before delivery.
Our guide to anonymizing data for AI training covers the tools and standards in more detail.
Does the Cybersecurity Information Sharing Act cover this?
The act’s provisions were extended to December 11, 2026, under the Continuing Appropriations and Extensions Act, 2027, according to a Congressional Research Service brief from September 2026.
One part of it is still worth copying. The act requires personally identifiable information to be removed from shared information, which is the right default for a commercial license too.
Your customer notification duties don’t change either. A contract that promised to tell customers before their data goes anywhere new still applies.
Who buys cybersecurity data?
- Mercor: alerts, triage decisions, investigation notes, case write-ups and private security code, for companies with 20 to 2,000 employees anywhere. Pays $20,000 to $750,000.
- micro1: software and engineering, support, sales, legal and operations processes, listed on its data partnerships page, for companies with 30 or more full-time staff. You can apply to micro1 here.
- Polyshares: a company’s own operational record, such as email and ticket history, but not records it holds for clients.
Exclusivity closes doors. Mercor rules out data already licensed exclusively through a broker, so read that clause before you sign the first deal.
Our list of companies that buy business data for AI has each buyer’s terms.
What are the steps for a security company, start to finish?
- Count complete cases. Alerts with the triage decision, the notes and the write-up attached, over several years.
- Split yours from your customers’. Read the MSA and the data processing terms for each account.
- Pull out received intelligence. Anything marked TLP:AMBER or stricter needs the source’s permission.
- Screen the code. Classify anything touching intrusion software against ECCNs 4D004 and 4E001.c before it goes in scope.
- Apply to a buyer. Mercor’s listing scopes the data on a call and asks whose data it is.
- Scrub secrets and identifiers. Commit history included, not just the working tree.
- Have counsel review the license. Our AI data licensing agreement checklist lists the clauses to check, including a ban on re-identification.
- Test a sample. Have an analyst try to name the customer from 20 anonymized cases.
Start with your own environment and closed cases over two years old. Nothing in that pile belongs to a customer, and the weaknesses are long since fixed.
Common mistakes when selling cybersecurity data to AI
The most common mistake is treating customer case files as the company’s own work product. These are the others:
- Shipping raw logs with no case context, which Mercor rejects
- Passing on TLP:AMBER intel without asking the source
- Scrubbing secrets from files but leaving them in the commit history
- Treating IP addresses and usernames as non-personal data
- Including pen test reports that describe weaknesses still open today
- Ignoring deemed exports because nothing physically leaves the country
- Assuming CISA 2015’s liability protections cover a paid license
- Reading Mercor’s $75,000 referral fee as what the company gets paid
Frequently asked questions
Can a cybersecurity company sell its data to AI companies?
Yes, for records it owns and has the right to license. Mercor rules out customer data the company can’t share, so an MSSP usually needs its customers’ written agreement first.
How much do AI companies pay for cybersecurity data?
Mercor’s cybersecurity listing pays $20,000 to $750,000, depending on case volume and rights. The referral fee of up to $75,000 goes to whoever refers the company, not to the company.
What cybersecurity data do AI companies want?
Alerts and triage decisions, investigation notes and case write-ups from the same incidents, plus private security code. SOAR logs, detection rules and pen test reports add to the price.
Do export controls stop you selling security code?
They can. Intrusion-software tools fall under ECCN 4D004 and the technology to develop them under 4E001.c, and License Exception ACE in 15 CFR 740.22 excludes some destinations and government end users.
Can you license threat intelligence you received from an ISAC?
Not on your own. The Traffic Light Protocol requires explicit permission from the original source before sharing beyond the original marking, and ISAC membership agreements usually repeat that.
Does the Cybersecurity Information Sharing Act protect selling data to AI?
No. It protects sharing threat information for cybersecurity purposes, not commercial licensing. Its provisions were extended only to December 11, 2026.
Last updated: November 6, 2026
Disclosure: some links on this page are affiliate links. If you sign up through one, we earn a commission at no extra cost to you.
This isn’t legal advice. Have counsel review any data deal, and your export control lead review anything touching security code, before you sign.






