All DevOps case studies / Case study 03 / 05

Talvane RH

AI security review of infrastructure code

A security review that understands the architecture, not just the syntax

In short

On every pull request that changes infrastructure, an AI agent reads the Terraform in context, spots dangerous combinations classic tools miss, explains the risk in a comment and proposes the fix.

Client
Talvane RH
Sector
Payroll software (SaaS)
Size
200 staff, data on 40,000 employees

The context

Talvane RH hosts the payslips of tens of thousands of employees on AWS. Every week, developers change the infrastructure in Terraform. Scanners checked each file in isolation, and the single security expert couldn’t review everything.

The challenge

  1. 01

    A setting can be fine on its own and dangerous combined with another.

  2. 02

    IAM rights and bucket policies are hard to review by hand.

  3. 03

    The review must not slow developers down.

  4. 04

    The proposed fix must itself pass every company rule.

Our approach

A GitHub Action fires on every Terraform pull request. Checkov and OPA rules check the basics first. An AI agent then builds the graph of the resources involved (buckets, policies, networks, roles) together with the existing state, and looks for exposure paths. It comments on the PR with the risk explained plainly, and pushes a fix commit that passes every check again.

The solution, step by step

  1. 01

    A pull request

    A developer adds a payroll exports bucket.

  2. 02

    Classic checks

    Checkov and OPA: no syntax error, everything looks fine.

  3. 03

    Context analysis

    The agent links the bucket, its policy, the VPC endpoint and the public subnet.

  4. 04

    The risk, explained

    A comment shows how payslips become readable from the public network.

  5. 05

    The fix, proposed

    The agent pushes a corrected commit; every check turns green.

Results

What we deliver

  • GitHub review action on every Terraform PR
  • Checkov and OPA baseline rules
  • Context analysis agent (resource graph)
  • PR comments and fix commits
  • Dashboard of prevented risks

Technologies

  • GitHub Actions
  • Terraform
  • Checkov
  • Open Policy Agent
  • OpenAI API / CodeLlama
  • AWS

Timeline

6 to 8 weeks

Team

1 DevSecOps engineer, 1 AI engineer

A similar project? Let’s talk
Next case · Pivelo SoftwareA pipeline that understands why it failed, and fixes itself when it can

Illustrative cases: clients and figures are fictional, representative of the solutions we deliver.