Threat & Vulnerability · Integration
CybelAngel
Add CybelAngel to your product for your customers, and give your AI agents governed access to it.
Embed a CybelAngel integration so your customers can read their own external exposure alerts and the assets each one relates to from inside your product, with governed agent access to the same findings. Each customer grants access to their own CybelAngel account, permissions are scoped per tenant, and every call is recorded so a finding can be traced to its source. fastn handles the authorisation and API upkeep, so an API change lands in the connector rather than your backlog.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let customers read their own exposure alerts into your product so external risk sits with the rest of their security workflow.
Read the assets and details attached to an alert so your product can route it to the right owner.
Update alert status from your product so triage happens where your users already work.
Trigger your product when a new alert is raised or an existing one changes status.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent reads an alert and its affected assets before summarising the exposure.
An agent updates alert status or ownership within governed permissions, with every action audited.
An agent reacts to a new critical alert and runs the next response step.
Example prompt
Summarise alerts raised this week by severity and list the assets each one affects.
Set up CybelAngel in 4 steps
- 01Open the CybelAngel connector from your fastn dashboard.
- 02Have each customer authenticate their own CybelAngel account with least-privilege scopes.
- 03Map the alert and asset fields your product uses, then enable actions and triggers.
- 04Call them from your product, or expose them to an agent through the MCP server.
Why teams use the CybelAngel integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a CybelAngel integration without building it. Your customers connect their own CybelAngel account inside your product and work their findings, detections and assets there, with no per-customer code on your side.
- Handle the part that actually costs time: a rescan re-reports everything, so the same finding arriving twice must not read as two problems. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a CybelAngel update is not your on-call problem.
- One integration serves your product and your agents. The same governed CybelAngel connection powers in-product features and gives AI agents scoped, audited access, so you get security findings in front of the people and systems that act on them without wiring it twice.
Used by these teams
Compare with
CrowdStrike Falcon
Microsoft SentinelWorks well with
AbuseIPDBOften used alongside
Tools the same teams tend to run next to CybelAngel, across other categories.
ServiceNow
Okta
DatadogCybelAngel integration FAQ
How do I add a CybelAngel integration to my product?
Enable the CybelAngel connector in your fastn dashboard, then let each customer authenticate their own CybelAngel account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no CybelAngel client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own CybelAngel account?
Yes. Every connection is scoped to the individual customer, so each authorises their own CybelAngel account and only ever sees their own findings, detections and assets. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this CybelAngel integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. An agent reads an alert and its affected assets before summarising the exposure.
Who maintains the CybelAngel integration?
fastn does. When CybelAngel changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
How does a new CybelAngel finding reach my product?
Through event triggers rather than polling, delivered per tenant, so your product reacts when a finding is raised or its severity changes rather than on a schedule that is always slightly out of date.
How is CybelAngel finding noise kept manageable?
Findings are deduplicated per asset so a rescan does not re-raise what you already have, and you can filter by severity and status before anything reaches your product. That matters more here than in most integrations, because the volume is what stops teams acting on any of it.
What can I build with the CybelAngel integration?
A common starting point: read their own exposure alerts into your product so external risk sits with the rest of their security workflow. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the CybelAngel integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding CybelAngel does not change your per-connector cost. You can start free with 3 connected accounts.
Add CybelAngel to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.