23 connectors, 30 curated CRMs. Inferred CRMs for the rest.
Connectors pull evidence directly from the vendor API. Curated Customer Responsibility Matrices say what each vendor covers and what stays with you, the split your SSP has to document. Where a vendor has no connector (PreVeil, Virtru, Brivo), you upload evidence against its curated CRM; Garde1 still needs a Microsoft 365, Google Workspace or AWS tenant to connect to. Anything else in your stack gets a CRM inferred from that product's profile and your scope.
Or start a 14-day trial and connect one system yourself.
23 connectors. Evidence pulled directly via the vendor API.
5 are generally available; the rest are in beta. Read-only by default. Write-capable scopes are opt-in per integration for remediation and baseline workflows only.
Workspace
Cloud Security
Identity
Endpoint
SIEM
Vulnerability Mgmt
Network
Dev, ticketing & training
7 more vendors. Curated CRM plus evidence upload.
Garde1 has no connector for these yet, but they show up constantly in DIB scopes: PreVeil, Virtru and Kiteworks for CUI email and file sharing, Brivo for physical access. Garde1 ships the Customer Responsibility Matrix so you can document them cleanly in your SSP package, and the platform's manual evidence upload lets you attach screenshots, exports, and configuration dumps directly to the controls those CRMs cover. No API required, no control left unevidenced.
We add integrations on customer request. Tell us what you run.
Build prioritization follows customer commitment. We don't back-burner the one connector that's blocking your assessment.
