Security FAQ - Security Frequently Asked Questions

— A feasible solution between “Trust us. It’s secure.” and a published threat model.

How can we get better at communicating the security properties of our systems? This article suggests vendors publish a Security FAQ - Security Frequently Asked Questions - and communicate the essence of their threat models.

Question & Answer

Building trust

The security communication of many services delivers poor information, and users are left worried. What if instead, vendors provided target audiences with the essential security properties of systems, building trust and loyalty?

Proposing Security FAQ

A good approach is: (1) to threat model our systems, and (2) to present the information from the threat model in a way that’s tailored to the target audience and clearly communicated.

FAQs - Frequently Asked Questions - have come a long way in customer communication. Let’s communicate our Threat Models as a FAQ!

Micro example: Pizza delivery

Q: What can I do with PizzaForEveryone?

A: Order pizza online. Have it delivered to your home.

Q: Can everyone see where I live?

A: No. Only the driver gets the address.

Q: What if there is a data breach?

A: Good for you: All customer info is deleted after 24 hours.

Q: [...]

A: You get the idea.

How to build a good Security FAQ

Security FAQs present security information in a question → answer style.

Questioner / Answerer roles

The document shows a lively conversation between a questioner and an answerer:

Suggested exploration structure

The FAQ conversation may follow a script:

  1. Exploring utility: The conversation starts out with little knowledge about the system. The questioner asks curiously about the utility of the system. A first question might be “What can I do with <service>?”. The answerer explains the key features.
  2. Challenging the security of features: The questioner then challenges the security of the features. The first questions can be quite naive and straight to the point, like in “Can everyone access <data>?”. The questioner treats undiscovered knowledge as if no mitigations were in place. The answerer presents core mitigations in place.
  3. Challenging mitigations: As it continues, the conversation can build on what came before and go deeper. The questioner challenges mitigations and asks for bypasses and follow-up threats, like in “Could someone guess the credentials?”. The answerer explains how the mitigations are robust.

More suggestions

Alternative words

I started out with FAQ TM (Frequently Asked Questions Threat Model) and QATM (Question Answer Threat Model), then considered Security FAQ a better term for this specific use case. Thanks Avi.

Thanks

Thank you, Marcus, Michel, Izar and Avi for your inspiration and feedback! Some feedback was controversial. Still I feel Security FAQ is a feasible solution between “Trust us. It's secure.” and a published threat model.

“Nobody ever reads the FAQ 😕 Thats why the same questions get asked so damn frequently” — Avi
“Anyone asking to see a TM [threat model] will not be satisfied by FAQs.” — Izar

This text includes remarks from Claude AI.