NodeMotion
Live Canvas
MODULE 03 OF 09•Threat Modeling Studio

Threat Modeling Studio: Canvas Badges & Visual Legend

Decode every red STRIDE/ATLAS badge, dashed Trust Boundary, transport & sensitivity pill, identity label, and Crown Jewel marker on the canvas.

MODULE 03 · THREAT CANVAS & BADGES⏱ 5 min read

“Every red badge on the canvas is a conversation you don't have to have at 3:00 AM during an incident.”

— NodeMotion AppSec Handbook
TL;DR in 15 Seconds:Learn to decode every S, T, R, I, D, E, and TI red badge, dashed Trust Boundary, Edge Classification pill (PCI_FINANCIAL · TLS_1_3), ENTRA_OIDC posture label, and Crown Jewel marker.
Live Anatomy: STRIDE Badges, Trust Boundaries & Crown Jewel MarkersANNOTATED VISUAL WALKTHROUGH
TRUST BOUNDARY · DMZ / PRIVATE SUBNETWeb StorefrontPUBLIC_UNTRUSTEDDPCI_FIN · TLS_1_3TIAPI GatewayENTRA_OIDCSDCRED · MTLSOrders Ledger DBENTRA_OIDC · RLSJEWELR
1
Red STRIDE Pills (S, T, R, I, D, E, TI)

Single letters mark individual threats (e.g. D = Denial of Service, R = Repudiation). Combined pills like TI flag both Tampering and Information Disclosure on the same hop.

2
Dashed Trust Boundary & Crossing Pill

Whenever a connector crosses a dashed zone boundary without mTLS or WAF inspection, the edge pill glows crimson/amber to highlight unauthenticated boundary crossings.

3
Edge Data Classification (PCI_FIN · TLS_1_3)

Shows the inferred data sensitivity (PUBLIC, INTERNAL, PII, PCI_FINANCIAL, CREDENTIALS) paired with transport security (PLAINTEXT, TLS_1_3, MTLS).

4
JEWEL Marker & Auth Posture Sub-Label

Amber JEWEL badges highlight Crown Jewel databases/vaults; sub-labels like ENTRA_OIDC or NONE reflect the component authentication posture.

Interactive visual anatomy of Threat Modeling Studio canvas badges and trust-boundary crossings.ANNOTATED ARCHITECTURE DIAGRAM

1. Anatomy of the Threat Modeling Studio Canvas

In Threat Modeling Studio, every visual element on the canvas communicates live security posture and deterministic threat state. Clicking the ? Legend button in the floating canvas toolbar opens the interactive reference overlay at any time:

Threat Studio Canvas Badges and Inline Visual Legend
Figure 3.1 — Threat Modeling Studio Canvas: Red STRIDE threat pills (D, TI, E), Edge Data-Classification & Transport pills (PCI_FINANCIAL · TLS_1_3), Node Auth posture labels (ENTRA_OIDC), Crown Jewel stars, and the open '? Legend' popover.LIVE PLAYWRIGHT CAPTURE

2. Complete Visual Legend: Red STRIDE & Combined Threat Pill Badges

Whenever the STRIDE + MITRE ATLAS Engine detects an open vulnerability on a node or connector, it renders a high-visibility crimson pill badge in the top-right corner of the node card or at the midpoint of the data-flow connector:

Threat Pill Badges
SSpoofing
TTampering
RRepudiation
IInfo Disclosure
DDenial of Service
EElevation
TICombined / ATLAS
Canvas Posture & Boundary Tokens
Dashed Trust BoundaryPCI_FINANCIAL · TLS_1_3ENTRA_OIDC★ Crown Jewel
BadgeSTRIDE CategoryRule ID & Inherent ScoreExact Trigger Condition in threatEngine.ts1-Click Auto-Fix / Remediation
SSpoofingNM-STRIDE-S01 (90 / 76)Connector crosses a Trust Boundary (srcTier !== dstTier or cross-subnet) with authMechanism === 'none' or originates from a threat_actor node.Click Enforce mTLS + Identity Auth (encrypt_mtls).
TTamperingNM-STRIDE-T01 (78)Publicly exposed or untrusted source connects to an internal service/gateway when no active inline waf, ddos, or zero_trust control exists.Click + Inject Cloud WAF & Zero-Trust Gate (inject_waf).
RRepudiationNM-STRIDE-R01 (68)Node is marked crownJewel === true while auditLogging === false and no active siem collector node is present on the canvas.Click + Attach SIEM & Audit Collector (inject_siem).
IInformation DisclosureNM-STRIDE-I01 (88 / 74 / 62)Connector uses plaintext transport (score 88), OR carries sensitive data (pii, pci_financial, credentials) without mtls (score 74 to Crown Jewel, 62 standard).Click Upgrade Flow to mTLS + X.509 (encrypt_mtls).
DDenial of ServiceNM-STRIDE-D01 (64)Internet-exposed compute or gateway node (publicExposure === true) operates without an upstream WAF or DDoS rate-limiting control.Click + Inject Cloud WAF & Zero-Trust Gate (inject_waf).
EElevation of PrivilegeNM-ATLAS-LLM01 (84) / NM-STRIDE-E02 (86)Triggered when an AI workload (agent, llm, rag_pipeline) lacks an active ai_guardrails/dlp node, OR when a security control is toggled to Simulated Failure (controlDisabled === true).Click + Inject AI Safety Guardrail & DLP or restore the disabled control.
TICombined Multi-Threat BadgeNM-STRIDE-T01 + NM-STRIDE-I01Rendered on connectors (such as #1 POST /checkout) that simultaneously exhibit Tampering (no WAF on public ingress) and Information Disclosure (PCI_FINANCIAL over standard TLS without mTLS pinning).Apply both 1-click auto-fixes to eliminate the badge completely.

3. Edge Classification Pills, Node Auth Sub-Labels & Trust Boundary Tiers

Edge Classification & Transport Pills

Every connector displays a pill beneath its protocol label formatted as <CLASSIFICATION> · <TRANSPORT>:

  • PCI_FINANCIAL · TLS_1_3 (inferred from checkout/payment/card/pci labels)
  • PII · TLS_1_3 (inferred from user/profile/customer/rag labels)
  • CREDENTIALS · MTLS (inferred from auth/token/jwt/secret labels)
  • INTERNAL · MTLS (inferred from gRPC/mTLS service calls)

Node Auth Sub-Labels & Crown Jewels

Each node card renders its active authentication posture (ENTRA_OIDC, MTLS_CERT, API_KEY, or NONE). Data stores (postgres, redis, cosmos, vector) and vault nodes are automatically marked as ★ Crown Jewels, increasing the severity of unencrypted incoming flows and requiring immutable SIEM audit logging.

4 Dashed Trust Boundary Tiers

Zone containers render with color-coded dashed borders according to their TrustTier rank:

  • Crimson (#ef4444): untrusted_public (Rank 0)
  • Amber (#f59e0b): dmz_edge (Rank 1)
  • Sky Blue (#38bdf8): private_compute (Rank 2)
  • Purple (#a855f7): restricted_data (Rank 3)

There Are No Dumb Questions

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

Q:If we already use TLS 1.3 on an edge, why does NodeMotion still flag it with a red badge?
A:Server-only TLS 1.3 encrypts the pipe, but sensitive PII/PCI/Credentials hops across trust boundaries still need Mutual TLS (mTLS) client pinning to prevent sidecar spoofing—and TLS alone does not stop SQLi/XSS tampering without a WAF.
Q:What does a combined "TI" badge mean on a connector?
A:It means both Tampering (T) and Information Disclosure (I) findings fired on that exact connector—for example, an unencrypted or non-mTLS sensitive crossing lacking WAF inspection.
INTERACTIVE EXERCISE

Sharpen Your Pencil · 60-Second Brain Challenge

A RAG pipeline retrieves unredacted customer PII from a Vector Store over plaintext HTTP without a guardrail. Which badge fires?

The Sticky-Note Takeaway
  • ▸Red pills (S, T, R, I, D, E, TI) show active STRIDE categories at a glance.
  • ▸Dashed borders highlight Trust Boundaries; amber/red crossings need mTLS or WAFs.
  • ▸Amber JEWEL tags prioritize Crown Jewel data stores during Blast-Radius analysis.