[{"data":1,"prerenderedAt":812},["ShallowReactive",2],{"page-\u002Frisk-assessment\u002Fmethodology-and-trust":3,"navigation":494},{"id":4,"title":5,"body":6,"description":16,"extension":487,"meta":488,"navigation":489,"path":490,"seo":491,"stem":492,"__hash__":493},"docs\u002F05.risk-assessment\u002F04.methodology-and-trust.md","Methodology and Trust",{"type":7,"value":8,"toc":476},"minimark",[9,13,17,25,39,47,52,59,66,76,87,95,99,107,199,206,214,218,221,231,241,248,252,263,266,292,310,313,391,407,411,414,440,443,447],[10,11,5],"h1",{"id":12},"methodology-and-trust",[14,15,16],"p",{},"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.",[14,18,19,20,24],{},"The Risk Assessment is built to ",[21,22,23],"strong",{},"under-claim",". Given the choice between a flattering summary and an honest gap, it shows the gap. There is no single \"risk score\" and no green \"all clear\" — on purpose. That restraint is not a missing feature; it is the property that makes the report defensible. This chapter is written for the reader who has to stand behind the numbers: the CISO briefing a board, the risk manager reconciling a register, the compliance or audit officer who needs to know exactly what the report does and does not assert.",[14,26,27,28,32,33,38],{},"This chapter is about ",[29,30,31],"em",{},"why to trust the numbers",". For how to read the bands, the likelihood × impact matrix, and the coverage posture, see ",[34,35,37],"a",{"href":36},"\u002Frisk-assessment\u002Freading-the-report","Reading the Report",".",[14,40,41,44],{},[34,42],{"id":43},"freshness",[34,45],{"id":46},"staleness",[48,49,51],"h2",{"id":50},"grounded-in-your-model-and-reproducible","Grounded in your model, and reproducible",[14,53,54,55,58],{},"The report is produced from ",[21,56,57],{},"your own threat model, and nothing else",". There is no AI making judgment calls, no external threat-intelligence feed, no vendor benchmark, and no industry dataset blended in behind the scenes. Every band, every count, and every coverage ratio resolves to something you modeled — an element, a data flow, a control, a boundary, a technique mapping. Nothing arrives from outside your model, so there is no third-party data whose provenance, currency, or licensing an auditor would need to question.",[14,60,61,62,65],{},"Because the report draws only on your model and does no guessing, it is ",[21,63,64],{},"reproducible",". The same model produces the same report, every time. Generate it today, and generate it again next month over an unchanged model, and the two are identical — line for line, band for band. Nothing in between can quietly move a number: no model that \"learned\" something new, no feed that shifted overnight. This is the single most useful property to hand an auditor: give them the model, let them regenerate, and they get your report back, byte for byte.",[14,67,68,69,72,73,75],{},"Reproducibility also makes the report ",[21,70,71],{},"honest about time",". A Risk Assessment is a snapshot, bound to the exact state of your model at the moment you generated it. If the model changes afterward — someone adds a component, reclassifies a data item, declares a new boundary — the report notices and tells you, raising a notice that your model has changed since the report was generated. The remedy is to regenerate. You are never left holding a stale report that silently disagrees with the model it claims to describe. (For the notice itself and how it behaves, see ",[34,74,37],{"href":36},".)",[14,77,78,79,82,83,86],{},"The report also depends on the ",[21,80,81],{},"ATT&CK\u002FD3FEND reference data"," loaded on the platform, so it checks that too. When the reference data is updated, the report works out whether the update could have changed anything it concluded. If it provably could not — your model's assessed inputs are unchanged, so no coverage verdict moved, and only displayed details such as technique names, published mitigations, or reference links may be dated — the notice is ",[21,84,85],{},"informational",", not the amber alarm. Recreate when convenient to pick up the current details. If the update did move the assessment inputs, or the report cannot tell whether it did, the notice stays amber: recreate before you cite the report.",[14,88,89,92],{},[34,90],{"id":91},"point-in-time",[34,93],{"id":94},"coverage-denominator",[48,96,98],{"id":97},"what-the-numbers-mean-and-what-they-dont","What the numbers mean — and what they don't",[14,100,101,102,106],{},"Four disclaimers travel with every Risk Assessment, and they are carried onto the governance versions of the report as well (see ",[34,103,105],{"href":104},"\u002Frisk-assessment\u002Fstakeholder-reports","Stakeholder Reports","). They are not legal boilerplate to scroll past — each one tells you precisely how far a number may be pushed in a conversation, and how far it may not. Read them as the boundary of what you are entitled to assert on the report's authority.",[108,109,115],"div",{"className":110,"tabIndex":112,"role":113,"ariaLabel":114},[111],"table-frame",0,"region","Table: What the numbers mean — and what they don't",[116,117,118,131],"table",{},[119,120,121],"thead",{},[122,123,124,128],"tr",{},[125,126,127],"th",{},"The disclaimer, in plain terms",[125,129,130],{},"What it means for you",[132,133,134,150,165,180],"tbody",{},[122,135,136,143],{},[137,138,139,142],"td",{},[21,140,141],{},"Point-in-time snapshot."," This is the modeled posture as of the moment it was generated — not a live scan of your running environment. The model may have changed since.",[137,144,145,146,149],{},"The report describes the system ",[29,147,148],{},"as you drew it",", at one instant. Present it as a design-time assessment, not as evidence of what is deployed right now. If the model has moved on, regenerate before you cite it.",[122,151,152,158],{},[137,153,154,157],{},[21,155,156],{},"Ordinal, not absolute."," Likelihood, impact, and severity are relative rankings derived from modeled structure — not probabilities, not loss estimates, and not a single risk score.",[137,159,160,161,164],{},"The bands ",[29,162,163],{},"order"," your exposures so you know what to look at first. They do not quantify risk in money, percentages, or odds. Do not add them up, average them, or read a band as a dollar figure.",[122,166,167,177],{},[137,168,169,172,173,176],{},[21,170,171],{},"Modeled coverage."," Coverage reflects the controls present ",[29,174,175],{},"in the model",", not their real-world operating effectiveness. An uncovered finding may mean a control is unmodeled, not that it is absent.",[137,178,179],{},"A gap in coverage is a prompt to check two things: is the control missing, or merely not modeled yet? The report cannot tell the difference, and it does not pretend to.",[122,181,182,188],{},[137,183,184,187],{},[21,185,186],{},"No assurance."," The report expresses no assurance opinion. It is not an audit, a review, or a certification, and it does not verify the existence, design, or operating effectiveness of any control. It reflects the model as drawn, not the environment as operated.",[137,189,190,191,194,195,198],{},"This is a modeling tool, not an attestation. It does not certify compliance and it does not test controls. Use it to ",[29,192,193],{},"inform"," an audit or a filing — never to ",[29,196,197],{},"substitute"," for one.",[14,200,201,202,205],{},"The fourth disclaimer — ",[21,203,204],{},"no assurance"," — is carried on every version of the report, including the most detailed technical export. The most assertive artifact never carries a weaker caveat than the board deck. That symmetry is deliberate: whichever version of the report leaves your hands, it states its own limits.",[14,207,208,211],{},[34,209],{"id":210},"no-green",[34,212],{"id":213},"no-single-score",[48,215,217],{"id":216},"why-there-is-no-single-score-and-no-green","Why there is no single score, and no green",[14,219,220],{},"You will not find one headline risk number in a Risk Assessment, and you will not find a green \"you're safe\" state anywhere in it. Both absences are chosen.",[14,222,223,226,227,230],{},[21,224,225],{},"A single rolled-up score would hide the gaps that matter."," The moment ten findings collapse into one number, the two critical exposures average away against eight low ones, and the report starts telling a story that is comfortable rather than true. So the report keeps its signals ",[29,228,229],{},"segregated",". Findings are ranked into bands; an element's band is the highest of its findings' bands, never a blend that dilutes the worst case; roll-ups are shown as distributions — how many findings sit in each band — never as a sum. Nothing flattering hides behind an average, because there is no average to hide behind.",[14,232,233,236,237,240],{},[21,234,235],{},"There is no green because the report cannot see your live environment."," It knows what you modeled; it does not know what is running. Painting any part of the report \"safe\" would assert something it has no standing to assert. So where a control is present, the report shows it as present — a real, positive signal — but it never escalates that into an all-clear. And where the report cannot tell, it says so plainly: an unmeasured finding reads as ",[29,238,239],{},"unknown",", never quietly filed under \"low,\" and a place where coverage is undetermined is shown as undetermined, never rounded up into \"covered.\" Absent evidence is shown as absent.",[14,242,243,244,247],{},"This is where under-claiming earns its keep. In front of a board or an auditor, the credible report is the one that volunteers its own gaps. A tool that only ever shows green invites the question ",[29,245,246],{},"\"what aren't you seeing?\""," — and has no answer. A Risk Assessment answers that question on every screen: here is what I found, here is what I could not determine, and here is exactly where I stopped. That is a far stronger position to defend than a reassuring dashboard.",[48,249,251],{"id":250},"evidence-and-provenance","Evidence and provenance",[14,253,254,255,258,259,75],{},"Every finding is ",[21,256,257],{},"traceable to what produced it",". A finding names the modeled elements, flows, and techniques it rests on, and you can follow each one back to its place in your model. Nothing appears without a stated basis. (For navigating from a finding to its evidence, see ",[34,260,262],{"href":261},"\u002Frisk-assessment\u002Ffindings","Understanding Findings",[14,264,265],{},"Three principles govern how that evidence is presented, and each one exists to keep you from over- or under-reading it:",[267,268,269,276,282],"ul",{},[270,271,272,275],"li",{},[21,273,274],{},"Absence of a citation is not absence of basis."," Some findings cite an external framework and some do not, and the difference is about what a public source happens to have published — not about whether the finding is sound. A finding without a visible citation is not a finding without grounds. The report says this out loud wherever sources appear, so a reader never mistakes lighter citation for weaker validity.",[270,277,278,281],{},[21,279,280],{},"Synthesis is labeled as synthesis."," Where a technique mapping is Dethernety's own reasoning rather than a mapping the framework itself published, the report says so, right next to the mapping. You are never handed a synthesized link dressed up as an authoritative one — so you can present each to an auditor for exactly what it is.",[270,283,284,287,288,291],{},[21,285,286],{},"Guidance names a candidate, not a cure."," Where the report suggests the ",[29,289,290],{},"class"," of control a gap concerns, it presents it as a candidate class — the kind of control the gap is about — never as a specific product and never as a claim that adopting it changes the rating.",[14,293,294,295,298,299,302,303,306,307],{},"That last point deserves its own emphasis, because it is the single principle most often misread: ",[21,296,297],{},"having remediation guidance is not the same as a risk being fixed."," The report can tell you exactly what to change on an element to clear a finding. It will never let that guidance read as a claim that the change has been made, is scheduled, or has lowered the risk. Guidance tells you ",[29,300,301],{},"what to change","; only changing the model and regenerating actually ",[29,304,305],{},"moves a rating",". As the report itself puts it wherever it offers guidance: ",[29,308,309],{},"applying a control is a model change — recreate to see its effect on this rating.",[14,311,312],{},"To keep that line from ever blurring, the report holds itself to a strict vocabulary. It describes changes to make; it never announces that a finding has been dealt with.",[108,314,317],{"className":315,"tabIndex":112,"role":113,"ariaLabel":316},[111],"Table: Evidence and provenance",[116,318,319,329],{},[119,320,321],{},[122,322,323,326],{},[125,324,325],{},"The report will never tell you…",[125,327,328],{},"Because",[132,330,331,353,375],{},[122,332,333,350],{},[137,334,335,336,339,340,339,343,346,347],{},"that a finding is ",[21,337,338],{},"fixed",", ",[21,341,342],{},"closed",[21,344,345],{},"resolved",", or ",[21,348,349],{},"addressed",[137,351,352],{},"It cannot observe your live environment. It can only describe the change that would clear the finding — never confirm that you made it.",[122,354,355,372],{},[137,356,357,358,339,361,346,364,367,368,371],{},"that guidance ",[21,359,360],{},"reduces",[21,362,363],{},"lowers",[21,365,366],{},"mitigates"," the risk, or that a rating has ",[21,369,370],{},"moved"," to a lower band",[137,373,374],{},"A rating moves only when you change the model and regenerate. Advice on its own never moves a band.",[122,376,377,388],{},[137,378,335,379,339,382,346,385],{},[21,380,381],{},"remediated",[21,383,384],{},"scheduled",[21,386,387],{},"planned-fixed",[137,389,390],{},"Those are decisions that belong to your management process, recorded deliberately — not conclusions the analysis is entitled to draw on its own.",[14,392,393,394,397,398,401,402,406],{},"The distinction between a management ",[29,395,396],{},"decision"," about a risk and a ",[29,399,400],{},"computed fact"," about a finding is preserved throughout, and the two are never merged or summed. Where you record how you intend to treat a risk, that decision lives in the register alongside — never inside — the computed finding. See ",[34,403,405],{"href":404},"\u002Frisk-assessment\u002Fthe-risk-register","The Risk Register"," for how those authored decisions sit next to the analysis without ever altering it.",[48,408,410],{"id":409},"defending-this-report","Defending this report",[14,412,413],{},"When you take a Risk Assessment into a board meeting, a regulatory conversation, or an external audit, these are the properties you can stand behind without qualification:",[267,415,416,422,428,434],{},[270,417,418,421],{},[21,419,420],{},"It is reproducible."," Hand over the model and anyone can regenerate the exact report. There is no hidden state and no run-to-run drift to explain.",[270,423,424,427],{},[21,425,426],{},"It is grounded."," Every number resolves to something in your model. Nothing is inferred from outside data or from an AI's judgment, so there is no external source whose reliability you have to defend.",[270,429,430,433],{},[21,431,432],{},"It is bounded."," The report states its own limits on every version, and the strongest caveat — that this is not an audit and asserts no control effectiveness — is present even on the most technical export.",[270,435,436,439],{},[21,437,438],{},"It is conservative."," Where it cannot tell, it shows the gap rather than a comforting default. It under-claims by design, so the honest reading is always the one on the page.",[14,441,442],{},"Used this way, the report's restraint becomes your strongest argument. It does not ask anyone to trust a number on faith; it shows the basis for the number, states the limits of the number, and can be regenerated to prove it. A tool that volunteers its own gaps and refuses to overstate its own reach is precisely the tool an auditor is inclined to believe.",[48,444,446],{"id":445},"where-to-go-next","Where to go next",[267,448,449,454,459,464,469],{},[270,450,451,453],{},[34,452,37],{"href":36}," — how to read the bands, the likelihood × impact matrix, and the coverage posture.",[270,455,456,458],{},[34,457,262],{"href":261}," — following a finding back to the evidence that produced it.",[270,460,461,463],{},[34,462,105],{"href":104}," — the Board and Risk Committee versions, and the disclaimers they carry.",[270,465,466,468],{},[34,467,405],{"href":404}," — recording management decisions alongside the analysis without altering it.",[270,470,471,475],{},[34,472,474],{"href":473},"\u002Frisk-assessment\u002Ffaq","FAQ"," — common questions about trust, scope, and defensibility.",{"title":477,"searchDepth":478,"depth":478,"links":479},"",3,[480,482,483,484,485,486],{"id":50,"depth":481,"text":51},2,{"id":97,"depth":481,"text":98},{"id":216,"depth":481,"text":217},{"id":250,"depth":481,"text":251},{"id":409,"depth":481,"text":410},{"id":445,"depth":481,"text":446},"md",{},true,"\u002Frisk-assessment\u002Fmethodology-and-trust",{"title":5,"description":16},"05.risk-assessment\u002F04.methodology-and-trust","iqDkFs4DIMmwYluzQPiLEUMVsTlmAagxG0B6t-hIwwY",[495,550,585,640,673,707,722,792],{"title":496,"description":497,"path":498,"stem":499,"children":500,"page":-1},"Platform","Modelling, analysis, findings and controls in the Dethernety platform.","\u002Fplatform","01.platform",[501,505,510,515,520,525,530,535,540,545],{"title":502,"path":498,"stem":503,"description":504},"Dethernety User Documentation","01.platform\u002Findex","User guide for the Dethernety threat modeling platform",{"title":506,"path":507,"stem":508,"description":509},"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":511,"path":512,"stem":513,"description":514},"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":516,"path":517,"stem":518,"description":519},"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":521,"path":522,"stem":523,"description":524},"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":526,"path":527,"stem":528,"description":529},"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":531,"path":532,"stem":533,"description":534},"Issue Management Guide","\u002Fplatform\u002Fissue-management-guide","01.platform\u002F06.issue-management-guide","Issue tracking, filtering, and management in Dethernety.",{"title":536,"path":537,"stem":538,"description":539},"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":541,"path":542,"stem":543,"description":544},"Understanding Modules","\u002Fplatform\u002Funderstanding-modules","01.platform\u002F08.understanding-modules","How Dethernety's module system extends your threat modeling capabilities.",{"title":546,"path":547,"stem":548,"description":549},"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":551,"description":552,"path":553,"stem":554,"children":555,"page":-1},"BYODt cloud","Deploying the platform yourself and connecting it to the BYODt cloud.","\u002Fbyodt-cloud","02.byodt-cloud",[556,560,565,570,575,580],{"title":557,"path":553,"stem":558,"description":559},"BYODt Deployment","02.byodt-cloud\u002Findex","Run Dethernety on your own machine: install, configure, operate, and recover",{"title":561,"path":562,"stem":563,"description":564},"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":566,"path":567,"stem":568,"description":569},"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":571,"path":572,"stem":573,"description":574},"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":576,"path":577,"stem":578,"description":579},"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":581,"path":582,"stem":583,"description":584},"Troubleshooting the BYODt Deployment","\u002Fbyodt-cloud\u002Ftroubleshooting","02.byodt-cloud\u002F05.troubleshooting","Symptom, cause, and fix for the failures this deployment reports",{"title":586,"description":587,"path":588,"stem":589,"children":590,"page":-1},"Dethereal","The Claude Code plugin: build a threat model in conversation and publish it to the platform.","\u002Fdethereal","03.dethereal",[591,595,600,605,610,615,620,625,630,635],{"title":592,"path":588,"stem":593,"description":594},"Dethereal — Claude Code Plugin for Threat Modeling","03.dethereal\u002Findex","Comprehensive documentation for the Dethereal threat modeling plugin",{"title":596,"path":597,"stem":598,"description":599},"Getting Started with Dethereal","\u002Fdethereal\u002Fgetting-started","03.dethereal\u002F01.getting-started","Install the plugin, authenticate, and create your first threat model",{"title":601,"path":602,"stem":603,"description":604},"The 11-Step Guided Workflow","\u002Fdethereal\u002Fguided-workflow","03.dethereal\u002F02.guided-workflow","Complete walkthrough of the \u002Fdethereal:threat-model guided process",{"title":606,"path":607,"stem":608,"description":609},"Command Reference","\u002Fdethereal\u002Fcommand-reference","03.dethereal\u002F03.command-reference","Complete reference for all 14 Dethereal slash commands",{"title":611,"path":612,"stem":613,"description":614},"Threat Model Concepts","\u002Fdethereal\u002Fmodel-concepts","03.dethereal\u002F04.model-concepts","Components, boundaries, data flows, classes, attributes, and quality scoring",{"title":616,"path":617,"stem":618,"description":619},"Discovery and Enrichment","\u002Fdethereal\u002Fdiscovery-and-enrichment","03.dethereal\u002F05.discovery-and-enrichment","Infrastructure scanning, security attributes, MITRE ATT&CK, credentials, and compliance",{"title":621,"path":622,"stem":623,"description":624},"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":626,"path":627,"stem":628,"description":629},"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":631,"path":632,"stem":633,"description":634},"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":636,"path":637,"stem":638,"description":639},"Dethereal Glossary","\u002Fdethereal\u002Fglossary","03.dethereal\u002F09.glossary","Definitions for Dethereal-specific terminology",{"title":641,"description":642,"path":643,"stem":644,"children":645,"page":-1},"Threat Report","The residual-risk report over a threat model: reading it, filtering it and exporting it.","\u002Fthreat-report","04.threat-report",[646,649,654,658,663,668],{"title":641,"path":643,"stem":647,"description":648},"04.threat-report\u002Findex","Read, filter, drill into, and export a residual-risk report over a threat model",{"title":650,"path":651,"stem":652,"description":653},"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":37,"path":655,"stem":656,"description":657},"\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":659,"path":660,"stem":661,"description":662},"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":664,"path":665,"stem":666,"description":667},"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":669,"path":670,"stem":671,"description":672},"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":674,"description":675,"path":676,"stem":677,"children":678,"page":-1},"Risk assessment","The risk assessment module: the register, the reports and the method behind them.","\u002Frisk-assessment","05.risk-assessment",[679,683,687,691,696,697,700,704],{"title":680,"path":676,"stem":681,"description":682},"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":684,"path":473,"stem":685,"description":686},"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":688,"path":261,"stem":689,"description":690},"Findings","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":692,"path":693,"stem":694,"description":695},"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":5,"path":490,"stem":492,"description":16},{"title":37,"path":36,"stem":698,"description":699},"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":701,"path":104,"stem":702,"description":703},"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":405,"path":404,"stem":705,"description":706},"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":708,"description":709,"path":710,"stem":711,"children":712,"page":-1},"Threat Patterns","The Threat Patterns module and its modelling checklist.","\u002Fthreat-patterns","06.threat-patterns",[713,717],{"title":714,"path":710,"stem":715,"description":716},"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":718,"path":719,"stem":720,"description":721},"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":723,"description":724,"path":725,"stem":726,"children":727,"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",[728,732,737,742,747,752,757,762,767,772,777,782,787],{"title":729,"path":725,"stem":730,"description":731},"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":733,"path":734,"stem":735,"description":736},"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":738,"path":739,"stem":740,"description":741},"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":743,"path":744,"stem":745,"description":746},"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":748,"path":749,"stem":750,"description":751},"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":753,"path":754,"stem":755,"description":756},"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":758,"path":759,"stem":760,"description":761},"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":763,"path":764,"stem":765,"description":766},"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":768,"path":769,"stem":770,"description":771},"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":773,"path":774,"stem":775,"description":776},"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":778,"path":779,"stem":780,"description":781},"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":783,"path":784,"stem":785,"description":786},"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":788,"path":789,"stem":790,"description":791},"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":793,"description":794,"path":795,"stem":796,"children":797,"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",[798,802,807],{"title":799,"path":795,"stem":800,"description":801},"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":803,"path":804,"stem":805,"description":806},"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":808,"path":809,"stem":810,"description":811},"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",1793748186095]