Export

Export your threat models for sharing, review, or compliance documentation.

Formats

Format Content Best for
Report (HTML) Full stakeholder report: model structure, controls with implementation status, assurance summary, compliance coverage, risk tiers Sharing with stakeholders, GRC, CISOs — opens in any browser
PDF Same rich report as HTML, rendered as PDF Printing, archiving, email attachments
CSV Raw model structure (assets, attackers, COs, assumptions) Importing into spreadsheets, data analysis, tooling
Audit archive (JSON) Self-contained envelope of the model's current state: the latest version and its controls, live assertions with the CI runs behind their Tier 1/Tier 2 statuses, decisions in force, findings, and instance sufficiency signatures Audit retention, cross-instance portability, independent signature verification

How to export

  1. Go to the Models page or Assurance Dashboard
  2. Select a model
  3. Click Report (HTML), PDF, CSV, or Audit archive

The Report and PDF formats include the enriched report: trust boundaries, assets, attackers, control objectives, implementation controls with traffic-light status, assurance summary, risk tier breakdown, verification status, and compliance coverage (if a framework is selected). Whether a delegation to another model's control credits its objective depends on that model's controls, so a single model's export shows the delegation, not the provider's proof. Manual attestations are preserved.

The CSV format includes the raw model structure: trust boundaries, assets (with security properties), attackers, control objectives, and assumptions.

Audit archive (JSON)

The audit archive is a self-contained JSON envelope carrying the model's current state and the evidence an auditor needs to re-verify every current "verified implemented" claim — without needing access to the origin Mipiti instance. History (earlier versions, past changes to the controls, activity) stays on the platform; export again whenever you need a newer snapshot.

What it contains:

Independently verifiable:

Tampering with any signed field — flipping a Tier 1/Tier 2 verdict, mutating an assertion's parameters, adding or removing assertions after signing — invalidates the relevant signature on verify.

Importing an archive

Another Mipiti instance (or the same one) can import the archive via the Import audit archive button on the Models page. It becomes version 1 of a new model under a fresh model_id, so the same envelope can be imported any number of times. Title collisions in the target workspace auto-suffix (imported YYYY-MM-DD) — you can rename afterwards.

The archive's verdicts and signatures are shown as the origin's claims, never as judgements made here, and an import starts no judging: the imported model reads as awaiting judgement, and the import shows an estimate of judging it. Judge it from the model page when you choose to.

Via MCP, use export_threat_model_archive / import_threat_model_archive.

Viewing and verifying a sufficiency signature

On the Assurance tab, any control with an evaluated sufficiency verdict shows a small padlock next to its status badge. Click it to open the signature modal, which shows:

Tag export

For a report that spans several models, put them in a tag and use Export on the tag's page. It downloads a signed HTML report: the delegations among the members, each with its status and whether it credits its objective, followed by every member model's full report. This is the auditor artifact for a product or an audit scope.

Jira export

For Jira integration, use the dedicated "Export to Jira" button instead. This creates structured Jira issues rather than a flat document export. Each Jira issue includes mitigation group information in the description to show which controls are alternatives and which are defense-in-depth. See the Integrations section for details.