Talk about your next project
P0 Security case study

The lesson

Lead a technical case study with a bulleted takeaways list and a short answer paragraph, then break the challenge and the solution into numbered parts a security buyer can check one by one.

The move

Under the headline sits a "Key takeaways" list of six bullets, followed by a short paragraph titled "How did CNA Insurance solve GCP service account sprawl?" and a band headed "By the numbers: CNA Insurance's NHI challenge at a glance" with three figures: 40,000+ service accounts, 30,000+ static keys, <1 Hour deployment. "About CNA Insurance: Managing risk at enterprise scale" sets out the regulatory pressure, then "The challenge" lists three numbered problems, including a cost calculation of 3,333 hours of manual review. "The solution" walks through four numbered P0 capabilities, starting with discovery, and compares the deployment time with a vault or bastion approach.

Why it works

  • Our readThe takeaways list and answer paragraph give a skimming buyer the scale, the outcome and the deployment time before any story starts.
  • Our readNumbering the three problems and four capabilities lets a security reader map each pain to the feature that addressed it.
  • Our readTurning 40,000 accounts at five minutes each into 3,333 hours shows the cost of the old approach in terms a budget owner can weigh.

What not to copy

Don't copy CNA's GCP and insurance-regulation details, the Zero Standing Privilege terminology, or the third-party breach statistic. Keep the takeaways list, the short answer paragraph, the three-stat band, the customer profile with its compliance stakes, the numbered challenges with a cost calculation, and the numbered solution steps.

More from P0 Security

More case studies

Steal it for your brand.

Tell us what you want to make. We’ll talk through how to put these ideas to work for your brand.