Skip to main content

Integrations Overview

Containment.AI integrates with your existing security infrastructure to provide comprehensive AI governance. This guide covers available integrations and how they work.

Available Integrations

Core Integrations

IntegrationPurposePlansStatus
Chrome ExtensionBrowser-level policy enforcementAllAvailable
MDMDevice management deploymentPro, EnterpriseAvailable
Site ControlsPer-site rules and noticesPro, EnterpriseAvailable
SIEM ExportSecurity event forwardingEnterpriseCustom engagement (roadmap)
Offline PipelinesAir-gapped/on-premise deploymentEnterpriseCustom engagement (roadmap)

Identity Providers

IntegrationPurposePlansStatus
SSOSingle sign-on authenticationEnterpriseCustom engagement (roadmap)
SCIMUser provisioning/deprovisioningEnterpriseCustom engagement (roadmap)

Integration Status

Check integration status at Settings > Integrations:

StatusMeaning
ConnectedWorking normally
Not ConfiguredSetup needed

Setting Up Integrations

Chrome Extension

  1. Go to Settings > Integrations
  2. Click the Chrome Plugin card
  3. Record your MDM provider and install mode
  4. Follow the MDM deployment guide for your platform

Enterprise Integrations

SIEM Export, Offline Pipelines, SSO, and SCIM are delivered as custom Enterprise engagements. Their cards route to a sales conversation; there is no self-serve setup wizard, connection test, or API-key/OAuth flow for them today. Each integration's page describes the engagement process.

Data Flow

Today

  • The extension sends prompt text to the policy-check service for evaluation and receives an allow/block decision
  • Violation alerts and audit events appear in the dashboard

Designed (per engagement)

  • Alert and audit-event forwarding to your SIEM
  • User directory sync from your IdP (SCIM)
  • Authentication delegated to your IdP (SSO)

Privacy

Integration data handling:

  • Prompt content goes only to the policy-check service for evaluation; it is never sold or shared with advertisers or data brokers
  • Integrations receive violation alert metadata only (policy name, severity, message, matched term/pattern)
  • Designed to map to common privacy requirements

Verifying Your Deployment

Full workflow testing with the shipped product:

  1. Trigger a test policy violation on a monitored AI platform
  2. Confirm the extension blocks or records it per your policy
  3. Verify the alert appears in the dashboard

Best Practices

Security

  • Use least privilege
  • Monitor integration health
  • Review access regularly

Documentation

  • Document all integrations
  • Track configuration changes

Next Steps