ThreatZ integrates with 30+ tools across architecture modeling, code analysis, SBOM management, DevOps, security testing, and identity management. No lock-in — works with the tools your teams already use.
From network analysis through to OEM VSOC streaming and threat-intel ingest — 15 connected stages arranged around a single source of truth, aligned with ISO/SAE 21434 and UNECE R155. Click any stage to see which tools plug in there.
Import bus signals, comm-matrix metadata, and protocol stacks. Foundation for asset and threat modelling downstream.
Tell us which tool you use at this stage. We add new connectors based on real customer requests.
Data interchange: SARIF 2.1.0, Generic JSON, CycloneDX, SPDX v2.3 / v3, ReqIF, OpenXSAM, STIX, AUTOSAR, NVD, CNVD, OSV, GitHub Security Advisories.
Beyond the logo wall — the concrete data, format, and direction for the five integrations our customers configure first. Each diagram shows what crosses the boundary, in what serialization, and in which direction.
Direction: Bi-directional. Trigger: ThreatZ test campaign or CI pipeline invokes pre-authored CAPL test modules and Python harness scripts via the TestBench Agent. Format: Vector test report (XML) + BLF / ASC / MF4 trace, plus PCAPNG export from CANoe (signed by the TestBench Agent before upload). Auth: TestBench Agent local credential; CANoe licence per workstation (Vector dongle/SmartCard) or CANoe4SW server edition for CI.
Direction: One-way for the architecture (in); cybersecurity requirements feed back via ReqIF (Requirements Toolbox). Trigger: Model release / baseline update. Format: SLX (System Composer native) or SysML v1 XMI via the System Composer SysML interface; SysML v2 textual import on R2024a+. ReqIF 1.2 for the return path. Auth: File-based handover, or programmatic via MATLAB Engine API on a licensed host. Captures System Composer components, ports, interfaces, and stereotypes (with linked Simulink behaviour references) — populates the asset inventory without manual entry.
Direction: Bi-directional. Trigger: Risk-treatment creation in ThreatZ, status change in Jira. Format: Jira REST + custom-field mapping. Auth: OAuth 2.0 / Connect (Jira Cloud) or PAT (Jira Data Center 8.14+). Webhook on the Jira side propagates closures asynchronously (typically seconds, no SLA from Atlassian). Default 1:1 treatment↔issue link; optional 1:N for split treatments (design change + verification + acceptance evidence).
Direction: Up-stack from GitHub Actions; status check + annotations back to the PR. Trigger: Push, pull-request, or scheduled workflow. Format: SPDX 2.3 SBOM via GitHub's native Dependency Submission API, or CycloneDX 1.6 via Anchore sbom-action / Syft / CycloneDX-GitHub-Actions; plus SARIF 2.1.0 (CodeQL or any third-party SAST that emits SARIF). Auth: GitHub App (required for the Checks API) with checks:write, contents:read, pull-requests:write; fine-grained PAT supported for ingest only (Checks API is App-only). Portability: the SBOM + SARIF ingest contract is portable to Jenkins and GitLab CI; the PR-feedback path uses each platform's native status surface (Jenkins Checks plugin, GitLab external status checks).
Direction: Pull from SonarQube; resolution echo back via the issues/hotspot status APIs. Trigger: Scheduled poll on a project, or post-scan webhook. Format: SonarQube Web API JSON (/api/issues/search, /api/hotspots/search) on SonarQube 9.x / 10.x; ThreatZ maps the response to SARIF 2.1.0 internally (Sonar has no native SARIF output for issues; rule IDs and CWE mappings are preserved). Auth: User token with project Browse permission for issues; See Source Code if snippet context is needed; Administer Security Hotspots only when reading hotspot details beyond summary. Compatibility: Same endpoints work on SonarCloud (Bearer token + organization key required) and self-hosted SonarQube Server.
For other integrations — or to confirm a payload schema before connecting your tooling — talk to a solutions engineer in a 30-minute walkthrough. Book a session →
ThreatZ supports industry-standard identity providers for seamless authentication and access management across your organization.
SSO available on Professional and Enterprise plans. LDAP available on Enterprise with on-premise deployment.
Export your data in the formats your stakeholders need — from human-readable reports to machine-readable interchange standards compatible with tools like PTC Integrity, IBM DOORS, and Siemens Polarion.
Human-readable exports for stakeholders, auditors, and compliance teams.
Machine-readable formats for tool-to-tool interoperability across your engineering ecosystem.
ReqIF exports are compatible with IBM DOORS, Siemens Polarion, and PTC Integrity. STIX and AUTOSAR exports available on Enterprise plans.
Join our ecosystem as an integration partner or reseller and bring automotive cybersecurity to more teams worldwide.
Build a connector for your tool and reach 500+ automotive security professionals using ThreatZ.
Join our global channel program and bring VxLabs products to OEMs and Tier-1 suppliers in your region.
Tell us which tools your teams use and we will prioritize them on our roadmap. Our extensible parser framework makes adding new integrations fast.