Exporting and importing a vulnerability data

You can export and download your vulnerability data and import it into a new Concert instance to migrate or replicate an environment. The output of the export will be a .tar file and the output is stored in LZ bucket. The data is then reassessed when imported back into a Concert instance. You can export the vulnerability data, including image scans, code scans, runtime scans, and DAST/SAST scans.

Before you begin

Attention: To ensure the security and integrity of your organization's data and resources, it is recommended that you get approval from your CISO or security team before exporting, storing, or sharing Concert data.
  • You can export the following types of vulnerability scan files:
    • Source code CVE scan (code_scan)
    • Image CVE scan (image_scan)
    • Runtime CVE scan (vm_scan)
    • Static exposure SAST scan (static_code_scan)
    • Dynamic exposure DAST scan (dynamic_scan)

Instructions: Exporting vulnerability data using Concert API

  1. Use one of the following commands to export vulnerability data.
    1. Export by vulnerability data type:
      curl -k -X POST ‘<concert_domain>/core/api/v1/export/vulnerability?datatype=<data_type_options>’ \
      -H 'Authorization: Bearer <token>' \
      -H 'accept: application/json' \
      -H 'InstanceId: <InstanceId>’
      
    2. Export a specific vulnerability scan file:
      curl -k -X POST ‘<concert_domain>/core/api/v1/export/files?ids=<uuid_from_table_of_contents_el >’\
      -H 'Authorization: Bearer <token>’ \
      -H 'accept: application/json' \
      -H 'InstanceId: <InstanceId>’
      
    Note: Record the toc_id included in the response. You need this to download the exported file.
  2. Download the exported .tar file:
    curl '<concert_domain>/core/api/v1/export/job/<job-id>/download' \
     -H 'accept: application/json' \
     -H 'InstanceId: <InstanceId>' \
     -H 'Authorization: Bearer <token>' -k -O -J -L
    
    Note: The output of the exported vulnerability data will be a .tar file format and the output files are stored in LZ bucket.

Instructions: Importing vulnerability data using Concert API

Refer to the following command to import a file containing your vulnerability data to a new Concert instance.

curl -k -X POST 'https://<concert-domain>/ingestion/api/v1/import_files' \
     -H 'Authorization: Bearer <token>' \
     -H 'Content-Type: multipart/form-data' \
     -H 'InstanceId: <InstanceId>' \
     -F 'file=@<filepath>'

Instructions: Exporting an vulnerability data using Concert UI

Refer the following instructions to export vulnerability data to your workstation.

  1. Select Inventory > Evidence store.
  2. Choose the vulnerability scan type and click to enable the check box(es) next to the relevant vulnerability data(s).
  3. Click Export.
  4. Click View event status or select Administration > Event log to view the exported file.
  5. From the overflow menu against the exported file, choose Download.
    Note: The output of the exported application will be a .tar file.

Instructions: Importing an vulnerability data using Concert UI

Refer the following instructions to import vulnerability data from your workstation to a new Concert instance.

  1. Select Dimensions > Vulnerability.
  2. Click Upload vulnerability scan.
  3. Upload the relevant exported .tar file from the workstation.
  4. Click Upload.

Refresh the Vulnerability page to view the imported file.