PARTNERS

Add selected Workbench capabilities through bounded OEM and partner integrations

AI SECURITY WORKBENCH · INTEGRATIONS

Security evidence should land where the work already happens. Connectors first.

Connect Workbench outputs to engineering, ticketing, collaboration, security, CRM, documentation, learning, and evidence workflows. Native connectors, supported exports, and workflow compatibility are not the same thing.

0supported security connectors
40registry entries
14categories
36platforms
35planned security mappings

Trust Scanner runs natively inside the tools your security team already uses

40 integrations · new platforms added regularly

Collaboration

6

Slack, Teams, Mattermost, Discord, Google Chat, Telegram

Email & Docs

7

Gmail, Outlook, Word, Sheets, Docs, Notion, SharePoint

CRM

3

HubSpot, Salesforce, Intercom

Developer

3

JetBrains, Eclipse, Raycast

DevOps

2

Azure DevOps, Jira

Design

1

Figma

Registry maturity

Existence in the registry does not imply production support. Each entry is labeled by its actual build and validation state. These counts describe security and workflow records; Academy/LMS delivery is reported separately below.

Supported

0

Pilot

0

Fixture-tested

0

Prototype

3

Planned

35

Academy/LMS delivery

2

Training delivery packages remain separate from flagship Workbench security connectors. Their individual records carry their own supported, pilot, prototype, or planned state.

Registry object type

Object type and maturity answer different questions. A template or export does not become a connector merely because the Workbench can produce or consume it.

Connector

5

A bounded data path into or out of a named platform.

Integration

23

A platform-specific surface or workflow binding.

Extension

6

An IDE, browser, design, CMS, or launcher extension record.

Template

6

Deployable content or configuration; not a connector by itself.

Export

Tracked separately

JSON, SARIF, Markdown, PDF, webhook, and CLI outputs are not connector counts.

Reference adapter

0

Only an explicitly fixture-tested adapter qualifies for this label.

Manifest format coverage

The target manifest or schema format has been mapped for each platform below. Registry mapping is a planning step, not a built connector - see 0 supported connectors above for what actually ships today.

Slack App Manifest (YAML)1Figma plugin.json1Microsoft Teams manifest.json1WordPress block.json1Office Add-in manifest.xml2Raycast package.json (commands)1Zendesk Apps Framework manifest1Salesforce sfdx-project.json1Google Apps Script (appsscript.json)3Wix wix.config.json1Burp Suite Extension JAR1OWASP ZAP Add-on1Metasploit Auxiliary Module1

Building a Native Product Integration?

Partner integrations need a contract layer before public compatibility claims.

Explore Partner Interoperability for scanner findings, attack traces, partner evidence, Attack Path Analysis results, workforce objects, learner outcomes, and other bounded exchange contracts.

Full registry

Browse the full registry of 40 workflow integrations.

Supported connectors are highlighted by the live registry. The full registry remains visible for compatibility and planning.

40 of 40 apps

Early access

Want your integration prioritized?

Tell us which platform matters most and we'll prioritize it where it fits the product surface.