Import Aqua Security Report to Autobahn

This manual provides step-by-step instructions for exporting a container vulnerability report from Aqua Security and importing it into Autobahn.

  1. Exporting the Vulnerability Report from Aqua Security
  2. Uploading the Report to Autobahn

1. Exporting the Vulnerability Report from Aqua Security

Autobahn imports Aqua’s container vulnerability export — the same data shown on Aqua’s Vulnerabilities / Image Vulnerabilities screen, one row per (running container, package, vulnerability) finding. This is different from Aqua’s Compliance report, so make sure you’re exporting from the vulnerabilities view, not the compliance/CSPM view.

1.1 What Autobahn needs in the file

Whatever export flow your Aqua version uses, the resulting CSV must include these columns — Autobahn’s importer rejects a file missing any of them:

Required column Used for
VM Name The host/node running the container — this becomes the asset in Autobahn
Image Name The vulnerable container image
Vulnerability Name The CVE or vendor advisory ID (e.g. CVE-2025-68121, DSA-5769-1)
Severity Critical / High / Medium / Low / Negligible
Resource The affected package or component

1.2 Export steps

1 –  Log in to your Aqua Security console and open the Vulnerabilities screen (in some Aqua versions this is called the Image Vulnerabilities screen, and older versions surface the same data under Risk Explorer).

2 –  Make sure you’re viewing container/image vulnerabilities, not host vulnerabilities or a Compliance report — Autobahn’s importer expects the container export specifically.

3 – Narrow by application scope, cluster, or severity if you only want a subset. Autobahn accepts a file with any mix of severities — you don’t need to pre-filter to a single severity.

4 – Confirm the required columns from section 1.1 are included in the export (most Aqua versions let you choose columns before exporting; if yours doesn’t, they’re typically included by default).

5 – Use the Export / Export Vulnerabilities action on the screen (Aqua’s own documentation places this under the “Vulnerability Reports” section of the screen) and choose CSV as the format.

6 – Download the CSV locally. Keep it under 50MB — that’s Autobahn’s upload limit for this import.

Note: Aqua groups some advisories together in its UI (e.g. one Red Hat Security Advisory covering several CVEs) but expands them into individual rows in the CSV export — so your CSV’s row count may be higher than what the Aqua UI shows on screen. That’s expected and doesn’t need to be fixed before uploading.

2. Uploading the Report to Autobahn

Once you have the Aqua CSV file, upload it to Autobahn the same way you would any other external scan import.

1 – In Autobahn page, open Scans from the left-hand navigation, then click the Upload button in the top-right corner.

2 – A “File uploads” drawer opens on the right. Click Import file.

3 – In the import form that opens, set the Origin dropdown to Aqua Security.

4 – Select New if this is the first time you’re importing this scan, or Existing to add this file as the next revision of a scan you’ve imported before.

5 – Choose External for internet-facing assets or Internal for internal network scans, matching how these assets are scanned in Aqua.

6 – Enter a scan name, an optional description, and assign the scan to a team.

7 – Drag and drop the Aqua CSV file into the upload area (or click to browse for it), then click Import.

Monitoring progress

After clicking Import, you can track the upload from the same File uploads drawer (Scans → Upload). The status changes to Finished once processing completes, and a new entry then appears in the All scans table on the Scans page with Aqua Security shown as the Origin.