[{"data":1,"prerenderedAt":893},["ShallowReactive",2],{"page-\u002Frisk-assessment\u002Fgetting-started":3,"navigation":576},{"id":4,"title":5,"body":6,"description":568,"extension":569,"meta":570,"navigation":571,"path":572,"seo":573,"stem":574,"__hash__":575},"docs\u002F05.risk-assessment\u002F03.getting-started.md","Getting Started",{"type":7,"value":8,"toc":553},"minimark",[9,13,22,36,49,54,57,79,83,91,133,140,144,147,179,194,198,209,216,225,230,233,290,296,300,303,398,409,412,426,445,449,452,490,494,497,545],[10,11,5],"h1",{"id":12},"getting-started",[14,15,16,17,21],"p",{},"Risk Assessment turns a threat model you have built on the Dethernety platform into a grounded, board-ready ",[18,19,20],"strong",{},"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.",[14,23,24,25,30,31,35],{},"This guide is the on-ramp. It shows you where Risk Assessment lives, how to generate the report for the first time, how to read the dashboard at a glance, how to refresh the report after you change your model, and what the \"your model changed\" banner means. It does not go deep on interpretation — the ",[26,27,29],"a",{"href":28},"\u002Frisk-assessment\u002Freading-the-report","reading guide"," and the ",[26,32,34],{"href":33},"\u002Frisk-assessment\u002Fmethodology-and-trust","trust and methodology guide"," do that. Follow the links as you go.",[37,38,39],"blockquote",{},[14,40,41,44,45,48],{},[18,42,43],{},"What makes this report different."," It is deliberately honest and under-claims. Every number you see is a band, a count, or a coverage ratio traceable to your own model — there is no AI guess and no single black-box risk score. See ",[26,46,47],{"href":33},"Methodology and trust"," for the full story.",[50,51,53],"h2",{"id":52},"prerequisites","Prerequisites",[14,55,56],{},"Before you generate a report you need:",[58,59,60,67,73],"ul",{},[61,62,63,66],"li",{},[18,64,65],{},"A threat model on the Dethernety platform"," with elements, controls, data flows, and trust boundaries in place. Risk Assessment reports on what your model contains — an empty or sparse model produces a sparse report.",[61,68,69,72],{},[18,70,71],{},"The Risk Assessment analysis available in your workspace."," Risk Assessment is a paid product. If you do not see it as an option, contact your administrator.",[61,74,75,78],{},[18,76,77],{},"Permission to run analyses and view results"," on the model. If a model opens read-only for you, you can read a report someone else generated but cannot generate or recreate one.",[50,80,82],{"id":81},"opening-risk-assessment","Opening Risk Assessment",[14,84,85,86,90],{},"Risk Assessment runs as an analysis ",[87,88,89],"em",{},"of"," a threat model, so you reach it from the model itself.",[92,93,94,100,114,124],"ol",{},[61,95,96,99],{},[18,97,98],{},"Open your threat model"," on the platform.",[61,101,102,105,106,109,110,113],{},[18,103,104],{},"Open the model's analyses."," On the canvas toolbar down the left of the model, click the ",[18,107,108],{},"sparkle"," button (tooltip ",[18,111,112],{},"Analyses","). The dialog that opens is where every analysis of the model lives.",[61,115,116,119,120,123],{},[18,117,118],{},"Add a Risk Assessment analysis."," Start a new analysis and choose ",[18,121,122],{},"Risk Assessment"," from the list of reporting analyses. The platform creates one Risk Assessment for the model; you can keep it and revisit it later.",[61,125,126,129,130,132],{},[18,127,128],{},"Open it to view results."," The Risk Assessment opens in its own view, titled ",[18,131,122],{}," at the top.",[14,134,135,136,139],{},"The first time you open it — before you have ever run it — the view shows an empty state, not a blank page. You will see the heading ",[18,137,138],{},"No risk assessment generated yet"," with a short description and a single button.",[50,141,143],{"id":142},"generating-the-report","Generating the report",[14,145,146],{},"From that empty state:",[92,148,149,155,165],{},[61,150,151,154],{},[18,152,153],{},"Click Generate assessment."," The report computes from your model as it stands right now.",[61,156,157,160,161,164],{},[18,158,159],{},"Wait a moment."," The freshness line reads ",[18,162,163],{},"Generating assessment…"," while it runs. Generation reads your model and computes the whole report in one pass; it makes no external calls.",[61,166,167,170,171,174,175,178],{},[18,168,169],{},"Read the result."," When it finishes, the empty state is replaced by the full dashboard, and the freshness line changes to ",[18,172,173],{},"Reflects the model as of"," ",[87,176,177],{},"(date and time)",".",[14,180,181,182,185,186,189,190,178],{},"That date and time is the report's ",[87,183,184],{},"as-of"," stamp. The report is a ",[18,187,188],{},"point-in-time draft",": it reflects your model as it was the moment you generated it, and it does not silently change underneath you afterwards. Refreshing it is always your explicit action — see ",[26,191,193],{"href":192},"#refreshing-after-your-model-changes","Refreshing after your model changes",[50,195,197],{"id":196},"the-dashboard-at-a-glance","The dashboard at a glance",[14,199,200,201,204,205,208],{},"The dashboard has two parts: an ",[18,202,203],{},"executive band"," across the top that reads as a single unit, and a ",[18,206,207],{},"row of tabs"," below it for the detail.",[14,210,211],{},[212,213],"img",{"alt":214,"src":215},"The Risk Assessment dashboard after generating: the report header and freshness line, the executive band (the inherent-exposure matrix, the coverage posture with its takeaway, and the authored risk-register matrix), the row of tabs, and the start of the Priorities worklist.","\u002Fguides\u002Frisk-assessment\u002Fimages\u002Fdashboard-overview.png",[14,217,218],{},[87,219,220,221,224],{},"The dashboard at a glance. The executive band across the top — the exposure matrix, the coverage posture and its takeaway, and the authored risk-register matrix — sits above the tabs (Priorities, Findings, Distributions, Ledger, Register, Methodology). The header shows when the report reflects your model, with ",[18,222,223],{},"Recreate"," to refresh it.",[226,227,229],"h3",{"id":228},"the-executive-band","The executive band",[14,231,232],{},"Reading top to bottom, the band gives you the whole picture before you open a single tab:",[58,234,235,244,254,264,273,279],{},[61,236,237,240,241,243],{},[18,238,239],{},"The freshness banner."," States the report's as-of date and carries the one ",[18,242,223],{}," button. When the report is out of date it also shows a short banner saying so.",[61,245,246,249,250,253],{},[18,247,248],{},"Flags and provenance."," If any analysis setting makes the report ",[87,251,252],{},"less conservative"," than its default, it is named here in amber, with direction and who set it — so a reassuring number is never read without its caveat. Below that, a neutral line counts your model: how many findings were set aside (dispositioned), how many elements, and how many live findings.",[61,255,256,259,260,263],{},[18,257,258],{},"The risk matrix."," The report's centrepiece: a ",[18,261,262],{},"likelihood × impact"," grid placing your findings. It is monochrome by design — position and density carry the meaning, never colour. Click any populated cell to drill into the elements behind it.",[61,265,266,269,270,178],{},[18,267,268],{},"The coverage posture."," A one-line, honest account of security coverage over your highest-band findings — how many are covered, partially covered, uncovered, of unknown coverage, and how many of the uncovered are exposed. It is stated as plain counts and fractions, never a single \"percent covered\". Each number is a link into the ",[26,271,272],{"href":28},"Ledger",[61,274,275,278],{},[18,276,277],{},"The takeaway."," One plain-language board sentence, computed from the same counts, with a scope note reminding readers this is relative prioritization and coverage posture — not a calibrated risk score or loss estimate.",[61,280,281,284,285,289],{},[18,282,283],{},"The risk register card."," Appears only once your team has authored at least one open risk in the register (see the ",[26,286,288],{"href":287},"\u002Frisk-assessment\u002Fthe-risk-register","risk register guide","). Until then the band looks exactly as it did before, with a short invitation to author your first risk.",[14,291,292,293,295],{},"The ",[26,294,29],{"href":28}," explains how to interpret each of these in depth.",[226,297,299],{"id":298},"the-tabs","The tabs",[14,301,302],{},"Below the band, a row of tabs holds the detail. Each opens over the same report:",[304,305,311],"div",{"className":306,"tabIndex":308,"role":309,"ariaLabel":310},[307],"table-frame",0,"region","Table: The tabs",[312,313,314,327],"table",{},[315,316,317],"thead",{},[318,319,320,324],"tr",{},[321,322,323],"th",{},"Tab",[321,325,326],{},"What it holds",[328,329,330,341,354,364,373,386],"tbody",{},[318,331,332,338],{},[333,334,335],"td",{},[18,336,337],{},"Priorities",[333,339,340],{},"The ranked worklist — your findings in priority order, with a control for how many to show.",[318,342,343,348],{},[333,344,345],{},[18,346,347],{},"Findings",[333,349,350,351,178],{},"The ten kinds of finding, grouped, each shown as found, checked-and-clean, or not-computable. See ",[26,352,347],{"href":353},"\u002Frisk-assessment\u002Ffindings",[318,355,356,361],{},[333,357,358],{},[18,359,360],{},"Distributions",[333,362,363],{},"How your findings spread across bands and across trust zones and boundaries.",[318,365,366,370],{},[333,367,368],{},[18,369,272],{},[333,371,372],{},"The complete finding ledger — a searchable, filterable workbench where you review and set aside (dispose) findings.",[318,374,375,380],{},[333,376,377],{},[18,378,379],{},"Register",[333,381,382,383,178],{},"The risk records your team authors. This is the one tab you write to; see ",[26,384,385],{"href":287},"The risk register",[318,387,388,393],{},[333,389,390],{},[18,391,392],{},"Methodology",[333,394,395,396,178],{},"Limitations, the exact settings the report ran under, and the sources behind it. See ",[26,397,47],{"href":33},[14,399,292,400,403,404,408],{},[18,401,402],{},"Export"," menu in the header produces the audience-tiered stakeholder reports — Board, Risk Committee, Technical — and machine exports. The ",[26,405,407],{"href":406},"\u002Frisk-assessment\u002Fstakeholder-reports","stakeholder reports guide"," covers each tier.",[50,410,193],{"id":411},"refreshing-after-your-model-changes",[14,413,414,415,418,419,422,423,425],{},"The report is a snapshot in time. When you change your threat model — add or remove elements, adjust controls, redraw data flows or trust boundaries — the report does ",[18,416,417],{},"not"," update on its own. Instead, the next time you open it the freshness banner shows a ",[18,420,421],{},"\"your model changed since this report was generated\""," notice, and the report stays fully readable while it does. Stale is not broken: nothing is blanked, and the notice simply tells you what to do. Click ",[18,424,223],{}," to compute a fresh report from the current model; the new as-of stamp replaces the old one.",[37,427,428],{},[14,429,430,433,434,436,437,440,441,444],{},[18,431,432],{},"Authoring a risk never triggers this banner."," The risk register your team writes lives outside the computed report, so adding, editing, or closing a risk is not a \"model change\" and never marks the report stale. See ",[26,435,385],{"href":287}," and ",[26,438,47],{"href":439},"\u002Frisk-assessment\u002Fmethodology-and-trust#staleness"," for why. You may occasionally see a calmer, informational note (not the amber alarm) when only the underlying reference data has moved in a way that provably could not change a number — ",[26,442,47],{"href":443},"\u002Frisk-assessment\u002Fmethodology-and-trust#freshness"," explains that distinction.",[50,446,448],{"id":447},"your-first-few-minutes","Your first few minutes",[14,450,451],{},"Once the report is generated, a quick pass looks like this:",[92,453,454,460,469,481],{},[61,455,456,459],{},[18,457,458],{},"Read the takeaway."," One sentence, top of the band, tells you where this model stands.",[61,461,462,465,466,468],{},[18,463,464],{},"Scan the risk matrix and the top priorities."," Note which cells are populated, then open the ",[18,467,337],{}," tab for the ranked worklist.",[61,470,471,474,475,477,478,480],{},[18,472,473],{},"Open one finding."," In ",[18,476,337],{}," or ",[18,479,347],{},", drill into a single finding to see the evidence behind it.",[61,482,483,486,487,489],{},[18,484,485],{},"Look at the register."," Open the ",[18,488,379],{}," tab to see how your team turns findings into managed risks.",[50,491,493],{"id":492},"where-to-go-next","Where to go next",[14,495,496],{},"Read in this order:",[58,498,499,507,514,521,529,536],{},[61,500,501,506],{},[18,502,503],{},[26,504,505],{"href":28},"Reading the report"," — how to interpret the matrix, coverage posture, priorities, and distributions.",[61,508,509,513],{},[18,510,511],{},[26,512,347],{"href":353}," — the ten kinds of finding and what each one means.",[61,515,516,520],{},[18,517,518],{},[26,519,385],{"href":287}," — authoring and managing risks your team owns.",[61,522,523,528],{},[18,524,525],{},[26,526,527],{"href":406},"Stakeholder reports"," — the Board, Risk Committee, and Technical exports.",[61,530,531,535],{},[18,532,533],{},[26,534,47],{"href":33}," — why every number is grounded and what the report deliberately will not claim.",[61,537,538,544],{},[18,539,540],{},[26,541,543],{"href":542},"\u002Frisk-assessment\u002Ffaq","FAQ"," — common questions and troubleshooting.",[14,546,547,548,552],{},"Return to the ",[26,549,551],{"href":550},"\u002Frisk-assessment","Risk Assessment user guide index"," at any time.",{"title":554,"searchDepth":555,"depth":555,"links":556},"",3,[557,559,560,561,565,566,567],{"id":52,"depth":558,"text":53},2,{"id":81,"depth":558,"text":82},{"id":142,"depth":558,"text":143},{"id":196,"depth":558,"text":197,"children":562},[563,564],{"id":228,"depth":555,"text":229},{"id":298,"depth":555,"text":299},{"id":411,"depth":558,"text":193},{"id":447,"depth":558,"text":448},{"id":492,"depth":558,"text":493},"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.","md",{},true,"\u002Frisk-assessment\u002Fgetting-started",{"title":5,"description":568},"05.risk-assessment\u002F03.getting-started","BuGq-KW9EDbVP62Vexx7ckGfP2eEiqvhXvjc1lWFIus",[577,632,667,722,756,788,803,873],{"title":578,"description":579,"path":580,"stem":581,"children":582,"page":-1},"Platform","Modelling, analysis, findings and controls in the Dethernety platform.","\u002Fplatform","01.platform",[583,587,592,597,602,607,612,617,622,627],{"title":584,"path":580,"stem":585,"description":586},"Dethernety User Documentation","01.platform\u002Findex","User guide for the Dethernety threat modeling platform",{"title":588,"path":589,"stem":590,"description":591},"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":593,"path":594,"stem":595,"description":596},"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":598,"path":599,"stem":600,"description":601},"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":603,"path":604,"stem":605,"description":606},"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":608,"path":609,"stem":610,"description":611},"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":613,"path":614,"stem":615,"description":616},"Issue Management Guide","\u002Fplatform\u002Fissue-management-guide","01.platform\u002F06.issue-management-guide","Issue tracking, filtering, and management in Dethernety.",{"title":618,"path":619,"stem":620,"description":621},"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":623,"path":624,"stem":625,"description":626},"Understanding Modules","\u002Fplatform\u002Funderstanding-modules","01.platform\u002F08.understanding-modules","How Dethernety's module system extends your threat modeling capabilities.",{"title":628,"path":629,"stem":630,"description":631},"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":633,"description":634,"path":635,"stem":636,"children":637,"page":-1},"BYODt cloud","Deploying the platform yourself and connecting it to the BYODt cloud.","\u002Fbyodt-cloud","02.byodt-cloud",[638,642,647,652,657,662],{"title":639,"path":635,"stem":640,"description":641},"BYODt Deployment","02.byodt-cloud\u002Findex","Run Dethernety on your own machine: install, configure, operate, and recover",{"title":643,"path":644,"stem":645,"description":646},"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":648,"path":649,"stem":650,"description":651},"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":653,"path":654,"stem":655,"description":656},"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":658,"path":659,"stem":660,"description":661},"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":663,"path":664,"stem":665,"description":666},"Troubleshooting the BYODt Deployment","\u002Fbyodt-cloud\u002Ftroubleshooting","02.byodt-cloud\u002F05.troubleshooting","Symptom, cause, and fix for the failures this deployment reports",{"title":668,"description":669,"path":670,"stem":671,"children":672,"page":-1},"Dethereal","The Claude Code plugin: build a threat model in conversation and publish it to the platform.","\u002Fdethereal","03.dethereal",[673,677,682,687,692,697,702,707,712,717],{"title":674,"path":670,"stem":675,"description":676},"Dethereal — Claude Code Plugin for Threat Modeling","03.dethereal\u002Findex","Comprehensive documentation for the Dethereal threat modeling plugin",{"title":678,"path":679,"stem":680,"description":681},"Getting Started with Dethereal","\u002Fdethereal\u002Fgetting-started","03.dethereal\u002F01.getting-started","Install the plugin, authenticate, and create your first threat model",{"title":683,"path":684,"stem":685,"description":686},"The 11-Step Guided Workflow","\u002Fdethereal\u002Fguided-workflow","03.dethereal\u002F02.guided-workflow","Complete walkthrough of the \u002Fdethereal:threat-model guided process",{"title":688,"path":689,"stem":690,"description":691},"Command Reference","\u002Fdethereal\u002Fcommand-reference","03.dethereal\u002F03.command-reference","Complete reference for all 14 Dethereal slash commands",{"title":693,"path":694,"stem":695,"description":696},"Threat Model Concepts","\u002Fdethereal\u002Fmodel-concepts","03.dethereal\u002F04.model-concepts","Components, boundaries, data flows, classes, attributes, and quality scoring",{"title":698,"path":699,"stem":700,"description":701},"Discovery and Enrichment","\u002Fdethereal\u002Fdiscovery-and-enrichment","03.dethereal\u002F05.discovery-and-enrichment","Infrastructure scanning, security attributes, MITRE ATT&CK, credentials, and compliance",{"title":703,"path":704,"stem":705,"description":706},"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":708,"path":709,"stem":710,"description":711},"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":713,"path":714,"stem":715,"description":716},"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":718,"path":719,"stem":720,"description":721},"Dethereal Glossary","\u002Fdethereal\u002Fglossary","03.dethereal\u002F09.glossary","Definitions for Dethereal-specific terminology",{"title":723,"description":724,"path":725,"stem":726,"children":727,"page":-1},"Threat Report","The residual-risk report over a threat model: reading it, filtering it and exporting it.","\u002Fthreat-report","04.threat-report",[728,731,736,741,746,751],{"title":723,"path":725,"stem":729,"description":730},"04.threat-report\u002Findex","Read, filter, drill into, and export a residual-risk report over a threat model",{"title":732,"path":733,"stem":734,"description":735},"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":737,"path":738,"stem":739,"description":740},"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":742,"path":743,"stem":744,"description":745},"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":747,"path":748,"stem":749,"description":750},"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":752,"path":753,"stem":754,"description":755},"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":757,"description":758,"path":550,"stem":759,"children":760,"page":-1},"Risk assessment","The risk assessment module: the register, the reports and the method behind them.","05.risk-assessment",[761,765,769,772,773,777,780,784],{"title":762,"path":550,"stem":763,"description":764},"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":766,"path":542,"stem":767,"description":768},"FAQ and Troubleshooting","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":347,"path":353,"stem":770,"description":771},"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":5,"path":572,"stem":574,"description":568},{"title":774,"path":33,"stem":775,"description":776},"Methodology 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":737,"path":28,"stem":778,"description":779},"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":781,"path":406,"stem":782,"description":783},"Stakeholder Reports and Exports","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":785,"path":287,"stem":786,"description":787},"The 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":789,"description":790,"path":791,"stem":792,"children":793,"page":-1},"Threat Patterns","The Threat Patterns module and its modelling checklist.","\u002Fthreat-patterns","06.threat-patterns",[794,798],{"title":795,"path":791,"stem":796,"description":797},"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":799,"path":800,"stem":801,"description":802},"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":804,"description":805,"path":806,"stem":807,"children":808,"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",[809,813,818,823,828,833,838,843,848,853,858,863,868],{"title":810,"path":806,"stem":811,"description":812},"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":814,"path":815,"stem":816,"description":817},"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":819,"path":820,"stem":821,"description":822},"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":824,"path":825,"stem":826,"description":827},"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":829,"path":830,"stem":831,"description":832},"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":834,"path":835,"stem":836,"description":837},"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":839,"path":840,"stem":841,"description":842},"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":844,"path":845,"stem":846,"description":847},"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":849,"path":850,"stem":851,"description":852},"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":854,"path":855,"stem":856,"description":857},"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":859,"path":860,"stem":861,"description":862},"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":864,"path":865,"stem":866,"description":867},"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":869,"path":870,"stem":871,"description":872},"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":874,"description":875,"path":876,"stem":877,"children":878,"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",[879,883,888],{"title":880,"path":876,"stem":881,"description":882},"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":884,"path":885,"stem":886,"description":887},"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":889,"path":890,"stem":891,"description":892},"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",1793748186078]