Encryption questions in security questionnaires: common wording and sample answers

Security Questionnaires

Author:

Chris Mabry

Short answer: Encryption questions ask three things: is customer data encrypted while it moves (in transit), is it encrypted where it's stored (at rest), and who controls the keys. A strong answer says yes or no plainly, states the scope (which data, which systems, including backups), names who manages keys, and points to the policy section that says so. Only name algorithms, protocol versions or key lengths you can show evidence for.

In Iris: answers to encryption questions are drafted from your own encryption standard and SOC 2 report, with each answer linked to its source.

Who this is for: security engineers, GRC leads and sales engineers filling in a vendor questionnaire.

On this page

  1. How is the encryption question usually phrased?
  2. What is the reviewer really checking?
  3. Sample answers (fictional company)
  4. What evidence should you attach?
  5. Where do encryption answers go wrong?
  6. How Iris answers this about itself
  7. How Iris drafts encryption answers
  8. FAQ

How is the encryption question usually phrased?

The same control shows up under many wordings. Map each one to the fact it's really after before you answer.

Common phrasing (paraphrased)What it's really askingUsual answer format
"Is customer data encrypted at rest?"Storage encryption for databases, object storage and file storesYes/No + comment
"Is data encrypted in transit over public networks?"TLS on every external connectionYes/No + comment
"Is data encrypted in transit inside your environment?"Internal service-to-service traffic, not just the edgeYes/No/Partial + comment
"Are backups encrypted?"Whether at-rest encryption also covers snapshots and backup copiesYes/No
"Describe your key management process."Who generates, stores, rotates and can access keysFree text
"Do you support customer-managed keys (BYOK)?"Whether the buyer can control or revoke the keyYes/No
"Which encryption standards and protocols do you use?"Whether you rely on current, accepted methodsFree text
"Are laptops and endpoints encrypted?"Full-disk encryption on staff devicesYes/No
"Are secrets and credentials encrypted?"API keys, tokens and passwords held by the appYes/No + comment

In CAIQ this theme sits in the Cryptography, Encryption & Key Management domain; most other questionnaires have an equivalent section. See our CAIQ guide for the domain map.

What is the reviewer really checking?

  1. Coverage, not a slogan. "Encrypted everywhere" is a red flag. Reviewers want to know whether backups, logs, internal traffic and staff laptops are in scope.
  2. Key control. Who can decrypt? A managed key service with restricted access answers this better than a long list of ciphers.
  3. Consistency. Your answer must match your SOC 2 report, your DPA and your encryption policy. Reviewers compare them.
  4. Honesty on gaps. A clear "No, not yet" with a plan is scored better than a vague "Yes" that falls apart in a follow-up call.

Sample answers (fictional company)

Written for Fernhill Software, a fictional SaaS vendor hosted on a major cloud provider. Labelled examples, not templates to copy without checking your own policy.

Strong answer: encryption at rest

Answer: Yes.
Comment: All customer data stored in Fernhill's production databases, object storage and backups is encrypted at rest using our cloud provider's managed encryption. Keys are held in the provider's key management service; access to key administration is limited to the infrastructure team and logged. See Encryption Standard §2 and our SOC 2 Type II report (available under NDA).

Why it works: states scope (databases, storage, backups), names who controls keys without over-claiming detail, and cites two pieces of evidence.

Weak answer, rewritten: encryption in transit

Weak: "Yes, we use industry-standard bank-grade encryption."

"Bank-grade" means nothing to a reviewer, and the answer doesn't say where encryption applies.

Rewritten: Yes. All external connections to the Fernhill application and API require TLS; unencrypted HTTP requests are redirected. Traffic between internal services runs inside a private network, and connections to our managed database require TLS. See Encryption Standard §3.

Honest partial: customer-managed keys

Answer: No.
Comment: Fernhill does not currently offer customer-managed or bring-your-own keys. Customer data is encrypted at rest with keys managed in our cloud provider's key management service, with access restricted and logged. We'll confirm in writing if this changes.

Why it works: a clean "No" plus what is in place. Never answer "Yes" to BYOK because it's on a roadmap.

What evidence should you attach?

QuestionEvidence reviewers accept
At rest, in transit, backupsEncryption standard or policy (the relevant section), SOC 2 Type II report
Key managementKey management procedure; access list summary for key administration
EndpointsEndpoint or device management policy
Protocols and versionsOnly if you can produce a scan or configuration record that matches what you state
SecretsSecrets management procedure

Attach the section, not the whole policy library. If a control is inherited from your cloud provider, say so and reference the provider's attestation.

Where do encryption answers go wrong?

  • Naming ciphers you can't evidence. If the answer says a specific algorithm or key length, a reviewer may ask for proof. State only what your documentation shows.
  • Different answers in different rows. The same encryption fact appears in several sections of one questionnaire. Check every row agrees.
  • Copying an old answer forward after an infrastructure change. Date-stamp approved encryption answers and give them an owner.
  • Forgetting backups and logs. These are the follow-up questions reviewers ask most.
  • "Yes" to "end-to-end encryption" when you mean TLS plus storage encryption. Those aren't the same thing.

How Iris answers this about itself

As a worked example, Iris's approved public wording is short: customer data is encrypted in transit and at rest. Iris doesn't name ciphers or key details in marketing copy; those are provided through its security documentation process. That's the pattern this page recommends: a plain statement, backed by documents a reviewer can request.

How Iris drafts encryption answers

  • Answers come only from your content: your encryption standard, your SOC 2 report, synced SharePoint, Google Drive, Confluence or Notion, Vanta Trust Center resources, and approved answers from past questionnaires.
  • Every answer cites its source and carries a High, Medium, Low or Contradictory label. Contradictory means two of your documents disagree, for example an old policy that predates a key-management change.
  • When your documents are silent (say, nothing mentions BYOK), Iris answers "There is not enough information to answer the question" instead of guessing. Those answers can't be approved as-is.
  • Evidence reuse: attach your encryption standard to an approved answer once; Iris suggests it again when that answer is reused.
  • Owners and expiry: give the approved encryption answer an owner and an expiration date, so it's re-reviewed after infrastructure changes.

Iris is rated 4.8/5 on G2 from 92 reviews (November 2026). Try Iris free on an RFP you've already answered, or on a security questionnaire you've already completed, and compare the drafts.

FAQ

Should I list the exact encryption algorithm in a questionnaire?
Only if you can evidence it. Many vendors state "encrypted at rest using our cloud provider's managed encryption" and provide specifics in their security documentation on request.

What's the difference between encryption in transit and at rest?
In transit protects data moving over a network (typically TLS). At rest protects stored data on disks, databases and backups.

Is "we use AWS (or another cloud), so it's encrypted" a good answer?
Not on its own. Say which services hold customer data, that encryption is enabled on them, and who manages keys.

What if we don't encrypt internal traffic yet?
Say so, describe the network controls that are in place, and don't promise a date you can't commit to.

Do reviewers care about laptop encryption?
Yes. Endpoint encryption usually appears in the device-management section. See employee security questions for the related HR and offboarding answers.

See it live

Respond to RFPs
without the grind.

Book a demo and see your real auto-fill rate on a translation
RFP from your pipeline.