For security software vendors and security service firms
Cybersecurity Vendor Testimonials Without Names
A security buyer telling the world which tool protects them is telling attackers what to test. So security vendors face customers who are delighted and still refuse to be quoted. The answer is rarely one anonymous quote on the homepage. It is a choice of proof format for each customer, depending on what their policy allows and what your prospect needs to hear.
- Five questions about the customer’s rules and your buyer
- A proof format that reveals nothing about their stack
- An honest fallback when nothing can be published
The problem, solved
Why security customers will not be quoted, and what StoryProof can do
The refusal is usually reasonable. The aim is proof that helps your prospect without helping an attacker.
Situation 1 of 5
Naming our tool exposes their defences
A public quote tells attackers which product to research for weaknesses at that company.
How StoryProof solves it
Nothing is published until you approve it, so attribution can be cut to a role and sector, with no company name or stack detail.
Situation 2 of 5
The CISO will not appear on camera
A face makes a quote traceable, even without a name, and senior security staff are recognisable at conferences.
How StoryProof solves it
The same link takes an audio note or a written answer, and audio plays in widgets beside other testimonials.
Situation 3 of 5
Their answer included architecture details
Enthusiastic engineers describe exactly what was deployed where, which cannot go public.
How StoryProof solves it
Read and approve each answer first. If details need removing, ask the customer to resubmit a shorter version through the link.
Situation 4 of 5
Banks want to hear from banks
A financial services prospect discounts a quote from a retailer, even an anonymous one.
How StoryProof solves it
Tag each testimonial by sector and company size, and choose which approved ones appear on each industry page.
Situation 5 of 5
We never ask because we expect a no
Teams assume every security customer will refuse, so even customers who would agree to a role quote are never asked.
How StoryProof solves it
Add customers as contacts and email a request that offers unnamed attribution from the start.
Proof format picker
Choose the proof this customer can give
Answer for one customer at a time. The result is a starting point for a conversation with them, not a decision for them.
Your answers are scored in your browser. Nothing is saved or sent.
Prompts
What to ask a security customer, and what to keep out
Questions about outcomes and the working relationship produce quotes that are safe to publish.
Safe to ask
- What was hard before, in general terms?
- How did rollout go for your team?
- What is it like working with our support during an incident?
Leave out
- Which systems or endpoints is it deployed on?
- What other security tools do you run alongside it?
Remove before approving
- Keep: role, sector, company size band, outcome in words
Leave out
- Product names of their other tools
- Incident dates or descriptions
- Office locations or team names
In StoryProof
Run it in StoryProof
- You will need
- The customer’s answer to “what may we say about you?”
- An agreed attribution format
- 1
Ask with anonymity offered up front
Add the advocate as a contact and email a request that says you will not name the company unless they ask you to.
- 2
Let them choose voice or text
The link takes an audio note or written words; video is optional.
- 3
Check for stack details, then approve
Read or listen for system names, locations and incidents. Approve only clean answers with the agreed attribution.
- 4
Tag and place by sector
Tag by sector and size and choose testimonials for each industry page.
What happens next: Review unnamed testimonials once a year with the customer. Policies change, and some will later agree to be named.
Before you start
Honest limits
What this does not cover, and what to check on your side. Better to know now than after launch.
- 01
No automatic redaction
StoryProof does not detect or remove product names or architecture details. Review is a human job.
- 02
Their words stay theirs
Do not quietly rewrite a security customer’s answer. If a detail must go, ask them to resubmit a cleaner version through the link.
- 03
Audio can identify a voice
A voice note is less identifying than video, not anonymous. Tell the customer that before they record.
- 04
No reference call scheduling
StoryProof does not book or track reference calls. A private reference runs outside it.
FAQ
Questions people ask
Short answers to what usually comes up next.
Why will cybersecurity customers not give testimonials?
Naming a security product tells attackers what defends a company, and many organisations ban staff from endorsing vendors. Offer unnamed attribution from the first ask.
Is an anonymous security testimonial credible?
More so when the description is specific: role, sector and size. “A CISO” alone persuades nobody; “Head of security, regional bank” does much more.
Can a security vendor publish a case study without the customer’s name?
Yes, with their agreement on the description and every detail. Leave out anything that narrows it to one organisation.
What if a customer can only take reference calls?
That is still proof. Build a small reference programme so those customers are asked rarely and only by qualified prospects.
Still have a question? Ask the StoryProof team or book a demo.
Collect proof your customers can safely give
Set up a form that offers voice or text and keeps everything private until you approve it. No credit card needed to start.
Last updated 2026-11-07.