Kenna Security

Enable the Kenna Security connector in your fastn dashboard, then let each customer authenticate their own Kenna Security account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Kenna Security client code in your app and no per-customer branch in your codebase. Setup is 4 steps.

Yes. Every connection is scoped to the individual customer, so each authorises their own Kenna Security 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.

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 open findings and the assets behind them before recommending what to fix first.

fastn does. When Kenna Security 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.

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.

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.

A common starting point: read their own vulnerability findings into your product, ranked the way they already rank them. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.

It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Kenna Security does not change your per-connector cost. You can start free with 3 connected accounts.