CISO Assistant
  • 👋Welcome to CISO Assistant
  • Guide
    • Installation
    • Understanding decoupling
    • General tips
    • Journeys
    • 🏗️Creating your first perimeter
    • ✅Creating your first Audit
    • 📊Creating your first risk assessment
    • 🔎Overview
    • 🧰Extra tools
    • 🌐External resources
    • Understand mapping
    • Glossary
    • Data import wizard
  • Features highlight
    • Controls autosuggestion
    • Multi-level support
    • Flash mode
    • Evidences from clipboard
    • Library upgrade
    • Mapping explorer
    • SSO
      • Microsoft Entra ID
      • Okta
      • Keycloak
      • Google Workplace
    • Setting up Multi-Factor Authentication (MFA)
  • Model
    • 📁Organization
      • Add and manage users
      • User Groups
    • ⚙️Context
    • 🏛️Governance
    • 💣Risk
    • 📋Compliance
  • Deployment
    • Prerequisites
    • Local
    • Remote/Virtualization
    • Deploy on a VPS
    • Frequent questions
    • Setting up mailer
    • Updating your local instance
    • Helm Chart
    • Special cases
    • Upgrading a library
  • ✨Customization
    • Getting your custom framework
    • CIS Controls
    • Changing the language
  • Contributing
    • Internationalization
      • Translating the interface
    • Submit a library
  • Academy
    • Overview
    • Third Parties Risk Management
    • Etude EBIOS RM
Powered by GitBook

Community

  • Github
  • Discord

intuitem

  • Home
  • SaaS trial

© intuitem, 2018-2024

On this page
  • Overview
  • 📦 Assets
  • Template
  • Supported fields
  • Special considerations
  • ⚙️ Applied controls
  • Template
  • Supported fields
  • Special considerations
  • 📦 Perimeters
  • 📃 Audits
  • Template
  • Supported fields
  • Special considerations
  • Findings followup (eg. pentest)
  • Template
  • Users

Was this helpful?

Export as PDF
  1. Guide

Data import wizard

[Pro] guidelines on data import format

PreviousGlossaryNextControls autosuggestion

Last updated 18 days ago

Was this helpful?

Overview

If the object supports the domain column, the wizard will attempt to add the object to it, given you have the permission to do so. If the domain is not set, the wizard will default to the fallback domain set on the wizard form.

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

📦 Assets

Template

Supported fields

  • ref_id

  • name*

  • description

  • domain

  • type

    • PR : primary

    • SP : supporting

Special considerations

  • type will default to supporting if not set

⚙️ Applied controls

Template

Supported fields

  • ref_id

  • name*

  • description

  • domain

  • status

    • to_do

    • in_progress

    • on_hold

    • active

    • deprecated

  • category

    • policy

    • process

    • technical

    • physical

    • procedure

  • priority

    • integer from 1 to 4

  • csf_function

    • govern

    • identify

    • protect

    • detect

    • respond

    • recover

Special considerations

  • status will default to to_do

  • csf_function will default to govern

📦 Perimeters

Template

Supported fields

  • ref_id

  • name*

  • description

  • domain

  • status

    • undefined

    • in_design

    • in_dev

    • in_prod

    • eol

    • dropped

📃 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

  • description

  • compliance_result

    • not_assessed

    • partially_compliant

    • non_compliant

    • compliant

    • not_applicable

  • requirement_progress

    • to_do

    • in_progress

    • in_review

    • done

  • score

    • integer from 0 to 100

  • observations

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.

  • Unassessable rows are skipped.

Findings followup (eg. pentest)

Template

Supported fields

  • ref_id

  • name*

  • description

  • severity

    • low

    • medium

    • high

    • critical

  • status

    • identified

    • confirmed

    • dismissed

    • assigned

    • in_progress

    • mitigated

    • resolved

    • deprecated

Users

Supported fields

  • email

  • first_name

  • last_name

9KB
sample001.xlsx
9KB
sample002.xlsx
9KB
sample003.xlsx
9KB
sample004.xlsx
9KB
sample005.xlsx