Enabling Import from Devici

Enabling Import from Devici is a single action: an SD Elements administrator turns on the Import from Devici feature flag in Manage Features. The flag is system-wide. Once enabled, the import surface appears on every project in the tenant — both at project creation and on existing projects.

There is no per-project toggle, no Devici workspace credential to configure, and no network connection from SD Elements to Devici to set up. Import from Devici is a file-based import flow — users upload an OTM file exported from Devici.

Enabling the Import from Devici feature flag

Performed once per SD Elements tenant by an SD Elements administrator with the Manage Features permission.

Steps:

  1. Open the menu option Manage Features.

  2. Locate Import from Devici in the feature list.

  3. Toggle Import from Devici to On.

  4. Click Save.

The change takes effect immediately. No restart is required, and existing projects are not modified — only the availability of the import surface changes.

Import from Devici is off by default on all SD Elements tenants when you upgrade to 2026.6.1. Existing survey-driven projects are unaffected at upgrade. The flag must be enabled before the import surface becomes available to users.

What appears after the flag is enabled

Once Import from Devici is on, the import surface appears in two places:

Surface What appears

Get Started Modal on the project

When a user opens a new or empty project, the Get Started Modal gains an additional setup option — Import from a Devici file — alongside the standard survey-based setup. Choosing it sets up the project by populating its attribute pool from the uploaded OTM file and generating Countermeasures from those attributes.

Devici tab on an existing project

Every project gains a new Devici tab in the project navigation. From the Devici tab, a user can upload an OTM file to add Devici-sourced architecture to a project that was previously survey-driven, or to re-import an updated model into a project that was previously imported from Devici. The Devici tab is also where the embedded Devici diagram appears once a model has been imported.

See Importing into SD Elements for the import procedure at each entry point.

The Devici tab appears on every project in the tenant once the flag is enabled — including projects that have never had a Devici file imported. On a project with no imported model, the tab shows a prompt to upload an OTM file. This is the canonical entry point for adding a Devici threat model to an existing project after the fact.

Disabling the Import from Devici feature flag

To disable the import surface system-wide:

Steps:

  1. Open the menu option Settings → Manage Features.

  2. Locate Import from Devici in the feature list.

  3. Toggle Import from Devici to Off.

  4. Click Save.

The Import from a Devici file option is removed from the Get Started Modal on all projects. The Devici tab on existing projects is hidden. Previously imported attributes, generated Countermeasures, embedded diagrams, and pushed tracker tickets are retained on the projects where they were imported.

Disabling the flag does not delete any previously imported data. It only hides the import surface. To remove imported content from a specific project, see Removing imported Devici content below.

Removing imported Devici content from a project

To delete everything an Import from Devici operation wrote to a single project — the imported attributes, the Countermeasures generated from them, and the embedded diagram:

Steps:

  1. Open the project from Applications → [Application] → [Project].

  2. Click the Devici tab.

  3. Click Remove Devici Content. A confirmation dialog opens listing the number of imported attributes and generated Countermeasures that will be deleted.

  4. Type the project name to confirm.

  5. Click Delete.

Remove Devici Content deletes:

  • Every attribute that was added to the project’s attribute pool by a Devici import.

  • Every Library Countermeasure that was generated from those attributes (including any that have been transitioned manually in tracker).

  • Every custom Countermeasure tagged devici that was created for a custom Devici mitigation.

  • The embedded Devici diagram on the Devici tab.

Manually-set attributes, survey-driven attributes, survey-driven Countermeasures, manually-added custom Countermeasures, and any Components on the project are not affected. Tracker tickets in Jira / GitHub / Azure DevOps are not deleted — they remain in your tracker with their last known state and become orphaned references. This action cannot be undone.

results matching ""

    No results matching ""