[{"data":1,"prerenderedAt":1604},["ShallowReactive",2],{"page-\u002Fthreat-report\u002Freachability":3,"navigation":1287},{"id":4,"title":5,"body":6,"description":1272,"extension":1273,"meta":1274,"navigation":1282,"path":1283,"seo":1284,"stem":1285,"__hash__":1286},"docs\u002F04.threat-report\u002F04.reachability.md","Reachability and Flow Routes",{"type":7,"value":8,"toc":1241},"minimark",[9,13,26,39,42,47,50,129,138,153,155,159,162,167,173,217,229,232,236,243,307,325,341,345,352,354,358,363,367,377,402,405,409,412,490,496,500,507,580,587,590,594,612,662,682,684,688,706,710,716,754,765,769,788,791,922,925,940,942,946,949,973,995,997,1000,1007,1011,1018,1022,1031,1035,1041,1067,1074,1078,1085,1089,1103,1105,1109,1112,1178,1180,1184],[10,11,5],"h1",{"id":12},"reachability-and-flow-routes",[14,15,16,17,21,22,25],"p",{},"The ",[18,19,20],"strong",{},"Reachability"," tab helps you see how data moves through your model toward the things you care about most, and which threats sit along the way. Pick an origin and the tab traces the ",[18,23,24],{},"flow routes"," — directed paths that follow your modeled data flows — to your crown jewels, or between any two elements you choose. For each route it shows you how many hops it takes, where it crosses a security boundary, what data sensitivity it carries, and the worst live threat sitting on it.",[14,27,28,29,32,33,38],{},"Before you read any of that, read this once: ",[18,30,31],{},"these are flow routes, not attack paths."," The tab models your topology — how flows connect — and nothing about how hard a real attacker would work to traverse them. Used with that framing, it is a sharp tool for validating your segmentation intent and spotting surprises. Used as an attack-path predictor, it will mislead you and anyone you brief. The whole of ",[34,35,37],"a",{"href":36},"#how-to-read-this-correctly","How to Read This Correctly"," exists to keep you on the right side of that line, and the same caveat is printed at the top of the tab itself.",[40,41],"hr",{},[43,44,46],"h2",{"id":45},"three-ways-to-trace","Three Ways to Trace",[14,48,49],{},"The tab opens on a short caveat line and a three-button toggle:",[51,52,58],"div",{"className":53,"tabIndex":55,"role":56,"ariaLabel":57},[54],"table-frame",0,"region","Table: Three Ways to Trace",[59,60,61,77],"table",{},[62,63,64],"thead",{},[65,66,67,71,74],"tr",{},[68,69,70],"th",{},"Mode",[68,72,73],{},"Button",[68,75,76],{},"Use it to",[78,79,80,96,110],"tbody",{},[65,81,82,88,93],{},[83,84,85],"td",{},[18,86,87],{},"Crown-jewel reachability",[83,89,90],{},[91,92,87],"code",{},[83,94,95],{},"Rank your crown jewels by whether — and how directly — they can be reached from a chosen origin.",[65,97,98,103,107],{},[83,99,100],{},[18,101,102],{},"Pick two",[83,104,105],{},[91,106,102],{},[83,108,109],{},"Trace and read the individual flow routes between any two elements you select.",[65,111,112,117,121],{},[83,113,114],{},[18,115,116],{},"Blast radius",[83,118,119],{},[91,120,116],{},[83,122,123,124,128],{},"Pick one node and see ",[125,126,127],"em",{},"everything"," it can reach by modeled flows — the containment question: \"if this were compromised, how far does it spread?\"",[14,130,131,132,134,135,137],{},"A faithful minimap of your model sits alongside all three modes. It paints the active route — or, in ",[18,133,116],{},", the whole reachable cone — so you can see it in the shape of your real diagram, and in ",[18,136,102],{}," it doubles as a way to choose your endpoints by clicking nodes.",[139,140,141],"blockquote",{},[14,142,143,146,147,149,150,152],{},[18,144,145],{},"Crown jewels come first."," A crown jewel is a component you have flagged as a high-value asset (the crown toggle on a component's settings). If no component in the model is flagged, ",[18,148,87],{}," has nothing to rank — it tells you so and points you to ",[18,151,102],{},", which traces routes between any elements regardless of flagging.",[40,154],{},[43,156,158],{"id":157},"crown-jewel-reachability","Crown-Jewel Reachability",[14,160,161],{},"This mode answers one question for every crown jewel in the model: starting from a chosen origin, is there a modeled flow route to it — and if so, how direct is it?",[163,164,166],"h3",{"id":165},"choosing-the-origin","Choosing the origin",[14,168,16,169,172],{},[18,170,171],{},"From"," selector sets where routes start. It defaults to the model's external entry-points and lets you choose any single node instead.",[51,174,177],{"className":175,"tabIndex":55,"role":56,"ariaLabel":176},[54],"Table: Choosing the origin",[59,178,179,189],{},[62,180,181],{},[65,182,183,186],{},[68,184,185],{},"Origin",[68,187,188],{},"What it means",[78,190,191,202],{},[65,192,193,199],{},[83,194,195,198],{},[18,196,197],{},"External entry-points"," (default)",[83,200,201],{},"Every external entity in the model becomes a starting point at once. This is the structural \"from outside the model\" view.",[65,203,204,210],{},[83,205,206,209],{},[18,207,208],{},"A single node"," (assumed-breach)",[83,211,212,213,216],{},"You pick one component and ask: if this node were the starting point, which crown jewels could be reached onward from it? The label reads ",[91,214,215],{},"assuming \u003Cnode> is breached",".",[139,218,219],{},[14,220,221,224,225,228],{},[18,222,223],{},"\"Assumed-breach\" is a structural premise, not a verdict."," Choosing a node as the origin does not say that node is weak, untrusted, or compromised. It is simply a what-if: ",[125,226,227],{},"start the trace here."," The tab never makes a trust judgment about any node.",[14,230,231],{},"If the model has no external entities, the default origin has nothing to start from. The tab says so and invites you to pick a specific node as an assumed-breach origin instead.",[163,233,235],{"id":234},"reading-the-per-jewel-results","Reading the per-jewel results",[14,237,238,239,242],{},"A summary line reports how many of your crown jewels are reachable from the chosen origin — for example ",[91,240,241],{},"3 of 5 crown jewels reachable from external entry",". Below it, each crown jewel appears as a row:",[51,244,247],{"className":245,"tabIndex":55,"role":56,"ariaLabel":246},[54],"Table: Reading the per-jewel results",[59,248,249,259],{},[62,250,251],{},[65,252,253,256],{},[68,254,255],{},"You see",[68,257,258],{},"It means",[78,260,261,272,282,296],{},[65,262,263,269],{},[83,264,265,266],{},"A filled dot and ",[18,267,268],{},"reachable",[83,270,271],{},"A modeled flow route exists from the origin to this jewel.",[65,273,274,279],{},[83,275,276],{},[91,277,278],{},"shortest route N hops · M crossings",[83,280,281],{},"The fewest data-flow steps to reach it, and how many boundary crossings that shortest route makes.",[65,283,284,289],{},[83,285,286],{},[91,287,288],{},"worst on any route: \u003Cband>",[83,290,291,292,295],{},"The most severe live threat sitting on ",[125,293,294],{},"any"," route to this jewel (this may be a longer route than the shortest one).",[65,297,298,304],{},[83,299,300,301],{},"An open dot and ",[18,302,303],{},"no modeled flow route",[83,305,306],{},"No directed flow route from the origin reaches this jewel in the model.",[14,308,309,310,313,314,317,318,320,321,324],{},"A jewel name is clickable — it opens that element's ",[18,311,312],{},"Component Profile",". Reachable jewels also offer ",[18,315,316],{},"view strip"," (open the shortest route as a readable strip in ",[18,319,102],{},") and ",[18,322,323],{},"show on map"," (paint the route on the minimap).",[139,326,327],{},[14,328,329,332,333,336,337,340],{},[18,330,331],{},"Read \"no modeled flow route\" as exactly that — a statement about the model, not a guarantee."," It means the diagram contains no directed chain of data flows from the origin to this jewel. It does ",[18,334,335],{},"not"," mean the asset is segmented, isolated, or safe. The most common cause is an incomplete model. When a count reads ",[91,338,339],{},"0 reachable",", the tab deliberately labels it a modeled-topology gap and points you to the report's scope banner — never a reassuring green.",[163,342,344],{"id":343},"tracing-onward-step-by-step","Tracing onward, step by step",[14,346,347,348,351],{},"Each node on a route carries an ",[18,349,350],{},"onward"," action. Clicking it re-anchors the origin to that node and recomputes the crown-jewel list from there. This lets you explore a model one step at a time — \"starting from here, what's reachable next; and from there, what next\" — without typing in new endpoints each time. It is a navigation aid for following the topology, nothing more.",[40,353],{},[43,355,357],{"id":356},"pick-two","Pick Two",[14,359,360,362],{},[18,361,102],{}," enumerates the flow routes between any two elements you choose and renders one of them as a readable strip.",[163,364,366],{"id":365},"choosing-the-endpoints","Choosing the endpoints",[14,368,369,370,372,373,376],{},"You have two ways to set the ",[18,371,185],{}," and ",[18,374,375],{},"Target",", and they stay in sync:",[378,379,380,392],"ul",{},[381,382,383,386,387,372,389,391],"li",{},[18,384,385],{},"The autocompletes."," Type into the ",[91,388,185],{},[91,390,375],{}," fields and choose from the list. Each is clearable.",[381,393,394,397,398,401],{},[18,395,396],{},"The minimap."," Enlarge the map with its expand button (top-left corner), then click nodes directly: your first click sets the origin (it shows a dashed outline as a pending pick), the second sets the target, and a third click starts over. A ",[18,399,400],{},"reset selection"," link clears both.",[14,403,404],{},"The map hint below the minimap tells you which endpoint it's waiting for next.",[163,406,408],{"id":407},"reading-the-route-strip","Reading the route strip",[14,410,411],{},"Once both endpoints are set, the tab lists the routes it found, shortest first. Selecting a route draws it as a linear strip — like a transit line — that reads left to right from origin to target:",[51,413,416],{"className":414,"tabIndex":55,"role":56,"ariaLabel":415},[54],"Table: Reading the route strip",[59,417,418,428],{},[62,419,420],{},[65,421,422,425],{},[68,423,424],{},"Strip element",[68,426,427],{},"What it tells you",[78,429,430,440,448,468,482],{},[65,431,432,435],{},[83,433,434],{},"A node glyph and name",[83,436,437,438,216],{},"A component on the route. A crown jewel uses a distinct hexagon glyph. The name opens its ",[18,439,312],{},[65,441,442,445],{},[83,443,444],{},"An italic flow name between nodes",[83,446,447],{},"The data flow making that hop. Click it to open the flow's profile.",[65,449,450,453],{},[83,451,452],{},"A sensitivity chip on a hop",[83,454,455,456,459,460,463,464,467],{},"The highest data ",[18,457,458],{},"sensitivity"," that flow carries (for example ",[91,461,462],{},"Restricted","). ",[91,465,466],{},"unclassified"," means the flow carries data with no sensitivity set, which is not the same as Public.",[65,469,470,479],{},[83,471,472,475,476],{},[91,473,474],{},"◂ EXIT \u003Cboundary>"," \u002F ",[91,477,478],{},"▸ ENTER \u003Cboundary>",[83,480,481],{},"A security-boundary crossing on that hop. The flow leaves one boundary (EXIT) or enters another (ENTER). Click it to open the boundary.",[65,483,484,487],{},[83,485,486],{},"A colored dot",[83,488,489],{},"The worst live threat on that node or flow, by severity band (critical, high, medium, low).",[14,491,492,493,495],{},"Each node also carries the same ",[18,494,350],{}," action as crown-jewel mode, so you can pivot from any point on a strip into a fresh trace.",[163,497,499],{"id":498},"when-there-are-many-routes-or-none","When there are many routes — or none",[14,501,502,503,506],{},"Route enumeration is ",[18,504,505],{},"bounded",": routes are simple paths (no node is visited twice), capped in length and in how many are collected. The tab is always honest about that boundary:",[51,508,511],{"className":509,"tabIndex":55,"role":56,"ariaLabel":510},[54],"Table: When there are many routes — or none",[59,512,513,521],{},[62,514,515],{},[65,516,517,519],{},[68,518,255],{},[68,520,258],{},[78,522,523,533,543,553,566],{},[65,524,525,530],{},[83,526,527],{},[91,528,529],{},"N flow routes found",[83,531,532],{},"The full set fit within the limits — this is all of them.",[65,534,535,540],{},[83,536,537],{},[91,538,539],{},"Showing X of N routes.",[83,541,542],{},"More routes exist than are shown; X are displayed out of N counted.",[65,544,545,550],{},[83,546,547],{},[91,548,549],{},"Showing X routes — enumeration capped; more exist.",[83,551,552],{},"The model is dense enough that enumeration stopped early. The exact total is not claimed.",[65,554,555,560],{},[83,556,557],{},[91,558,559],{},"No routes within 6 hops connect \u003Corigin> → \u003Ctarget> (respecting flow direction) — longer routes are not enumerated.",[83,561,562,563,565],{},"Nothing was found inside the hop limit. The tab adds that this reflects the modeled topology, not a segmentation assessment. It is ",[18,564,335],{}," a claim that no path exists — a route longer than the limit would not be enumerated.",[65,567,568,573],{},[83,569,570],{},[91,571,572],{},"No routes within 6 hops were enumerated between \u003Corigin> → \u003Ctarget> — they connect only by longer routes.",[83,574,575,576,579],{},"The stronger variant, shown when the choke-point analysis has established that the target ",[125,577,578],{},"is"," reachable: the two are connected, just not within the hop limit. That analysis covers every route, of any length.",[14,581,582,583,586],{},"The hop limit is ",[18,584,585],{},"6",". It bounds enumeration, not reality: read \"no routes\" as \"none within six hops,\" never as \"no connection.\"",[14,588,589],{},"This banner is persistent — it stays on screen and travels into exports. The tab never silently truncates a route list.",[163,591,593],{"id":592},"choke-points-the-node-every-route-must-pass-through","Choke points — the node every route must pass through",[14,595,596,597,599,600,607,608,611],{},"Above the route list, whenever the target is reachable, ",[18,598,102],{}," answers the question the routes only imply: ",[125,601,602,603,606],{},"of all the ways from origin to target, which node does ",[18,604,605],{},"every"," one of them go through?"," That node is a ",[18,609,610],{},"choke point"," — controlling it severs every modeled flow route between the two. It is the defender's \"where do I place one control\" lever.",[51,613,616],{"className":614,"tabIndex":55,"role":56,"ariaLabel":615},[54],"Table: Choke points — the node every route must pass through",[59,617,618,626],{},[62,619,620],{},[65,621,622,624],{},[68,623,255],{},[68,625,258],{},[78,627,628,642,652],{},[65,629,630,636],{},[83,631,632,635],{},[91,633,634],{},"Every modeled route passes through: \u003Cnode>"," (a chain when there are several)",[83,637,638,639,641],{},"Each listed node sits on ",[125,640,605],{}," origin→target route — an ordered sequence the routes share. Each chip opens its profile and shows its worst-threat band and the boundaries crossed to reach it.",[65,643,644,649],{},[83,645,646],{},[91,647,648],{},"A direct modeled flow connects them — no intermediary to control",[83,650,651],{},"The origin flows straight to the target; there is no in-between node to harden.",[65,653,654,659],{},[83,655,656],{},[91,657,658],{},"No single choke point — at least two internally disjoint routes exist",[83,660,661],{},"The routes fan out enough that no one node is on all of them; controlling any single node leaves another route open.",[14,663,664,665,667,668,671,672,675,676,678,679,681],{},"Two things make this trustworthy. First, it is computed by testing whether removing a node disconnects the target — ",[18,666,335],{}," by intersecting the route list above — so it stays ",[18,669,670],{},"complete even when route enumeration is capped"," (the strip says so when that happens). Second, the caveat stays attached: a choke point sits on every ",[125,673,674],{},"modeled"," flow route only. Controlling it does ",[18,677,335],{}," address unmodeled flows, shared credentials, or non-flow lateral movement, and \"no single choke point\" is ",[18,680,335],{}," a verdict that the path is well-segmented. The number of choke points is never a risk score.",[40,683],{},[43,685,687],{"id":686},"blast-radius","Blast Radius",[14,689,690,691,694,695,697,698,701,702,705],{},"Where the first two modes ask ",[125,692,693],{},"\"which flow routes lead to a specific target?\"",", ",[18,696,116],{}," asks the ",[18,699,700],{},"containment"," question: ",[125,703,704],{},"if this one node were compromised, how much of the model is exposed?"," You pick a node — its assumed-breach origin — and the tab shows every component reachable from it by following modeled flows downstream.",[163,707,709],{"id":708},"choosing-the-node-and-the-scope","Choosing the node and the scope",[14,711,16,712,715],{},[18,713,714],{},"Assume breached"," selector picks the origin node — or click any node directly on the minimap (enlarge it with ⤢ for easier clicks); clicking another node re-anchors the radius. A two-button toggle sets how far the radius extends:",[51,717,720],{"className":718,"tabIndex":55,"role":56,"ariaLabel":719},[54],"Table: Choosing the node and the scope",[59,721,722,732],{},[62,723,724],{},[65,725,726,729],{},[68,727,728],{},"Scope",[68,730,731],{},"What it shows",[78,733,734,744],{},[65,735,736,741],{},[83,737,738,198],{},[18,739,740],{},"Full radius",[83,742,743],{},"Every component transitively reachable downstream — the complete blast radius. Each node is labelled with how many hops away it is.",[65,745,746,751],{},[83,747,748],{},[18,749,750],{},"Direct (1-hop)",[83,752,753],{},"Only the immediate downstream neighbours — the nodes one flow away.",[14,755,756,757,760,761,764],{},"The radius is ",[18,758,759],{},"forward only",": it follows flow direction outward from the node to what its flows lead ",[125,762,763],{},"to",", never backward toward it.",[163,766,768],{"id":767},"reading-the-radius","Reading the radius",[14,770,771,772,775,776,779,780,783,784,787],{},"A summary line reports the triage signals — for example ",[91,773,774],{},"Storefront reaches 5 of 6 other components · ⬢ 3 crown jewels in radius · worst in radius: Critical",". Directly below it, a ",[18,777,778],{},"containment row"," lists the distinct trust boundaries the blast crosses — ",[91,781,782],{},"Crosses 2 trust boundaries: DMZ, App"," (each name clickable into its profile). If no modeled flow leaves the origin's own boundary, that row reads ",[91,785,786],{},"No modeled flow leaves its boundary — a containment signal, not a segmentation guarantee"," instead.",[14,789,790],{},"Below that, each reachable node is a row, ordered nearest-first:",[51,792,795],{"className":793,"tabIndex":55,"role":56,"ariaLabel":794},[54],"Table: Reading the radius",[59,796,797,805],{},[62,798,799],{},[65,800,801,803],{},[68,802,255],{},[68,804,258],{},[78,806,807,818,828,848,880,888,896,908],{},[65,808,809,815],{},[83,810,811,814],{},[91,812,813],{},"⬢"," before the name",[83,816,817],{},"This reachable node is a crown jewel — a high-value asset caught in the radius.",[65,819,820,825],{},[83,821,822],{},[91,823,824],{},"N hops",[83,826,827],{},"The fewest flow steps to reach it from the origin.",[65,829,830,835],{},[83,831,832],{},[91,833,834],{},"first → \u003Cflow> [sensitivity]",[83,836,16,837,840,841,844,845,847],{},[18,838,839],{},"first hop out of the breached origin"," on the shortest route to this node — the first flow along that route, and the data that flow carries ",[125,842,843],{},"in motion"," (distinct from the data the node handles at rest). The flow name opens its profile. For a direct (1-hop) neighbour this is simply the origin→node flow. ",[91,846,466],{}," means the flow carries data with no sensitivity set (not the same as Public).",[65,849,850,859],{},[83,851,852,475,855,858],{},[91,853,854],{},"◂ EXIT",[91,856,857],{},"▸ ENTER"," boundary chips",[83,860,16,861,864,865,868,869,872,873,875,876,879],{},[18,862,863],{},"net"," trust-boundary crossings from the breached origin to this node — which zones the blast leaves and enters to reach it (e.g. ",[91,866,867],{},"◂ Web tier ▸ API tier","). Same vocabulary as ",[18,870,871],{},"Boundary Crossings","; each chip opens that boundary's profile. This is the ",[125,874,863],{}," origin→node delta, not a per-hop tally — so a node that sits back in the origin's own zone shows ",[91,877,878],{},"· same zone as origin"," rather than chips, even if it is several hops away.",[65,881,882,885],{},[83,883,884],{},"A severity dot + band",[83,886,887],{},"The worst live threat sitting on that reachable node.",[65,889,890,893],{},[83,891,892],{},"A sensitivity chip",[83,894,895],{},"Sensitive data that node handles.",[65,897,898,902],{},[83,899,900],{},[18,901,316],{},[83,903,904,905,907],{},"Open the route(s) from the breached origin to this node in ",[18,906,102],{}," — the full flow-by-flow strip, with every hop's data and boundary crossings.",[65,909,910,915],{},[83,911,912],{},[91,913,914],{},"▸ set as origin",[83,916,917,918,921],{},"Re-anchor the radius to ",[125,919,920],{},"that"," node — trace its own blast radius, step by step outward.",[14,923,924],{},"The whole reachable cone is painted on the minimap at once, so you can see the spread in the shape of your real diagram.",[139,926,927],{},[14,928,929,932,933,935,936,939],{},[18,930,931],{},"An empty radius is a containment result, not a clean bill of health."," If a node reaches nothing downstream, the tab says so plainly — and immediately adds that this is ",[18,934,335],{}," a proof of isolation. Unmodeled flows, shared credentials, and non-flow vectors are all outside what this view can see. Read it as \"no ",[125,937,938],{},"modeled flow"," spreads from here,\" never as \"this node is safely contained.\" The blast radius is a reachability count, never a risk score.",[40,941],{},[43,943,945],{"id":944},"the-minimap-and-the-route-legend","The Minimap and the Route Legend",[14,947,948],{},"The minimap is a small, faithful copy of your hand-laid diagram — it uses your real layout, not an auto-generated one. It serves all three modes:",[378,950,951,961,967],{},[381,952,953,956,957,960],{},[18,954,955],{},"Crown jewels"," are drawn in red and ",[18,958,959],{},"external entry-points"," in amber, so you can spot them at a glance.",[381,962,16,963,966],{},[18,964,965],{},"active route"," is painted in cyan — both the nodes and the exact flow edges along it — so you can see the route in the context of the whole model.",[381,968,969,970,972],{},"The expand button opens a larger, labeled view. In ",[18,971,102],{}," that enlarged map is the primary place to click your two endpoints.",[14,974,975,976,979,980,982,983,986,987,990,991,216],{},"A ",[18,977,978],{},"Route legend"," appears beneath the minimap in ",[18,981,102],{},", decoding the strip's glyphs: the component and crown-jewel markers, the flow-name connector, the ",[91,984,985],{},"EXIT","\u002F",[91,988,989],{},"ENTER"," crossing signs, the worst-threat dots from critical to low, and the data-sensitivity chips. The legend reuses the strip's own colors, so what you see in the legend matches the strip exactly. The shared minimap and sensitivity vocabulary are described once in ",[34,992,994],{"href":993},"\u002Fthreat-report\u002Freading-the-report","Reading the Report",[40,996],{},[43,998,37],{"id":999},"how-to-read-this-correctly",[14,1001,1002,1003,1006],{},"This is the part to internalize before you brief anyone. The tab is a ",[18,1004,1005],{},"topological"," view. It tells you how your modeled data flows connect — and deliberately models nothing about attacker behavior.",[163,1008,1010],{"id":1009},"flow-routes-are-not-attack-paths","Flow routes are not attack paths",[14,1012,1013,1014,1017],{},"A route here is a chain of ",[125,1015,1016],{},"modeled data flows",", traced in the direction those flows run. It is not a sequence of exploits, and it makes no claim that an attacker could actually walk it. Two systems that exchange data are connected by a flow route whether or not that connection is exploitable.",[163,1019,1021],{"id":1020},"a-hop-count-is-proximity-not-effort","A hop count is proximity, not effort",[14,1023,1024,1027,1028,1030],{},[91,1025,1026],{},"3 hops"," means three data-flow steps along the diagram. It does ",[18,1029,335],{}," mean three steps of attacker work, three vulnerabilities, or \"easy.\" A three-hop route across hardened, well-controlled systems is harder to abuse than a one-hop route across an unpatched one — and the tab cannot tell the difference, because effort is not what it measures.",[163,1032,1034],{"id":1033},"what-the-analysis-does-not-model","What the analysis does not model",[14,1036,1037,1038,1040],{},"The trace is purely structural. It does ",[18,1039,335],{}," account for:",[378,1042,1043,1049,1055,1061],{},[381,1044,1045,1048],{},[18,1046,1047],{},"Credential reuse or token theft"," — moving by stealing an identity rather than by following a flow.",[381,1050,1051,1054],{},[18,1052,1053],{},"Exploit chaining"," — stringing vulnerabilities together to pivot.",[381,1056,1057,1060],{},[18,1058,1059],{},"Controls as obstacles"," — a route's hop count is unchanged by how well each node is defended.",[381,1062,1063,1066],{},[18,1064,1065],{},"Trust levels"," — the origin set is external entities or a node you chose, never an \"untrusted\" classification.",[14,1068,1069,1070,1073],{},"The threat dots on a route tell you which ",[125,1071,1072],{},"modeled findings"," sit on those elements; they do not turn the route into an exploitability estimate.",[163,1075,1077],{"id":1076},"no-modeled-flow-route-is-not-safe","\"No modeled flow route\" is not \"safe\"",[14,1079,1080,1081,1084],{},"This is the easiest claim to get wrong. An unreachable crown jewel means the ",[125,1082,1083],{},"model"," contains no directed flow chain to it — most often because the model is incomplete, not because the asset is isolated. Always check the report's scope banner alongside it. Never report an unreachable jewel as \"segmented\" or \"protected.\"",[163,1086,1088],{"id":1087},"language-to-use-with-stakeholders","Language to use with stakeholders",[139,1090,1091,1097],{},[14,1092,1093,1096],{},[18,1094,1095],{},"Say this:"," \"In our model, customer records are reachable from external entry in two flow hops, crossing one boundary, with a high-severity finding on the route.\" This is precise and defensible.",[14,1098,1099,1102],{},[18,1100,1101],{},"Not this:"," \"An attacker can reach customer records in two steps.\" That over-claims — it converts a modeling statement into an attack prediction the tool never made.",[40,1104],{},[43,1106,1108],{"id":1107},"common-uses","Common Uses",[14,1110,1111],{},"Within those limits, the tab earns its place in a review:",[378,1113,1114,1123,1132,1152,1165],{},[381,1115,1116,1119,1120,1122],{},[18,1117,1118],{},"Validate segmentation intent."," You believe a sensitive store should only be reachable through a gateway. Set the store as a ",[18,1121,102],{}," target (or check it in crown-jewel mode) and confirm every route passes through the boundary and node you expect. A route that skips them is a modeling finding worth investigating — either the model is wrong, or your segmentation is.",[381,1124,1125,1128,1129,1131],{},[18,1126,1127],{},"Spot unexpectedly short routes to crown jewels."," A crown jewel reachable from external entry in one hop is worth a second look. The hop count won't tell you it's exploitable, but a surprisingly direct ",[125,1130,674],{}," connection is exactly the kind of thing a design review should question.",[381,1133,1134,1137,1138,986,1140,1142,1143,1145,1146,1149,1150,216],{},[18,1135,1136],{},"Find sensitive data crossing boundaries."," Read the sensitivity chips and ",[91,1139,985],{},[91,1141,989],{}," signs along a route to see where ",[91,1144,462],{}," or ",[91,1147,1148],{},"Confidential"," data leaves one boundary and enters another. That tells you where to focus controls and where to look harder in ",[34,1151,871],{"href":993},[381,1153,1154,1157,1158,1160,1161,1164],{},[18,1155,1156],{},"Walk an assumed-breach what-if."," Pick a node as the origin and use ",[18,1159,350],{}," to step through what the topology connects to from there — a structured way to explore reach ",[125,1162,1163],{},"in the model",", framed honestly as topology rather than prediction.",[381,1166,1167,1170,1171,1173,1174,1177],{},[18,1168,1169],{},"Size a node's blast radius."," Use ",[18,1172,116],{}," to ask the containment question directly: if this node fell, how many components — and which crown jewels — does a modeled flow reach from it? A surprisingly wide radius is a segmentation prompt; a narrow one is a containment signal (not a safety guarantee). Use ",[18,1175,1176],{},"set as origin"," to walk the spread node by node.",[40,1179],{},[43,1181,1183],{"id":1182},"next-steps","Next Steps",[378,1185,1186,1195,1211,1223,1232],{},[381,1187,1188,1192,1193,216],{},[18,1189,1190],{},[34,1191,994],{"href":993}," — the shared minimap and data-sensitivity language, plus ",[18,1194,871],{},[381,1196,1197,1203,1204,1207,1208,1210],{},[18,1198,1199],{},[34,1200,1202],{"href":1201},"\u002Fthreat-report\u002Fworking-with-findings","Working with Findings"," — the ",[18,1205,1206],{},"Residual Risk"," ledger and the ",[18,1209,312],{}," that route elements drill into.",[381,1212,1213,1203,1219,1222],{},[18,1214,1215],{},[34,1216,1218],{"href":1217},"\u002Fthreat-report\u002Funderstanding-coverage","Understanding Coverage",[18,1220,1221],{},"Coverage & Gaps"," MITRE ATT&CK matrix.",[381,1224,1225,1231],{},[18,1226,1227],{},[34,1228,1230],{"href":1229},"\u002Fthreat-report\u002Fgetting-started","Getting Started"," — generate, refresh, and export the report.",[381,1233,1234,1240],{},[18,1235,1236],{},[34,1237,1239],{"href":1238},"\u002Fthreat-report","Guide Index"," — the full Threat Report documentation set.",{"title":1242,"searchDepth":1243,"depth":1243,"links":1244},"",3,[1245,1247,1252,1258,1262,1263,1270,1271],{"id":45,"depth":1246,"text":46},2,{"id":157,"depth":1246,"text":158,"children":1248},[1249,1250,1251],{"id":165,"depth":1243,"text":166},{"id":234,"depth":1243,"text":235},{"id":343,"depth":1243,"text":344},{"id":356,"depth":1246,"text":357,"children":1253},[1254,1255,1256,1257],{"id":365,"depth":1243,"text":366},{"id":407,"depth":1243,"text":408},{"id":498,"depth":1243,"text":499},{"id":592,"depth":1243,"text":593},{"id":686,"depth":1246,"text":687,"children":1259},[1260,1261],{"id":708,"depth":1243,"text":709},{"id":767,"depth":1243,"text":768},{"id":944,"depth":1246,"text":945},{"id":999,"depth":1246,"text":37,"children":1264},[1265,1266,1267,1268,1269],{"id":1009,"depth":1243,"text":1010},{"id":1020,"depth":1243,"text":1021},{"id":1033,"depth":1243,"text":1034},{"id":1076,"depth":1243,"text":1077},{"id":1087,"depth":1243,"text":1088},{"id":1107,"depth":1246,"text":1108},{"id":1182,"depth":1246,"text":1183},"Exploring flow routes to crown-jewel assets and between any two elements — and what the analysis does and does not model","md",{"category":1275,"position":1276,"tags":1277},"documentation",5,[1278,1279,1280,1281],"threat-report","reachability","flow-routes","crown-jewels",true,"\u002Fthreat-report\u002Freachability",{"title":5,"description":1272},"04.threat-report\u002F04.reachability","IG5gTV_ZGY0OOHsMBprJprUfTNZi6SJGB3dWFGXzrhs",[1288,1343,1378,1433,1456,1499,1514,1584],{"title":1289,"description":1290,"path":1291,"stem":1292,"children":1293,"page":-1},"Platform","Modelling, analysis, findings and controls in the Dethernety platform.","\u002Fplatform","01.platform",[1294,1298,1303,1308,1313,1318,1323,1328,1333,1338],{"title":1295,"path":1291,"stem":1296,"description":1297},"Dethernety User Documentation","01.platform\u002Findex","User guide for the Dethernety threat modeling platform",{"title":1299,"path":1300,"stem":1301,"description":1302},"Quick Start","\u002Fplatform\u002Fquick-start","01.platform\u002F01.quick-start","Install Dethernety on your own machine, draw a four-element model and read its first threat finding.",{"title":1304,"path":1305,"stem":1306,"description":1307},"Building Your First Model","\u002Fplatform\u002Fbuilding-your-first-model","01.platform\u002F02.building-your-first-model","Build a threat model of an online store in about 30 minutes, run a Threat Report on it, and raise an issue from a finding.",{"title":1309,"path":1310,"stem":1311,"description":1312},"Security Analysis Workflow","\u002Fplatform\u002Fsecurity-analysis-workflow","01.platform\u002F03.security-analysis-workflow","How to run security analysis and interpret results to improve your threat models.",{"title":1314,"path":1315,"stem":1316,"description":1317},"Managing Findings","\u002Fplatform\u002Fmanaging-findings","01.platform\u002F04.managing-findings","Record decisions on system-generated exposures and countermeasures — affirm them as confirmed live risk, or mute them as not applicable, false positive, waived, or superseded — instead of deleting them.",{"title":1319,"path":1320,"stem":1321,"description":1322},"Working with Security Controls","\u002Fplatform\u002Fworking-with-security-controls","01.platform\u002F05.working-with-security-controls","Learn how to create, manage, and assign reusable security controls in Dethernety to protect your threat models.",{"title":1324,"path":1325,"stem":1326,"description":1327},"Issue Management Guide","\u002Fplatform\u002Fissue-management-guide","01.platform\u002F06.issue-management-guide","Issue tracking, filtering, and management in Dethernety.",{"title":1329,"path":1330,"stem":1331,"description":1332},"Boundary Trust Zones","\u002Fplatform\u002Fboundary-trust-zones","01.platform\u002F07.boundary-trust-zones","Record each security boundary's trust zone, business domains, operational role, and approved channels to document how your system is meant to be segmented.",{"title":1334,"path":1335,"stem":1336,"description":1337},"Understanding Modules","\u002Fplatform\u002Funderstanding-modules","01.platform\u002F08.understanding-modules","How Dethernety's module system extends your threat modeling capabilities.",{"title":1339,"path":1340,"stem":1341,"description":1342},"Component Configuration Guide","\u002Fplatform\u002Fcomponent-configuration-guide","01.platform\u002F09.component-configuration-guide","Detailed guide on configuring different types of components and their security implications.",{"title":1344,"description":1345,"path":1346,"stem":1347,"children":1348,"page":-1},"BYODt cloud","Deploying the platform yourself and connecting it to the BYODt cloud.","\u002Fbyodt-cloud","02.byodt-cloud",[1349,1353,1358,1363,1368,1373],{"title":1350,"path":1346,"stem":1351,"description":1352},"BYODt Deployment","02.byodt-cloud\u002Findex","Run Dethernety on your own machine: install, configure, operate, and recover",{"title":1354,"path":1355,"stem":1356,"description":1357},"Installing the BYODt Deployment","\u002Fbyodt-cloud\u002Finstallation","02.byodt-cloud\u002F01.installation","Install Dethernety on your own machine: check the requirements, download and verify the signed bundle, start it, and confirm the deployment is healthy",{"title":1359,"path":1360,"stem":1361,"description":1362},"Configuring the BYODt Deployment","\u002Fbyodt-cloud\u002Fconfiguration","02.byodt-cloud\u002F02.configuration","The .env settings reference, the generated secret file, database storage, and how to apply a change",{"title":1364,"path":1365,"stem":1366,"description":1367},"Operating the BYODt Deployment","\u002Fbyodt-cloud\u002Foperations","02.byodt-cloud\u002F03.operations","The byodt command reference and the day-to-day tasks: start, stop, inspect, back up, restore, TLS, upgrade, remove",{"title":1369,"path":1370,"stem":1371,"description":1372},"Connecting the BYODt Deployment to the Cloud","\u002Fbyodt-cloud\u002Fcloud","02.byodt-cloud\u002F04.cloud","Add cloud sign-in and content packages from the operator console, and disconnect again",{"title":1374,"path":1375,"stem":1376,"description":1377},"Troubleshooting the BYODt Deployment","\u002Fbyodt-cloud\u002Ftroubleshooting","02.byodt-cloud\u002F05.troubleshooting","Symptom, cause, and fix for the failures this deployment reports",{"title":1379,"description":1380,"path":1381,"stem":1382,"children":1383,"page":-1},"Dethereal","The Claude Code plugin: build a threat model in conversation and publish it to the platform.","\u002Fdethereal","03.dethereal",[1384,1388,1393,1398,1403,1408,1413,1418,1423,1428],{"title":1385,"path":1381,"stem":1386,"description":1387},"Dethereal — Claude Code Plugin for Threat Modeling","03.dethereal\u002Findex","Comprehensive documentation for the Dethereal threat modeling plugin",{"title":1389,"path":1390,"stem":1391,"description":1392},"Getting Started with Dethereal","\u002Fdethereal\u002Fgetting-started","03.dethereal\u002F01.getting-started","Install the plugin, authenticate, and create your first threat model",{"title":1394,"path":1395,"stem":1396,"description":1397},"The 11-Step Guided Workflow","\u002Fdethereal\u002Fguided-workflow","03.dethereal\u002F02.guided-workflow","Complete walkthrough of the \u002Fdethereal:threat-model guided process",{"title":1399,"path":1400,"stem":1401,"description":1402},"Command Reference","\u002Fdethereal\u002Fcommand-reference","03.dethereal\u002F03.command-reference","Complete reference for all 14 Dethereal slash commands",{"title":1404,"path":1405,"stem":1406,"description":1407},"Threat Model Concepts","\u002Fdethereal\u002Fmodel-concepts","03.dethereal\u002F04.model-concepts","Components, boundaries, data flows, classes, attributes, and quality scoring",{"title":1409,"path":1410,"stem":1411,"description":1412},"Discovery and Enrichment","\u002Fdethereal\u002Fdiscovery-and-enrichment","03.dethereal\u002F05.discovery-and-enrichment","Infrastructure scanning, security attributes, MITRE ATT&CK, credentials, and compliance",{"title":1414,"path":1415,"stem":1416,"description":1417},"Sync and Version Control","\u002Fdethereal\u002Fsync-and-version-control","03.dethereal\u002F06.sync-and-version-control","Push\u002Fpull workflow, conflict handling, git integration, and multi-model projects",{"title":1419,"path":1420,"stem":1421,"description":1422},"Review and Attack Surface Analysis","\u002Fdethereal\u002Freview-and-analysis","03.dethereal\u002F07.review-and-analysis","Quality review, attack surface summary, and platform analysis integration",{"title":1424,"path":1425,"stem":1426,"description":1427},"Agents, Tools, and Hooks","\u002Fdethereal\u002Fagents-and-architecture","03.dethereal\u002F08.agents-and-architecture","How the 5 AI agents, 22 MCP tools, and 3 lifecycle hooks work together",{"title":1429,"path":1430,"stem":1431,"description":1432},"Dethereal Glossary","\u002Fdethereal\u002Fglossary","03.dethereal\u002F09.glossary","Definitions for Dethereal-specific terminology",{"title":1434,"description":1435,"path":1238,"stem":1436,"children":1437,"page":-1},"Threat Report","The residual-risk report over a threat model: reading it, filtering it and exporting it.","04.threat-report",[1438,1441,1445,1448,1452,1453],{"title":1434,"path":1238,"stem":1439,"description":1440},"04.threat-report\u002Findex","Read, filter, drill into, and export a residual-risk report over a threat model",{"title":1442,"path":1229,"stem":1443,"description":1444},"Getting Started with the Threat Report","04.threat-report\u002F01.getting-started","Generate, open, refresh, and export a threat report over a model",{"title":994,"path":993,"stem":1446,"description":1447},"04.threat-report\u002F02.reading-the-report","Navigating the report, the shared visual language, and the Posture and Boundary Crossings views",{"title":1449,"path":1217,"stem":1450,"description":1451},"Understanding Coverage and Gaps","04.threat-report\u002F03.understanding-coverage","Reading the MITRE ATT&CK coverage matrix: tiers, prevent vs detect, off-grid notes, and what coverage does and does not mean",{"title":5,"path":1283,"stem":1285,"description":1272},{"title":1202,"path":1201,"stem":1454,"description":1455},"04.threat-report\u002F05.working-with-findings","The Residual Risk ledger, triaging findings, filtering, and the per-element Component Profile",{"title":1457,"description":1458,"path":1459,"stem":1460,"children":1461,"page":-1},"Risk assessment","The risk assessment module: the register, the reports and the method behind them.","\u002Frisk-assessment","05.risk-assessment",[1462,1466,1471,1476,1480,1485,1489,1494],{"title":1463,"path":1459,"stem":1464,"description":1465},"Dethernety Risk Assessment User Guide","05.risk-assessment\u002Findex","Dethernety Risk Assessment turns a threat model you have built on the Dethernety platform into a grounded, board-ready draft risk report. From one point-in-time assessment of your model you get a prioritized worklist, a likelihood × impact risk matrix, a security-coverage posture, ten kinds of finding, a management risk register your team authors and maintains, and audience-tiered stakeholder reports — Board, Risk Committee, and Technical — plus machine-readable data exports.",{"title":1467,"path":1468,"stem":1469,"description":1470},"FAQ and Troubleshooting","\u002Frisk-assessment\u002Ffaq","05.risk-assessment\u002F01.faq","Short answers to the questions analysts, risk managers, and compliance officers ask most often about the Risk Assessment. Each answer links to the guide that covers it in full.",{"title":1472,"path":1473,"stem":1474,"description":1475},"Findings","\u002Frisk-assessment\u002Ffindings","05.risk-assessment\u002F02.findings","A finding is a specific observation the Risk Assessment makes about your threat model. Every finding is grounded in something concrete you have declared — an element, a data flow, a trust zone, a crown jewel — and it points you at a place worth a closer look. This guide is the reference to open when you see a finding and want to know what it means and what to do about it.",{"title":1230,"path":1477,"stem":1478,"description":1479},"\u002Frisk-assessment\u002Fgetting-started","05.risk-assessment\u002F03.getting-started","Risk Assessment turns a threat model you have built on the Dethernety platform into a grounded, board-ready draft risk report — a prioritized worklist, a likelihood × impact matrix, a security-coverage posture, ten kinds of finding, a risk register your team authors, and audience-tiered stakeholder reports and exports.",{"title":1481,"path":1482,"stem":1483,"description":1484},"Methodology and Trust","\u002Frisk-assessment\u002Fmethodology-and-trust","05.risk-assessment\u002F04.methodology-and-trust","Every number in a Risk Assessment is meant to survive scrutiny. This chapter explains why you can trust the report and — just as importantly — what it deliberately declines to claim, so you can put it in front of your board, a regulator, or an external auditor and defend every line.",{"title":994,"path":1486,"stem":1487,"description":1488},"\u002Frisk-assessment\u002Freading-the-report","05.risk-assessment\u002F05.reading-the-report","The Risk Assessment turns your threat model into a single, scannable draft risk report: an executive summary at the top and a set of analytical tabs below it. This guide explains how to read what you see — what a matrix cell means, how coverage is stated, what a severity band is (and is not), and how to interpret each tab.",{"title":1490,"path":1491,"stem":1492,"description":1493},"Stakeholder Reports and Exports","\u002Frisk-assessment\u002Fstakeholder-reports","05.risk-assessment\u002F06.stakeholder-reports","One assessment produces reporting for every audience you answer to. From a single generated Risk Assessment you can hand your board a one-page brief, give your risk committee the full reconciliation, keep the complete technical detail for your own team, and export the underlying data into your GRC tool — without ever re-running anything or reconciling one document against another.",{"title":1495,"path":1496,"stem":1497,"description":1498},"The Risk Register","\u002Frisk-assessment\u002Fthe-risk-register","05.risk-assessment\u002F07.the-risk-register","The Risk Register is where your team records and manages the real risks your organisation is carrying — on top of, but separate from, what the analysis computed for you. Each entry is written by a person: a plain-language risk statement, your own assessment of how likely it is and how much it would hurt, the findings and elements from the analysis that back it up, a treatment decision, an owner, a review date, and a reference handle you can quote in a ticket or a board pack.",{"title":1500,"description":1501,"path":1502,"stem":1503,"children":1504,"page":-1},"Threat Patterns","The Threat Patterns module and its modelling checklist.","\u002Fthreat-patterns","06.threat-patterns",[1505,1509],{"title":1506,"path":1502,"stem":1507,"description":1508},"Threat Patterns User Guide","06.threat-patterns\u002Findex","Threat Patterns finds threats in your model that no single element shows on its own. Each one appears only when several elements line up. For example, an agent may read content anyone can write, hold private data, and be able to send data where an outsider reads it. Each element can look acceptable alone, but together they form a path an attacker can use.",{"title":1510,"path":1511,"stem":1512,"description":1513},"Modelling Checklist","\u002Fthreat-patterns\u002Fmodelling-checklist","06.threat-patterns\u002F01.modelling-checklist","Threat Patterns decides a leg only from what your model states. An unanswered attribute or field is undetermined, never read as \"no\". This checklist lists the facts and drawings the analysis asks for most often. For each one it says where to set it and which leg it settles. Attribute names are shown as they appear on the class, in code.",{"title":1515,"description":1516,"path":1517,"stem":1518,"children":1519,"page":-1},"Agentic modelling","A hands-on training: model one agentic system step by step, with Threat Patterns after each step.","\u002Fagentic-modelling","07.agentic-modelling",[1520,1524,1529,1534,1539,1544,1549,1554,1559,1564,1569,1574,1579],{"title":1521,"path":1517,"stem":1522,"description":1523},"Model an Agentic Architecture","07.agentic-modelling\u002Findex","A hands-on training in modelling systems that run AI agents, so that Threat Patterns can analyse them. You build one system, a fictional customer-support copilot, in eleven short lessons. Each lesson adds one thing to the model, and you run Threat Patterns after each one to see what the change did.",{"title":1525,"path":1526,"stem":1527,"description":1528},"Lesson 1: Draw the Agent and What It Talks To","\u002Fagentic-modelling\u002F01-draw-the-agent","07.agentic-modelling\u002F01.01-draw-the-agent","Training overview · Lesson 1 of 11 · Next: Say what data moves",{"title":1530,"path":1531,"stem":1532,"description":1533},"Lesson 2: Say What Data Moves","\u002Fagentic-modelling\u002F02-say-what-data-moves","07.agentic-modelling\u002F02.02-say-what-data-moves","Training overview · Lesson 2 of 11 · Previous: Draw the agent · Next: Mark who is outside",{"title":1535,"path":1536,"stem":1537,"description":1538},"Lesson 3: Mark Who Is Outside","\u002Fagentic-modelling\u002F03-mark-who-is-outside","07.agentic-modelling\u002F03.03-mark-who-is-outside","Training overview · Lesson 3 of 11 · Previous: Say what data moves · Next: Draw a tool that reaches any host",{"title":1540,"path":1541,"stem":1542,"description":1543},"Lesson 4: Draw a Tool That Reaches Any Host","\u002Fagentic-modelling\u002F04-draw-a-tool-that-reaches-any-host","07.agentic-modelling\u002F04.04-draw-a-tool-that-reaches-any-host","Training overview · Lesson 4 of 11 · Previous: Mark who is outside · Next: State what the agent can do",{"title":1545,"path":1546,"stem":1547,"description":1548},"Lesson 5: State What the Agent Can Do","\u002Fagentic-modelling\u002F05-state-what-the-agent-can-do","07.agentic-modelling\u002F05.05-state-what-the-agent-can-do","Training overview · Lesson 5 of 11 · Previous: Draw a tool that reaches any host · Next: Fix a finding with a fact",{"title":1550,"path":1551,"stem":1552,"description":1553},"Lesson 6: Fix a Finding With a Fact","\u002Fagentic-modelling\u002F06-fix-a-finding-with-a-fact","07.agentic-modelling\u002F06.06-fix-a-finding-with-a-fact","Training overview · Lesson 6 of 11 · Previous: State what the agent can do · Next: Record a compensating control",{"title":1555,"path":1556,"stem":1557,"description":1558},"Lesson 7: Record a Compensating Control","\u002Fagentic-modelling\u002F07-record-a-compensating-control","07.agentic-modelling\u002F07.07-record-a-compensating-control","Training overview · Lesson 7 of 11 · Previous: Fix a finding with a fact · Next: Leave what you don't know open",{"title":1560,"path":1561,"stem":1562,"description":1563},"Lesson 8: Leave What You Don't Know Open","\u002Fagentic-modelling\u002F08-leave-unknowns-open","07.agentic-modelling\u002F08.08-leave-unknowns-open","Training overview · Lesson 8 of 11 · Previous: Record a compensating control · Next: Follow a credential",{"title":1565,"path":1566,"stem":1567,"description":1568},"Lesson 9: Follow a Credential","\u002Fagentic-modelling\u002F09-follow-a-credential","07.agentic-modelling\u002F09.09-follow-a-credential","Training overview · Lesson 9 of 11 · Previous: Leave what you don't know open · Next: Watch what gets into knowledge and memory",{"title":1570,"path":1571,"stem":1572,"description":1573},"Lesson 10: Watch What Gets Into Knowledge and Memory","\u002Fagentic-modelling\u002F10-what-gets-in","07.agentic-modelling\u002F10.10-what-gets-in","Training overview · Lesson 10 of 11 · Previous: Follow a credential · Next: Draw tools from others and hand-offs",{"title":1575,"path":1576,"stem":1577,"description":1578},"Lesson 11: Draw Tools From Others and Hand-offs","\u002Fagentic-modelling\u002F11-tools-and-handoffs","07.agentic-modelling\u002F11.11-tools-and-handoffs","Training overview · Lesson 11 of 11 · Previous: Watch what gets into knowledge and memory",{"title":1580,"path":1581,"stem":1582,"description":1583},"The recipe at a glance","\u002Fagentic-modelling\u002Frecipe-at-a-glance","07.agentic-modelling\u002F12.recipe-at-a-glance","The ten steps of the training on one page. Each lesson teaches one or two of them.",{"title":1585,"description":1586,"path":1587,"stem":1588,"children":1589,"page":-1},"BYODt subscription","Subscribing on the BYODt Portal, and moving a deployment you already run to a new team.","\u002Fbyodt-subscription","08.byodt-subscription",[1590,1594,1599],{"title":1591,"path":1587,"stem":1592,"description":1593},"BYODt Subscription","08.byodt-subscription\u002Findex","Buy content for the deployment you run yourself, and decide where that deployment goes when you buy a team edition",{"title":1595,"path":1596,"stem":1597,"description":1598},"Your Subscription","\u002Fbyodt-subscription\u002Fyour-subscription","08.byodt-subscription\u002F01.your-subscription","Create an account, subscribe by card, and find the values your deployment needs on the portal",{"title":1600,"path":1601,"stem":1602,"description":1603},"Moving a Deployment to a New Team","\u002Fbyodt-subscription\u002Fmoving-a-deployment-to-a-new-team","08.byodt-subscription\u002F02.moving-a-deployment-to-a-new-team","What to do with the deployment you already run once you buy a team edition: three ways forward, best first",1793748184936]