NodeMotion
Live Canvas
MODULE 06 OF 09•Threat Modeling Studio

Top Toolbar, Bidirectional Sync & Enterprise Exports

Real-world workflows for Attack Paths, Workspaces, Sync to Studio, CISO STRIDE Report (PDF), Threat Register CSV, OWASP Threat Dragon v2, OASIS SARIF v2.1.0, and .nodemotion.json.

MODULE 06 · TOOLBAR, SYNC & EXPORTS⏱ 4 min read

“Security architecture only scales when its outputs plug directly into GitHub Security, Jira, and the CISO's board deck.”

— DevSecOps Automation Guide
TL;DR in 15 Seconds:Use Sync to Studio for bidirectional hardening, and export OASIS SARIF v2.1.0, OWASP Threat Dragon v2 JSON, Jira CSV, CISO PDF Reports, and .nodemotion.json snapshots.

1. Top Toolbar Mechanics: Risk Scoreboard, Attack Paths, Workspaces & Sync

The Threat Modeling Studio top bar provides continuous risk telemetry and one-click synchronization with Architecture Studio:

Threat Studio Top Toolbar and Executive & Compliance Exports Menu
Figure 6.1 — Threat Studio Top Toolbar & Open File Menu: Inherent/Residual Risk scoreboard, Attack Paths toggle, Workspaces drawer, Sync to Studio, and the 5 Enterprise Security Export formats.LIVE PLAYWRIGHT CAPTURE

Inherent vs. Residual Risk Score Calculation

runEnterpriseStrideEngine computes both scores across all active findings plus architectural mitigation slots (activeMitigationCount):

  • Each active WAF/Zero-Trust, SIEM, or AI Guardrail/DLP adds +2 mitigation slots (inherent: 76, residual: 12); Vault/PKI/IAM and mTLS connectors add +1 slot each.
  • Inherent Risk is the mean inherent score across all findings and mitigation slots (capped at 98).
  • Residual Risk is the mean disposition-adjusted residual score across all findings and mitigation slots—dropping into the green band (≤ 35/100) as controls and mitigations are applied.

Bidirectional Handoff (Sync to Studio)

Clicking Sync to Studio serializes the updated nodes (including newly injected WAFs, SIEM collectors, and AI Safety Guardrails), upgraded mTLS edges, and trust zones and navigates back to Architecture Studio so your Word/PDF engineering runbooks automatically include every security control added during threat modeling.

2. Complete Specification of the 5 Enterprise Security Exports

Export Menu ItemGenerator FunctionFile ExtensionSchema & Enterprise Integration Details
1. CISO STRIDE Report (Export PDF)openPrintableThreatReport().pdf / Print HTMLRenders a dedicated print-styled executive dossier with Inherent vs. Residual Risk KPIs, STRIDE distribution table, Assumptions Register verification status, and full finding cards mapped to CWE, OWASP, NIST 800-53, and ISO 27001.
2. Threat Register CSV (Jira / GRC)exportToThreatCsv()-threat-register.csvRFC 4180 CSV with columns: ID, RuleId, STRIDE, Severity, InherentScore, ResidualScore, Disposition, Owner, Title, Target, Preconditions, AttackScenario, Mitigation, Frameworks, Notes.
3. OWASP Threat Dragon v2 (.json)exportToThreatDragonJson()-threat-dragon-v2.jsonProduces an OWASP Threat Dragon version: '2.0' document mapping ZoneBox to trust-boundary-box, nodes to actor / store / process cells, edges to flow cells, and findings to embedded cell threats[].
4. OASIS SARIF v2.1.0 (GitHub Security)exportToSarifJson().sarif.jsonConforms to https://json.schemastore.org/sarif-2.1.0.json with tool driver NodeMotion Threat Studio, rules[], and results[] mapped to error (Critical/High) and warning (Medium/Low).
5. Save NodeMotion Threat ProjecthandleExport('nodemotion').nodemotion-threat.jsonLossless JSON bundle containing nodes, edges, zones, and threatModel (nodePostures, edgePostures, zonePostures, triageRecords, assumptions).

There Are No Dumb Questions

Candid answers to the skeptical questions every security engineer asks first.

Q:Can I bring my team back and forth between Architecture Studio and Threat Modeling Studio?
A:Yes! Use Threat Model in Architecture Studio to analyze security, and Sync to Studio in Threat Modeling Studio to push every newly spliced WAF, SIEM, or Guardrail back into your architecture runbook.
Q:How do I prove these findings in our CI/CD pipeline?
A:Export OASIS SARIF v2.1.0 from the File menu and upload it to GitHub Advanced Security via github/codeql-action/upload-sarif@v3.
The Sticky-Note Takeaway
  • ▸Every diagram node, edge, and trust boundary stays synchronized across studios.
  • ▸1-click countermeasures update both the visual topology and Residual Risk score.
  • ▸Export SARIF v2.1.0, Threat Dragon v2 JSON, Jira CSV, and CISO PDFs anytime.