Threat & Vulnerability · Integration
21RISK
Add 21RISK to your product for your customers, and give your AI agents governed access to it.
21RISK exposes a read only OData API under 21risk.com/api/v1/odata with an API key issued from the account. The entity sets cover reports, sites, organisations and risk models, so you can pull completed audit results and the model they were scored against, but you cannot create audits or corrective actions through the public endpoints. Because it is OData, filtering, selection and expansion use $filter, $select and $expand rather than bespoke query parameters, and clients that assume plain REST paging will miss the server driven paging links. On the category: findings and assets map cleanly onto 21RISK audit findings and the sites they attach to, but there is no security detection concept here, so treat that noun as inapplicable. Reports are tied to an audit run, so trending a site over time means grouping by site and run date rather than reading one current score. fastn stores each customer's key, keeps the read only boundary explicit and handles upkeep as the entity sets change.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let a customer connect their own 21RISK account so their audit reports and site risk scores appear in your dashboard
Track risk score movement per site across audit runs and show which locations are deteriorating
Pull the risk model behind a report so users can see which questions drove a score rather than just the number
Feed completed audit findings into your own remediation tracker, since 21RISK itself will not accept writes
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
Ask an agent which sites scored worst on a named risk model in the latest audit round
Have an agent explain the findings behind a site's score, with every read audited per tenant against that customer's key
Let an agent compare two audit runs for a site and report which findings were resolved and which recurred
Example prompt
Which of our sites dropped on the fire risk model between the last two audits?
Set up 21RISK in 4 steps
- 01Enable the 21RISK connector from your fastn dashboard.
- 02Have each customer authorise their own 21RISK account, so calls run under their credentials rather than a shared key.
- 03Decide which findings, detections and assets your product needs, map those fields, then enable the actions and triggers you want.
- 04Call it from your product and expose it to your agents through the same governed connection.
Why teams use the 21RISK integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a 21RISK integration without building it. Your customers connect their own 21RISK 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 21RISK update is not your on-call problem.
- One integration serves your product and your agents. The same governed 21RISK 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
AWS Security Hub
Microsoft Sentinel
CrowdStrike FalconOften used alongside
Tools the same teams tend to run next to 21RISK, across other categories.
ServiceNow
Okta
Datadog21RISK integration FAQ
How do I add a 21RISK integration to my product?
Enable the 21RISK connector in your fastn dashboard, then let each customer authenticate their own 21RISK account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no 21RISK client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own 21RISK account?
Yes. Every connection is scoped to the individual customer, so each authorises their own 21RISK 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 21RISK integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. Ask an agent which sites scored worst on a named risk model in the latest audit round
Who maintains the 21RISK integration?
fastn does. When 21RISK 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 21RISK 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 21RISK 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 21RISK integration?
A common starting point: let a customer connect their own 21RISK account so their audit reports and site risk scores appear in your dashboard. 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 21RISK integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding 21RISK does not change your per-connector cost. You can start free with 3 connected accounts.
Add 21RISK to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.