Skip to main content

Import findings into the Cye platform from external sources

Import findings from other systems into the Cye platform by uploading your own data or using the optional import template.

Overview

Structured import brings findings from systems that are not integrated with the Cye platform, such as scanner exports and risk registers, into an engagement from a CSV file. You fill in the template or map your own file's columns, confirm the count, and the platform adds new findings and updates existing ones.

There is no editing step during import. To change a value, edit the file before you upload it, or edit the finding in the platform after import. Rows that fail come back as a spreadsheet you can fix and upload again.

There is no undo after import. Once findings are committed, the Cye platform has no undo. Check the count on Review & confirm before you click Execute Import.

Prerequisites

Before you start, make sure the following is in place:

  • User access to the Cye platform

  • Admin permissions in the Cye platform (at either the platform or engagement level)

Note: Findings must always be imported into a specific engagement. You won’t be able to complete the import unless you have the right access at that level.

  • One or more findings to import from another system

  • A basic understanding of NIST maturity framework terms (for filling in the NIST-related template fields)

Prepare your file

You can fill in the Cye platform template or use your own spreadsheet. Either way, use the platform's permitted values. Differences in capitalization and spacing are forgiven; misspellings are not.

  • Download the template: Click Download template on the Upload file screen. It already contains the exact field names the platform expects, so its columns map automatically.

  • Row 2 is guidance: It explains how to complete each field. Delete it before you upload; if you leave it in, it appears as a failed row in the summary, but it does not block the import.

  • Mandatory fields: Finding name, Severity, Summary, and at least one NIST CSF ID in v1.1 or v2.0. A row with a missing or unrecognized value in any of these is not imported.

  • List values: For fields with a fixed set of values, such as Severity, Status, or Security Domain, capitalization and extra spaces don't matter. high, HIGH, and High all import as High, stored in the platform's own spelling. Misspellings are not corrected: critcal is not Critical.

  • Optional fields never fail a row: If an optional field holds a value the platform can't recognize, such as a misspelled Status or a Probability outside 1 to 100, that value is skipped and the finding imports with the field empty.

  • Multiple values: For fields that allow several values, such as NIST CSF, separate them with a semicolon and no space, for example PR.AA-01;PR.AA-05.

  • Probability: Optional, 1 to 100. Required for the finding to appear in the Org Attack Graph.

  • NIST fields: Enter values in either v1.1 or v2.0; the platform fills in the other version. Security Domain is filled in from your NIST values.

  • Accepted values: The full list of fields and formats is in the Import Template Fields Reference.

Import findings, step by step

1. Upload file

  • Open the import: Go to Operations → Findings and click Import.

  • Select the engagement: Choose the target Engagement. Findings are imported into that engagement.

  • Add the file: Drag and drop it, or click Choose a file. CSV, up to 50 MB and up to 500 findings.

  • Check the details: The File uploaded card shows the file name, type, size, and upload time. Click Next to continue, or replace file to choose a different one.

Processing

The platform processes the file in the background after you click Next, and again after you execute the import.

  • What you see: A Processing screen with the file name, size, and upload date.

  • Keep working: You can leave this page. The status widget in the corner shows Import in progress, then a button to the next step when processing is done.

  • If processing fails: The widget shows Import failed with the reason. Click Replace file to return to the upload step.

  • Cancel at any step: Click Cancel. The file and your column mapping are discarded, and you return to the upload step.

2. Map columns

The mapping screen aligns your file's columns with the Cye platform's fields. Columns whose names match a platform field exactly are mapped for you.

  • Layout: On the left, your file's columns, each with a data sample. On the right, a dropdown of Cye platform fields, each with an example value.

  • Your job: Choose the platform field for every column that wasn't matched automatically, then click Next.

Helpful hints while mapping:

  • Mandatory fields are marked with a red asterisk in the dropdown. You must map these before continuing:

  • You’ll also see a red message below the table reminding you if any required fields are still unmapped:

  • The Cye platform previews data samples to help you make decisions:

  • Example values show expected formats (e.g., for severity: “Low” instead of “82”):

Tip: the Cye platform automatically maps columns when their names match exactly (e.g., "Status" to "Status"). This auto-mapping is case-insensitive but doesn’t handle typos or synonyms (e.g., "Likelihood" won’t match "Probability").

Using the the Cye platform template can make this process easier, since it already includes the exact field names the Cye platform expects.

Save your column mapping (optional but recommended)

If you’ve spent time mapping 10, 15, or more fields, you probably don’t want to do that every time.

Here’s how to save a reusable template:

  • Check the box labeled Save Column Mapping in the bottom-left corner of the screen (footer):

  • Enter a name for your template:

  • Click Save Column Mapping:

Error scenarios you might see:

  • Server error: You’ll get a message asking you to try again.

  • Duplicate name: You’ll be prompted to pick a different name (the Cye platform won’t overwrite existing ones).

Load a previously saved mapping

When you upload a new file, you can reuse a column mapping template you saved earlier:

  • Click the small arrow in the Select template dropdown at the top right.

  • Choose the template you want to apply from the list.

This automatically fills in the column mappings based on what you previously configured.

  • The Cye platform will try to match the column names from your current file with what you saved, And you will see the following confirmation message:

If some matches are missing (e.g., a new column or one with a different name), the Cye platform will show only what it recognizes. Partial matches are okay — you can map the rest manually.

Manage your saved templates

From the Manage Template menu, you can:

  • Rename a template

  • Delete a template

Important: Changes here apply to everyone in your company using the Cye platform. If someone deletes or renames a template, it disappears for all users.

Templates cannot be edited directly. If you want to update the mappings, load the template, adjust the fields, and then save it again under a new name.

3. Review & confirm

  • Count: The screen shows Findings: N ready to import.

  • Existing findings: A note reminds you that findings which already exist in the platform are updated with your file's values.

  • No row-level review: This screen has no table, no editing, and no per-row status.

  • Execute: Click Execute Import. Processing runs again, and the status widget shows View summary when the import is done.

⚠️ Critical: Imports are permanent. The Cye platform cannot roll back findings once the import is executed. Check the count before you click Execute Import.

4. View summary

  • Results: The summary shows how many findings were imported (new and updated) and how many failed.

  • Fix failed rows: Click the download icon on the failed row to get a spreadsheet of the rows with errors. Correct them and upload that file again. You do not need to redo the whole import.

  • Why rows fail: A mandatory field is missing or holds a value the platform doesn't recognize. Optional fields never fail a row. A finding that already exists in Restricted Share Mode without your access also fails; contact the finding's owner, or rename your finding to make it unique.

  • What the errors list tells you: Each failed row names the field, the value you entered, and the accepted values. When your value is close to one of them, the list suggests it, for example Severity: "critcal" is not one of critical, high, medium, low, informative. Did you mean "critical"? The suggestion is not applied for you; correct the value in the file.

  • Open the results: Click the open icon on the imported row to see the Findings page filtered to this import.

  • Finish: Close ends the import session. Upload another file returns to the upload step.

  • Come back later: The summary stays available for about 30 hours, or until you click Close. Reopen it from the status widget (View summary) or by returning to Import.

Finding imported findings later

  • Import tag: Every imported finding carries a tag made of the file name and the import date and time, in the format <file name> DDMMYY HHMM. Long file names are cut to fit; hover the tag to see the full name. For example, Acme-Risk-Register-Q3.csv imported on 28 September 2026 at 09:15 gets the tag Acme-Risk-Register 280926 0915.

  • Filtering: On the Findings page, filter by the tag, by file name, or by import date. The Source field shows Import.

If the import can't be completed

Processing stops and the platform shows This import couldn't be completed with the reason. Return to the upload step to try again with a corrected file. Common reasons:

  • The file has more than 500 findings, or more rows than a single import allows.

  • The file is password-protected, encrypted, or can't be read.

How existing findings are handled

  • How a row is matched: By Finding name, within the target engagement. A row with no match creates a new finding.

  • Identical finding exists: It is not imported again.

  • Finding exists with different values: It is updated with your file's values. The latest import always wins.

Importing from unstructured files

For files such as assessment reports and penetration test reports, use Import with CYE AI on the Findings page. It extracts findings and their remediation assets without a template or column mapping. See Import Findings with CYE AI.

Wrap-up / Next Steps

  • Review: Open the Findings page filtered by your import tag, check the imported findings, and correct any value there.

  • Add to the graph: Findings with a Probability value appear in the Org Attack Graph.

Related articles
See also: [Import Template Fields Reference]
See also: [Working with Findings in the Cye platform]

Related Articles
Did this answer your question?