Integrations
Keep your tools. Connect them.
ResiliencePilot connects to the service desk, identity and training tools you already run. Incidents, people, devices and training records flow into one connected record, without a big migration.
ResiliencePilot
Works with the tools you already run
- ServiceNow
- Jira
- Freshdesk
- Microsoft Entra ID
- Microsoft Intune
- KnowBe4
- xAPI
- SAML 2.0 · OIDC
What connects
Your teams keep working where they are
Each connection feeds the part of the platform that needs it, so the record stays current without anyone retyping it.
Service desk and ITSM
- ServiceNow
- Jira
- Freshdesk
Incidents raised in your service desk arrive in ResiliencePilot automatically, so the risk, continuity and regulatory side sees them as they happen.
- Your own status, severity and field mapping
- Connect with OAuth (ServiceNow, Jira) or an API key (Freshdesk)
- Connection health checked regularly
FeedsOperations: incident management, linked to services, risks and controls, with DORA and NIS2 deadlines
Identity
- Microsoft Entra ID
- SAML 2.0
- OIDC
Single sign-on for your people, and a directory check that reads MFA coverage, guest and dormant accounts, admin roles and Conditional Access, then turns gaps into findings.
- Import the users you choose, not the whole directory
- Findings raised and resolved as your directory changes
- MFA and role-based access, down to the action
FeedsAssurance: readiness checks and findings. Settings: users
Devices
- Microsoft Intune
Managed devices land in your asset register, matched against the assets you already have so nothing is counted twice.
- Matched by serial number, then MAC address
- Alongside assets found by the discovery agent
- The same assets your BIA dependencies and incidents point to
FeedsOperations: asset management. Continuity: dependencies
Security awareness
- KnowBe4
- xAPI
Training enrolments and phishing simulation results from KnowBe4, and completions from any learning platform that supports xAPI, matched to your people.
- Click and report rates next to your training records
- xAPI credentials you generate and revoke for each tool
- Training records ready to use as evidence
FeedsAssurance: training and security awareness
How it fits together
In from your tools, out to the people who need it
Your tools
- ServiceNow, Jira, Freshdesk
- Entra ID and Intune
- KnowBe4 and your learning platform
- CSV import
One connected record
Assets feed risk. Risk feeds continuity. Continuity feeds incidents.
Out to
- Webhooks, 32 event types
- Reports and audit packs
- Regulatory reports, approved by your team
Open by design
Nothing locked in, nothing left out
Webhooks
Send events to your own systems the moment they happen, signed and retried.
- incident.created
- bcp.activated
- crisis.declared
- evidence.expired
- change.approved
Import what you have
Bring existing records in by CSV, including incidents, assets, business services and control mappings. A one-off, not a project.
Sign in your way
Enterprise SSO via SAML 2.0, OIDC and Microsoft Entra ID, with MFA and role-based access across every module.
Integrations FAQ
- No. Your service desk, identity provider and training tools stay where they are and connect in. Records you keep today in spreadsheets or documents, such as a risk register or BIAs, come in once by import and from then on live in ResiliencePilot.
- Into ResiliencePilot from your service desk, Entra ID, Intune, KnowBe4 and your learning platform. Out of ResiliencePilot through webhooks, reports and audit packs. Regulatory reports are drafted and approved in the platform and submitted by your team.
- OAuth tokens and API keys are encrypted at rest, and you can disconnect a connection at any time. Everything is hosted and processed in the EU, on Microsoft Azure (Sweden Central).
- Often, yes, through webhooks, xAPI or CSV import. Tell us what you run and we'll show you how it fits in the walkthrough.
Do we have to migrate everything?
Which way does the data flow?
How are connection credentials protected?
Our tool isn't listed. Can it still connect?
See it connected to your stack
A 30-minute walkthrough, mapped to your framework and the tools you already run.