Avoiding IaC misconfiguration (on multiple platforms)
summary
Describes common infrastructure-as-code misconfigurations (general and platform-specific) such as overly permissive storage, unauthenticated databases, and exposed ports, and recommends scanning IaC during builds to raise alerts or fail the build. Demonstrates using the open-source KICS security scanner to find misconfigurations across multiple IaC platforms so teams can run one tool against different templates (e.g., Kubernetes manifests, AWS cloud templates).
AI-written summary · about
related talks
11mAWS On Air ft. Checkmarx
36mInfrastructure as Code Done Right: Discovering and Fixing Common Missteps
48mWhy checking your infrastructure-as-code for misconfigurations is not enough – How ...
18mInfrastructure as Code Security Best Practices & Strats
32mCode Quality and Infrastructure as Code
22mOur Journey to Shift-left Security with Infrastructure as Code
15mInfrastructure as a Code: Best Practices and Myths
34mIaC – Improving and Securing Infrastructure Provisioning in the Cloud