review-kics

To triage KICS Infrastructure as Code findings safely, use a structured workflow that applies read-only checks to verify misconfigurations without altering your live infrastructure. This approach distinguishes reconnaissance data from actual vulnerabilities.

The best way to extract resource identifiers from KICS results is by running the provided extraction script with the resources argument. This script summarizes the KICS output and identifies specific resource identifiers for your triage workflow.

Yes, you can verify KICS misconfigurations without altering infrastructure by enforcing a safe, read-only verification workflow. This ensures that findings are assessed automatically without risking unauthorized changes to your environment.

Yes, the KICS triage workflow requires KICS results to be available under the findings/<org-name>/kics-results directory. The built-in extraction scripts depend on this specific directory path to locate and process the scan output.

You should expect a concise, validated set of KICS exposures with evidence-ready steps for remediation planning. The triage report provides a structured summary of misconfigurations and publicly exposed resources before deployment.

You need to run a read-only verification check on IaC findings when assessing KICS scan results for an organization's repositories. This ensures potential misconfigurations are validated safely before deployment without modifying live infrastructure.