Google CASA Verification: What It Is and Who Needs It

The short answer
Google CASA (Cloud Application Security Assessment) is the security assessment Google requires, every year, from apps that use restricted Gmail scopes such as gmail.modify and store or transmit that data on servers. An App Defense Alliance authorized lab validates the app against OWASP ASVS-based requirements and issues a Letter of Validation. It is a security baseline, not a Google endorsement.
What is Google CASA? The security assessment required for apps that use restricted Gmail scopes: levels, cost, timeline and how to check an app.
On this page
- 01What is Google CASA verification?
- 02Does an email app need CASA to connect to Gmail?
- 03CASA tiers vs assurance levels: Tier 2, AL1 and AL2
- 04How the CASA process works, step by step
- 05Getting CASA certified: cost, timeline and what the lab checks
- 06What happens if an app is not verified
- 07How to check whether an email app is Google verified
- 08Common misconceptions about Google CASA
- 09How CASA shows up in AI Emaily
What is Google CASA verification?#
Google CASA verification is the security assessment step of Google's restricted-scope review. Any app that requests a restricted Gmail scope, such as gmail.modify, and stores or transmits that mail data on its servers must pass it before Google approves the scope. An authorized lab validates the app against CASA requirements, then the developer sends the lab's Letter of Validation to Google.
CASA comes from the App Defense Alliance (ADA), and its requirements are built on the OWASP Application Security Verification Standard (ASVS). People call the result a CASA certification, assessment, audit or review; Google's own pages say security assessment. It repeats every year. Whether an app needs it depends on the scopes it asks for:
| Scopes the app requests | Who reviews it | Is CASA required? | Gmail example |
|---|---|---|---|
| Non-sensitive | No scope review (brand verification can still apply) | No | gmail.labels |
| Sensitive | Google's OAuth app verification | No | gmail.send |
| Restricted, but data never stored or sent through the developer's servers | Google's restricted-scope verification | No | gmail.readonly used only on the device |
| Restricted, with data stored or transmitted on servers | Google, plus an ADA authorized lab | Yes, every year | gmail.modify, gmail.readonly, mail.google.com |
Some apps are exempt from review
Does an email app need CASA to connect to Gmail?#
Almost always, if it is a full email client with a back end. Google's Gmail API scope table lists most of the scopes an email app needs as restricted: https://mail.google.com/, gmail.readonly, gmail.modify, gmail.compose, gmail.insert, gmail.metadata and gmail.settings.basic. Only a few are lighter. gmail.send is sensitive, and gmail.labels is non-sensitive.
gmail.compose is restricted too, so an app that only writes drafts is still in scope. Apps that reach Gmail over IMAP or SMTP with OAuth need the full https://mail.google.com/ scope, since Google documents it as the scope for IMAP, POP and SMTP access. Google's own guidance is to avoid that full-access scope unless an app must permanently delete mail and bypass the trash.
For a closer look at what each permission lets an app do, see restricted vs sensitive Gmail scopes and what Gmail OAuth permissions actually allow.
CASA tiers vs assurance levels: Tier 2, AL1 and AL2#
Older CASA material, assessor pages and some Google pages still talk about Tier 2 and Tier 3. Google's current Security Assessment help page uses assurance levels instead: every assessed app is assigned AL1 or AL2. The lower level is widely treated as the successor to Tier 2 and AL2 as the successor to Tier 3. The ADA does not publish an official one-to-one mapping, so follow the wording in your own notice from Google.
The developer does not pick the level. The ADA says the framework user (Google, in this case) sets the required level based on how sensitive the data is, how many users the app has, and other risk signals. Google adds that the level can go up as the user base or data practices change, and that an app validated at AL2 stays at AL2 in later years.
| AL1 | AL2 | |
|---|---|---|
| ADA label | Lab tested, lab verified | Lab tested, lab verified |
| How it is assessed | Authorized labs describe it as evidence the developer provides, such as scan results and a security questionnaire, verified by the lab | The lab tests the application, its deployment infrastructure and any user data storage |
| Requirements | All CASA requirements | All CASA requirements |
| Older name | Usually described as Tier 2 | Usually described as Tier 3 |
| Who gets it | Assigned by Google based on risk | Higher-risk apps, assigned by Google |
How the CASA process works, step by step#
CASA is the last step of restricted-scope verification, not the first. Google says to finish its other verification requirements before the assessment starts.
- 1
Submit the app for restricted-scope verification
The developer configures the OAuth consent screen, lists the scopes, links a privacy policy and justifies each restricted scope in the Google Cloud console.
- 2
Wait for Google's notice
Google's Trust and Safety team tells the developer when to start the security assessment and how to proceed.
- 3
Choose an ADA authorized lab
The ADA publishes its list of authorized labs. Firms such as Bishop Fox, DEKRA, NetSentries, TAC Security and Valuementor appear on it. Labs must be ISO/IEC 17025 accredited.
- 4
Complete the assessment and fix findings
The app is checked against the CASA requirements, which come from OWASP ASVS. Findings are fixed and rechecked until every requirement is met.
- 5
Send the Letter of Validation to Google
Once the app passes, the lab issues a Letter of Validation (LOV). The developer submits it to Trust and Safety to complete the review.
- 6
Revalidate every year
Google requires reverification and a new assessment at least every 12 months from the assessor's approval date, and emails the developer when it is due. Keeping restricted scopes depends on it.
Getting CASA certified: cost, timeline and what the lab checks#
Google does not run the assessment and says it has no control over it. Issues go to the lab you chose. These are the figures Google publishes. Its Google Health API verification page gives them for CASA in general, and the Gmail-specific pages give no numbers.
- What the lab checks: CASA requirements drawn from OWASP ASVS, covering areas such as authentication, session management, access control, data protection and cryptography.
- What it is not: a feature review, a privacy-policy audit or a check on how the vendor uses AI. Those questions stay with you.
- Budget for the year, not just the first pass: the assessment and its fee come back every 12 months.
| Question | What Google says | Notes |
|---|---|---|
| Who gets paid | Fees are payable to the third-party assessor | Google itself does not list a fee |
| Cost | $500 to $4,500 USD, depending on the app's complexity | Labs set their own prices; the higher level costs more |
| Assessment time | 2 to 3 weeks for tier-2 apps, 4 to 6 weeks for tier-3 apps | Time spent fixing findings comes on top |
| Whole restricted-scope review | Can take several weeks | Brand verification is usually 2 to 3 business days |
| Shortcuts | HITRUST, SOC 2 and ISO/IEC 27001 certifications may expedite CASA | Through the CASA accelerator |
| Renewal | Every year | A new assessment each cycle |
What happens if an app is not verified#
Google shows an unverified app screen before the consent screen when an app requests sensitive or restricted scopes and has not finished verification, or when the scopes in its code do not match its consent screen. Until it is verified, the app is limited to 100 new users. Google's Security Checkup can also list it as risky and unverified.
That warning is about verification as a whole, not only CASA. An app showing it might be new, mid-review, waiting on its lab, or missing an earlier step such as brand verification. From the warning alone you cannot tell which.
Inside Google Workspace, verification and admin approval are separate. In the Admin console (Security, then Access and data control, then API controls), admins set each app to Trusted, Limited, Specific Google data or Blocked, and can restrict Gmail to configured apps only. Verified apps show a Verified label there, but Google does not say verification grants access by itself.
For team rollouts, check admin policy too
How to check whether an email app is Google verified#
There is no single public lookup to rely on, so check the app itself and ask the vendor.
- 1
Read the screens when you connect
A verified app goes straight to Google's consent screen, with no unverified warning first. Read the list of permissions it asks for.
- 2
Match the scopes to the requirement
If it asks for full mailbox access (read, change or delete mail) and runs a cloud service, it is in CASA scope. Ask the vendor which assurance level it was assigned and when its last Letter of Validation was issued.
- 3
Review it later in your Google Account
Your Google Account lists every third-party app with access and what it can see. Workspace admins can check the Verified label under API controls. See how to review third-party apps with Gmail access.
Common misconceptions about Google CASA#
- Is CASA a Google endorsement? No. It shows the app met a security baseline at the time of assessment, not that Google vouches for its quality, features or reliability.
- Does an unverified warning mean the app failed CASA? No. It means verification is not complete, which can have several causes, including steps that come before CASA.
- Does CASA cover everything a vendor does with my mail? No. It checks application security against CASA requirements. Ask separately about AI model use, sub-processors and retention; see does AI email train on your emails.
- Is CASA the same as SOC 2? No. Google accepts SOC 2, ISO/IEC 27001 and HITRUST to speed CASA up, but a CASA letter is not a SOC 2 report.
- Is passing once enough? No. Restricted-scope apps revalidate every year, so ask when the most recent assessment was completed.

How CASA shows up in AI Emaily#
We build AI Emaily, so this is our own example. AI Emaily connects to Gmail with the restricted gmail.modify scope, which it needs to label, archive and triage mail, and it does not request the full https://mail.google.com/ scope. That puts it in CASA scope.
Our CASA Tier 2 / AL1 assessment is completed, verified by an authorized lab, and Google verified our consent screen in July 2026. It renews annually. Workspace admins who restrict Gmail access still decide whether to trust it. Details are on our security page, and the vendor question list covers what else to ask.
Frequently asked
See it in AI Emaily
Keep reading
Sources
- Google for Developers — Restricted scope verification
- Google Cloud Help — Security assessment
- Google for Developers — Gmail API scopes
- Google for Developers — Google Health API app verification (CASA fees and timeline)
- Google Cloud Help — Unverified apps
- App Defense Alliance — CASA assurance levels
- App Defense Alliance — Authorized labs
- Google Workspace Admin Help — Control which apps access Google Workspace data

Written by
Nafiul HasanNafiul Hasan is an entrepreneur and AI automation system builder with 10+ years of experience turning messy, manual workflows into reliable automated systems. He designs and ships AI enterprise solutions end-to-end — the agent logic, the data plumbing, and the product people actually use — and founded AI Emaily to give busy professionals their attention back. He writes here from the builder's seat: what works, what breaks, and how to put AI to work without giving up control.