liveBook · Manning

Infrastructure as code scanning

As explained in Grokking Software Architecture

Infrastructure scanning is the automated analysis of infrastructure definitions for security violations and unsafe configurations.

Infrastructure as code scanning automatically checks infrastructure definitions against security policies before deployment. A CI/CD pipeline can fail a build when a change creates an unsafe network route. section 11.7.1

Catch a risky route

Suppose a Terraform change connects a vendor subnet to a protected point-of-sale subnet. An IaC scanner such as Checkov or tfsec can flag the route, and the pipeline can block the build. Teams can also write automated tests for policies and simulate an attacker to check that guardrails work before deployment. section 11.7.1

How Grokking Software Architecture covers it

How deep it goes
Checks Terraform network routes against coded policies and describes automated tests that simulate an attacker.
Examples
Flags a Terraform route linking a vendor subnet to a protected point-of-sale subnet and fails the build.
What you can do after
Configure CI/CD checks that reject unsafe infrastructure routes and run automated tests of security policies.
How it connects
Connects infrastructure scanning with Policy as Code, Open Policy Agent, and CI/CD pipelines.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Grokking Software Architecture. The section links point to the parts of the book it draws on.