Data import wizard

Applicable for: Data import wizard (Pro) and CLI (Community and Pro)

Overview

The Data Import Wizard and the CLI both support batch creation and updates of fields. They provide the same capabilities; the only difference lies in how the import is initiated:

• through the user interface for the Data Import Wizard

• through the command line for the CLI

When an object already exists during an import, one of the following conflict-resolution strategies can be applied:

• Stop the import (default): the import is aborted as soon as a conflict is detected

• Skip the row: the existing field is left unchanged and the import continues

• Update the row: the existing field is updated with the imported data

The Update strategy enables batch updates of existing fields and is particularly useful for changes that could technically be performed through the graphical interface, but become tedious or error-prone when repeated across many objects. In such cases, downloading the existing objects, applying the required transformations in an Excel file, and re-importing the updated data can be significantly faster and more reliable than performing the same actions manually in the UI. This approach reduces repetitive interactions, minimizes the risk of manual mistakes, and provides a clear, auditable workflow for large-scale updates.

In this workflow, it is strongly recommended to retain the field IDs (UUIDs) in the import schema. Doing so ensures reliable object matching during re-import, even if other attributes (such as names or labels) have changed, making the update process fail-safe.

If the imported object supports the domain attribute, the wizard will attempt to assign it to the specified domain, provided you have the required permissions. If no domain is specified, the wizard will automatically fall back to the default domain configured in the wizard form.

Fields with (*) are mandatory and don't have any supported fallback.

Unless marked as mandatory, ref_id fields can be left blank but the column must still exist.

📦 Assets

Template

Supported fields

• ref_id

• name*

• description

• domain

Special considerations

• type will default to supporting if the column does not exist

⚙️ Applied controls

Template

Supported fields

• ref_id

• name*

• description

• domain

Special considerations

• status will default to to_do

• csf_function will default to govern

📦 Perimeters

Template

Supported fields

• ref_id

• name*

• description

• domain

📃 Audits

Template

To avoid any mixup on the expected fields and the requirements reference, you can get a template for the expected framework by going into Catalog/Frameworks

The framework needs to be loaded and when clicking on it, you'll see a button to get the excel file.

Supported fields

• urn*

• assessable

• ref_id*

• name

Special considerations

• The wizard will attempt to match based on the ref_id and fallback to the urn otherwise. If none could be used, the row will be skipped.

• name and description columns are not used but serve as an anchor point for reference.

• Assessable will fallback to false

🐞 Findings followup (eg. pentest)

Template

Supported fields

• ref_id

• name*

• description

• severity

👥 Users

Template

Supported fields

• email*

• first_name

• last_name

☣️ Risk assessment

The risk assessment is an advanced object that needs special considerations. Make sure to pick the matrix that will be used to map your labels to the values on CISO Assistant. If you have a specific matrix, you should start by including it as a custom library.

inherent_level, current_level and residual_level are kept on the excel sample just for visual aid. The application computes them based on impact and probability to ensure consistency with the matrix definition.

Controls are created on picked based on the perimeter's domain. Line breaks are used as seperator.

Template:

Supported fields:

• ref_id

• name*

• description

• inherent_impact

⚙️ Elementary actions

Elementary actions are useful to model a killchain during the 4th workshop of an EBIOS RM study.

Supported fields:

• ref_id

• name*

• description

• attack_stage*

Reference controls

Reference controls are templates of the controls to apply.

Supported fields:

• ref_id

• name

• description

• category

Reference controls can be bundled also as a library.

Threats

• ref_id

• name

• description

• domain

Third parties ecosystems

Adding entities, solutions and contracts go through the same file to be able to keep consistent relationships. Each concept needs to be on a separate tab of the excel sheet.

The file has to be divided into 3 sheets namely "Entities", "Solutions" and "Contracts"

Supported fields

*: Required fields

Entities

• ref_id

• name *

• description

Solutions

• ref_id

• name *

• description

Contracts

• ref_id

• name *

• description

Processings

Template

Supported fields

• internal_id

• ref_id

• name*

• description

Policies

Supported fields

• ref_id

• name

• description

• domain

Exceptions

Supported fields

• ref_id

• name

• description

• domain

Incidents

Supported fields

• ref_id

• name

• description

• domain