[{"data":1,"prerenderedAt":1137},["ShallowReactive",2],{"page-\u002Frisk-assessment\u002Fstakeholder-reports":3,"navigation":821},{"id":4,"title":5,"body":6,"description":16,"extension":814,"meta":815,"navigation":816,"path":817,"seo":818,"stem":819,"__hash__":820},"docs\u002F05.risk-assessment\u002F06.stakeholder-reports.md","Stakeholder Reports and Exports",{"type":7,"value":8,"toc":792},"minimark",[9,13,17,25,49,54,61,83,88,92,98,180,186,204,224,229,248,252,259,265,272,277,284,288,292,303,330,349,354,358,371,375,382,386,389,447,459,463,466,469,474,479,482,495,498,664,685,691,694,698,764,768],[10,11,5],"h1",{"id":12},"stakeholder-reports-and-exports",[14,15,16],"p",{},"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.",[14,18,19,20,24],{},"Every one of these outputs is drawn from the ",[21,22,23],"strong",{},"same frozen assessment",". A number on the board brief is the same number on the technical report, because both are filtered and framed from one point-in-time truth, not recomputed. That is what makes the reporting defensible: the framing changes for the reader, the numbers never do.",[14,26,27,28,33,34,38,39,43,44,48],{},"This guide covers the three audience-tiered reports, how to preview and download them, the governance disclaimers they carry, and the two data exports (JSON and the register CSV). For how the numbers are produced and why they can be trusted, see ",[29,30,32],"a",{"href":31},"\u002Frisk-assessment\u002Freading-the-report","Reading the Report"," and ",[29,35,37],{"href":36},"\u002Frisk-assessment\u002Fmethodology-and-trust","Methodology and Trust",". For how risks get into the register in the first place, see ",[29,40,42],{"href":41},"\u002Frisk-assessment\u002Fthe-risk-register","The Risk Register"," — this guide is only about getting them ",[45,46,47],"em",{},"out",".",[50,51,53],"h2",{"id":52},"before-you-export","Before you export",[14,55,56,57,60],{},"The ",[21,58,59],{},"Export"," menu lives in the report header, next to the title. It becomes available once you have generated a report. The menu is unavailable — and the button explains why on hover — in three cases:",[62,63,64,71,77],"ul",{},[65,66,67,70],"li",{},[21,68,69],{},"No report yet."," Generate the assessment first.",[65,72,73,76],{},[21,74,75],{},"A run is in flight."," A Generate or Recreate is still finishing; wait for it to complete.",[65,78,79,82],{},[21,80,81],{},"Pending dispositions."," You have triaged findings that are not yet reflected in the numbers. Recreate to fold them in before exporting, so the report you send matches the decisions you made.",[14,84,85],{},[29,86],{"id":87},"tiers",[50,89,91],{"id":90},"the-three-report-tiers","The three report tiers",[14,93,94,95,97],{},"Open the ",[21,96,59],{}," menu and you will see five items. The first three are formatted reports, each written for a specific reader:",[99,100,106],"div",{"className":101,"tabIndex":103,"role":104,"ariaLabel":105},[102],"table-frame",0,"region","Table: The three report tiers",[107,108,109,128],"table",{},[110,111,112],"thead",{},[113,114,115,119,122,125],"tr",{},[116,117,118],"th",{},"Report",[116,120,121],{},"Who it's for",[116,123,124],{},"What it contains",[116,126,127],{},"What it omits",[129,130,131,148,164],"tbody",{},[113,132,133,139,142,145],{},[134,135,136],"td",{},[21,137,138],{},"Board \u002F Executive",[134,140,141],{},"Your board, executive committee, or anyone who needs the posture in one page",[134,143,144],{},"The headline takeaway; the four-state coverage counts (always with denominators, never a bare percentage); the uncovered\u002Fexposed top-band count; the inherent likelihood × impact matrix; the four governance disclaimers; a summary of your authored risks with the top open risks by assessed impact; and the governance flags (risks rated below the computed severity, risks accepted via disposition, open risks with no decided treatment)",[134,146,147],{},"Finding codes, MITRE technique references, the full findings ledger, architectural-findings detail, analyst appendices, and methodology parameters — only an \"as of · methodology version\" line is carried",[113,149,150,155,158,161],{},[134,151,152],{},[21,153,154],{},"Risk Committee",[134,156,157],{},"Your risk committee, second line, or internal audit liaison",[134,159,160],{},"Everything the board sees, plus: the full four-state coverage and finding-type summary, conservatism-reducing parameter flags, the full scope-and-limitations panel, the complete authored register with evidence liveness, the acceptances, and the reconciliations between what management recorded and what the analysis computed (see below)",[134,162,163],{},"Raw knowledge-graph and reasoning appendices, and per-technique guidance",[113,165,166,171,174,177],{},[134,167,168],{},[21,169,170],{},"Technical (full)",[134,172,173],{},"Your security team and the analyst who owns the assessment",[134,175,176],{},"The complete assessment rendered in full, including finding codes, every finding across every element, and all analyst appendices (reasoning, coverage evidence, framework guidance)",[134,178,179],{},"Nothing — this is the full detail",[14,181,182,185],{},[21,183,184],{},"The reconciliations"," in the Risk Committee report are the reason it exists as its own tier. It places management's recorded decisions next to the analysis's computed facts and shows where they differ, rather than hiding the gap:",[62,187,188,198],{},[65,189,190,193,194,197],{},[21,191,192],{},"Treatment vs. disposition."," A ",[21,195,196],{},"treatment"," is a management decision you author on a risk (accept, mitigate, transfer, avoid). \"Accepted via disposition\" is a computed fact about a finding's evidence. A risk may carry one, both, or a deliberate mismatch — the report shows them side by side and frames the difference as a conversation to have, not an error to fix.",[65,199,200,203],{},[21,201,202],{},"The divergence view."," Where you rated a risk's impact below the model's computed severity band (frozen at the moment you linked the evidence), the committee report surfaces it, so a deliberately downgraded risk is visible rather than buried.",[14,205,206,209,210,214,215,219,220,223],{},[21,207,208],{},"Evidence from Threat Patterns."," A risk can cite findings that ",[29,211,213],{"href":212},"\u002Fthreat-patterns","Threat Patterns"," recorded in your register (see ",[29,216,218],{"href":217},"\u002Frisk-assessment\u002Fthe-risk-register#threat-patterns","Risks recorded from Threat Patterns","). This report does not judge those findings itself: their liveness is Threat Patterns' answer. So the evidence column of such a risk adds the note ",[45,221,222],{},"\"Includes Threat Patterns findings, judged by Threat Patterns\"",". Threat Patterns severities are on their own scale, so they never enter the divergence view.",[225,226,228],"h3",{"id":227},"which-report-to-send-whom","Which report to send whom",[62,230,231,237,242],{},[65,232,233,234,236],{},"Send the ",[21,235,138],{}," report to anyone who needs the answer, not the working. It is one page, register-led, and carries the disclaimers that make it safe to forward.",[65,238,233,239,241],{},[21,240,154],{}," report to a second-line or audit audience who needs to see the reconciliations and challenge the ratings.",[65,243,244,245,247],{},"Keep the ",[21,246,170],{}," report for the people who will act on individual findings.",[225,249,251],{"id":250},"one-truth-filtered-and-framed","One truth, filtered and framed",[14,253,254,255,258],{},"All three reports are built from the ",[21,256,257],{},"same frozen assessment plus your current register",". No tier recalculates anything — each one shows a different selection of the same underlying values. This has one guarantee that matters for governance:",[260,261,262],"blockquote",{},[14,263,264],{},"A number can never disagree across the three reports. A coverage count on the board brief is the same coverage count on the technical report. A screenshot of any tier can be trusted against any other.",[14,266,267],{},[268,269],"img",{"alt":270,"src":271},"One frozen assessment and its risk register feed a single filter-and-frame step, which produces the Board, Risk Committee, and Technical reports; no arrow returns to the assessment, so nothing is recomputed.","\u002Fguides\u002Frisk-assessment\u002Fimages\u002Fone-assessment-three-reports.svg",[14,273,274],{},[45,275,276],{},"One frozen assessment and its risk register feed a single filter-and-frame step. The Board, Risk Committee, and Technical reports are framings of that one source — nothing flows back to be recomputed.",[14,278,279,280,283],{},"Because the tiers share one source, the board brief is a strict ",[45,281,282],{},"subset"," of what the technical report shows — never a re-derivation that could drift.",[50,285,287],{"id":286},"preview-and-download-a-report","Preview and download a report",[225,289,291],{"id":290},"governance-tiers-open-a-preview-first","Governance tiers open a preview first",[14,293,56,294,33,296,298,299,302],{},[21,295,138],{},[21,297,154],{}," reports open a short ",[21,300,301],{},"Export preview"," before they download. This is a governance sign-off step, not a rendered page of the report. It shows you:",[62,304,305,311,321,327],{},[65,306,56,307,310],{},[21,308,309],{},"as-of"," timestamp the report will carry.",[65,312,313,314,33,317,320],{},"A ",[21,315,316],{},"Shows",[21,318,319],{},"Omits"," list — the exact scope claim the reader will see, so you confirm what you are and are not sending.",[65,322,313,323,326],{},[21,324,325],{},"staleness line"," if the underlying model looks like it has changed since the assessment was generated.",[65,328,329],{},"How many of your open authored risks rest on evidence that is now flagged stale, so nothing is forwarded on quietly outdated grounds.",[14,331,332,333,336,337,340,341,344,345,348],{},"Click ",[21,334,335],{},"Download"," to produce the report, or ",[21,338,339],{},"Cancel"," to back out. If the model looks meaningfully stale, the preview promotes a ",[21,342,343],{},"Recreate"," action to the front and relabels the download ",[21,346,347],{},"Download stale copy"," — so confirming a stale export is never easier than refreshing it first. A report downloaded while stale is stamped as such inside the file, so a forwarded copy cannot pass itself off as current.",[14,350,56,351,353],{},[21,352,335],{}," button stays disabled until your register has finished loading. This prevents a board report from asserting \"no open authored risks\" about a register that simply had not been read yet.",[225,355,357],{"id":356},"direct-downloads","Direct downloads",[14,359,56,360,362,363,366,367,370],{},[21,361,170],{}," report, the ",[21,364,365],{},"JSON (full snapshot)"," export, and the ",[21,368,369],{},"Register (CSV)"," export download immediately with no preview — they carry no board-facing framing to confirm.",[225,372,374],{"id":373},"a-report-is-a-point-in-time-snapshot","A report is a point-in-time snapshot",[14,376,377,378,381],{},"Every download captures the assessment and register ",[21,379,380],{},"as they are at that moment",". It does not update itself afterward. If you change the model and Recreate, or edit the register, download again to reflect the change. The as-of timestamp on each report tells the reader exactly which moment it represents.",[50,383,385],{"id":384},"the-governance-disclaimers","The governance disclaimers",[14,387,388],{},"The Board \u002F Executive and Risk Committee reports open with four plain-language disclaimers. They are not legal boilerplate bolted on at the end — they state precisely what the report claims and, just as importantly, what it does not:",[99,390,393],{"className":391,"tabIndex":103,"role":104,"ariaLabel":392},[102],"Table: The governance disclaimers",[107,394,395,405],{},[110,396,397],{},[113,398,399,402],{},[116,400,401],{},"Disclaimer",[116,403,404],{},"In plain terms",[129,406,407,417,427,437],{},[113,408,409,414],{},[134,410,411],{},[21,412,413],{},"Point-in-time",[134,415,416],{},"This is a snapshot of the modeled posture at a moment, not a live or deployed-state scan. The environment may have changed since it was generated.",[113,418,419,424],{},[134,420,421],{},[21,422,423],{},"Relative, not absolute",[134,425,426],{},"Likelihood, impact, and severity are ordinal comparisons drawn from the modeled structure — not probabilities, financial loss estimates, or a single risk score.",[113,428,429,434],{},[134,430,431],{},[21,432,433],{},"Coverage reflects what's modeled",[134,435,436],{},"Coverage describes the controls represented in the model, not their real-world operating effectiveness. An uncovered finding may mean a control is simply not modeled yet, not that it is absent.",[113,438,439,444],{},[134,440,441],{},[21,442,443],{},"No assurance opinion",[134,445,446],{},"The report is not an audit, review, or certification. It expresses no assurance and does not verify the existence, design, or operating effectiveness of any control. It reflects the model as drawn, not the environment as operated.",[14,448,449,452,453,456,457,48],{},[21,450,451],{},"Why this helps you."," These disclaimers are what make the report defensible to a board or an auditor. They ensure the report never claims more than it can support, so a reader can trust exactly what the numbers mean and nothing beyond it. The \"no assurance\" statement rides ",[45,454,455],{},"all three"," tiers — including the footer of the technical report — so the most detailed, most assertive artifact never carries a weaker caveat than the one-page board brief. The full meaning behind each disclaimer, and the trust model it comes from, is covered in ",[29,458,37],{"href":36},[50,460,462],{"id":461},"data-exports","Data exports",[14,464,465],{},"Two menu items give you the data itself rather than a formatted report.",[225,467,365],{"id":468},"json-full-snapshot",[14,470,471,473],{},[21,472,365],{}," downloads the complete assessment data, plus a provenance footer recording when and under what methodology it was generated. Use it when you want to feed the assessment into your own tooling, archive a machine-readable record, or build a custom view. It is the raw source the three reports are framed from.",[14,475,476],{},[29,477],{"id":478},"csv-safety",[225,480,369],{"id":481},"register-csv",[14,483,484,486,487,490,491,494],{},[21,485,369],{}," downloads your risk register as a flat spreadsheet, ready to import into your GRC tool, Excel, or Google Sheets. It carries ",[21,488,489],{},"one row per risk"," and includes ",[21,492,493],{},"both open and closed risks",", so closing a risk preserves it in your history rather than erasing it — the status is a column your importer can filter on.",[14,496,497],{},"Each row carries the fields your GRC tool needs to key on and report from:",[99,499,502],{"className":500,"tabIndex":103,"role":104,"ariaLabel":501},[102],"Table: Register (CSV)",[107,503,504,514],{},[110,505,506],{},[113,507,508,511],{},[116,509,510],{},"Field",[116,512,513],{},"What it holds",[129,515,516,533,545,559,567,575,583,595,603,611,619,634],{},[113,517,518,526],{},[134,519,520,521,525],{},"Reference handle (",[522,523,524],"code",{},"ref_id",")",[134,527,528,529,532],{},"The human-facing GRC reference, such as ",[522,530,531],{},"DT-CS-260717-4",". Convenient to read, but it can be empty on older risks, edited by an operator, or in rare cases reused — so do not rely on it as your only key.",[113,534,535,538],{},[134,536,537],{},"Source",[134,539,540,541,544],{},"Always ",[522,542,543],{},"authored"," — a built-in reminder that every register row is management opinion, not a computed finding.",[113,546,547,550],{},[134,548,549],{},"Status",[134,551,552,555,556,48],{},[522,553,554],{},"open"," or ",[522,557,558],{},"closed",[113,560,561,564],{},[134,562,563],{},"Cause, event, impact, and the full statement",[134,565,566],{},"The three-part risk statement, both as separate parts and as the assembled sentence.",[113,568,569,572],{},[134,570,571],{},"Owner",[134,573,574],{},"The named owner, or empty.",[113,576,577,580],{},[134,578,579],{},"Assessed likelihood and assessed impact",[134,581,582],{},"Your hand-assigned ratings, or empty where a risk is not yet assessed.",[113,584,585,588],{},[134,586,587],{},"Treatment, treatment plan, treatment due",[134,589,590,591,594],{},"The recorded management decision and its plan and due date. The treatment always carries a word (",[522,592,593],{},"undecided"," when no decision has been made) so \"no decision yet\" is never confused with \"no data\".",[113,596,597,600],{},[134,598,599],{},"Review-by date, notes",[134,601,602],{},"The review date and free-text notes, or empty.",[113,604,605,608],{},[134,606,607],{},"Evidence count",[134,609,610],{},"How many pieces of evidence support the risk — a plain count, carrying no verdict.",[113,612,613,616],{},[134,614,615],{},"Created by, created at",[134,617,618],{},"Who first recorded the risk, and when.",[113,620,621,627],{},[134,622,623,624,525],{},"Stable id (",[522,625,626],{},"risk_id",[134,628,629,630,633],{},"The immutable, never-empty, globally unique identifier. ",[21,631,632],{},"Key and de-duplicate on this",", not on the reference handle.",[113,635,636,642],{},[134,637,638,639,525],{},"Evidence sources (",[522,640,641],{},"evidence_sources",[134,643,644,645,647,648,651,652,655,656,659,660,663],{},"The last column, after ",[522,646,626],{},": which products the risk's evidence comes from, as module identifiers, sorted and separated by ",[522,649,650],{},";"," — ",[522,653,654],{},"dethermine-risk-assessment"," (Risk Assessment), ",[522,657,658],{},"dethermine-threat-patterns"," (Threat Patterns), or ",[522,661,662],{},"dethermine-risk-assessment;dethermine-threat-patterns",". Empty for a risk with no evidence. A record of where the evidence came from, carrying no verdict.",[14,665,666,669,670,673,674,673,677,680,681,684],{},[21,667,668],{},"A safety note on formulas."," If any authored text (an owner name, a note) begins with a character a spreadsheet reads as a formula — ",[522,671,672],{},"=",", ",[522,675,676],{},"+",[522,678,679],{},"-",", or ",[522,682,683],{},"@"," — it is automatically neutralized so it opens as plain text and cannot execute when someone opens the file. This is a deliberate protection against a malicious cell running in a colleague's spreadsheet. It slightly changes those values (a leading apostrophe is added), so treat the exported value as authoritative; if you match on the reference handle as an exact key, strip a single leading apostrophe first.",[14,686,687,690],{},[21,688,689],{},"Encoding."," The file is written so that accented characters and other Unicode open correctly in Excel and Google Sheets, with no garbled text — no manual import settings needed.",[14,692,693],{},"The register CSV deliberately carries no computed severity, coverage, or liveness rollup. Those live in the JSON export and the Risk Committee report; the CSV is the authored record.",[50,695,697],{"id":696},"troubleshooting","Troubleshooting",[99,699,702],{"className":700,"tabIndex":103,"role":104,"ariaLabel":701},[102],"Table: Troubleshooting",[107,703,704,714],{},[110,705,706],{},[113,707,708,711],{},[116,709,710],{},"Symptom",[116,712,713],{},"What to check",[129,715,716,726,737,748,756],{},[113,717,718,723],{},[134,719,56,720,722],{},[21,721,59],{}," button is greyed out.",[134,724,725],{},"You have not generated a report yet, a run is in flight, or you have pending dispositions. Hover the button for the exact reason; Recreate if it asks you to.",[113,727,728,734],{},[134,729,730,731,733],{},"The preview's ",[21,732,335],{}," button stays disabled.",[134,735,736],{},"The register is still loading. Wait for it to finish — the button enables once the register is read.",[113,738,739,742],{},[134,740,741],{},"The preview shows a staleness warning.",[134,743,744,745,747],{},"The model looks changed since the report was generated. Use ",[21,746,343],{}," first for an accurate report, or download the stale copy knowingly — it will be stamped as stale.",[113,749,750,753],{},[134,751,752],{},"A reference handle looks off in the CSV (a leading apostrophe, or a gap in the numbering).",[134,754,755],{},"The apostrophe is the formula-safety protection above. Numbering gaps mean a risk was deleted; a repeated number means a delete-then-recreate. Always key on the stable id, not the handle.",[113,757,758,761],{},[134,759,760],{},"The board report says \"no open authored risks\" but you have some.",[134,762,763],{},"The register had not finished loading. Reopen the report tab, let the register load, and export again.",[50,765,767],{"id":766},"what-to-read-next","What to read next",[62,769,770,775,780,785],{},[65,771,772,774],{},[29,773,32],{"href":31}," — what the numbers on screen mean.",[65,776,777,779],{},[29,778,42],{"href":41}," — how to author, rate, and close the risks that flow into these exports.",[65,781,782,784],{},[29,783,37],{"href":36}," — the full meaning of the disclaimers and why the reporting is defensible.",[65,786,787,791],{},[29,788,790],{"href":789},"\u002Frisk-assessment\u002Ffaq","FAQ"," — common questions and error messages.",{"title":793,"searchDepth":794,"depth":794,"links":795},"",3,[796,798,802,807,808,812,813],{"id":52,"depth":797,"text":53},2,{"id":90,"depth":797,"text":91,"children":799},[800,801],{"id":227,"depth":794,"text":228},{"id":250,"depth":794,"text":251},{"id":286,"depth":797,"text":287,"children":803},[804,805,806],{"id":290,"depth":794,"text":291},{"id":356,"depth":794,"text":357},{"id":373,"depth":794,"text":374},{"id":384,"depth":797,"text":385},{"id":461,"depth":797,"text":462,"children":809},[810,811],{"id":468,"depth":794,"text":365},{"id":481,"depth":794,"text":369},{"id":696,"depth":797,"text":697},{"id":766,"depth":797,"text":767},"md",{},true,"\u002Frisk-assessment\u002Fstakeholder-reports",{"title":5,"description":16},"05.risk-assessment\u002F06.stakeholder-reports","ggg-XY3TB1CXT4URSatPDoiR9Fn2sSE2l0rlc5F60bI",[822,877,912,967,1000,1034,1047,1117],{"title":823,"description":824,"path":825,"stem":826,"children":827,"page":-1},"Platform","Modelling, analysis, findings and controls in the Dethernety platform.","\u002Fplatform","01.platform",[828,832,837,842,847,852,857,862,867,872],{"title":829,"path":825,"stem":830,"description":831},"Dethernety User Documentation","01.platform\u002Findex","User guide for the Dethernety threat modeling platform",{"title":833,"path":834,"stem":835,"description":836},"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":838,"path":839,"stem":840,"description":841},"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":843,"path":844,"stem":845,"description":846},"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":848,"path":849,"stem":850,"description":851},"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":853,"path":854,"stem":855,"description":856},"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":858,"path":859,"stem":860,"description":861},"Issue Management Guide","\u002Fplatform\u002Fissue-management-guide","01.platform\u002F06.issue-management-guide","Issue tracking, filtering, and management in Dethernety.",{"title":863,"path":864,"stem":865,"description":866},"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":868,"path":869,"stem":870,"description":871},"Understanding Modules","\u002Fplatform\u002Funderstanding-modules","01.platform\u002F08.understanding-modules","How Dethernety's module system extends your threat modeling capabilities.",{"title":873,"path":874,"stem":875,"description":876},"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":878,"description":879,"path":880,"stem":881,"children":882,"page":-1},"BYODt cloud","Deploying the platform yourself and connecting it to the BYODt cloud.","\u002Fbyodt-cloud","02.byodt-cloud",[883,887,892,897,902,907],{"title":884,"path":880,"stem":885,"description":886},"BYODt Deployment","02.byodt-cloud\u002Findex","Run Dethernety on your own machine: install, configure, operate, and recover",{"title":888,"path":889,"stem":890,"description":891},"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":893,"path":894,"stem":895,"description":896},"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":898,"path":899,"stem":900,"description":901},"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":903,"path":904,"stem":905,"description":906},"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":908,"path":909,"stem":910,"description":911},"Troubleshooting the BYODt Deployment","\u002Fbyodt-cloud\u002Ftroubleshooting","02.byodt-cloud\u002F05.troubleshooting","Symptom, cause, and fix for the failures this deployment reports",{"title":913,"description":914,"path":915,"stem":916,"children":917,"page":-1},"Dethereal","The Claude Code plugin: build a threat model in conversation and publish it to the platform.","\u002Fdethereal","03.dethereal",[918,922,927,932,937,942,947,952,957,962],{"title":919,"path":915,"stem":920,"description":921},"Dethereal — Claude Code Plugin for Threat Modeling","03.dethereal\u002Findex","Comprehensive documentation for the Dethereal threat modeling plugin",{"title":923,"path":924,"stem":925,"description":926},"Getting Started with Dethereal","\u002Fdethereal\u002Fgetting-started","03.dethereal\u002F01.getting-started","Install the plugin, authenticate, and create your first threat model",{"title":928,"path":929,"stem":930,"description":931},"The 11-Step Guided Workflow","\u002Fdethereal\u002Fguided-workflow","03.dethereal\u002F02.guided-workflow","Complete walkthrough of the \u002Fdethereal:threat-model guided process",{"title":933,"path":934,"stem":935,"description":936},"Command Reference","\u002Fdethereal\u002Fcommand-reference","03.dethereal\u002F03.command-reference","Complete reference for all 14 Dethereal slash commands",{"title":938,"path":939,"stem":940,"description":941},"Threat Model Concepts","\u002Fdethereal\u002Fmodel-concepts","03.dethereal\u002F04.model-concepts","Components, boundaries, data flows, classes, attributes, and quality scoring",{"title":943,"path":944,"stem":945,"description":946},"Discovery and Enrichment","\u002Fdethereal\u002Fdiscovery-and-enrichment","03.dethereal\u002F05.discovery-and-enrichment","Infrastructure scanning, security attributes, MITRE ATT&CK, credentials, and compliance",{"title":948,"path":949,"stem":950,"description":951},"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":953,"path":954,"stem":955,"description":956},"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":958,"path":959,"stem":960,"description":961},"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":963,"path":964,"stem":965,"description":966},"Dethereal Glossary","\u002Fdethereal\u002Fglossary","03.dethereal\u002F09.glossary","Definitions for Dethereal-specific terminology",{"title":968,"description":969,"path":970,"stem":971,"children":972,"page":-1},"Threat Report","The residual-risk report over a threat model: reading it, filtering it and exporting it.","\u002Fthreat-report","04.threat-report",[973,976,981,985,990,995],{"title":968,"path":970,"stem":974,"description":975},"04.threat-report\u002Findex","Read, filter, drill into, and export a residual-risk report over a threat model",{"title":977,"path":978,"stem":979,"description":980},"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":32,"path":982,"stem":983,"description":984},"\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":986,"path":987,"stem":988,"description":989},"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":991,"path":992,"stem":993,"description":994},"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":996,"path":997,"stem":998,"description":999},"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":1001,"description":1002,"path":1003,"stem":1004,"children":1005,"page":-1},"Risk assessment","The risk assessment module: the register, the reports and the method behind them.","\u002Frisk-assessment","05.risk-assessment",[1006,1010,1014,1019,1024,1027,1030,1031],{"title":1007,"path":1003,"stem":1008,"description":1009},"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":1011,"path":789,"stem":1012,"description":1013},"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":1015,"path":1016,"stem":1017,"description":1018},"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":1020,"path":1021,"stem":1022,"description":1023},"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":37,"path":36,"stem":1025,"description":1026},"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":32,"path":31,"stem":1028,"description":1029},"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":5,"path":817,"stem":819,"description":16},{"title":42,"path":41,"stem":1032,"description":1033},"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":213,"description":1035,"path":212,"stem":1036,"children":1037,"page":-1},"The Threat Patterns module and its modelling checklist.","06.threat-patterns",[1038,1042],{"title":1039,"path":212,"stem":1040,"description":1041},"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":1043,"path":1044,"stem":1045,"description":1046},"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":1048,"description":1049,"path":1050,"stem":1051,"children":1052,"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",[1053,1057,1062,1067,1072,1077,1082,1087,1092,1097,1102,1107,1112],{"title":1054,"path":1050,"stem":1055,"description":1056},"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":1058,"path":1059,"stem":1060,"description":1061},"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":1063,"path":1064,"stem":1065,"description":1066},"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":1068,"path":1069,"stem":1070,"description":1071},"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":1073,"path":1074,"stem":1075,"description":1076},"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":1078,"path":1079,"stem":1080,"description":1081},"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":1083,"path":1084,"stem":1085,"description":1086},"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":1088,"path":1089,"stem":1090,"description":1091},"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":1093,"path":1094,"stem":1095,"description":1096},"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":1098,"path":1099,"stem":1100,"description":1101},"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":1103,"path":1104,"stem":1105,"description":1106},"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":1108,"path":1109,"stem":1110,"description":1111},"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":1113,"path":1114,"stem":1115,"description":1116},"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":1118,"description":1119,"path":1120,"stem":1121,"children":1122,"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",[1123,1127,1132],{"title":1124,"path":1120,"stem":1125,"description":1126},"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":1128,"path":1129,"stem":1130,"description":1131},"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":1133,"path":1134,"stem":1135,"description":1136},"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",1793748186106]