Bring leak findings into the tools you use
Six connections, six separate data paths. Choose your tool to see who initiates the request, what is carried, and whether it can be used today.
For connections that require the Enterprise plan, talk to our team
Choose your tool
LeakData
Claude
- Initiated by
- You, when you ask in Claude
- Carries
- A short leak summary and counts for the prefix group
- Status
- Listed in the Connectors Directory as a Community connector.
- LeakData access
- Your primary email verified. Every plan includes the connector with a daily request limit.
The arrow starts from the side that initiates the request. The response travels in the opposite direction.View
Current status of the six connections
Compare each connection's availability and the access required to set it up.
| Tool | What it does | Connection flow | Status | LeakData access |
|---|---|---|---|---|
| Available | ||||
| Claude | Lets you query, from Claude, the leak summary for your verified primary email and a password hash prefix. | Tool queries LeakData | Listed in the Connectors Directory as a Community connector. | Your primary email verified. Every plan includes the connector with a daily request limit. |
| Okta | Sends a signed risk signal to Okta when a verified high-severity leak occurs; your Okta policy makes the decision. | LeakData sends | Listed in the Okta Integration Network as LeakData Shared Signals. | Enterprise with SIEM integration access. |
| Conditional setup | ||||
| GitHub | Matches public member emails against your verified domains; shows aggregate counts only. | LeakData reads the tool | Available when the GitHub provider is enabled. | A LeakData account and ownership-verified domains; domain limits follow your plan. |
| AWS Security Hub | Sends verified findings to Security Hub in ASFF format, without personal data. | LeakData sends | Customer-private connector; AWS catalog listing is pending. | Enterprise with SIEM integration access. |
| Elastic Security | Elastic Agent pulls leak alerts that contain no personal data from LeakData. | Tool pulls from LeakData | Candidate package; not yet in the Elastic Package Registry. | Enterprise with SIEM integration access. |
| Not yet available | ||||
| Microsoft Security | A Security Copilot agent is being prepared to compare the LeakData summary with Sentinel delivery records. | Tool queries LeakData | Certification pending | Preview access is not open yet; you can submit a request. |
Arrows show the side that initiates the request. The response travels in the opposite direction.
What to know before setup
Connection direction and release status are separate things.
How a connection carries data doesn't tell you whether it is available today. Read both in the same row of the comparison.
Okta, AWS Security Hub, and Elastic Security require Enterprise SIEM access.
Claude connects on every plan, with a daily request limit. GitHub requires verified domains; the domain limit depends on your plan.
Microsoft Security is not yet available.
Preview access has not opened yet and certification is pending. There is no connection you can set up today.
Alongside corporate services
Each integration has a different data scope and different access requirements; compare them to find the right connection for your needs.
Let's talk about which connection is right for you
Talk to our team about integrations that require the Enterprise plan.