Implementing Google Workspace Phishing Protection

Implementing Google Workspace Phishing Protection

Overview

Google Workspace provides advanced phishing and malware protection through the Admin Console under Apps > Google Workspace > Gmail > Safety. Key features include Enhanced Pre-Delivery Scanning that examines messages more thoroughly before they reach inboxes, attachment and link protection that scans for malware and checks against known malicious sites, and spoofing detection for domain and employee name impersonation. Google's Advanced Protection Program (APP) provides the strongest account security for high-privilege users.

When to Use

Trigger phrases:

• "implementing google workspace phishing protection"

• "Configure Google Workspace advanced phishing and malware protection settings inc"

• When deploying or configuring implementing google workspace phishing protection capabilities in your environment

• When establishing security controls aligned to compliance requirements

• When building or improving security architecture for this domain

• When conducting security assessments that require this implementation

Prerequisites

• Google Workspace Business Standard or higher license
• Gmail Settings administrator privilege
• Understanding of organizational email flow and third-party integrations
• Access to Google Admin Console (admin.google.com)
• DNS management access for SPF, DKIM, DMARC configuration

Workflow

# Example: IOC detection
import re

IOC_PATTERNS = {
    "ip": r"\b(?:\d{1,3}\.){3}\d{1,3}\b",
    "domain": r"\b[a-z0-9-]+\.[a-z]{2,}\b",
    "hash_md5": r"\b[a-f0-9]{32}\b",
    "hash_sha256": r"\b[a-f0-9]{64}\b",
}

def extract_iocs(text: str) -> dict:
    return {k: re.findall(v, text) for k, v in IOC_PATTERNS.items()}

1. Isolate the sample — ensure the malware is in a sandboxed environment with no network access
2. Record file metadata — hash the sample and note file type, size, and compile timestamp
3. Static analysis — examine strings, imports, and disassembled code without execution
4. Dynamic analysis — execute in a monitored sandbox and record behavior (file, registry, network)
5. Document IOCs — extract indicators of compromise and write the analysis report

Step 1: Configure Advanced Phishing Protection

• Navigate to Admin Console > Apps > Google Workspace > Gmail > Safety
• Enable "Protect against domain spoofing based on similar domain names"
• Enable "Protect against spoofing of employee names"
• Enable "Protect against inbound emails spoofing your domain"
• Set action for detected spoofing: quarantine or move to spam with warning banner
• Apply settings to all organizational units or specific high-risk groups

Step 2: Enable Enhanced Pre-Delivery Scanning

• In Safety settings, enable "Enhanced pre-delivery message scanning"
• This adds additional delay (seconds) to scan messages more thoroughly
• Configure to detect phishing attempts that evade initial filters
• Enable "Identify links behind shortened URLs"
• Enable "Scan linked images" for image-based phishing detection

Step 3: Configure Attachment Protection

• Enable "Protect against encrypted attachments from untrusted senders"
• Enable "Protect against attachments with scripts from untrusted senders"
• Enable "Protect against anomalous attachment types in emails"
• Configure action: warn users, move to spam, or quarantine
• Create exceptions for known legitimate encrypted file senders

Step 4: Enable Enhanced Safe Browsing

• Navigate to Admin Console > Security > Gmail Enhanced Safe Browsing
• Enable Enhanced Safe Browsing for the organization (off by default)
• This provides real-time protection against phishing URLs in emails
• Configure at organizational unit level for phased rollout
• Monitor user feedback for false positive impact

Step 5: Enroll High-Risk Users in Advanced Protection Program

• Identify high-privilege accounts: super admins, executives, finance leadership
• Enroll users in Google's Advanced Protection Program (APP)
• APP requires FIDO2 security keys for authentication
• APP blocks third-party app access unless explicitly approved
• APP provides enhanced scanning for Gmail and Drive downloads

Step 6: Configure Email Authentication

• Publish SPF record: v=spf1 include:_spf.google.com ~all
• Enable DKIM signing in Admin Console > Apps > Google Workspace > Gmail > Authenticate email
• Configure DMARC with monitoring: v=DMARC1; p=none; rua=mailto:dmarc@company.com
• Progress DMARC to enforcement per organizational readiness

When NOT to Use

• You need to test the implementation (use performing-* skills)
• Task is about configuring existing tools (use configuring-* skills)
• You need to analyze security events (use analyzing-* skills)
• Task is about building detection rules (use building-* skills)
• You don't have access to the target environment
• Task requires vendor-specific expertise (consult vendor docs)

Red Flags

• Performing actions without explicit written authorization from the asset owner
• Testing against production systems without a defined scope and rules of engagement
• Analyzing malware on a machine connected to the production network
• Failing to isolate the analysis environment from the internet
• Executing samples without proper containment (VM, sandbox)

Verification

• All steps executed successfully against a test environment before production use
• Output documented with screenshots or logs demonstrating expected behavior
• Sample hash recorded and verified (MD5, SHA-1, SHA-256)
• Analysis environment confirmed isolated from production network
• Indicators of compromise (IOCs) extracted and documented

Tools & Resources

• Google Admin Console: Central management for all security settings
• Google Workspace Security Investigation Tool: Threat analysis and response
• Google Security Center: Security health recommendations and dashboard
• Gmail Security Sandbox: Attachment detonation for enterprise licenses
• Google Advanced Protection Program: Strongest account security

Validation

• Spoofing protection blocks test email with lookalike domain
• Pre-delivery scanning catches test phishing with delayed weaponization
• Attachment protection warns on test encrypted attachment
• Enhanced Safe Browsing blocks known phishing URL clicked in email
• APP-enrolled accounts reject non-FIDO2 authentication attempts
• SPF, DKIM, DMARC all pass for outbound messages

Process

1. Analyze the task requirements
2. Apply domain expertise
3. Verify output quality

Anti-Rationalization Table