SHEET 06INTEGRATION ECOSYSTEM

Your toolchain
already speaks ThreatZ.

30+ tools across architecture modeling, code analysis, SBOM management, DevOps, security testing and identity — no lock-in, no retyping. Every import is staged and reviewed; nothing lands on the graph silently.

30+ INTEGRATIONS
7 CATEGORIES
4 VULNERABILITY FEEDS
7+ EXPORT FORMATS

Cybersecurity engineering pipeline

15 connected stages. One connected graph.

From network analysis to OEM VSOC streaming and threat-intel ingest — aligned with ISO/SAE 21434 and UN R155. Click any stage to see which tools plug in there.

ThreatZ ThreatZ ALIGNED WITH ISO/SAE 21434 · UN R155
STAGE 01 · NETWORK & COMM MATRIX DESIGN

Import bus signals, comm-matrix metadata and protocol stacks. The foundation for asset and threat modeling downstream.

DON'T SEE YOUR TOOL? WE ADD CONNECTORS FROM REAL CUSTOMER REQUESTS — SUGGEST ONE
CONNECTED TOOLS & FORMATS
ARXML DBC VSS (Vehicle Signal Specification)

DATA INTERCHANGE: SARIF 2.1.0 · GENERIC JSON · CYCLONEDX · SPDX v2.3/v3 · REQIF · OPENXSAM · STIX · AUTOSAR · NVD · CNVD · OSV · GITHUB SECURITY ADVISORIES

How the data actually flows

Top 5 integrations, in detail.

Beyond the logo wall — the concrete data, serialization and direction for the five integrations customers configure first.

Vector CANoe CAN-bus & Automotive-Ethernet test execution
ThreatZ test plan → TestBench Agent (CAPL + Python) → CANoe → vehicle HW → verdict → TARA
DIRECTION  Bi-directional FORMAT  Vector test report (XML) + BLF/ASC/MF4 · PCAPNG (signed) AUTH  Agent credential · CANoe license / CANoe4SW for CI
MATLAB & Simulink System Composer architecture import
System Composer → SLX / SysML XMI → asset graph + trust boundaries → TARA scope ⇢ ReqIF feedback
DIRECTION  In (architecture) · ReqIF back FORMAT  SLX native · SysML v1 XMI · SysML v2 (R2024a+) · ReqIF 1.2 AUTH  File handover or MATLAB Engine API
Atlassian Jira Risk treatments & security tasks
Risk treatment → REST → Jira issue (project · epic · custom fields) ⇢ webhook → status back
DIRECTION  Bi-directional FORMAT  Jira REST + custom-field mapping · 1:1 or 1:N per treatment AUTH  OAuth 2.0 / Connect (Cloud) · PAT (Data Center 8.14+)
GitHub SBOM, CodeQL findings & PR status checks
Actions on PR/push → SBOM (SPDX/CycloneDX) + SARIF → correlate vs TARA → status check → PR
DIRECTION  Up-stack · checks back to PR FORMAT  SPDX 2.3 · CycloneDX 1.6 · SARIF 2.1.0 · portable to GitLab/Jenkins AUTH  GitHub App (checks:write) · fine-grained PAT for ingest
SonarQube Static-analysis findings correlated to TARA threats
sonar-scanner → Web API pull → SARIF → map → SBOM + threat IDs ⇢ resolution echo
DIRECTION  Pull · resolution echo back FORMAT  Web API JSON (9.x/10.x) → SARIF 2.1.0 · CWE preserved AUTH  User token (Browse) · SonarCloud Bearer + org key
IDENTITY & ACCESS

Enterprise single sign-on.

Microsoft Entra ID Google Workspace GitHub SSO SAML 2.0 LDAP
SSO on Professional and Enterprise plans · LDAP on Enterprise with on-premise deployment.
EXPORT & INTEROPERABILITY

Speaks your industry language.

REPORTS PDF CSV Excel
INTERCHANGE ReqIF SARIF 2.1.0 OpenXSAM STIX AUTOSAR
ReqIF exports are compatible with IBM DOORS, Siemens Polarion and PTC Integrity. STIX and AUTOSAR exports on Enterprise.

Need a different integration?

Tell us which tools your teams use — the extensible parser framework makes new connectors fast, and we prioritize from real customer requests.

Request an integration
TITLEINTEGRATION ECOSYSTEM — PIPELINE & FORMATS
TOOLS30+ · 7 CATEGORIES
FEEDSNVD · CNVD · OSV · GHSA
EXPORTS7+ FORMATS

Stage 01 — Network & Comm Matrix (DESIGN)

Import bus signals, comm-matrix metadata and protocol stacks. The foundation for asset and threat modeling downstream.

Stage 02 — System Modelling (DESIGN)

Architecture as designed — components, ports, interfaces and stereotypes read from your engineering source of record.

Stage 03 — Asset Identification (DESIGN)

Diagnostic catalogs and signal specs become the asset inventory — mapping reviewed before commit, never applied silently.

Stage 04 — TARA (ANALYSIS)

Threat scenarios, damage scenarios and risk values on the graph — plus migration paths for the TARAs you already have.

Stage 05 — Goals & Requirements (ANALYSIS)

Cybersecurity goals and requirements flow to and from your requirements management tools.

Stage 06 — SW Architecture (SOFTWARE)

Software units mapped to the system model, ready to receive composition analysis and SBOM data.

Stage 07 — SBOM (SOFTWARE)

Software bills of materials per unit — imported as delivered, versioned per baseline, diffed on re-import.

Stage 08 — SAST (SOFTWARE)

Static-analysis findings correlated to SBOM components and TARA threats; treatment status echoed back.

Stage 09 — Binary Analysis (SOFTWARE)

Findings from binary scanners land on the same components as source-level results.

Stage 10 — SCA (SOFTWARE)

Software composition analysis results reconciled with supplier SBOMs — one component inventory, not two.

Stage 11 — Vulnerability Databases (MONITORING)

Continuous matching of the component inventory against public and regional vulnerability feeds.

Stage 12 — Testing (VALIDATION)

Attack-path-derived campaigns drive the bench; results return as verification evidence on the assurance chain.

Stage 13 — Data Exchange (EVIDENCE)

Machine-readable interchange with the rest of your engineering ecosystem — their format, your render step.

Stage 14 — OEM VSOC (OPERATIONS)

Fleet security events stream into Incident Command; incident records feed back into the risk model.

Stage 15 — Threat Intel (OPERATIONS)

Threat intelligence ingest keeps feasibility ratings and threat scenarios current with the real world.