Security Through Transparency: Scaling Your Customer Trust Program
summary
Company publishes core policies and evidence on the open web, builds a public-facing wiki, a trust center with gated NDA access for sensitive reports, and a searchable security Q&A database surfaced via Slack and Salesforce. Implementation uses markdown in git for versioning, took about three to twelve months, and handles ~700–800 vendor reviews yearly. Results show roughly one third fewer incoming reviews and sales cycles shorten by about two to three weeks, with attacker-sensitive details kept internal under a “safe” framework.
AI-written summary · about
chapters (21)
- 0:00Introduction
- 0:42Why Care About Transparency
- 2:00Story Time
- 3:47Why Care
- 5:46Public
- 6:32Sharing
- 7:22Externality
- 7:58Getting Started
- 8:53Customers
- 9:39Reputation
- 10:40Customer Benefits
- 11:59Trust Center
- 13:10Sales Organization
- 14:20Make Friends
- 16:23The Sales Cycle
- 19:47How to Get Started
- 21:18Common Objections
- 23:12Sharing Links
- 24:48Managing Content
- 26:52AI
- 28:53Metrics
related talks
44mA Matter Of Trust: When Security Is Not Enough
43mDeveloper Driven Security In High-Growth Environments
40mLearning to build an effective security design review program
24mConcrete Steps to Create a Security Culture
23mAdventures in Vendor Security and Continuous Review
40mSix Years in Review: Transforming Company Culture to Embrace Risk
45mHow Leading Companies Are Scaling Their Security
47mBuilding Trust in Open Source: A Practical Guide to Securing Your ...
