Skip to main content

Better Integration Handling for IaC/Legacy Environments

Customers using infrastructure-as-code (e.g., Terraform) experienced repetitive findings and slow feedback loops, since changes required a code change followed by waiting for a fixed weekly re-scan cycle.

Proposed Solutions:

  • Deduplicate repetitive findings across scans.

  • Support on-demand/manual re-scan triggers instead of relying solely on fixed weekly cycles.

  • Allow scoping of integrations down to a single cloud account or project.

Acceptance Criteria:

  • Repeated findings from the same underlying issue are grouped or deduplicated in the UI.

  • Users can trigger a manual re-scan on demand rather than waiting for the next scheduled cycle.

  • Integration setup allows selecting a specific account/project scope rather than an entire environment.

Log in to comment and vote

No comments yet

Be the first to share your thoughts.