How CSPM Can Help to Secure Your Cloud and Avoid Configuration Disasters

Mikael Nilsson opens with the case for cloud security posture management (CSPM). He cites Verizon's 2023 breach report and the OWASP Top 10 to show how often misconfigurations appear in breaches. He then walks through an application that passes static, dynamic, composition and container scans, yet still leaks data through an open storage bucket, an exposed database or an overly broad dataset. CSPM targets that infrastructure layer surrounding the code.

The middle of the talk covers organisation and process. Product security and cloud infrastructure teams have traditionally owned different halves of security, and infrastructure as code means developers now share responsibility for what they deploy. CSPM tools evaluate cloud resources against framework, regulatory and internal policy rules, then track findings over time. Nilsson recommends choosing a few frameworks, such as ISO 27001, SOC 2, NIST CSF, GDPR or CIS benchmarks, instead of starting with everything. His triage approach sorts findings into quick switch-flips, high-effort changes that need planning or compensating controls, and high-volume or regressing issues that point to broken controls. He also shows posture scores and severity trends as progress measures, and a cloned load balancer rule that enforces an internal TLS 1.3 policy.

He closes by urging regular meetings between developers and operations, and by pairing standard benchmarks with custom rules for enterprise policy. The examples use mock data from one commercial CSPM product, presented as one option among many.