[{"data":1,"prerenderedAt":858},["ShallowReactive",2],{"page-\u002Fagentic-modelling\u002F03-mark-who-is-outside":3,"navigation":536},{"id":4,"title":5,"body":6,"description":528,"extension":529,"meta":530,"navigation":531,"path":532,"seo":533,"stem":534,"__hash__":535},"docs\u002F07.agentic-modelling\u002F03.03-mark-who-is-outside.md","Lesson 3: Mark Who Is Outside",{"type":7,"value":8,"toc":513},"minimark",[9,13,31,36,39,42,46,54,58,63,66,73,78,88,94,100,105,110,118,122,153,196,199,203,209,251,257,260,291,297,308,312,334,344,358,364,368,371,379,391,396,424,429,432,458,460,480,484,490,497,500,503,507],[10,11,5],"h1",{"id":12},"lesson-3-mark-who-is-outside",[14,15,16,21,22,26,27],"p",{},[17,18,20],"a",{"href":19},"\u002Fagentic-modelling","Training overview"," · Lesson 3 of 11 · Previous: ",[17,23,25],{"href":24},"\u002Fagentic-modelling\u002F02-say-what-data-moves","Say what data moves"," · Next: ",[17,28,30],{"href":29},"\u002Fagentic-modelling\u002F04-draw-a-tool-that-reaches-any-host","Draw a tool that reaches any host",[32,33,35],"h2",{"id":34},"goal","Goal",[14,37,38],{},"Zones decide who can read what the agent sends.",[14,40,41],{},"After this lesson you know why an outside party belongs in a boundary with the Untrusted zone (Open internet), why a vendor belongs in one with the Vendor zone (Trusted external), and what happens when you leave someone outside every boundary.",[32,43,45],{"id":44},"what-you-start-from","What you start from",[14,47,48,49,53],{},"Your model from lesson 2, or import ",[17,50,52],{"href":51},"\u002Fguides\u002Fagentic-modelling\u002FL2-solution.zip","L2-solution.zip",".",[32,55,57],{"id":56},"the-recipe-step","The recipe step",[59,60,62],"h3",{"id":61},"step-3-mark-who-is-outside","Step 3: Mark who is outside",[14,64,65],{},"Put the open internet, and anyone who can write content the agent reads without being one of your own vetted staff or systems, in a boundary with the Untrusted zone (Open internet); an account does not make content trusted. Put vendor-operated elements in a boundary with the Vendor zone (Trusted external). The zone is what counts: a zone-only boundary needs no class. Never leave an outside party outside every boundary: it reads as internal.",[14,67,68,72],{},[69,70,71],"strong",{},"Why:"," Zones decide who can read what the agent sends, and who can write what it reads.",[14,74,75],{},[69,76,77],{},"Ask:",[79,80,81,85],"ul",{},[82,83,84],"li",{},"Who can write content that reaches the agent? Anyone who can sign up counts as outside.",[82,86,87],{},"Which elements does a vendor operate?",[14,89,90,93],{},[69,91,92],{},"Classes:"," Network Segment, Container.",[14,95,96,99],{},[69,97,98],{},"Zones:"," Untrusted (Open internet), Vendor (Trusted external), Internal.",[14,101,102],{},[69,103,104],{},"What the analysis reads here:",[79,106,107],{},[82,108,109],{},"A model endpoint: never counted as a way out: Hosted LLM API, Self-Hosted LLM Inference.",[14,111,112,113,117],{},"In the worked system, anyone on the internet can write a ticket, so the customer goes in a boundary with the Untrusted zone (Open internet). The CRM and the hosted model are run by vendors, so each goes in its own boundary with the Vendor zone (Trusted external). See ",[17,114,116],{"href":115},"\u002Fagentic-modelling#zone-names-in-the-editor","Zone names in the editor"," for where to set each zone.",[32,119,121],{"id":120},"steps","Steps",[14,123,124,125,128,129,132,133,136,137,140,141,144,145,148,149,152],{},"Add each boundary from the palette and name it. On its ",[69,126,127],{},"Zoning"," tab, pick its zone in the ",[69,130,131],{},"Trust zone"," list: ",[69,134,135],{},"Open internet"," for ",[69,138,139],{},"Internet",", which the diagram then shows as the pill ",[69,142,143],{},"Untrusted",", and ",[69,146,147],{},"Trusted external"," for the two vendors, shown as ",[69,150,151],{},"Vendor",". Leave its class empty: the zone is what the analysis reads, so a boundary that only marks a zone needs no class. To move an element into a boundary, drag it onto the boundary.",[154,155,156,162,168,173,182,189],"ol",{},[82,157,158,159,161],{},"Add the boundary ",[69,160,139],{}," with zone Untrusted (Open internet) and no class.",[82,163,158,164,167],{},[69,165,166],{},"CRM vendor"," with zone Vendor (Trusted external) and no class.",[82,169,158,170,167],{},[69,171,172],{},"Model provider",[82,174,175,176,179,180,53],{},"Move ",[69,177,178],{},"Customer"," into ",[69,181,139],{},[82,183,175,184,179,187,53],{},[69,185,186],{},"CRM",[69,188,166],{},[82,190,175,191,179,194,53],{},[69,192,193],{},"Hosted model",[69,195,172],{},[14,197,198],{},"Generate again.",[32,200,202],{"id":201},"what-you-should-see","What you should see",[14,204,205,208],{},[69,206,207],{},"Findings:"," 1 systemic finding: 1 Confirmed · 0 Not ruled out.",[210,211,217],"div",{"className":212,"tabIndex":214,"role":215,"ariaLabel":216},[213],"table-frame",0,"region","Table: What you should see",[218,219,220,236],"table",{},[221,222,223],"thead",{},[224,225,226,230,233],"tr",{},[227,228,229],"th",{},"Finding",[227,231,232],{},"State",[227,234,235],{},"Legs",[237,238,239],"tbody",{},[224,240,241,245,248],{},[242,243,244],"td",{},"Lethal trifecta at Support copilot",[242,246,247],{},"Confirmed · unmitigated",[242,249,250],{},"U present · P present · X present · W undetermined (aggravating)",[14,252,253,256],{},[69,254,255],{},"Facts to establish:"," 3 questions.",[14,258,259],{},"Facts that could raise a finding:",[79,261,262,274,288],{},[82,263,264,265,268,269,273],{},"Set the attribute ",[69,266,267],{},"Code Execution Tools Present"," (",[270,271,272],"code",{},"code_execution_tools_present",", in Application Security) on Support copilot, or draw its Agent Tool Call to the harness",[82,275,264,276,268,279,282,283,268,285,287],{},[69,277,278],{},"Consequential Tools Present",[270,280,281],{},"consequential_tools_present",", in Human Oversight) or ",[69,284,267],{},[270,286,272],{},", in Application Security) on Support copilot",[82,289,290],{},"Draw the runtime boundary or the Agent Tool Call that ties Support copilot to its harness",[14,292,293,296],{},[69,294,295],{},"Model gaps:"," 1 of 1 agents have no hosting harness drawn, so their W cannot be read from one (on Support copilot)",[14,298,299,300,303,304,307],{},"The lethal trifecta at the support copilot is now ",[69,301,302],{},"Confirmed",". The questions about outbound flows are gone. What remains is about the copilot itself, under ",[69,305,306],{},"Facts that could raise a finding",": what its tools can do, its harness, and whether it can reach the CRM API key.",[32,309,311],{"id":310},"what-changed-and-why","What changed and why",[14,313,314,317,318,321,322,325,326,329,330,333],{},[69,315,316],{},"X is present."," Expand the finding and look at the X leg. The copilot's reply leaves in two hops: ",[69,319,320],{},"Post reply"," takes it to the ticket system, and ",[69,323,324],{},"Reply e-mail"," takes it on to the customer, who is now in the Untrusted zone. So what the copilot writes can reach an outsider. In the X leg's route list, this route names ",[69,327,328],{},"Ticket system"," and reads ",[69,331,332],{},"via neighbour",": the copilot transmits through a neighbouring element. You did not state the route; the analysis followed the flows you drew.",[14,335,336,339,340,343],{},[69,337,338],{},"U gains a second source."," The ticket comes from a customer in the Untrusted zone. The ticket's U route still reads ",[69,341,342],{},"stated",", from the origin you set in lesson 2, and its basis now adds that the ticket text is also carried from the customer, in the Untrusted zone.",[14,345,346,349,350,353,354,357],{},[69,347,348],{},"One present route is enough."," The copilot's own route to the CRM is still open: can an untrusted party read what reaches the CRM? A vendor destination is a question, not an answer. While another route makes X present, that open route does not change the result, so ",[69,351,352],{},"Facts to establish"," does not ask it. You still see it inside the expanded X leg, as a ",[69,355,356],{},"to settle:"," line on the copilot's route to the CRM.",[14,359,360,363],{},[69,361,362],{},"Confirmed means every required leg is present."," U, P and X are all present. W, the aggravating leg (the agent writes without approval), is still undetermined. It never decides the finding: when present, it only ranks it above otherwise equal findings.",[32,365,367],{"id":366},"exercise-outside-every-boundary","Exercise: Outside every boundary",[14,369,370],{},"Make this change and generate again:",[14,372,373,374,378],{},"On a scratch copy: import ",[17,375,377],{"href":376},"\u002Fguides\u002Fagentic-modelling\u002FL3-solution.zip","L3-solution.zip"," and rename it.",[154,380,381,386],{},[82,382,175,383,385],{},[69,384,178],{}," out of every boundary.",[82,387,388,389,53],{},"Delete ",[69,390,139],{},[14,392,393,395],{},[69,394,207],{}," 1 systemic finding: 0 Confirmed · 1 Not ruled out.",[210,397,400],{"className":398,"tabIndex":214,"role":215,"ariaLabel":399},[213],"Table: Exercise: Outside every boundary",[218,401,402,412],{},[221,403,404],{},[224,405,406,408,410],{},[227,407,229],{},[227,409,232],{},[227,411,235],{},[237,413,414],{},[224,415,416,418,421],{},[242,417,244],{},[242,419,420],{},"Not ruled out · unmitigated",[242,422,423],{},"U present · P present · X undetermined · W undetermined (aggravating)",[14,425,426,428],{},[69,427,255],{}," 7 questions.",[14,430,431],{},"Open questions on Not ruled out findings:",[79,433,434],{},[82,435,436,437],{},"Lethal trifecta at Support copilot:\n",[79,438,439,442,452,455],{},[82,440,441],{},"Can an untrusted party read what reaches CRM?",[82,443,444,445,268,448,451],{},"Draw the outbound flows of Staff console, or answer ",[69,446,447],{},"Markdown Image Rendering Policy",[270,449,450],{},"markdown_image_rendering_policy",", in Output Rendering Exfiltration) on Staff console",[82,453,454],{},"Every drawn route from Ticket system ends inside; assert its outbound flows complete if nothing else leaves it",[82,456,457],{},"Every drawn route from CRM ends inside; assert its outbound flows complete if nothing else leaves it",[14,459,259],{},[79,461,462,468,478],{},[82,463,264,464,268,466,273],{},[69,465,267],{},[270,467,272],{},[82,469,264,470,268,472,282,474,268,476,287],{},[69,471,278],{},[270,473,281],{},[69,475,267],{},[270,477,272],{},[82,479,290],{},[14,481,482,296],{},[69,483,295],{},[14,485,486,487,53],{},"The way out falls back to undetermined: an element outside every boundary reads as internal. The customer is still drawn, and still receives the reply e-mail, but the analysis no longer knows the customer is an outsider. The trifecta returns to ",[69,488,489],{},"Not ruled out",[14,491,492,493,496],{},"Look for this question on the finding: ",[494,495,441],"em",{}," With the reply route no longer reaching an outsider, nothing else makes X present, so the copilot's route to the CRM decides again, and the CRM's Vendor zone turns it into a question. Placing a party in a zone is an answer; leaving it out of every boundary is not.",[14,498,499],{},"The ticket system's question is back too: every drawn route from it ends inside, because the customer now reads as internal. Do not assert its outbound flows complete. Nothing else leaves the ticket system, but the reply e-mail still reaches an outsider; the fix is the customer's zone.",[14,501,502],{},"Delete the copy when you are done.",[32,504,506],{"id":505},"next","Next",[14,508,509,512],{},[17,510,511],{"href":29},"Lesson 4: Draw a tool that reaches any host",". The copilot gains a web-fetch tool, and you draw it as both a way out and a way in.",{"title":514,"searchDepth":515,"depth":515,"links":516},"",3,[517,519,520,523,524,525,526,527],{"id":34,"depth":518,"text":35},2,{"id":44,"depth":518,"text":45},{"id":56,"depth":518,"text":57,"children":521},[522],{"id":61,"depth":515,"text":62},{"id":120,"depth":518,"text":121},{"id":201,"depth":518,"text":202},{"id":310,"depth":518,"text":311},{"id":366,"depth":518,"text":367},{"id":505,"depth":518,"text":506},"Training overview · Lesson 3 of 11 · Previous: Say what data moves · Next: Draw a tool that reaches any host","md",{},true,"\u002Fagentic-modelling\u002F03-mark-who-is-outside",{"title":5,"description":528},"07.agentic-modelling\u002F03.03-mark-who-is-outside","p5ufKRFvhrd5QVAo4hERgETRAWNfkj2u1jyex7hvv3U",[537,592,627,682,716,760,775,838],{"title":538,"description":539,"path":540,"stem":541,"children":542,"page":-1},"Platform","Modelling, analysis, findings and controls in the Dethernety platform.","\u002Fplatform","01.platform",[543,547,552,557,562,567,572,577,582,587],{"title":544,"path":540,"stem":545,"description":546},"Dethernety User Documentation","01.platform\u002Findex","User guide for the Dethernety threat modeling platform",{"title":548,"path":549,"stem":550,"description":551},"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":553,"path":554,"stem":555,"description":556},"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":558,"path":559,"stem":560,"description":561},"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":563,"path":564,"stem":565,"description":566},"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":568,"path":569,"stem":570,"description":571},"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":573,"path":574,"stem":575,"description":576},"Issue Management Guide","\u002Fplatform\u002Fissue-management-guide","01.platform\u002F06.issue-management-guide","Issue tracking, filtering, and management in Dethernety.",{"title":578,"path":579,"stem":580,"description":581},"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":583,"path":584,"stem":585,"description":586},"Understanding Modules","\u002Fplatform\u002Funderstanding-modules","01.platform\u002F08.understanding-modules","How Dethernety's module system extends your threat modeling capabilities.",{"title":588,"path":589,"stem":590,"description":591},"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":593,"description":594,"path":595,"stem":596,"children":597,"page":-1},"BYODt cloud","Deploying the platform yourself and connecting it to the BYODt cloud.","\u002Fbyodt-cloud","02.byodt-cloud",[598,602,607,612,617,622],{"title":599,"path":595,"stem":600,"description":601},"BYODt Deployment","02.byodt-cloud\u002Findex","Run Dethernety on your own machine: install, configure, operate, and recover",{"title":603,"path":604,"stem":605,"description":606},"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":608,"path":609,"stem":610,"description":611},"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":613,"path":614,"stem":615,"description":616},"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":618,"path":619,"stem":620,"description":621},"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":623,"path":624,"stem":625,"description":626},"Troubleshooting the BYODt Deployment","\u002Fbyodt-cloud\u002Ftroubleshooting","02.byodt-cloud\u002F05.troubleshooting","Symptom, cause, and fix for the failures this deployment reports",{"title":628,"description":629,"path":630,"stem":631,"children":632,"page":-1},"Dethereal","The Claude Code plugin: build a threat model in conversation and publish it to the platform.","\u002Fdethereal","03.dethereal",[633,637,642,647,652,657,662,667,672,677],{"title":634,"path":630,"stem":635,"description":636},"Dethereal — Claude Code Plugin for Threat Modeling","03.dethereal\u002Findex","Comprehensive documentation for the Dethereal threat modeling plugin",{"title":638,"path":639,"stem":640,"description":641},"Getting Started with Dethereal","\u002Fdethereal\u002Fgetting-started","03.dethereal\u002F01.getting-started","Install the plugin, authenticate, and create your first threat model",{"title":643,"path":644,"stem":645,"description":646},"The 11-Step Guided Workflow","\u002Fdethereal\u002Fguided-workflow","03.dethereal\u002F02.guided-workflow","Complete walkthrough of the \u002Fdethereal:threat-model guided process",{"title":648,"path":649,"stem":650,"description":651},"Command Reference","\u002Fdethereal\u002Fcommand-reference","03.dethereal\u002F03.command-reference","Complete reference for all 14 Dethereal slash commands",{"title":653,"path":654,"stem":655,"description":656},"Threat Model Concepts","\u002Fdethereal\u002Fmodel-concepts","03.dethereal\u002F04.model-concepts","Components, boundaries, data flows, classes, attributes, and quality scoring",{"title":658,"path":659,"stem":660,"description":661},"Discovery and Enrichment","\u002Fdethereal\u002Fdiscovery-and-enrichment","03.dethereal\u002F05.discovery-and-enrichment","Infrastructure scanning, security attributes, MITRE ATT&CK, credentials, and compliance",{"title":663,"path":664,"stem":665,"description":666},"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":668,"path":669,"stem":670,"description":671},"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":673,"path":674,"stem":675,"description":676},"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":678,"path":679,"stem":680,"description":681},"Dethereal Glossary","\u002Fdethereal\u002Fglossary","03.dethereal\u002F09.glossary","Definitions for Dethereal-specific terminology",{"title":683,"description":684,"path":685,"stem":686,"children":687,"page":-1},"Threat Report","The residual-risk report over a threat model: reading it, filtering it and exporting it.","\u002Fthreat-report","04.threat-report",[688,691,696,701,706,711],{"title":683,"path":685,"stem":689,"description":690},"04.threat-report\u002Findex","Read, filter, drill into, and export a residual-risk report over a threat model",{"title":692,"path":693,"stem":694,"description":695},"Getting Started with the Threat Report","\u002Fthreat-report\u002Fgetting-started","04.threat-report\u002F01.getting-started","Generate, open, refresh, and export a threat report over a model",{"title":697,"path":698,"stem":699,"description":700},"Reading the Report","\u002Fthreat-report\u002Freading-the-report","04.threat-report\u002F02.reading-the-report","Navigating the report, the shared visual language, and the Posture and Boundary Crossings views",{"title":702,"path":703,"stem":704,"description":705},"Understanding Coverage and Gaps","\u002Fthreat-report\u002Funderstanding-coverage","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":707,"path":708,"stem":709,"description":710},"Reachability and Flow Routes","\u002Fthreat-report\u002Freachability","04.threat-report\u002F04.reachability","Exploring flow routes to crown-jewel assets and between any two elements — and what the analysis does and does not model",{"title":712,"path":713,"stem":714,"description":715},"Working with Findings","\u002Fthreat-report\u002Fworking-with-findings","04.threat-report\u002F05.working-with-findings","The Residual Risk ledger, triaging findings, filtering, and the per-element Component Profile",{"title":717,"description":718,"path":719,"stem":720,"children":721,"page":-1},"Risk assessment","The risk assessment module: the register, the reports and the method behind them.","\u002Frisk-assessment","05.risk-assessment",[722,726,731,736,741,746,750,755],{"title":723,"path":719,"stem":724,"description":725},"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":727,"path":728,"stem":729,"description":730},"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":732,"path":733,"stem":734,"description":735},"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":737,"path":738,"stem":739,"description":740},"Getting Started","\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":742,"path":743,"stem":744,"description":745},"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":697,"path":747,"stem":748,"description":749},"\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":751,"path":752,"stem":753,"description":754},"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":756,"path":757,"stem":758,"description":759},"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":761,"description":762,"path":763,"stem":764,"children":765,"page":-1},"Threat Patterns","The Threat Patterns module and its modelling checklist.","\u002Fthreat-patterns","06.threat-patterns",[766,770],{"title":767,"path":763,"stem":768,"description":769},"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":771,"path":772,"stem":773,"description":774},"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":776,"description":777,"path":19,"stem":778,"children":779,"page":-1},"Agentic modelling","A hands-on training: model one agentic system step by step, with Threat Patterns after each step.","07.agentic-modelling",[780,784,789,793,794,798,803,808,813,818,823,828,833],{"title":781,"path":19,"stem":782,"description":783},"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":785,"path":786,"stem":787,"description":788},"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":790,"path":24,"stem":791,"description":792},"Lesson 2: 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":5,"path":532,"stem":534,"description":528},{"title":795,"path":29,"stem":796,"description":797},"Lesson 4: 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":799,"path":800,"stem":801,"description":802},"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":804,"path":805,"stem":806,"description":807},"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":809,"path":810,"stem":811,"description":812},"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":814,"path":815,"stem":816,"description":817},"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":819,"path":820,"stem":821,"description":822},"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":824,"path":825,"stem":826,"description":827},"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":829,"path":830,"stem":831,"description":832},"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":834,"path":835,"stem":836,"description":837},"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":839,"description":840,"path":841,"stem":842,"children":843,"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",[844,848,853],{"title":845,"path":841,"stem":846,"description":847},"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":849,"path":850,"stem":851,"description":852},"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":854,"path":855,"stem":856,"description":857},"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",1793748186431]