> An outside lab tested Gnuke under Google's CASA security program in November 2026, and Gnuke passed all 20 requirements. Read the letter and what was checked.

*Source: https://getgnuke.com/security*

# Security

Google requires apps that can read or change Gmail to pass a security assessment called CASA. An outside lab tested Gnuke in November 2026, and it passed every requirement.

- 20 of 20 passed
- Independent lab
- Renewed every year

**Independent security assessment** CASA, App Defense Alliance
Passed
Lab TAC Security Result All 20 requirements passed Level AL1, lab verified Valid November 13, 2026 to November 14, 2027 [Read the letter (PDF)](/files/gnuke-casa-letter-2026.pdf) ID e55d990f

## Who tested Gnuke, and how?

CASA (Cloud Application Security Assessment) is the App Defense Alliance's security standard for apps that connect to Google accounts. It builds on OWASP's Application Security Verification Standard, and Google requires it every year from apps with restricted Gmail access, which Gnuke needs to move mail to the Trash.

TAC Security, a lab the App Defense Alliance authorizes, assessed Gnuke at Assurance Level 1 (AL1). We gave the lab evidence for each requirement, and the lab checked it and ran its own tests where a requirement called for them. Its letter is dated November 13, 2026, and Google approved Gnuke's access to Gmail on November 16, 2026.

The letter covers the Gnuke phone app on Google Play and the App Store, the web app at [app.getgnuke.com](https://app.getgnuke.com/), and the Chrome extension.

## What did the lab check?

These are the 20 requirements on our letter, in the letter's own words and groups.

### Authentication 3 of 3 passed

- Implement strong password security measures
- Disable any default accounts for public application access interfaces
- Out of band verifiers shall be random and not reused

### Session management 4 of 4 passed

- URLs shall not expose authentication material
- Implement session invalidation on logout, user request, and password change
- Implement and secure application session tokens
- Protect sensitive account modifications

### Access control 3 of 3 passed

- Implement access control mechanisms to protect data and APIs
- Implement secure OAuth integrations to protect user data and prevent unauthorized access
- Application exposed administrative interfaces shall use appropriate multi-factor authentication

### Communications 1 of 1 passed

- Protect data through strong cryptography

### Data validation and sanitization 2 of 2 passed

- Implement validation & input sanitation
- Securely handle untrusted files

### Configuration 7 of 7 passed

- Keep all components up to date
- Disable debug modes in production environments
- The origin header shall not be used for authentication of access control decisions
- Protect application from subdomain takeover
- Do not log credentials or payment details
- Securely clear client storage during logout
- Securely store server-side secrets

## What does it mean, and what doesn't it mean?

### It means

- An independent lab checked Gnuke against CASA's security requirements and found no failures.
- Google accepted that result when it approved Gnuke's access to Gmail.
- We do it again every year. This letter is valid until November 14, 2027, and this page will show the next one.

### It doesn't mean

- That Google endorses Gnuke. Gnuke is an independent app, not made by or affiliated with Google.
- That nothing can ever go wrong. It's a check against a published standard, at CASA's first assurance level.
- That we read your mail. Gnuke still works in your browser or on your phone, and no Gnuke server sees your mail. [How Gnuke handles your mail](/privacy)

## Found a security problem?

Email [security@getgnuke.com](mailto:security@getgnuke.com) with what you found and how to reproduce it. We read every report.
