SECENG TRUST SCANNER — INTEGRATIONS
Security evidence should land where the work already happens. Connectors first.
Connect SecEng outputs to engineering, ticketing, collaboration, security, CRM, documentation, learning, and evidence workflows. Native connectors, supported exports, and workflow compatibility are not the same thing.
Trust Scanner runs natively inside the tools your security team already uses
40 integrations · new platforms added regularly
Collaboration
6Slack, Teams, Mattermost, Discord, Google Chat, Telegram
Email & Docs
7Gmail, Outlook, Word, Sheets, Docs, Notion, SharePoint
CRM
3HubSpot, Salesforce, Intercom
Developer
3JetBrains, Eclipse, Raycast
DevOps
2Azure DevOps, Jira
Design
1Figma
Local first
24
Designed to stay in the customer environment for supported flows.
On-demand only
9
Leaves only when a user explicitly triggers the scan or sync.
Webhook-backed
7
May route through customer-controlled webhook or server handling.
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 2 supported connectors above for what actually ships today.
Building a Native Product Integration?
Partner integrations need a contract layer before public compatibility claims.
Explore the SecEng Partner Interoperability Framework for scanner findings, attack traces, partner evidence, APC results, workforce content, and learner outcomes.
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.
Early access
Want your integration prioritized?
Tell us which platform matters most and we'll prioritize it where it fits the product surface.