CyberGuard dictionary / Cloud Security
Infrastructure as Code
Infrastructure as code is the practice of defining cloud resources and settings in versioned, machine-readable configuration.
In simple terms
Instead of clicking settings into place by hand, teams review and deploy a declared resource template. The template can repeat both good controls and mistakes.
Technical explanation
IaC workflows should review changes, restrict deployment roles, detect drift, and keep secrets out of templates. Automated checks can flag risky configurations before resources are created.
IaC defines infrastructure in versioned files, making changes reviewable and repeatable. Its templates, state files, build identities, and deployment permissions need protection because a bad change can spread widely.
Examples in practice
A pull request changes a bucket policy; an automated check blocks the deployment because it would allow public reads.
A pull request opens a database to all networks. Automated policy checks flag the rule, and a reviewer corrects it before the deployment pipeline applies the template.
Why it matters
Versioned configuration improves review and rollback when paired with appropriate access controls.
VERIFY & LEARN MORE
Sources and further reading
Published 2026-10-15 · Last updated 2026-10-15 · CyberGuard editorial content. Source links provide context; they do not imply endorsement.