Security & Identity · Integration
CyberArk Identity
Add CyberArk Identity to your product for your customers, and give your AI agents governed access to it.
Embed a CyberArk Identity integration so your customers can manage their own users, roles, application assignments, and access policies from inside your product, with governed agent access to the same records. Identity changes carry a large blast radius, so each customer grants only the scopes your enabled actions need, permissions are scoped per tenant, and every call is recorded. fastn handles per-customer authorisation and API upkeep, so supporting another tenant 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 users and roles into your product so access questions are answered where the work happens.
Provision or deprovision a user from your product when someone joins, moves, or leaves.
Read application assignments so your product shows what a user can actually reach.
Trigger your product when a user, role, or assignment changes.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent reads a user's roles and application assignments before answering an access question.
An agent grants or removes access within governed permissions, with every action audited.
An agent reacts to a role change and runs the next provisioning step.
Example prompt
List users with administrative roles who have not signed in for 60 days.
Set up CyberArk Identity in 4 steps
- 01Open the CyberArk Identity connector from your fastn dashboard.
- 02Have each customer authenticate their own CyberArk Identity tenant with least-privilege scopes.
- 03Map the user, role, and application 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 CyberArk Identity integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a CyberArk Identity integration without building it. Your customers connect their own CyberArk Identity account inside your product and work their users, groups and roles there, with no per-customer code on your side.
- Handle the part that actually costs time: the blast radius of an error is large, so least-privilege and auditability are non-negotiable. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a CyberArk Identity update is not your on-call problem.
- One integration serves your product and your agents. The same governed CyberArk Identity connection powers in-product features and gives AI agents scoped, audited access, so you keep access and identity in step across a customer's estate without wiring it twice.
Used by these teams
Compare with
Okta
Microsoft Entra IDWorks well with
CyberArk ConjurOften used alongside
Tools the same teams tend to run next to CyberArk Identity, across other categories.
ServiceNow
Datadog
PagerDuty
AWS CloudWatchCyberArk Identity integration FAQ
How do I add a CyberArk Identity integration to my product?
Enable the CyberArk Identity connector in your fastn dashboard, then let each customer authenticate their own CyberArk Identity account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no CyberArk Identity client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own CyberArk Identity account?
Yes. Every connection is scoped to the individual customer, so each authorises their own CyberArk Identity account and only ever sees their own users, groups and roles. 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 CyberArk Identity 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 a user's roles and application assignments before answering an access question.
Who maintains the CyberArk Identity integration?
fastn does. When CyberArk Identity 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.
What permissions does the CyberArk Identity integration need?
Only the scopes required for the actions you enable. Each customer grants access to their own CyberArk Identity tenant, permissions are scoped per tenant, and every call is recorded so an access change can be traced to its source.
Can access changes be automated safely?
Yes. Provisioning and deprovisioning can be driven from your product or an agent within governed permissions, with every action audited, which is what makes automated access changes reviewable after the fact.
What can I build with the CyberArk Identity integration?
A common starting point: read their own users and roles into your product so access questions are answered where the work happens. 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 CyberArk Identity integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding CyberArk Identity does not change your per-connector cost. You can start free with 3 connected accounts.
Add CyberArk Identity to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.