NodeMotion
Live Canvas
MODULE 09 OF 09•AI, IaC & Enterprise Governance

Capabilities, Limitations, BYOK & CI/CD

Honest What is There vs. What is Not matrix, BYOK privacy lifecycle (Gemini, OpenAI, Anthropic), Zero-Secret S3/Azure SAS cloud workspaces, and GitHub Actions SARIF pipelines.

MODULE 09 · CAPABILITIES, BYOK & CI/CD⏱ 5 min read

“Zero-secret architecture means you never have to trust our server with your LLM keys or cloud storage tokens.”

— NodeMotion Trust Engineering
TL;DR in 15 Seconds:Review exact deterministic capabilities, BYOK sessionStorage isolation, Azure/AWS CI/CD security gates, and what stays client-side vs. optional cloud sync.

1. Honest Comparison Matrix: What's Built-In vs. Known Boundaries

NodeMotion is designed for principal engineers, security architects, and compliance reviewers who require complete clarity on how deterministic vs. AI-assisted features operate:

What's Built-In & Production Ready
  • Deterministic <5ms STRIDE + MITRE ATLAS Engine: 100% browser-executed graph evaluation across Spoofing, Tampering, Repudiation, Info Disclosure, DoS, Elevation of Privilege, and Agentic AI (NM-ATLAS-LLM01).
  • Dual-Engine IaC & GitHub Ingestion: Serverless AI extraction (/api/parse-iac) paired with an instant offline deterministic HCL/Bicep/Compose/K8s/OpenAPI parser.
  • 1-Click Architectural Auto-Fixes & Control-Break Simulator: Mutates live DFD topology to splice Cloud WAFs, attach SIEM collectors, inject AI Safety Guardrails, upgrade edges to mTLS 1.3, or simulate control failures (NM-STRIDE-E02).
  • 5 Security Exports + 7 Architecture Exports: OASIS SARIF v2.1.0, OWASP Threat Dragon v2, Jira CSV, CISO PDF, DOCX/PDF Runbooks, Animated SVG, Mermaid, PlantUML, and .nodemotion.json.
What NodeMotion Is Not (Operational Boundaries)
  • Not an Application Source-Code SAST/DAST Scanner: NodeMotion threat-models architectural Data Flow Diagrams and IaC definitions—it complements (rather than replaces) CodeQL, Semgrep, or Snyk for line-by-line C#/Python/Go vulnerabilities.
  • No Dynamic Terraform State Execution: The deterministic HCL fallback parses resource blocks and attributes statically without running terraform plan against live cloud credentials.
  • Public GitHub Repos for Direct Browser Tree Fetch: Direct browser tree discovery calls api.github.com (60 req/hr unauthenticated limit). For private repos, upload .tf / .bicep files via the File Upload tab.

2. Bring Your Own Key (BYOK) & Zero-Secret Privacy Architecture

Clicking Account → Settings in either Architecture Studio or Threat Modeling Studio opens the Settings & Bring Your Own Key (BYOK) Modal, allowing you to bypass the default starter quota using your own API key from Google Gemini, OpenAI, or Anthropic Claude:

NodeMotion Settings and Bring Your Own Key (BYOK) Modal
Figure 9.1 — Settings & Bring Your Own Key (BYOK) Modal: Supports Google Gemini, OpenAI, and Anthropic Claude with browser-local storage isolation.LIVE PLAYWRIGHT CAPTURE
Security LayerImplementation MechanismPrivacy & Compliance Guarantee
BYOK Local IsolationlocalStorage['nodemotion_byok_config_v1']Your personal API key is stored strictly in your browser's localStorage and forwarded over TLS 1.3 only during active AI requests—never written to Azure Table Storage or server logs.
Zero-Secret Cloud UploadssaveToPreSignedOrSasUrl()Uploads exported diagrams/runbooks directly to your AWS S3 Pre-Signed URL or Azure Blob SAS URL over HTTPS. Optional /api/storage-relay blocks internal RFC1918 IP ranges against SSRF.
OWASP Edge Hardeningstaticwebapp.config.jsonEnforces strict Content-Security-Policy, Strict-Transport-Security, X-Frame-Options: DENY, X-Content-Type-Options: nosniff, and locked-down Permissions-Policy.

3. CI/CD DevSecOps Pipelines: GitHub Actions & Azure DevOps SARIF Upload

Export your threat model as OASIS SARIF v2.1.0 (security/nodemotion-threat-model.sarif.json) and integrate it directly into your repository's automated security gates:

.github/workflows/threat-model-sarif.yml (GitHub Actions)
name: Upload NodeMotion SARIF v2.1.0
on:
  push:
    branches: [ main ]
    paths: [ 'security/**.sarif.json' ]
  pull_request:
    branches: [ main ]

permissions:
  contents: read
  security-events: write

jobs:
  upload-sarif:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - name: Upload STRIDE + ATLAS SARIF
        uses: github/codeql-action/upload-sarif@v3
        with:
          sarif_file: security/nodemotion-threat-model.sarif.json
          category: nodemotion-architectural-stride
azure-pipelines-sarif.yml (Azure DevOps Advanced Security)
trigger:
  branches:
    include: [ main ]
  paths:
    include: [ 'security/*.sarif.json' ]

pool:
  vmImage: 'ubuntu-latest'

steps:
  - checkout: self
  - task: AdvancedSecurity-Publish@1
    displayName: 'Publish NodeMotion STRIDE SARIF'
    inputs:
      SarifsInputDirectory: '$(Build.SourcesDirectory)/security'

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.