Cloud App Security Administration Guide for G Suite
- Cloud App Security
- Understanding Cloud App Security
- Configuring Cloud App Security
- Managing Quarantine for G Suite
- Using the SonicWall Cloud App Security Dashboard
- Managing Security Events
- Managing Policies
- Managing Spam and Anti-Phishing
- Managing Spam
- Customizing Warning Messages
- Managing Nickname Impersonation
- Managing the Anti-Phishing Exceptions
- Configuring and Using Click-Time Protection
- Using Cloud App Security Analytics
- Configuring Cloud Applications in the Cloud App Store
- Managing Security Applications in the Security App Store
- Managing Anomaly Exceptions
- Managing Security Tool Exceptions
- Using the System Log
- Managing Cloud App Security Licenses
- SonicWall Support
Understanding Email Security
The widespread adoption of G Suite makes it an easy target for every hacker. Never have they given so many mailboxes with identical security. Hackers also leverage the fact these cloud accounts are sources of authentication to other enterprise SaaS apps. This is the real and present danger of the cloud security monoculture. What bypasses one, bypasses all. Unfortunately, native cloud security is not enough. Secure Email Gateways (SEGs) are not built for the cloud, only secure inbound and outbound email, and broadcast themselves to hackers.
Given the many limitations of securing cloud email with traditional SEGs and security shortfalls within G Suite filters, a best-practice solution must be cloud-native and designed to augment, not replace, existing security layers. This ensures that the basic filtering as well as new attack signatures are constantly updated, while advanced threat analyses address modern targeted phishing and evolving zero-day attacks.
A best practice solution must:
- Block harmful messages, URLs, and attachments from reaching the inbox
- Scan all emails preventing insider threats from compromised or trusted internal accounts
- Synchronous threat management via Capture Cloud Platform
Cloud App Security complements the default security of G Suite by connecting within the G Suite environment via API and scanning emails after the email provider’s built-in security scan. This has several advantages over the proxy method utilized by SEGs.
By scanning after the default security of G Suite, Cloud App Security utilizes the built-in security features as opposed to scanning before default security in the case of SEGs. This allows Cloud App Security to focus on more sophisticated phishing attacks that are designed to bypass the filters in place by G Suite.
By connecting to the cloud environment via the G Suite API, Cloud App Security can extend their security beyond just inbound and outbound emails to scan internal emails as well for account compromised and data leakage.
- Before You Set Email Policies
- Managing Spam and Anti-Phishing
- Understanding Post-Delivery Email Recheck
Was This Article Helpful?
Help us to improve our support portal