Batch Import
netbobr supports bulk validation of firewall rules through file import. Drop a file onto the Batch Import tab and netbobr automatically detects the format, extracts flows, and evaluates each one against all enabled compliance frameworks.
Import Methods
| Method | Formats | Details |
|---|---|---|
| CSV Import | .csv, .txt | 4-5 columns (source, destination, protocol, port, optional purpose), header optional, quote port lists ("80,443"); up to 500 rules |
| Cloud Imports | .json, .yaml, .yml, .tf | Native configs from AWS, Azure, GCP, Terraform, and Kubernetes |
How It Works
- Export your firewall configuration from your cloud provider, or prepare a CSV file
- Upload by dragging the file onto the import area, or click to browse
- Analyze -- netbobr auto-detects the format and evaluates each flow against all enabled frameworks
Each parsed flow receives a risk score (0-100), compliance findings, and zone assignments just like manually entered flows.
Status and Errors
The status line under the upload area summarises each import:
- Green -- every row or flow was analysed.
- Amber -- the results are shown, but some rows had errors, rows over the 500-row limit were ignored, or the parser reported warnings, e.g.
1 of 2 flows analysed from sg.json - 1 flow had errors, 1 warning. - Red -- nothing could be analysed, or the file could not be read or parsed. The message names the file and the reason (for example invalid JSON, or js-yaml could not be loaded from its CDN).
Rows that cannot be analysed stay in the results table and the export as error rows with their message. Parser warnings (such as a source or destination that cannot be resolved to a CIDR and was substituted with 0.0.0.0/0) are listed one by one in the warnings banner below the status line. A file with no importable flows shows the amber status No flows to analyse - see the warnings below. when the parser explains why; no results table is shown in that case.
Every new upload replaces the previous file's results, even when it fails. Results can be exported with Export CSV ↓; see Export columns for the column reference.
Supported Formats
- CSV -- 4 or 5 columns (source, destination, protocol, port, optional purpose); see CSV Import
- AWS Security Groups --
aws ec2 describe-security-groupsJSON output - Azure NSG --
az network nsg show/az network nsg listJSON output - GCP Firewall Rules --
gcloud compute firewall-rules listJSON output - Terraform Plan JSON --
terraform show -jsonoutput - Terraform HCL --
.tffiles - Kubernetes NetworkPolicy --
kubectl get networkpolicy -o yamloutput
Accepted file extensions: .csv, .json, .yaml, .yml, .tf, .txt, .md