Getting started with Integrations

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.

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

The integrations fall into a few families, and which ones matter depends on where your systems already live.

Cloud Platform Integrations

Cloud integrations check the security configuration of the platform itself: IAM, encryption, and network rules.

Amazon Web Services (AWS):

• Security baseline compliance monitoring
• IAM configuration validation
• Encryption settings verification
• Network security group compliance

Microsoft Azure:

• Azure Security Center integration
• Azure Active Directory configuration checks
• Azure Policy compliance monitoring
• Resource encryption validation

Google Cloud Platform:

• Cloud Security Command Center integration
• Identity and Access Management monitoring
• Cloud Resource Manager compliance
• Security configuration baseline checks

Development Platform Integrations

Code platform integrations check repository and pipeline security: branch protection, scanning, and dependency risk.

GitHub:

• Repository security settings monitoring
• Branch protection rule compliance
• Code scanning results integration
• Dependency vulnerability tracking

GitLab:

• Project security configuration validation
• CI/CD pipeline security compliance
• Container scanning results integration
• License compliance monitoring

Jira Cloud:

• Issue tracking integration for compliance workflows
• Project management compliance monitoring
• Audit trail integration
• Change management process tracking

Workspace and Productivity Integrations

Workspace integrations check the admin-level security settings of the tools your whole company uses.

Google Workspace:

• Admin console security settings
• User account management compliance
• Data loss prevention configuration
• Mobile device management settings

Kandji:

• macOS device management compliance
• Security policy enforcement monitoring
• Software deployment compliance tracking
• Device security baseline validation

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

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

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.