Integrations

Asenion connects to external systems through named connections configured in Settings → Connections. Connections are scoped to an organization and managed by Org Admins.

Category Systems What it enables
Cloud platforms Azure, AWS, GCP Model discovery and test evidence
Experiment tracking MLflow Linking test runs to assessment controls
Work management Jira Corrective action and assignment tickets
Knowledge base Confluence Importing pages and attachments as evidence
Notification channels Slack, Microsoft Teams Risk alert and workflow delivery
ITSM ServiceNow Ticketing from governance actions
Identity Okta, Microsoft Entra ID Single Sign-On for organization members

Credentials supplied on any connection are encrypted at rest and are only ever used server-side — no integration secret is exposed to the browser.

Cloud Platform Connections

Connect Asenion to your cloud AI infrastructure to enable Model Discovery — automatic scanning and import of deployed AI models into your inventory.

Platform What connects
Azure Azure Machine Learning workspaces
AWS AWS SageMaker endpoints and models
GCP Google Cloud Vertex AI model registry

Each connection requires:

  • A display name for the connection
  • Account / subscription / project credentials (service principal, access key, or service account)
  • Region or workspace name (platform-dependent)

Once connected, Asenion can scan the platform and surface deployed models for review and import. See Model Discovery.

MLflow Connections

MLflow connections link Asenion to an MLflow experiment tracking server so that test run results can be imported as assessment evidence.

Each MLflow connection requires:

  • A display name
  • The MLflow tracking server URL
  • Optional username and password (for authenticated tracking servers)

Once connected, users can browse MLflow experiments and runs from within an assessment and link a specific run’s metrics directly to policy controls — auto-populating scored answers from test results. See Assurance for how MLflow evidence flows into assessments.

Jira

A Jira connection lets Asenion raise issues in your Atlassian Cloud Jira project so that governance work is tracked in the same backlog your delivery teams already use.

Configuration

From Settings → Connections → Connect to Jira:

Field Description
Site URL Your Atlassian Cloud site, e.g. https://your-org.atlassian.net. Only https Atlassian Cloud sites are accepted.
Email The Atlassian account email that issues are created as.
API token An Atlassian API token for that account. Encrypted at rest and never returned to the browser.
Default project key The Jira project that GRC issues are created in, e.g. GRC.
Default issue type Issue type used when creating issues. Defaults to Task.

Credentials are validated against Jira before the connection is saved, so a bad token or an unreachable site is reported immediately rather than at the first ticket. If you already have a Confluence connection on the same Atlassian site, you can reuse its site URL and email when creating the Jira connection.

What Asenion creates in Jira

Trigger Issue created
Risk alert raises a corrective action [GRC] Corrective action: <risk dimension> rose to <status> for <AI system>
Assessment assignment (review, approval, submission) [GRC] <Assignment type>: <assessment> (<AI system>)
Manual Create Jira ticket action on an assignment Same as the assignment issue above

Every issue includes a description with the context of the change, the owner, and a deep link back into Asenion. Issues are labelled asenion, grc, and either corrective-action or the assignment type, and carry the Asenion due date as the Jira due date. Once created, the Jira key and URL are stored on the Asenion record so the ticket can be opened from the assignment.

Behaviour and limits

  • Ticket creation is opt-in per AI system: enable Create Jira tickets for corrective actions under AI System → Settings → Risk Alerts.
  • Automatic creation is best-effort. If Jira is unreachable, the risk alert, corrective action record, assignment, and email still complete — only the ticket is skipped.
  • The manual Create Jira ticket action reports failures directly, and refuses to create a second issue for an assignment that already has one linked.
  • If no active Jira connection exists, the Jira actions are hidden rather than failing on click.

Confluence

A Confluence connection lets teams import existing governance documentation from your wiki straight into an AI system’s Document Hub instead of downloading and re-uploading it by hand.

Configuration

From Settings → Connections → Connect to Confluence:

Field Description
Site URL Your Atlassian Cloud site, e.g. https://your-org.atlassian.net.
Email The Atlassian account email used to read Confluence.
API token An Atlassian API token for that account. Encrypted at rest.
Default space key The space shown first when importing, e.g. POLICY. Other spaces can still be browsed.

The connection is validated against Confluence before it is saved. Jira and Confluence connections are independent — you can configure either one alone, or both on the same Atlassian site.

What the connection can do

The integration is read-only. Asenion can list the spaces and pages the connected account can see, and fetch page content and attachments. It never writes to Confluence.

See Document Hub for the import flow.

Single Sign-On (Okta and Microsoft Entra ID)

SSO providers are configured by Org Admins from the same Settings → Connections page, in the Single Sign-On (SSO) section. Asenion supports Okta (including Auth0 tenants) and Microsoft Entra ID, discovered by email domain at sign-in.

See Security → Single Sign-On for the full configuration reference.

Notification Channels

Slack and Microsoft Teams connections enable risk alert and workflow notifications to be delivered to channels alongside in-app delivery.

Channel Configuration
Slack OAuth app connection; select channels per AI system in notification settings
Microsoft Teams Incoming webhook or app connection; configure per AI system

Notification channel setup is done from Settings → Connections, and channel selection per AI system is done from AI System → Settings → Risk Alerts.

ServiceNow

Asenion can connect to a ServiceNow instance for ITSM integration — creating and tracking tickets from governance actions and risk alerts.

Configuration requires ServiceNow instance URL and service account credentials.

Who can manage connections?

Only Org Admins (with org:manage_settings capability) can create, edit, activate, or delete connections.

Any member with appropriate project access can use an active connection (e.g. link an MLflow run to an assessment they are working on).