A security-questionnaire question, answered without certification
How do you manage secrets and credentials?
The honest answer pattern
State where secrets actually live — environment configuration on your hosting platform is a real answer — and confirm they are not in source control. Describe who can read them, which usually tracks production access. If rotation is ad hoc, say it is performed on personnel change or suspected exposure rather than claiming a schedule you do not keep.
What a credible answer looks like
A credible answer is specific and current-tense only where it's true: it names your actual provider and systems, states what is in place today, and moves anything that isn't into a clearly labelled roadmap item instead of an aspirational “yes”. Reviewers read dozens of these a quarter — vague assurances are what get a vendor flagged, not missing certifications.
You can see this pattern applied end-to-end in the full sample security pack — a real trust page, three policies, and an answer bank generated by the same pipeline a paying customer uses, shown without any email gate.
The facts your answer needs (from the Trustpack intake):
- Describe your development security practices.
- Who can access production systems and customer data?
Answer the whole questionnaire, not one row
Trustpack turns your own attested answers into three security policies, a copy-paste answer bank covering the canonical questionnaire topics, and a live public trust page. Every document is vendor-attested and says so plainly — it never claims certification. Flat $49, one time.