Threat & Vulnerability · Integration
Cisco SecureX
Add Cisco SecureX to your product for your customers, and give your AI agents governed access to it.
Embed a Cisco SecureX integration, previously Cisco Threat Response, so your customers can work their own incidents, observables, and investigations from inside your product. Only the scopes required for the actions you enable are requested, each customer grants access to their own organisation, and every call is recorded so an investigation step can be traced to its source. fastn handles per-customer authorisation and API upkeep, so onboarding an organisation is configuration rather than a release.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let customers read their own incidents and their linked observables into your product.
Enrich an observable from inside your product so analysts get verdicts without leaving your app.
Create or update an investigation from your product so casework stays in one place.
Trigger your product when an incident is created or its severity changes.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent enriches the observables on an incident and summarises what is known.
An agent creates or updates an investigation within governed permissions, with every action audited.
An agent reacts to a new high-severity incident and assembles the context a responder needs.
Example prompt
List incidents opened today by severity and show the observables each one is built from.
Set up Cisco SecureX in 4 steps
- 01Open the Cisco SecureX connector from your fastn dashboard.
- 02Have each customer authenticate their organisation with least-privilege API credentials.
- 03Map the incident, observable, and investigation 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 Cisco SecureX integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Cisco SecureX integration without building it. Your customers connect their own Cisco SecureX 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 Cisco SecureX update is not your on-call problem.
- One integration serves your product and your agents. The same governed Cisco SecureX 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
Cisco Secure EndpointWorks well with
Cisco MerakiOften used alongside
Tools the same teams tend to run next to Cisco SecureX, across other categories.
ServiceNow
Okta
Datadog
Microsoft Entra IDCisco SecureX integration FAQ
How do I add a Cisco SecureX integration to my product?
Enable the Cisco SecureX connector in your fastn dashboard, then let each customer authenticate their own Cisco SecureX account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Cisco SecureX client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Cisco SecureX account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Cisco SecureX 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 Cisco SecureX 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 enriches the observables on an incident and summarises what is known.
Who maintains the Cisco SecureX integration?
fastn does. When Cisco SecureX 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 Cisco SecureX 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 Cisco SecureX 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 Cisco SecureX integration?
A common starting point: read their own incidents and their linked observables into your product. 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 Cisco SecureX integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Cisco SecureX does not change your per-connector cost. You can start free with 3 connected accounts.
Add Cisco SecureX to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.