Tutorials / Code & Cloud

Infrastructure as Code (IaC) Security

Prancer enables full IaC security assessment, including Static Code Analysis, compliance evaluation, and automated remediation via pull requests. The process mirrors the Code Security workflow but is tailored for infrastructure templates and IaC environments.

Step 1: Connect Your IaC Repository

1. Navigate to Collection Management, select your target collection.

2. Click the hamburger menu → choose Third-Party Integrations.

3. Select your Git provider (e.g., GitHub, GitLab, Bitbucket).

4. Check the IaC option to enable the IaC panel.

5. Click Authenticate, connect to your repo, then choose the repository hosting your IaC code.

6. Click Finish—this creates a Connector and configures IaC scanning for that collection.

You’ll see this new connector listed in your collection.

Step 2: Run IaC Scanning

With the connector in place, simply click Start in the collection. Prancer will automatically:

Crawl the IaC files in the repository

Evaluate them against built-in policies and compliance rules (e.g., CIS, HIPAA, NIST, PCI)

Note: If your collection also includes cloud connectors, a parallel CSPM analysis will also run.

Step 3: Review IaC Findings

Once scanning completes, go to Infrastructure Findings, filter by Source: Git, and select your collection to view all IaC-related findings.

The findings include policy violations, misconfigurations, and compliance gaps in your IaC templates.

Step 4: Automated Remediation via Pull Requests

Prancer supports auto-remediation for IaC issues. Here’s how it works:

1. Open a finding marked as remediable—click the Remediate button.

2. Prancer:

Checks out the repository

Creates a new branch

Applies the fix in code

Opens a Pull Request (PR) with a title, description, and code diff

Ensure your connector uses a token with write permissions to enable this feature.

3. Review the PR—view proposed changes and approve to merge.

Why Use Prancer for IaC Security?

Shift-left security: Identify IaC misconfigurations early in the CI/CD pipeline.

Compliance enforcement: Supports multiple frameworks including CIS, NIST, PCI, HIPAA, HITRUST, CSA-CCM, and ISO 27001.

Automated fixes: Generates PRs to address issues, reducing manual effort and accelerating remediation.

Summary Table

| Step | Action |

| 1 | Enable IaC scanning via Third-Party Integration (Git + IaC) |

| 2 | Start the scan—Prancer analyzes templates against security policies |

| 3 | Review violations in Infrastructure Findings using Git filter |

| 4 | Remediate via PR with automated code fixes |

| 5 | Approve and merge PR to apply changes in IaC repo |

Additional Screenshots

Additional screenshots, in order of appearance.