[{"data":1,"prerenderedAt":476},["ShallowReactive",2],{"page-\u002Fbyodt-subscription\u002Fmoving-a-deployment-to-a-new-team":3,"navigation":152},{"id":4,"title":5,"body":6,"description":137,"extension":138,"meta":139,"navigation":147,"path":148,"seo":149,"stem":150,"__hash__":151},"docs\u002F08.byodt-subscription\u002F02.moving-a-deployment-to-a-new-team.md","Moving a Deployment to a New Team",{"type":7,"value":8,"toc":126},"minimark",[9,13,17,20,23,28,31,64,67,71,74,81,86,89,93,96,98,102],[10,11,5],"h1",{"id":12},"moving-a-deployment-to-a-new-team",[14,15,16],"p",{},"Buying a team edition creates a team. It does not move the deployment you were already running — that stays bound to your personal account, which is the safe default and occasionally the surprising one. Nothing has moved and nothing is at risk. But if you want the team's deployment to be the one you have been using, there are three ways to get there, and they are not equally safe.",[14,18,19],{},"This applies when a purchase creates a new team. A team that moves to a larger edition of the same kind keeps the subscription it holds, and no deployment has anything to redo.",[21,22],"hr",{},[24,25,27],"h2",{"id":26},"three-ways-forward-best-first","Three ways forward, best first",[14,29,30],{},"The order is the advice. The first way is not merely the easiest: it is the one with nothing at risk. The last is an expert path.",[32,33,34,42,54],"ol",{},[35,36,37,41],"li",{},[38,39,40],"strong",{},"Stand up a new deployment for the team."," Nothing to migrate and nothing at risk, and the deployment you already run stays yours. The right answer for anyone whose solo work was exploratory.",[35,43,44,47,48,53],{},[38,45,46],{},"Back up your graph, then carry it across."," The safe route if the data has to come with you. Take the backup first — there is no refund window and no undo, so a restore is the only thing standing between a bad move and starting again. Taking and restoring a backup is covered in ",[49,50,52],"a",{"href":51},"\u002Fbyodt-cloud\u002Foperations#backing-up-and-restoring-the-graph","Backing up and restoring the graph",".",[35,55,56,59,60,53],{},[38,57,58],{},"Re-point the running deployment in place."," The expert path, and it is genuinely dangerous. Disconnecting removes your content mounts, your installed artifacts and the knowledge-graph connection; reconnecting restores only the last of those, and what is left behind is deleted at the next platform start. Record what is mounted and installed before you touch anything — nothing can reconstruct that list afterwards — and talk to us before you run it, at ",[49,61,63],{"href":62},"mailto:support@dether.net","support@dether.net",[14,65,66],{},"This guide gives no step-by-step sequence for the third way. Talk to us first. What is here is the part that holds regardless: what the risk is, and what to record before you touch anything.",[24,68,70],{"id":69},"why-the-third-one-is-dangerous","Why the third one is dangerous",[14,72,73],{},"A disconnect removes all three kinds of cloud module — content mounts, installed artifacts and the knowledge-graph connection — and a reconnect restores only the knowledge-graph connection. The other two are separate operator actions on separate controls, and nothing keeps a record of what was swept. A deployment left that way loses the classes those modules declare, and every relationship those classes are in, at its next platform start.",[14,75,76,77,53],{},"What a disconnect costs is set out in full in ",[49,78,80],{"href":79},"\u002Fbyodt-cloud\u002Fcloud#disconnecting","Disconnecting",[82,83,85],"h3",{"id":84},"and-putting-the-files-back-is-not-proof","And putting the files back is not proof",[14,87,88],{},"What protects a module is loading healthily, not being present on disk. The startup sweep builds its keep-list from the modules that loaded, so a directory that is there and fails to load is not skipped — it is invisible to the keep-list and goes with its classes. Verify every module came back healthy, because a silent load failure looks exactly like success until the classes are gone.",[24,90,92],{"id":91},"one-precondition-on-all-of-it","One precondition on all of it",[14,94,95],{},"The new team's edition has to cover at least what the deployment mounts today. Anything it does not cover cannot be re-mounted, and goes the same way: its classes, and every relationship they are in, at the next platform start.",[21,97],{},[24,99,101],{"id":100},"related","Related",[103,104,105,112,119],"ul",{},[35,106,107,111],{},[49,108,110],{"href":109},"\u002Fbyodt-subscription\u002Fyour-subscription","Your subscription"," — subscribing, and where your deployment's values are on the portal.",[35,113,114,118],{},[49,115,117],{"href":116},"\u002Fbyodt-cloud\u002Fcloud#check-the-connection","Check the connection"," — three checks for a deployment once it is connected to the team.",[35,120,121,125],{},[49,122,124],{"href":123},"\u002Fbyodt-cloud\u002Fcloud#changing-who-may-sign-in","Changing who may sign in"," — narrowing a connected deployment to some of the team's members.",{"title":127,"searchDepth":128,"depth":128,"links":129},"",3,[130,132,135,136],{"id":26,"depth":131,"text":27},2,{"id":69,"depth":131,"text":70,"children":133},[134],{"id":84,"depth":128,"text":85},{"id":91,"depth":131,"text":92},{"id":100,"depth":131,"text":101},"What to do with the deployment you already run once you buy a team edition: three ways forward, best first","md",{"category":140,"position":128,"tags":141},"documentation",[142,143,144,145,146],"byodt","subscription","team","deployment","migration",true,"\u002Fbyodt-subscription\u002Fmoving-a-deployment-to-a-new-team",{"title":5,"description":137},"08.byodt-subscription\u002F02.moving-a-deployment-to-a-new-team","uwJAfZIJ-QvQr4crIEsx4z-fVQs9j7-FmeE_oMiLlRk",[153,208,243,298,332,376,391,461],{"title":154,"description":155,"path":156,"stem":157,"children":158,"page":-1},"Platform","Modelling, analysis, findings and controls in the Dethernety platform.","\u002Fplatform","01.platform",[159,163,168,173,178,183,188,193,198,203],{"title":160,"path":156,"stem":161,"description":162},"Dethernety User Documentation","01.platform\u002Findex","User guide for the Dethernety threat modeling platform",{"title":164,"path":165,"stem":166,"description":167},"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":169,"path":170,"stem":171,"description":172},"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":174,"path":175,"stem":176,"description":177},"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":179,"path":180,"stem":181,"description":182},"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":184,"path":185,"stem":186,"description":187},"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":189,"path":190,"stem":191,"description":192},"Issue Management Guide","\u002Fplatform\u002Fissue-management-guide","01.platform\u002F06.issue-management-guide","Issue tracking, filtering, and management in Dethernety.",{"title":194,"path":195,"stem":196,"description":197},"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":199,"path":200,"stem":201,"description":202},"Understanding Modules","\u002Fplatform\u002Funderstanding-modules","01.platform\u002F08.understanding-modules","How Dethernety's module system extends your threat modeling capabilities.",{"title":204,"path":205,"stem":206,"description":207},"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":209,"description":210,"path":211,"stem":212,"children":213,"page":-1},"BYODt cloud","Deploying the platform yourself and connecting it to the BYODt cloud.","\u002Fbyodt-cloud","02.byodt-cloud",[214,218,223,228,233,238],{"title":215,"path":211,"stem":216,"description":217},"BYODt Deployment","02.byodt-cloud\u002Findex","Run Dethernety on your own machine: install, configure, operate, and recover",{"title":219,"path":220,"stem":221,"description":222},"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":224,"path":225,"stem":226,"description":227},"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":229,"path":230,"stem":231,"description":232},"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":234,"path":235,"stem":236,"description":237},"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":239,"path":240,"stem":241,"description":242},"Troubleshooting the BYODt Deployment","\u002Fbyodt-cloud\u002Ftroubleshooting","02.byodt-cloud\u002F05.troubleshooting","Symptom, cause, and fix for the failures this deployment reports",{"title":244,"description":245,"path":246,"stem":247,"children":248,"page":-1},"Dethereal","The Claude Code plugin: build a threat model in conversation and publish it to the platform.","\u002Fdethereal","03.dethereal",[249,253,258,263,268,273,278,283,288,293],{"title":250,"path":246,"stem":251,"description":252},"Dethereal — Claude Code Plugin for Threat Modeling","03.dethereal\u002Findex","Comprehensive documentation for the Dethereal threat modeling plugin",{"title":254,"path":255,"stem":256,"description":257},"Getting Started with Dethereal","\u002Fdethereal\u002Fgetting-started","03.dethereal\u002F01.getting-started","Install the plugin, authenticate, and create your first threat model",{"title":259,"path":260,"stem":261,"description":262},"The 11-Step Guided Workflow","\u002Fdethereal\u002Fguided-workflow","03.dethereal\u002F02.guided-workflow","Complete walkthrough of the \u002Fdethereal:threat-model guided process",{"title":264,"path":265,"stem":266,"description":267},"Command Reference","\u002Fdethereal\u002Fcommand-reference","03.dethereal\u002F03.command-reference","Complete reference for all 14 Dethereal slash commands",{"title":269,"path":270,"stem":271,"description":272},"Threat Model Concepts","\u002Fdethereal\u002Fmodel-concepts","03.dethereal\u002F04.model-concepts","Components, boundaries, data flows, classes, attributes, and quality scoring",{"title":274,"path":275,"stem":276,"description":277},"Discovery and Enrichment","\u002Fdethereal\u002Fdiscovery-and-enrichment","03.dethereal\u002F05.discovery-and-enrichment","Infrastructure scanning, security attributes, MITRE ATT&CK, credentials, and compliance",{"title":279,"path":280,"stem":281,"description":282},"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":284,"path":285,"stem":286,"description":287},"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":289,"path":290,"stem":291,"description":292},"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":294,"path":295,"stem":296,"description":297},"Dethereal Glossary","\u002Fdethereal\u002Fglossary","03.dethereal\u002F09.glossary","Definitions for Dethereal-specific terminology",{"title":299,"description":300,"path":301,"stem":302,"children":303,"page":-1},"Threat Report","The residual-risk report over a threat model: reading it, filtering it and exporting it.","\u002Fthreat-report","04.threat-report",[304,307,312,317,322,327],{"title":299,"path":301,"stem":305,"description":306},"04.threat-report\u002Findex","Read, filter, drill into, and export a residual-risk report over a threat model",{"title":308,"path":309,"stem":310,"description":311},"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":313,"path":314,"stem":315,"description":316},"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":318,"path":319,"stem":320,"description":321},"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":323,"path":324,"stem":325,"description":326},"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":328,"path":329,"stem":330,"description":331},"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":333,"description":334,"path":335,"stem":336,"children":337,"page":-1},"Risk assessment","The risk assessment module: the register, the reports and the method behind them.","\u002Frisk-assessment","05.risk-assessment",[338,342,347,352,357,362,366,371],{"title":339,"path":335,"stem":340,"description":341},"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":343,"path":344,"stem":345,"description":346},"FAQ and Troubleshooting","\u002Frisk-assessment\u002Ffaq","05.risk-assessment\u002F01.faq","Short answers to the questions analysts, risk managers, and compliance officers ask most often about the Risk Assessment. Each answer links to the guide that covers it in full.",{"title":348,"path":349,"stem":350,"description":351},"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":353,"path":354,"stem":355,"description":356},"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":358,"path":359,"stem":360,"description":361},"Methodology and Trust","\u002Frisk-assessment\u002Fmethodology-and-trust","05.risk-assessment\u002F04.methodology-and-trust","Every number in a Risk Assessment is meant to survive scrutiny. This chapter explains why you can trust the report and — just as importantly — what it deliberately declines to claim, so you can put it in front of your board, a regulator, or an external auditor and defend every line.",{"title":313,"path":363,"stem":364,"description":365},"\u002Frisk-assessment\u002Freading-the-report","05.risk-assessment\u002F05.reading-the-report","The Risk Assessment turns your threat model into a single, scannable draft risk report: an executive summary at the top and a set of analytical tabs below it. This guide explains how to read what you see — what a matrix cell means, how coverage is stated, what a severity band is (and is not), and how to interpret each tab.",{"title":367,"path":368,"stem":369,"description":370},"Stakeholder Reports and Exports","\u002Frisk-assessment\u002Fstakeholder-reports","05.risk-assessment\u002F06.stakeholder-reports","One assessment produces reporting for every audience you answer to. From a single generated Risk Assessment you can hand your board a one-page brief, give your risk committee the full reconciliation, keep the complete technical detail for your own team, and export the underlying data into your GRC tool — without ever re-running anything or reconciling one document against another.",{"title":372,"path":373,"stem":374,"description":375},"The Risk Register","\u002Frisk-assessment\u002Fthe-risk-register","05.risk-assessment\u002F07.the-risk-register","The Risk Register is where your team records and manages the real risks your organisation is carrying — on top of, but separate from, what the analysis computed for you. Each entry is written by a person: a plain-language risk statement, your own assessment of how likely it is and how much it would hurt, the findings and elements from the analysis that back it up, a treatment decision, an owner, a review date, and a reference handle you can quote in a ticket or a board pack.",{"title":377,"description":378,"path":379,"stem":380,"children":381,"page":-1},"Threat Patterns","The Threat Patterns module and its modelling checklist.","\u002Fthreat-patterns","06.threat-patterns",[382,386],{"title":383,"path":379,"stem":384,"description":385},"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":387,"path":388,"stem":389,"description":390},"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":392,"description":393,"path":394,"stem":395,"children":396,"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",[397,401,406,411,416,421,426,431,436,441,446,451,456],{"title":398,"path":394,"stem":399,"description":400},"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":402,"path":403,"stem":404,"description":405},"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":407,"path":408,"stem":409,"description":410},"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":412,"path":413,"stem":414,"description":415},"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":417,"path":418,"stem":419,"description":420},"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":422,"path":423,"stem":424,"description":425},"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":427,"path":428,"stem":429,"description":430},"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":432,"path":433,"stem":434,"description":435},"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":437,"path":438,"stem":439,"description":440},"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":442,"path":443,"stem":444,"description":445},"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":447,"path":448,"stem":449,"description":450},"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":452,"path":453,"stem":454,"description":455},"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":457,"path":458,"stem":459,"description":460},"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":462,"description":463,"path":464,"stem":465,"children":466,"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",[467,471,475],{"title":468,"path":464,"stem":469,"description":470},"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":472,"path":109,"stem":473,"description":474},"Your Subscription","08.byodt-subscription\u002F01.your-subscription","Create an account, subscribe by card, and find the values your deployment needs on the portal",{"title":5,"path":148,"stem":150,"description":137},1793748186287]