Connect with your
existing tools
ComplyShield uses a driver-based architecture — swap in your preferred providers for ticketing, SIEM, notifications, and more. No lock-in, no complex middleware.
Ticketing
Jira · ServiceNow
Create and sync tickets from incidents, contract expirations, and policy reviews.
SIEM
Splunk · Sentinel · QRadar
Forward security events and incident data to your SIEM platform.
Security Rating
SecurityScorecard · BitSight
Import vendor security scores and findings for risk assessments.
Asset Discovery
AWS · Azure · GCP
Discover and sync cloud assets into your ICT asset registry.
Threat Intelligence
MISP · STIX-TAXII
Consume and publish threat indicators for proactive risk management.
Vulnerability Scanner
Qualys · Nessus · Rapid7
Import vulnerability scan results and track remediation.
Notifications
Microsoft Teams
Send real-time alerts for incidents, assessments, and contract expirations.
SSO
Azure AD
Single Sign-On with automatic user provisioning and role mapping.
REST API
Sanctum
Full CRUD API with token authentication for custom integrations.
How It Works
Driver-based architecture
Every integration in ComplyShield follows a driver pattern. Out of the box each channel uses a NullDriver that silently discards calls — no errors, no setup required.
When you are ready to go live, add your credentials to the environment config and ComplyShield switches to the real driver automatically. All integration work runs through queued jobs, so your application stays fast and resilient even when external services are slow.
Zero-config default
NullDriver ships as the default for every channel. Install and run — nothing breaks.
Credential-activated
Add API keys or OAuth tokens to your environment and the real driver activates instantly.
Event-driven & queued
Integration calls are dispatched as queued jobs, keeping your UI snappy and retryable on failure.
Need a custom integration?
Let’s talk. We can build a driver for any platform your organisation relies on.
Get in Touch