Answer guide · Access control

Password storage and hashing: how to answer it in a security questionnaire

Usually asked as: “How are user passwords stored and protected (hashing algorithms, salting)?”

Updated

What the buyer is really asking

If your database leaked, would the passwords be usable? Buyers look for a slow, salted hashing algorithm, or confirmation that an identity provider stores passwords so you never hold them.

Other ways buyers ask it

Every one of these wants the same answer:

  • “How are user passwords stored?”
  • “What hashing algorithm do you use for passwords?”
  • “Are passwords salted?”

Evidence to have ready

  • The hashing algorithm and parameters in use
  • Your identity provider's documentation, if it stores passwords on your behalf

How Tyrvar answers this

Tyrvar treats every wording above as one question. You write the answer once, attach the evidence, and revisit it when your setup changes. Each buyer gets that approved answer no matter how their questionnaire words it. If you have not answered it yet, Tyrvar flags the question for you and does not make something up. Try it on your own questionnaire.

Related access control questions

All access control questions

Private alpha application

Bring one real questionnaire.

We are recruiting the first teams willing to work through the imperfect version with us. The form is the primary path; a calendar is optional.

  1. 01Send a work email, company, and role. Context is optional.
  2. 02Troy replies directly by email to check mutual fit.
  3. 03If it fits, we agree on one evidence set and one real questionnaire to start.
Not ready to apply? Email a question to [email protected] or read the response workflow guide.

Check mutual fit

Required fields are marked with an asterisk.

Sending this form starts a one-to-one alpha conversation. No newsletter and no automatic sales sequence. See the privacy policy.

Prefer a live conversation? Schedule an optional fit call.