# Getting started with Integrations > Integrations connect Tidal Control to the systems you already run, so compliance tests read your real configuration instead of someone attesting to it. Source: https://tidalcontrol.com/docs/integrations/getting-started Integrations connect Tidal Control to the systems you already run, so that compliance tests read your real configuration instead of someone attesting to it. All of them are read-only, and each one is set up once in Settings with credentials you create in the other system. ## Navigating the Integrations overview page The Integrations page in Settings shows all available external system connections and your current configuration status. ![Integrations overview](/images/help/integrations_overview.png) **What you see in the overview:** - **Configured Integrations** - Active integrations already set up - **Available Integrations** - Available systems for new connections - **Integration tiles** - Visual cards per external system ### Configured vs Available Integrations Configured integrations are already running tests; available ones are one click away from being connected. **Configured Integrations section:** - **Active connections** already set up and working - **Test execution** possible via these integrations **Available Integrations section:** - **Available systems** for new connections - **Click the plus icon** to configure integrations for use **Initial setup status:** ``` "You have not configured any integrations yet." ``` This means you haven't connected any external systems yet and all integrations are still available for configuration. ## Understanding available integrations Tidal Control supports 32 integrations, grouped below by what kind of system they connect to. Which ones matter depends entirely on where your systems already live, so most organisations configure a handful rather than all of them. ### Cloud providers Cloud integrations check the security configuration of the platform itself: identity and access, encryption, network rules and backups. - [Amazon Web Services (AWS)](/docs/integrations/aws) - [Microsoft Azure](/docs/integrations/azure) - [Google Cloud Platform](/docs/integrations/google-cloud-platform) - [Cloudflare](/docs/integrations/cloudflare) - [CockroachDB Cloud](/docs/integrations/cockroachdb) - [DigitalOcean](/docs/integrations/digitalocean) - [Hetzner Cloud](/docs/integrations/hetzner) - [Neon](/docs/integrations/neon) - [OVHcloud](/docs/integrations/ovhcloud) - [Scaleway](/docs/integrations/scaleway) - [STACKIT](/docs/integrations/stackit) - [Supabase](/docs/integrations/supabase) - [Vercel](/docs/integrations/vercel) ### Source code management Code platform integrations check repository and pipeline security: branch protection, scanning and dependency risk. - [GitHub](/docs/integrations/github) - [GitLab](/docs/integrations/gitlab) - [Azure DevOps](/docs/integrations/azure-devops) - [Atlassian Admin](/docs/integrations/atlassian-admin) ### Issue trackers These connect the systems your teams already work in, so findings and remediation live where the work happens. Several also serve as external issue targets. - [Jira Cloud](/docs/integrations/jira-cloud) - [Linear](/docs/integrations/linear) - [TOPdesk](/docs/integrations/topdesk) - [Notion](/docs/integrations/notion) - [Google Workspace](/docs/integrations/google-workspace) ### Security scanners Scanners bring existing vulnerability and threat findings into your compliance evidence. - [Aikido](/docs/integrations/aikido) - [Datadog](/docs/integrations/datadog) - [Microsoft Sentinel](/docs/integrations/microsoft-sentinel) - [Web Security Scanner](/docs/integrations/web-security-scanner) ### Observability Observability tools receive production data, so their access and privacy configuration is in audit scope in its own right. - [Sentry](/docs/integrations/sentry) - [PostHog](/docs/integrations/posthog) - [Datadog](/docs/integrations/datadog) ### Mobile device management Device management integrations provide the endpoint evidence auditors ask for on encryption and enrolment. - [Kandji (now Iru)](/docs/integrations/kandji) - [Microsoft Azure](/docs/integrations/azure) ### AI providers AI integrations check how your organisation's use of model providers is configured and governed. - [Anthropic](/docs/integrations/anthropic) - [OpenAI](/docs/integrations/openai) - [Claude Enterprise](/docs/integrations/claude-enterprise) ### Document management These check how documents shared outside your organisation are protected. - [Papermark](/docs/integrations/papermark) ### CRM - [HubSpot](/docs/integrations/hubspot) > **info:** **Some integrations appear in more than one family.** Datadog covers both security scanning and observability, and Microsoft Azure covers both the cloud platform and device management, so they are listed under each. ## Integration activation process Every integration follows the same shape: create read-only credentials in the other system, then paste them into Tidal. ### General activation steps **For each integration, follow a similar process:** 1. **Select integration** from Available Integrations section 2. **Click plus icon** to start setup 3. **Follow configuration wizard** for specific integration 4. **Configure authentication** (API keys, OAuth, service accounts) 5. **Test connectivity** to verify operation ### Authentication and security When setting up authentication, pay attention to the following security measures: - **Least privilege principle** - Don't give Tidal integration more rights than necessary. It's often sufficient to give Tidal read rights to specific system functionality. - **Encrypted connections** to all external systems - **Regular credential** rotation according to best practices > **info:** Tidal stores credential information securely in a protected 'key vault' and only communicates with encrypted connections. **Suspect credentials are compromised?** Change or remove them immediately, and send an email to support@tidalcontrol.com ## Integration impact on Tests Connecting an integration is what makes its tests available; until then they cannot run at all. ### How integrations activate Tests Which tests become available depends on which integration you connect: each one unlocks a different set. **Integration configuration enables external tests:** 1. **Integration becomes active** after successful configuration 2. **External tests become available** for that integration 3. **Tests can retrieve data** from connected systems 4. **Real-time compliance** monitoring becomes possible > **tip:** Read more about [using automatic tests](/docs/tests). ## Integrations versus manual controls **Integrations** enable Tidal Control to connect with external systems and tools for **real-time compliance monitoring**. By configuring integrations, external tests can automatically retrieve data from your existing IT infrastructure. **Core functionalities:** - **Real-time data retrieval** from external systems for compliance validation - **Automatic compliance tests** based on actual system configurations - **Centralised monitoring** of distributed IT infrastructure - **Objective compliance measurements** without manual data collection - **Continuous compliance** monitoring instead of periodic audits ### Integrations vs manual compliance controls Integrations suit anything a system can report on itself; a manual control is still needed for judgment calls a system can't make. **Integrations are ideal for:** - Technical configuration validation (encryption, access control) - Real-time security baseline monitoring - Automatic collection of compliance evidence - Large-scale infrastructure compliance monitoring **Manual controls remain necessary for:** - Procedural compliance (training, awareness) - Qualitative assessments (policy effectiveness) - Business process evaluations - Strategic compliance decisions ## Next steps Now that you understand Integrations: - **Identify critical external systems** for compliance monitoring - **Prioritise integrations** based on business and compliance impact - **Start with one integration** to learn the process - **Select specific integration** from articles below for detailed setup instructions For specific integration setup instructions, see the individual articles in this section for each available integration.