ScoutSuite Reporting,
Beyond the HTML Report
ScoutSuite report import that keeps every flagged rule and resource. Load the scoutsuite_results file and triage AWS, Azure, and GCP issues in one queue.
Import Once. Report From One Place.
ScoutSuite produces an HTML report that is great to click through and slow to turn into findings. Every flagged rule, its rationale, and the resources it caught sit inside a single-page report and a JavaScript results file. Neuron imports that results file directly.
Load the scoutsuite_results_*.js file from the report folder, or a JSON export, and every rule with flagged items becomes a scan issue. The ScoutSuite service it belongs to, its danger or warning level, the rationale, remediation, references, and compliance mappings come with it, and each flagged resource is listed with its region and account.
Upload it in the browser, or run neuron import on it from the box that ran the audit. The CLI recognises the results file from its content.
$ scout aws --profile acme-audit \ --report-dir ./scout-acme Saving data to scoutsuite_results_aws-acme.js $ neuron import scout-acme/scoutsuite-results/scoutsuite_results_*.js✓ ScoutSuite: 31 issues, 187 resources- 15:27 Finding Security group opens SSH to all
- 15:20 Import ScoutSuite: 31 issues, 187 resources
- 15:06 Command scout aws --profile acme-audit
- 14:02 Import Prowler: 58 issues, 412 resources
Why ScoutSuite Reporting Takes So Long
ScoutSuite audits a whole cloud account in one pass and groups what it finds by service: IAM, S3, EC2, CloudTrail, and the rest. The HTML report is excellent for exploring a tenant, but a client deliverable needs findings, not a dashboard.
So testers click through each service, copy rule descriptions and rationale, then expand the flagged items one by one to collect resource paths. The JavaScript file that holds all of it is not something anyone wants to parse by hand the night before delivery.
Audit several accounts, or a mix of AWS, Azure, and Google Cloud, and the same rule ends up written three different ways in the same report.
Everything ScoutSuite Produces, On the Engagement
Import ScoutSuite output from the browser or with neuron import, and it lands the moment the import finishes.
Flagged Rules as Issues
Every ScoutSuite rule with flagged items as a scan issue, titled with ScoutSuite's own description. Rules with nothing flagged are left out.
Severity from Level
ScoutSuite's danger and warning levels mapped to high and medium severity, so the queue sorts the way the report should read.
Flagged Resources
Each flagged item as an affected resource, with the full ScoutSuite path, the resource it points at, its region, and the account it lives in.
Rationale and Remediation
ScoutSuite's rationale lands as the impact, alongside its remediation text, references, and compliance mappings.
Service Grouping
Issues keep the ScoutSuite service they came from, iam, s3, ec2, and so on, so the queue groups by Service the way the HTML report did.
Account-Scoped Rescans
Issues are scoped to the provider and the account, project, or subscription, so re-importing one account updates its issues and marks resolved rules fixed without touching another.
How to Import ScoutSuite Results
- 01
Run the ScoutSuite audit
Run scout against the provider with the credentials the client gave you. It writes the HTML report and a scoutsuite-results folder beside it. scout azure --cli and scout gcp --user-account work the same way.
$ scout aws --profile acme-audit --report-dir ./scout-acme - 02
Audit with read-only credentials
Ask the client for a read-only audit identity, such as ReadOnlyAccess plus SecurityAudit on AWS or Reader on Azure. ScoutSuite needs nothing more, and the Neuron import needs no cloud credentials at all.
- 03
Import the results file
Point neuron import at the scoutsuite_results_*.js file and it is recognised from its content. For a JSON export, add --source scoutsuite. Each file imports on its own.
$ neuron import scout-acme/scoutsuite-results/scoutsuite_results_*.js - 04
Or upload it in the browser
Choose Import on the engagement and pick ScoutSuite under Cloud Security, then drop in the same .js or .json file.
Your Infrastructure. Your Data.
Neuron is self-hosted. Import ScoutSuite results from the browser or the CLI and they land on your own server, inside your network. Scan data never passes through a third-party cloud.
From ScoutSuiteto the Final Report
Each ScoutSuite rule arrives as one decision with its flagged resources attached. Confirm it, mark the resources that are expected as not affected, and promote it into a finding that names exactly what the client has to change.
ScoutSuite's rationale and remediation are a starting point. Your Findings Library supplies the approved write-up for recurring cloud issues, and the scan issue shows the match, so the finding reads like the rest of your report whichever provider it came from.
Every finding then goes through the QA pipeline with its resource list intact, and the client reviews it in the client portal instead of a zipped HTML report.
ScoutSuite Integration FAQ
The questions teams ask most about ScoutSuite and Neuron.
How do I import a ScoutSuite report into a pentest report?
Import the scoutsuite_results_*.js file from the ScoutSuite report folder into the engagement, in the browser or with neuron import. Every rule with flagged items becomes a scan issue with its resources, rationale, and remediation, ready to triage and promote into a finding.
Which ScoutSuite file does Neuron need?
The scoutsuite_results_*.js file inside the scoutsuite-results folder that ScoutSuite writes next to its HTML report, or a JSON export of the same results. The ScoutSuite HTML page only renders that data, so import the results file.
How are ScoutSuite danger and warning levels mapped?
ScoutSuite danger becomes high severity, warning becomes medium, and anything else is imported as low. The scanner's severity is a starting point, and the severity on the finding is still yours to set.
Does the ScoutSuite import work for Azure and Google Cloud?
Yes. ScoutSuite issues are scoped to the provider and the AWS account, Azure subscription, or GCP project in the results, so audits of different tenants in one engagement never collide.
What happens when I import a ScoutSuite rescan?
Issues for that account update in place, and rules that are no longer flagged are marked fixed. Import the retest audit and the queue shows what changed.
Can I use ScoutSuite and Prowler on the same engagement?
Yes. Both land in the same Scan Issues queue, filterable by Scanner, so overlapping checks from ScoutSuite and Prowler are triaged side by side and can be linked to the same finding.
More Neuron Integrations
Prowler Reporting and Cloud Scan Import
Cloud and MobileMobSF Report Import for Mobile Pentests
Cloud and MobileBloodHound Reporting and Attack Path Import
Active DirectoryPCAP Import: Hosts and Services From Captures
Network DiscoveryNessus Reporting and .nessus File Import
Vulnerability ScannersQualys Report Import for Pentest Reporting
Vulnerability ScannersOpenVAS Reporting and Greenbone Report Import
Vulnerability ScannersNexpose and InsightVM Report Import
Vulnerability ScannersReady to Transform Your Security Practice?
See how Neuron helps security teams replace fragmented tools with a single platform for offensive security, bringing structure, visibility, and consistency to every engagement.
Platform