<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Wiz on Dominik Jaro</title><link>https://dominikjaro.pages.dev/tags/wiz/</link><description>Recent content in Wiz on Dominik Jaro</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>Dominik Jaro</copyright><lastBuildDate>Tue, 20 Oct 2026 15:50:53 +0100</lastBuildDate><atom:link href="https://dominikjaro.pages.dev/tags/wiz/index.xml" rel="self" type="application/rss+xml"/><item><title>How I integrated Wiz Security Scanning into our Infrastructure Workflow</title><link>https://dominikjaro.pages.dev/p/how-i-integrated-wiz-security-scanning-into-our-infrastructure-workflow/</link><pubDate>Tue, 20 Oct 2026 00:00:00 +0000</pubDate><guid>https://dominikjaro.pages.dev/p/how-i-integrated-wiz-security-scanning-into-our-infrastructure-workflow/</guid><description>&lt;img src="https://dominikjaro.pages.dev/p/how-i-integrated-wiz-security-scanning-into-our-infrastructure-workflow/wiz_iac.jpg" alt="Featured image of post How I integrated Wiz Security Scanning into our Infrastructure Workflow" />&lt;h3 id="-how-i-integrated-wiz-security-scanning-into-our-infrastructure-workflow">🧙‍♂️ How I integrated Wiz Security Scanning into our Infrastructure Workflow
&lt;/h3>&lt;p>&lt;strong>1. 💻 Local Testing: Shifting Security Left&lt;/strong>
To help developers identify and remediate vulnerabilities before committing code, I introduced a local scanning workflow. This allows the team to catch and fix misconfigurations early in the development cycle.&lt;/p>
&lt;ul>
&lt;li>🛠️ Created a central &lt;code>Makefile&lt;/code> and helper script (&lt;code>scripts/wiz-scan-tfplan/wiz-scan-tfplan.sh&lt;/code>).&lt;/li>
&lt;li>🚀 Developers can simply run &lt;code>make wiz-scan env=[PATH_TO_TERRAFORM_DIRECTORY]&lt;/code> to initialize, plan, and scan their Terraform modules locally.&lt;/li>
&lt;li>🔍 The script utilizes &lt;code>wizcli iac scan&lt;/code> to authenticate and evaluate the generated &lt;code>.tfplanjson&lt;/code> against our security baselines.&lt;/li>
&lt;/ul>
&lt;p>&lt;strong>2. 🤖 CI/CD Integration: Atlantis Automation&lt;/strong>
To ensure continuous security and centralized visibility, we integrated &lt;code>wizcli&lt;/code> directly into our Atlantis pull request workflow.&lt;/p>
&lt;ul>
&lt;li>&lt;strong>🐳 Custom Environment:&lt;/strong> Built and deployed a custom Atlantis Docker image pre-configured with &lt;code>wizcli&lt;/code>.&lt;/li>
&lt;li>&lt;strong>🔄 Automated Pipeline:&lt;/strong> During the PR plan phase, Atlantis generates the plan, parses it via &lt;code>terraform show -json&lt;/code>, and executes our custom &lt;code>wiz-atlantis-scan.sh&lt;/code> script.&lt;/li>
&lt;li>&lt;strong>💬 Actionable PR Feedback:&lt;/strong> Scan results are emitted to the Wiz platform for central tracking, while a clean, formatted summary is automatically posted back to the GitHub PR as a standalone comment.&lt;/li>
&lt;li>🧹 All temporary plan and JSON files are securely removed immediately after the scan completes.&lt;/li>
&lt;/ul>
&lt;p>&lt;strong>3. 🚧 Next Steps: Policy Enforcement &amp;amp; Blocking&lt;/strong>
Our next phase focuses on establishing a firm security baseline and enforcing compliance on all new infrastructure:&lt;/p>
&lt;ul>
&lt;li>&lt;strong>📋 Triage &amp;amp; Baseline:&lt;/strong> Review current scan results and apply global policy exclusions.&lt;/li>
&lt;li>&lt;strong>📜 Policy Configuration:&lt;/strong> Create a dedicated IaC policy in the Wiz Portal targeting the &amp;ldquo;Build&amp;rdquo; lifecycle to define our exact security thresholds.&lt;/li>
&lt;li>&lt;strong>🛑 Block Deployments:&lt;/strong> Update the Atlantis workflow script to exit with a non-zero status upon detecting new policy violations (e.g., CRITICAL or HIGH findings), effectively failing the plan step and blocking &lt;code>terraform apply&lt;/code>.&lt;/li>
&lt;/ul></description></item></channel></rss>