π₯Data Import Wizard
[Pro] guidelines on data import format
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: primarySP: supporting
Special considerations
type will default to
supportingif not set
βοΈ Applied controls
Template
Supported fields
ref_id
name*
description
domain
status
to_doin_progresson_holdactivedeprecated
category
policyprocesstechnicalphysicalprocedure
priority
integer from
1 to 4
csf_function
governidentifyprotectdetectrespondrecover
Special considerations
status will default to
to_docsf_function will default to
govern
π¦ Perimeters
Template
Supported fields
ref_id
name*
description
domain
status
undefinedin_designin_devin_prodeoldropped
π 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_assessedpartially_compliantnon_compliantcompliantnot_applicable
requirement_progress
to_doin_progressin_reviewdone
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
lowmediumhighcritical
status
identifiedconfirmeddismissedassignedin_progressmitigatedresolveddeprecated