The trail from alert to resolution is what AI data buyers ask security teams for.

Managed security and MDR providers, in-house SOCs, penetration-testing firms and security product companies: founders and heads of security operations deciding whether case records or code can be licensed.

Mercor's listing for cybersecurity companies puts a deal at $20,000 to $750,000 ("Depends on case volume and rights").

AIData.Broker represents you in selling it: we value your data against public prices, describe it without your name to every buyer whose published rules it meets, at the same time, and help you negotiate the terms, for holders based in the United States, the United Kingdom and Canada. Our fee is 12% of the first $250,000 a sale pays you, and nothing if no sale closes.

1

buyers quoted below on what they want from companies like yours

4 of 4

kinds of record below that the valuation measures or values

2

rights questions to settle before a buyer sees a record

What companies like yours hold

What you typically have, where it sits, and whether the valuation can measure or value it. Buyers price what exists together, over how many years, and how well it links.

  • Alert-to-resolution cases
    Where it sits, and what the evidence shows
    SIEM and endpoint alerts with the triage decision, investigation notes and case write-up, in Splunk, Sentinel, CrowdStrike, ServiceNow or similar.
    How the valuation reads it
    Measured from your tickets exportCounted with tickets and projects
  • Detection rules and playbooks
    Where it sits, and what the evidence shows
    The rules the team wrote and the SOAR playbooks that acted on them.
    How the valuation reads it
    Measured from your documents exportCounted with documents and knowledge
  • Penetration test reports
    Where it sits, and what the evidence shows
    Findings with the steps that proved them.
    How the valuation reads it
    Measured from your documents exportCounted with documents and knowledge
  • Private security code
    Where it sits, and what the evidence shows
    The company's own tools and products, scrubbed of secrets.
    How the valuation reads it
    Measured from your code history exportCounted with code with its historyValue a codebasepriced on its own, per repository

What buyers say they want from companies like you

In their own words, from their own pages or from reporting on what they bought. Each opens its source.

  • “License security alerts, investigations and case write-ups, or security software.”
    Mercor, its listing "Cybersecurity Company"Its own page, 27 Oct 2026
  • “Alert-to-resolution records the company owns, or private security software. The right to license them; customer data only with customer agreement”
    Mercor, what the listing asks forIts own page, 27 Oct 2026
  • “SOAR and containment logs. Detection rules. Penetration test reports. Repositories already scrubbed of secrets”
    Mercor, what it would also likeIts own page, 27 Oct 2026

What raises the value

  • Every case kept whole: the alert, what the analyst decided and why, and how it ended.
  • Several years of cases, false positives included.
  • Data the company owns rather than its customers'.
  • History the listing measures in its own words: "Several years of cases".

What lowers the value

  • What the listing rules out: "Logs without case context", "Customer data the company can't share".
  • Raw logs with no case around them.
  • Repositories that still hold keys or credentials.

A line that quotes a buyer names it. The others are our checklist, drawn from the factors buyers state in general: no buyer publishes how much each one moves a price. How often each factor matters across 156 kinds of data.

The rights to settle first

These stop a sale more often than price does. Each can be settled before any buyer sees a record.

The full rights checklist
  • An MSSP's case data is mostly about its customers' systems: their contracts decide whether any of it can leave, and most need each customer's agreement.
  • Penetration test reports describe a client's weaknesses: licensable only with the client's agreement and with every identifying detail removed.

What is already on offer from companies like you

Read this morning from the brokers' and marketplaces' own catalogues. A buyer compares your records with these; settled rights, more years and more linked systems are what set one apart.

184

lots on offer like yours

4.2 years

of history in the middle of them

11 of 47

say the rights are settled

What holders like you ask

What is a cybersecurity company's data worth to an AI buyer?
Mercor's listing for cybersecurity companies puts a deal at $20,000 to $750,000 ("Depends on case volume and rights"). It asks for 20–2,000 employees (Anywhere). What moves an offer within the range is what the listing names: how complete the records are, how far back they go and whether you can license them.
What exactly does the buyer ask for?
Mercor's listing asks for "Alert-to-resolution records the company owns, or private security software", "The right to license them; customer data only with customer agreement". It would also like "SOAR and containment logs", "Detection rules", "Penetration test reports", "Repositories already scrubbed of secrets". It rules out "Logs without case context", "Customer data the company can't share".
What will a buyer ask us first?
Mercor's listing names its first questions: "Do you keep case write-ups together with the alerts behind them?", "Is the data your own or your customers'?", "Which SIEM and EDR tools do you run?", "Do you have private security software?". Have the answers before you start.
How do we sell through you?
Start with the valuation. It reads what you hold against public prices and against the rules each buyer publishes; then either we run the sale for you, describing your records without your name to every buyer whose rules they meet, or, where a buyer's own programme fits you better, we introduce you to it, free for you. The holder pays us a fee fixed in the mandate, and only if a sale closes. In a sale we run no buyer pays us, so our fee depends on what you are paid, not on which buyer pays it. A buyer pays us only if you choose to apply to it through its own referral programme, and you see that amount in writing before you choose.

In this topic

What sells

  1. Start hereWhich data do AI labs want, and who holds it?Each kind of data the market prices, the businesses that hold it, what labs are asking for now and what they turn away.
  2. GuideWhat Are RL Environments? Who Builds, Buys and Prices ThemAn RL environment is a sandbox where an AI agent attempts tasks with tools and a verifier scores each try. Who builds them, who buys them and what they cost.
  3. GuideHow to Sell Your Videos for AI Training: Prices and BuyersAI companies pay to license your videos for training, by the hour or the minute. What each buyer pays, which footage sells, and the rights every frame needs.
  4. GuideSelling audio and speech recordings for AI trainingWhat AI companies pay for call recordings, podcasts, radio, meeting audio and voice data, why archive audio sells cheapest, and the recording-consent law state by state.
  5. GuideSelling photos and image archives for AI trainingWho buys photos for AI training, what stock agencies pay contributors (shares and bonuses, not prices), what image archives sell for, consent and releases agency by agency, and how to prepare a library for a sale.
  6. GuideSelling your company's Slack data for AI training: what the export allows and who buys itYes, a company can license its Slack history to AI buyers. What Slack's export and API terms allow on each plan, whose messages are inside, what buyers pay and the steps.
  7. GuideSelling company documents and shared drives for AI trainingYes, a company can license its documents, wikis and shared drives to AI buyers. Which documents they pay for, what Google Workspace, Microsoft 365, Confluence and Notion let you export, who owns the files, and the steps.
  8. GuideSelling customer support tickets and chats for AI trainingOften yes, after three checks: your customer contracts and privacy notice, your help desk's export terms, and removing personal data. What buyers want in a ticket, what records with tickets fetch, and the steps.
  9. GuideSelling a company's email archive for AI training: exports, consent and priceYes, a company can license its own email to AI buyers. How Google Workspace and Microsoft 365 let you export a whole organisation's mail, the deadlines when a subscription lapses, the law on staff and customer messages, and what buyers pay.
  10. GuideSelling CRM data for AI training: Salesforce and HubSpot records, consent and priceA company can license its CRM history to AI buyers, but CRM records are customer data first. What buyers value in Salesforce and HubSpot, how each lets you export, why the contact list usually stays out, and what CRM history fetches.
  11. GuideSelling meeting recordings and transcripts for AI trainingCan a company license its Zoom, Google Meet or Teams recordings and notetaker transcripts to AI buyers? Recording consent state by state, what Zoom's terms allow, what meeting audio and transcripts fetch, and the steps.
  12. GuideSelling accounting and finance records for AI training: QuickBooks, Xero and NetSuiteA company can license its accounting history to AI buyers, but finance records carry customers', suppliers' and lenders' confidential terms and staff payroll. What buyers value in QuickBooks, Xero and NetSuite books, how each lets you export, what has to come out, and what finance records fetch.
  13. GuideSelling Jira and Linear issue history for AI trainingYes, a company can license its Jira or Linear issue history to AI buyers. It is valued when each issue links to the code that closed it. What each export keeps, what buyers ask for, and what it fetches.
  14. GuideSelling design files and product history for AI training: Figma and beyondYes, a company can license its Figma files and design history to AI buyers. What buyers value, what Figma lets you export, client work, fonts and other assets that are not yours, who owns the designs, and the steps.
  15. GuideSelling IT service desk records for AI training: ServiceNow tickets, runbooks and incidentsOften yes. IT tickets, incidents and runbooks teach agents to resolve real problems, once credentials, hostnames and people are removed. What ServiceNow and Jira Service Management let you export, what buyers ask for, and what the records fetch.
  16. GuideSelling Books to AI Companies: Prices, Deals and Who Gets PaidAI companies license books by the title, mostly from publishers' backlists. What deals paid per book, how much reaches the author, and how to sell a catalogue.
  17. GuideSelling Game Code and Game Data to AI CompaniesAI companies license game studios' code with its history and gameplay recorded with the player's inputs. Who buys, what studios are offered, and what you may not sell.
  18. PageWhere data comes fromWho holds each kind of data, how much exists and how it reaches buyers.
  19. RegisterCompanies closingCompanies closing, sold or gone dark, and the records they leave.

See what you hold, measured on your own computer. Only the counts leave it.