AegisAI Perspectives · 164

How does a SaaS company answer a customer security questionnaire about email security?

A SaaS company answers each email item in a security questionnaire with the setting behind it and evidence from DNS, the admin console or an audit log.

TL;DR
Answer
Give a yes or no, the setting behind it and one piece of evidence for each item. That answers "How does a SaaS company answer a customer security questionnaire about email security?"
Who it's for
If you answer customer security questionnaires for a SaaS company, build one dated evidence pack for the email section and reuse it for every customer.
Watch out for
If your DMARC policy is still p=none, say so and give the date you plan to reach quarantine and then reject.
What AegisAI does
Removal needs write access your admin grants and can revoke. Every verdict comes with its reason in plain language, so your team can check it and share it.
Book a demo

See it on your own Google Workspace or Microsoft 365 tenant. No MX change.

Or get the Q3 2026 State of the AI Attack report (free, instant download)

Not ready for a demo? Check your domain.

How does a SaaS company answer a customer security questionnaire about email security?

A SaaS company answers each email item in a customer security questionnaire with a yes or no, the setting behind it and one piece of evidence. AegisAI investigates every email for what it is trying to do21. The evidence is a DNS record, an admin console screen, or an audit or retention export. Start with SPF, DKIM, DMARC and TLS, the controls NIST lists for enterprise email7.

The question "How does a SaaS company answer a customer security questionnaire about email security?" usually lands on one person at the company. If that is you, build one evidence pack and reuse it for every customer. To pick a product, read choosing email security for a SaaS company. For the filtering layer behind one of the answers, see inbound email security. Start with the template your customer sent.

What you can do by the end

  • Match each email item in a SIG or CAIQ questionnaire to the admin setting that answers it.
  • Collect the DNS record, console screen or log export that proves each answer.
  • Keep a dated evidence pack you can reuse for the next customer questionnaire.

Key takeaways

- The CAIQ v4.1 has 283 questions3.

- The Cloud Security Alliance accepts both CAIQ versions until December 20274.

- NIST SP 800-177 Rev. 1 covers SPF, DKIM and DMARC for the sending domain, plus TLS in transit.

- Google says to allow 48 hours after SPF or DKIM before you set up DMARC, starting at p=none10.

- Microsoft keeps audit records 180 days for non-E5 licenses and one year for E518.

The short answer

QuestionAnswerSource
How does a SaaS company answer a customer security questionnaire about email security?Answer each email item with a yes or no, the setting behind it and one piece of evidence. Start with SPF, DKIM, DMARC and TLS.NIST
What are the SIG and the CAIQ?The SIG is the Shared Assessments questionnaire for third-party risk5. The CAIQ is the Cloud Security Alliance set of yes or no control questions2.Shared Assessments press release; Cloud Security Alliance
What proves domain authentication?The published SPF, DKIM and DMARC records, and a DMARC policy value of none, quarantine or reject11.Google Workspace Admin Help
How long are audit records kept?Microsoft Purview keeps them 180 days for non-E5 licenses and one year for E518.Microsoft Learn

Short on time? Watch the explainer, or book a demo.

What are the SIG and the CAIQ?

They are two public questionnaire templates, one from the Cloud Security Alliance and one from Shared Assessments. Know which one you have before you answer.

The CAIQ comes from the Cloud Security Alliance. It is a set of yes or no questions that assess security controls2. It maps to the Cloud Controls Matrix, which has 207 controls across 17 security domains1. Version 4.1 has 283 questions3. The Cloud Security Alliance accepts both versions until December 20274. Check the version number on the customer's file before you copy old answers into it.

The SIG comes from Shared Assessments. Shared Assessments says the SIG has helped organizations standardize third-party risk assessment for more than two decades5. SIG EV moves the Excel workbook to a web platform, where users build SIG Lite, SIG Core or a custom assessment6. Ask the customer whether they sent SIG Lite, SIG Core or a custom build before you start.

Which email items should you prepare for?

Prepare for six email items, from domain authentication to mail retention. The first two come from NIST SP 800-177 Rev. 1.

  • SPF, DKIM and DMARC on every sending domain.
  • TLS between mail servers.
  • MFA for every user and every admin.
  • The phishing and malware protections turned on, and any layer you add.
  • Audit logging, with what is logged, who can search it and for how long.
  • Mail retention, and what overrides it.

Open the customer file and tag each email question with one of these six items.

Build each answer in this order

Start with SPF, because Google says to allow 48 hours after SPF or DKIM before you set up DMARC10.

  1. Publish SPF. In Google Workspace the record is v=spf1 include:_spf.google.com ~all, and SPF can take up to 48 hours to start working8. In Microsoft 365 the record is v=spf1 include:spf.protection.outlook.com -all when Microsoft 365 is the only mail source12. Keep one SPF record per domain. Attach a DNS lookup of the TXT record.

  2. Turn on DKIM. In the Google Admin console, go to Apps, then Google Workspace, then Gmail, then Authenticate email9. Google offers a 2048 bit key where the domain provider supports it, and DKIM can take up to 48 hours to start working9. Attach a screenshot of the Authenticate email page for your domain, showing the DKIM status.

  3. Publish DMARC. Add a TXT record named _dmarc at your domain host, starting at p=none, 48 hours after SPF or DKIM. Then move to quarantine, which marks failing mail as spam, and to reject, which rejects it. Microsoft gives the same order for every custom domain and subdomain13. Attach the DMARC TXT record and the date of each policy change.

  4. Confirm TLS. Gmail always tries to send over a secure TLS connection by default16. The Secure transport (TLS) compliance setting bounces outgoing mail and rejects incoming mail that does not use TLS. In the Google Admin console, go to Apps, then Google Workspace, then Gmail, then Compliance16. Attach a screenshot of the setting, with the partner domains it covers.

  5. Prove MFA. In Google Workspace, 2-Step Verification can be optional or required, and Google is enforcing it for administrator accounts14. In Microsoft 365, security defaults require every user to register for MFA, require it for admins and block legacy authentication15. Attach the enforcement setting and the enrollment report.

  6. List the filtering. Google's advanced settings cover suspicious attachments and scripts, links behind short URLs and external images, and spoofing of domain and employee names17. AegisAI reports on its inbound email security page that 3 in 10 confirmed phishing emails cleared native Gmail and Microsoft filters in Q3 202622. Attach a screenshot of each setting, plus the name of any added layer.

  7. Show the audit trail. Microsoft Purview audit search is on by default for enterprise organizations. Gmail log events search needs the Audit & Investigation admin privilege and shows the last 7 days by default19. Attach a sample search with the date range visible.

  8. State retention. In Google Vault, Gmail retention starts the day a message is sent or received, and can be a set number of days or indefinite20. Holds take precedence over retention rules. Attach the retention rule and any holds.

Date every screenshot on the day you take it.

Use this evidence table for the email section

Copy each answer into the customer file and attach the evidence named in its row.

Questionnaire itemAnswer to giveEvidence to attachWhere the evidence comes from
SPF on sending domainsYes, one record per domainDNS TXT lookupYour DNS provider
DKIM signingYes, 2048 bit key where supportedAuthenticate email pageGoogle Admin console
DMARC policyCurrent p value and the date you reach rejectDMARC TXT record, change datesYour DNS provider
TLS in transitTLS by default, enforced for named partnersSecure transport (TLS) compliance settingGoogle Admin console
MFA for users and adminsRequired for all, enforced for adminsEnforcement setting, enrollment reportGoogle Admin console or Microsoft Entra ID
Phishing and malware filteringSettings on, plus any added layerScreenshot of each settingGoogle Admin console
Audit loggingOn, with retention period and the role that searches itSample audit searchMicrosoft Purview or Gmail log events
Mail retention and holdsRetention period, holds override itRetention rule and holds listGoogle Vault

Store the table and its evidence in one folder, and update it when a setting changes.

How AegisAI handles this

AegisAI investigates every email for what it is trying to do, and removes the ones that fail from every mailbox they reached. It reads mail through the Microsoft 365 or Google Workspace API after delivery23. Removal needs write access your admin grants and can revoke24. Every verdict comes with its reason in plain language, so your team can check it and share it25.

Book a demoSee inbound email security

See your own records: Check your domain.

How to measure it in 30 days

Track three numbers, each from a record you already keep.

  • Email items answered from the evidence pack, against all email items in the last questionnaire.
  • The DMARC policy value on each sending domain, and the date it changed.
  • Accounts enrolled in 2-Step Verification or MFA, against all accounts.

For the added filtering layer, book a live demo. Compare the three numbers on day 30.

Questions people ask

How does a SaaS company answer a customer security questionnaire about email security?

Answer each email item with a yes or no, the setting behind it and one piece of evidence. Cover SPF, DKIM, DMARC and TLS first. For the filtering item, see the section How AegisAI handles this.

What is the difference between the SIG and the CAIQ?

The SIG is the Shared Assessments questionnaire for third-party risk, built as SIG Lite, SIG Core or a custom assessment. The CAIQ is the Cloud Security Alliance set of yes or no questions mapped to the Cloud Controls Matrix.

Can we answer yes to DMARC if our policy is p=none?

Answer yes to a published record, and state the policy value. Google and Microsoft both start at none and move to quarantine, then reject. Give the date you plan to reach reject.

What evidence do customers accept for MFA?

Attach the enforcement setting and the enrollment report. In Microsoft 365, security defaults require MFA registration for every user and block legacy authentication.

How long should we say email logs are kept?

Give the period your plan sets. Microsoft Purview keeps audit records 180 days for non-E5 licenses and one year for E5. Gmail log events search shows the last 7 days by default.

Sources

  1. (Cloud Security Alliance: Cloud Controls Matrix and CAIQ v4.1, 27 January 2026)
  2. (Cloud Security Alliance: CCM v4.1 transition timeline, 19 February 2026)
  3. (Shared Assessments press release: SIG Evolution launch, 17 March 2026)
  4. (NIST: SP 800-177 Rev. 1, Trustworthy Email, February 2019)
  5. (Google Workspace Admin Help: Set up SPF, read 18 November 2026)
  6. (Google Workspace Admin Help: Set up DKIM, read 18 November 2026)
  7. (Google Workspace Admin Help: Set up DMARC, read 18 November 2026)
  8. (Microsoft Learn: Set up SPF for Microsoft 365, 3 July 2026)
  9. (Microsoft Learn: Set up DMARC for Microsoft 365, 3 July 2026)
  10. (Google Workspace Admin Help: Protect your business with 2-Step Verification, read 18 November 2026)
  11. (Microsoft Learn: Security defaults in Microsoft Entra ID, 21 July 2025)
  12. (Google Workspace Admin Help: Send email over a secure TLS connection, read 18 November 2026)
  13. (Google Workspace Admin Help: Advanced phishing and malware protection, read 18 November 2026)
  14. (Microsoft Learn: Search the audit log, 19 June 2026)
  15. (Google Workspace Admin Help: Gmail log events, read 18 November 2026)
  16. (Google Workspace Admin Help: How retention works in Vault, read 18 November 2026)
  17. (AegisAI: email security for a lean IT team with no SOC)
  18. (AegisAI: Inbound email security, read 18 November 2026)
  19. (AegisAI: email security for SaaS companies)
  20. (AegisAI: demo request page)

Recent posts

Every email, investigated.