Your S3 bucket just got flagged as publicly accessible. Is it actually a problem?
Without knowing it also holds PII, hasn't been accessed in 47 days, and was provisioned by a contractor — you can't tell.
That's what we built CQ Insights to fix 🧵
Not limited to built-in sources.
Define custom checks with Policies and they surface in the same Insights view — correlated against your full asset inventory. SQL-powered, built on the data you've already synced. No extra agents.
We wrote out all five queries with full explanations, plus how to go from ad hoc investigation to automated CSPM in four weeks: https://t.co/e4kBUIfFQk
The CSPM market hit $1.64B in 2023, growing 45% YoY. Organizations keep buying more security tools. Misconfiguration rates stay flat. Something about this approach isn't working. Here's what we think is broken and how SQL fixes it. 🧵
Same query serves triple duty: investigation tool at 2am, compliance evidence for auditors, and automated policy check on a schedule. No translation between "what I wrote to investigate" and "what runs in production." Zero language gap.
If your governance only runs when code ships, you're blind to most infrastructure changes that actually cause incidents. Deploy-time checks cover one pathway. Console changes, config drift, and cloud provider updates bypass your pipeline entirely. 🧵
Start with highest-risk policies on a schedule: public S3 buckets, open security groups, unencrypted storage, IAM without MFA. Low false-positive, high-risk checks where drift creates the most damage. Get these running first, then expand.