This article is aimed at pilots who wish to integrate a large volume of data into Tenacy without entering it one by one: audit results, metric history, complete organization, etc. It lists the different types of bulk import available in the solution and presents the public API as an alternative for recurring or automated needs.
💡 Every bulk import in Tenacy follows the same principle: download the Excel template provided by the solution (with an "Instructions" tab), complete it, then reimport it. Using the template is essential to ensure that the columns and identifiers are correct.
⚠️ After an import, you can check that it went smoothly (and view any errors) in ⚙️ > Reports or Logs.
Importing your organization, its properties, and its contacts
You can bulk import and export the perimeters and groups of your organization, as well as their custom properties and contacts, from the Organization module.
🔎 For the complete procedure on importing properties and contacts, see Importing and exporting perimeter properties and contacts.
Importing implemented measures into the security baseline
This import allows you to bulk instantiate security measures as implemented on a perimeter. It is the recommended method for quickly initializing the existing security baseline of a new perimeter, without declaring each measure one by one.
Go to the Security Baselines module, click "All measures" or select the relevant policy, then click on the relevant perimeter.
Click the three-dot button, then "Import operated measures (XLS)."
Click "Download import template" to retrieve the Excel file, then complete it following the "Instructions" sheet.
Select the completed file and click "Import."
💡 Once the import is complete, the measures appear as implemented in the perimeter's baseline, and your compliance score and Trusted Score are updated immediately.
Importing recurring tasks
A recurring task is a periodic check associated with a security measure, which ensures that it remains operational over time (unlike an action, which has an end date and an implementation objective). You can bulk import recurring tasks to quickly instantiate them on your measures, without creating them one by one.
⚠️ The relevant security measure must already be implemented (or a beneficiary) in the perimeter's baseline before a recurring task can be attached to it.
Go to the Recurring Tasks module, and create a recurring task register if necessary ("Add a register").
In the relevant register, click the arrow then select "XLS Import" to download the import template.
Complete the file following the mandatory elements indicated in the "Instructions" sheet.
Return to the register and click "XLS Import" again to import the completed file.
💡 Once imported, the recurring tasks are instantiated on their measure: they generate occurrences at each period according to the defined frequency, and contribute to the operational performance score of the measure. You can view them both from the security baseline and from the recurring task register.
Importing gaps
You can bulk import a list of gaps into an existing gap register, for example to directly integrate the findings of an audit or a penetration test.
⚠️ A gap register must already exist before gaps can be imported into it.
Create the remediation actions upstream in the corresponding action plan (recommended). Note the identifiers of these actions: they will allow you to link them to the gaps in the import file. This step can be skipped if you prefer to link actions to gaps manually after the import.
In the target gap register, click the arrow then "Import XLS," then "Download template."
Complete the file with one line per gap: title, description, criticality, gap group (optional), relevant perimeter, violated requirement (optional), and identifiers of the remediation actions to link.
Select the completed file, click "Import XLS" then "Import."
Importing exemptions
You can bulk import a list of exemptions into an existing exemption register.
⚠️ An exemption register must already exist before exemptions can be imported into it.
In the target exemption register, click the arrow then "Import XLS," then "Download template."
Complete the file with one line per exemption: relevant requirement, perimeter, justification, start and end dates of validity.
Select the completed file, click "Import XLS" then "Import."
Importing incidents
You can bulk import a list of incidents.
In the Incidents module, click the arrow then "Import XLS," then "Download template."
Complete the file with one line per incident: title, detection date, severity, impacted perimeters.
Select the completed file, click "Import XLS" then "Import."
Importing projects
You can bulk import a list of projects.
In the Projects module, click the arrow then "Import XLS," then "Download template."
Complete the file with one line per project: name, associated perimeter, lifecycle phase.
Select the completed file, click "Import XLS" then "Import."
Importing actions
You can bulk import actions into an existing action plan, for example to quickly integrate the results of an audit or a list of fixes.
⚠️ Action imports are done register by register. The import only feeds one register at a time.
Importing risks
You can bulk import a list of risks into a risk register, for example following a risk analysis carried out outside of Tenacy.
🔎 For the complete procedure, see Importing and exporting risks.
Importing operational indicators
You can bulk import indicators, whether they are reusable templates or indicators already instantiated on a perimeter.
🔎 For the complete procedure, see Importing operational indicators.
Importing metrics
You can bulk import metrics and their value history, which is in particular mandatory for entering the very first value of a newly created metric.
🔎 For the complete procedure, see Creating or importing a metric and Entering a metric.
Importing campaigns and assessment results
You can bulk import several assessment campaigns at once, as well as the results of an already created assessment campaign.
🔎 For the complete procedure, see Importing and exporting campaigns and assessment results.
The public API: an alternative for automated integrations
The XLS imports described above are suited to one-off or semi-regular operations carried out manually in the interface. If you need to synchronize data between Tenacy and a third-party tool on a recurring or automated basis (for example a risk analysis tool, a CMDB, or your own script), Tenacy's public API is the preferred alternative.
To use the API, you must first create an API key from ⚙️ > Public API.
🔎 To find out how to create and manage your API keys, see Creating and managing an API key.
Frequently asked questions
Do I need to use the Excel template provided by Tenacy for each import? Yes. Each import has its own expected columns and identifiers; using the provided template (or the export of an existing register) greatly reduces the risk of error.
How do I know if my import was successful? Go to ⚙️ > Reports to view the result of your imports and any lines with errors.
Can I import measures directly as "being implemented" rather than as "implemented"? The bulk import of operated measures declares them as implemented. For a measure being implemented (with an ongoing implementation action), you must go through the manual declaration from the security baseline.
Can I import a recurring task onto a non-implemented measure? No. The measure must already be implemented (or a beneficiary) on the relevant perimeter before a recurring task can be attached to it, whether imported or created manually.
Can I link my imported gaps to remediation actions that do not yet exist? No, the action identifiers entered in the import file must correspond to already created actions. Create your remediation actions before the import, or link them manually to the gaps once the import is complete.
When should I prefer the API over an XLS import? XLS import is suited to one-off manual operations. The API is preferable whenever you need recurring or automated synchronization with a third-party tool.