# Integrations

### Single Sign-On (SSO) <a href="#integrate_into_cicd_systems" id="integrate_into_cicd_systems"></a>

Xygeni provides Single Sign-On (SS) through integration with 3rd party Identity Providers (IdPs) using SAML2 protocol.

{% hint style="info" %}
See [Xygeni Single Sign-On (SSO) Authentication](/xygeni-administration/platform-administration/integrations/xygeni-single-sign-on-sso-authentication.md) for further reference.
{% endhint %}

### Integrate into CI/CD Systems <a href="#integrate_into_cicd_systems" id="integrate_into_cicd_systems"></a>

The build pipeline is a good point for running the Xygeni scanner, as it can check early in the build cycle if there are issues that should be resolved before advancing to the next step.

The Continuous Integration/Delivery System can run a scan step in a given pipeline for ensuring that the software and the build pipeline itself are free of issues that bad actors may leverage to breach the software supply chain, inserting malicious or unintended code, or exfiltrating sensitive information for nefarious purposes.

{% hint style="info" %}
See [Integrate into CI/CD Systems](/xygeni-administration/platform-administration/integrations/integrate-scanner-cli-into-ci-cd-systems.md) for further details
{% endhint %}

### Xygeni Sensors <a href="#xygeni_sensors" id="xygeni_sensors"></a>

Xygeni provides 'plugins' (Xygeni Sensor) for Source Code Managers (SCMs) like Azure DevOps, BitBucket, GitHub or GitLab or standalone CI/CD systems like Jenkins. The sensor captures important events, like administrative changes, new commits or pull requests, pipeline events, and other relevant activity, and sends them to the Xygeni servers typically using webhooks.

Xygeni analyzes the events and emits an alert when an unusual activity anomaly is identified. Unusual activity typically demands to take immediate action to mitigate the risk and prevent further damage.

{% hint style="info" %}
See [Xygeni Sensors](/xygeni-products/anomaly-detection/xygeni-sensors.md) for further information
{% endhint %}

### Collaboration & Communication Tools

Xygeni allows users to configure **Slack** as a channel to publish issues found by Xygeni platform.

{% hint style="info" %}
See [Collaboration & communication Tools](/xygeni-administration/platform-administration/integrations/collaboration-and-communication-tools.md) for further information
{% endhint %}

### Ticketing Systems

Xygeni allows users to create tickets from issues found. Supported ticketing systems are **Jira** and **GitHub**.

After configured the integration, you will be able to create tickets from the details slide of any issue.

{% hint style="info" %}
See [Ticketing Systems](/xygeni-administration/platform-administration/integrations/ticketing-systems.md) for further information
{% endhint %}

### Remediation (auto-fix)

Xygeni allows users to automatically fix of certain types of issues (vulnerabilities of open source dependencies).&#x20;

{% hint style="info" %}
See [Remediation systems](/xygeni-administration/platform-administration/integrations/remediation-systems.md) for further information
{% endhint %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.xygeni.io/xygeni-administration/platform-administration/integrations.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.