Skip to content

IaC scanning troubleshooting

The errors and warnings vulnetix iac prints, the misconfigurations it quietly does not report, their causes and the fix for each.

Updated 04 Nov 2026Markdown

Use this page when vulnetix iac stops with an error, or reports less than you expect. Errors print as Error: <message> on stderr. Exit codes are on the output page.

Starting a scan

Symptom or message Cause Fix
invalid rule reference "<value>": expected org/repo --rule was given a URL or a bare name Pass org/repo, for example --rule Vulnesis/opa-fugue-regula. Set another host with --rule-registry.
--fail-on: unknown rule "<value>" (valid: low, medium, high, critical, ...) A misspelt severity Use low, medium, high or critical.
cannot infer output format for "<path>": use .cdx.json for CycloneDX or .sarif for SARIF -o was given a file name with no recognised extension End it in .sarif, .sarif.json or .report.json. See Output.

Rule packs

Symptom or message Cause Fix
Warning: rules registry not found: <org>/<repo>: <error> The pack could not be cloned The scan continues without it and can exit 0. Check the name, access and network. See How packs are fetched.
A pack’s Dockerfile checks do not run under vulnetix containers The KICS and Trivy Dockerfile rules are kind iac Run them with vulnetix iac --rule .... See Rule packs.
A pack’s sast, container or api rules do not run vulnetix iac keeps only rules of kind iac Use the matching command, or vulnetix scan --rule. See The kind lock.

Results look wrong

Symptom or message Cause Fix
Nothing reported for Kubernetes, CloudFormation, ARM or Ansible The seven built-in rules are Terraform on AWS only Add a rule pack. See Rule packs.
A module under infra/modules/<name>/main.tf is not checked It is at depth 4; the default --depth is 3 Pass --depth 10 or more.
A misconfiguration set through a variable, local or module input is not reported The rules read literals, not evaluated HCL Expected. See Overview.
Hard-coded AWS keys in Terraform are not reported VNX-TF-008 is a secrets rule Run vulnetix secrets.
nosec on the resource does not silence a finding The comment is not on the line the rule reports Check the line in the report first. See nosec comments.
An ignore rule with --line silences the whole file IaC findings are matched without a line Use a nosec comment for one resource.

In CI

Symptom or message Cause Fix
The build fails at a different severity from --fail-on The organisation’s quality gate replaced it Run with -v to see org policy applied: --severity <level>.
.vulnetix/sast.sarif holds SAST or secrets results sast, secrets and iac write the same path Pass -o iac.sarif.
/v2/cli.iac chunk 1/1 submit failed: <error> The upload failed The exit code is unchanged. Check the credential with vulnetix auth verify.

Still stuck

Collect the CLI version (vulnetix version), the exact command including every --rule, its output with -v (with the Imported line), the SARIF from .vulnetix/sast.sarif or your -o file, and .vulnetix/memory.yaml if a suppression is involved. For sign-in and upload errors, start with Troubleshooting authentication.

esc
↑ ↓ move↵ openSearches in your browser. A key like autonomy.max or a code like threshold_required jumps straight to it.