Integrations
Connect Nuxari to your identity providers, SaaS applications, ticketing systems, and cloud platforms.
Last updated: June 2026
Who this is for
Admins configuring Nuxari's connections to external systems and platforms that your organization manages or relies on.
Before you start
You need the Admin or Owner role to add, modify, or remove integrations. Credentials for the external system must be prepared in advance and should have the minimum required permissions, not administrative access unless specifically required.
Integrations vs. connectors
In Nuxari, integrations are the configured connections to external systems, the authentication credentials, endpoints, and settings. Connectors are the operational engines that run against an integration to collect data, evaluate policy, and execute actions. You set up an integration once; connectors are what run governance work against it. SeeConnectors for the connector reference.
Supported integration types
- ·Identity providers: Microsoft Entra ID (Azure AD), Okta, Google Workspace, Keycloak, and other SAML/OIDC-compatible identity platforms. Used for user lifecycle governance, access reviews, and SSO.
- ·Microsoft 365: Exchange Online, SharePoint, Teams, and OneDrive. Used for license governance, access reviews, and provisioning workflows.
- ·Ticketing and service management: Jira Service Management and ServiceNow. Used for creating and closing service tickets as part of approval and remediation workflows.
- ·Cloud platforms: Azure, AWS, and GCP. Used for cloud governance posture checks and resource findings.
- ·HR and directory systems: Workday and similar HR platforms. Used as the source of truth for employee status during onboarding and offboarding workflows.
- ·Custom integrations: Use the import pipeline to ingest findings or data from tools not natively supported. CSV and JSON formats are accepted.
How to add an integration
- 1In Nuxari, go to Platform > Integrations.
- 2Click Add Integration and select the type from the catalog.
- 3Enter the required credentials: client ID, tenant ID, API key, or OAuth configuration depending on the integration type.
- 4Nuxari validates the connection by running a test call to the external system.
- 5Once validated, the integration is available for connectors to use. An audit event is generated capturing the configuration.
Integration lifecycle
- ·Active, the integration is connected and available for connectors.
- ·Degraded, Nuxari detected a connection problem on the last health check. Review the error and re-validate credentials.
- ·Disabled, the integration has been manually paused. Connectors using it will not run until it is re-enabled.
- ·Archived, the integration has been removed. Historical records are preserved but no new connector work can run against it.
Importing findings from external tools
If your team uses an external security or CSPM tool, you can import its findings into Nuxari using the import pipeline:
- ·CSV: include columns for title, severity, source system, affected resource, and description.
- ·JSON: submit an array of finding objects with equivalent fields.
- ·Imported findings are enriched with Nuxari's control mappings and flow through the same remediation pipeline as native findings.
Related docs
Connectors
Run governance work against your configured integrations
Edge Agents
On-premises connectivity for systems not reachable from the cloud
Settings
Workspace security policy and SSO configuration
Audit Log
Integration configuration events in the audit trail
Cloud Governance
Governance posture for cloud platform integrations