Back to catalog
Static reviewDevelopment

Skill dossier

implementing-google-workspace-phishing-protection

Source declaration

Configures Google Workspace advanced phishing and malware protection settings in the Admin Console — pre-delivery message scanning, attachment protection, spoofing/impersonation detection, and Enhanced Safe Browsing enforcement. Use when hardening Gmail against phishing, spoofing, and malware, or when tuning Workspace email security policies.

The author's original description, preserved in English. It describes intent, not verified performance.

Configures Google Workspace advanced phishing and malware protection settings in the Admin Console — pre-delivery message scanning, attachment protection, spoofing/impersonation detection, and Enhanced Safe Browsing enforcement. Use when hardening Gmail against phishing, spoofing, and malware, or when tuning Workspace email security policies.

developmentreferencesscripts

Research summary

Machine-generated analysis; pending human review

These observations come from deterministic source parsing, not a human security review or controlled task evaluation.

Configures Google Workspace advanced phishing and malware protection settings in the Admin Console — pre-delivery message scanning, attachment protection, spoofing/impersonation detection, and Enhanced Safe Browsing enforcement. Use when hardening Gmail against phishing, spoofing, and malware, or when tuning Workspace email security policies. This bilingual summary is generated deterministically from collected source text and file structure; it is pending human editorial review.

Review scope

Deterministic static analysis of collected SKILL.md and supporting text/code. Machine-assisted candidates and findings await human editorial review; no dynamic behavior or effect is assessed.

Observable capabilities

  • Workflow [Source statement; provisional, not tested. Evidence: skills/implementing-google-workspace-phishing-protection/SKILL.md:L81]
  • Step 1: Configure Advanced Phishing Protection [Source statement; provisional, not tested. Evidence: skills/implementing-google-workspace-phishing-protection/SKILL.md:L83]
  • Step 2: Enable Enhanced Pre-Delivery Scanning [Source statement; provisional, not tested. Evidence: skills/implementing-google-workspace-phishing-protection/SKILL.md:L91]
  • Step 3: Configure Attachment Protection [Source statement; provisional, not tested. Evidence: skills/implementing-google-workspace-phishing-protection/SKILL.md:L98]
  • Step 4: Enable Enhanced Safe Browsing [Source statement; provisional, not tested. Evidence: skills/implementing-google-workspace-phishing-protection/SKILL.md:L105]
  • Step 5: Enroll High-Risk Users in Advanced Protection Program [Source statement; provisional, not tested. Evidence: skills/implementing-google-workspace-phishing-protection/SKILL.md:L112]
  • Step 6: Configure Email Authentication [Source statement; provisional, not tested. Evidence: skills/implementing-google-workspace-phishing-protection/SKILL.md:L119]

Limitations & scope

  • Static analysis cannot assess runtime behavior, command success, network reachability, or model output quality.
  • No commands, scripts, network requests, model calls, or controlled skill executions were performed.
  • Category, tags, capabilities, workflows, and bilingual editorial summaries are deterministic candidates pending human review, not verified outcomes.
  • Exact token counts are unavailable until a later pipeline performs and records an official model-specific count.

Relevant for

  • Practitioners evaluating whether to inspect and install the source skill; this audience is inferred from the product context, not measured usage. [Evidence: skills/implementing-google-workspace-phishing-protection/SKILL.md:L1-L60]

What ships with the skill

The file inventory comes from the collected source at the recorded commit. Paths and sizes are structural observations, not a measure of quality.

files
8
Markdown files
5
scripts
2
references
4
Size
36.8 KB
Structural complexity
Low

File inventory

PathTypeBytes
skills/implementing-google-workspace-phishing-protection/assets/template.mdReference830 B
skills/implementing-google-workspace-phishing-protection/LICENSEOther11 KB
skills/implementing-google-workspace-phishing-protection/references/api-reference.mdReference1.8 KB
skills/implementing-google-workspace-phishing-protection/references/standards.mdReference1.3 KB
skills/implementing-google-workspace-phishing-protection/references/workflows.mdReference1.4 KB
skills/implementing-google-workspace-phishing-protection/scripts/agent.pyScript7.6 KB
skills/implementing-google-workspace-phishing-protection/scripts/process.pyScript7.3 KB
skills/implementing-google-workspace-phishing-protection/SKILL.mdInstruction5.6 KB

SKILL.md frontmatter

{
  "name": "implementing-google-workspace-phishing-protection",
  "description": "Configures Google Workspace advanced phishing and malware protection settings in the Admin Console — pre-delivery message scanning, attachment protection, spoofing/impersonation detection, and Enhanced Safe Browsing enforcement. Use when hardening Gmail against phishing, spoofing, and malware, or when tuning Workspace email security policies.",
  "domain": "cybersecurity",
  "subdomain": "phishing-defense",
  "tags": [
    "google-workspace",
    "gmail",
    "phishing",
    "email-security",
    "safe-browsing",
    "anti-spoofing",
    "admin-console"
  ],
  "version": "1.0",
  "author": "mahipal",
  "license": "Apache-2.0",
  "nist_csf": [
    "PR.AT-01",
    "DE.CM-09",
    "RS.CO-02",
    "DE.AE-02"
  ],
  "mitre_attack": [
    "T1566",
    "T1598",
    "T1534",
    "T1036",
    "T1027"
  ],
  "mitre_f3": {
    "version": "1.1",
    "tactics": [
      "reconnaissance",
      "resource-development",
      "initial-access",
      "stealth"
    ],
    "techniques": [
      {
        "id": "T1660",
        "name": "Phishing",
        "tactic": "initial-access",
        "source": "attack"
      },
      {
        "id": "T1598",
        "name": "Phishing for Information",
        "tactic": "reconnaissance",
        "source": "attack"
      },
      {
        "id": "T1672",
        "name": "Email Spoofing",
        "tactic": "stealth",
        "source": "attack"
      },
      {
        "id": "F1032",
        "name": "Impersonate Official",
        "tactic": "initial-access",
        "source": "f3"
      },
      {
        "id": "F1031",
        "name": "Impersonate Account Holder",
        "tactic": "initial-access",
        "source": "f3"
      },
      {
        "id": "F1020.002",
        "name": "Create Fake Materials: Fake Website",
        "tactic": "resource-development",
        "source": "f3"
      }
    ]
  }
}

A reading of the operating sequence

This workflow reconstructs the apparent sequence from source material. Unless controlled evaluation is explicitly recorded, it is provisional—not an observed trace.

  1. 01
    Action

    Overview

    Source-described action candidate under “Overview”; not verified execution.

  2. 02
    Decision

    When to Use

    Source-described decision candidate under “When to Use”; not verified execution.

  3. 03
    Action

    Workflow

    Source-described action candidate under “Workflow”; not verified execution.

  4. 04
    Action

    Step 1: Configure Advanced Phishing Protection

    Source-described action candidate under “Step 1: Configure Advanced Phishing Protection”; not verified execution.

  5. 05
    Action

    Navigate to Admin Console > Apps > Google Workspace > Gmail > Safety

    Source-described action candidate under “Step 1: Configure Advanced Phishing Protection”; not verified execution.

  6. 06
    Action

    Enable "Protect against domain spoofing based on similar domain names"

    Source-described action candidate under “Step 1: Configure Advanced Phishing Protection”; not verified execution.

Inspect all extracted workflow candidates (41 candidate steps)
  1. 07
    Action

    Enable "Protect against spoofing of employee names"

    Source-described action candidate under “Step 1: Configure Advanced Phishing Protection”; not verified execution.

  2. 08
    Action

    Enable "Protect against inbound emails spoofing your domain"

    Source-described action candidate under “Step 1: Configure Advanced Phishing Protection”; not verified execution.

  3. 09
    Action

    Set action for detected spoofing: quarantine or move to spam with warning banner

    Source-described action candidate under “Step 1: Configure Advanced Phishing Protection”; not verified execution.

  4. 10
    Action

    Apply settings to all organizational units or specific high-risk groups

    Source-described action candidate under “Step 1: Configure Advanced Phishing Protection”; not verified execution.

  5. 11
    Action

    Step 2: Enable Enhanced Pre-Delivery Scanning

    Source-described action candidate under “Step 2: Enable Enhanced Pre-Delivery Scanning”; not verified execution.

  6. 12
    Action

    In Safety settings, enable "Enhanced pre-delivery message scanning"

    Source-described action candidate under “Step 2: Enable Enhanced Pre-Delivery Scanning”; not verified execution.

  7. 13
    Action

    This adds additional delay (seconds) to scan messages more thoroughly

    Source-described action candidate under “Step 2: Enable Enhanced Pre-Delivery Scanning”; not verified execution.

  8. 14
    Action

    Configure to detect phishing attempts that evade initial filters

    Source-described action candidate under “Step 2: Enable Enhanced Pre-Delivery Scanning”; not verified execution.

  9. 15
    Action

    Enable "Identify links behind shortened URLs"

    Source-described action candidate under “Step 2: Enable Enhanced Pre-Delivery Scanning”; not verified execution.

  10. 16
    Action

    Enable "Scan linked images" for image-based phishing detection

    Source-described action candidate under “Step 2: Enable Enhanced Pre-Delivery Scanning”; not verified execution.

  11. 17
    Action

    Step 3: Configure Attachment Protection

    Source-described action candidate under “Step 3: Configure Attachment Protection”; not verified execution.

  12. 18
    Action

    Enable "Protect against encrypted attachments from untrusted senders"

    Source-described action candidate under “Step 3: Configure Attachment Protection”; not verified execution.

  13. 19
    Action

    Enable "Protect against attachments with scripts from untrusted senders"

    Source-described action candidate under “Step 3: Configure Attachment Protection”; not verified execution.

  14. 20
    Action

    Enable "Protect against anomalous attachment types in emails"

    Source-described action candidate under “Step 3: Configure Attachment Protection”; not verified execution.

  15. 21
    Action

    Configure action: warn users, move to spam, or quarantine

    Source-described action candidate under “Step 3: Configure Attachment Protection”; not verified execution.

  16. 22
    Action

    Create exceptions for known legitimate encrypted file senders

    Source-described action candidate under “Step 3: Configure Attachment Protection”; not verified execution.

  17. 23
    Action

    Step 4: Enable Enhanced Safe Browsing

    Source-described action candidate under “Step 4: Enable Enhanced Safe Browsing”; not verified execution.

  18. 24
    Action

    Navigate to Admin Console > Security > Gmail Enhanced Safe Browsing

    Source-described action candidate under “Step 4: Enable Enhanced Safe Browsing”; not verified execution.

  19. 25
    Action

    Enable Enhanced Safe Browsing for the organization (off by default)

    Source-described action candidate under “Step 4: Enable Enhanced Safe Browsing”; not verified execution.

  20. 26
    Action

    This provides real-time protection against phishing URLs in emails

    Source-described action candidate under “Step 4: Enable Enhanced Safe Browsing”; not verified execution.

  21. 27
    Action

    Configure at organizational unit level for phased rollout

    Source-described action candidate under “Step 4: Enable Enhanced Safe Browsing”; not verified execution.

  22. 28
    Action

    Monitor user feedback for false positive impact

    Source-described action candidate under “Step 4: Enable Enhanced Safe Browsing”; not verified execution.

  23. 29
    Action

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

    Source-described action candidate under “Step 5: Enroll High-Risk Users in Advanced Protection Program”; not verified execution.

  24. 30
    Action

    Identify high-privilege accounts: super admins, executives, finance leadership

    Source-described action candidate under “Step 5: Enroll High-Risk Users in Advanced Protection Program”; not verified execution.

  25. 31
    Action

    Enroll users in Google's Advanced Protection Program (APP)

    Source-described action candidate under “Step 5: Enroll High-Risk Users in Advanced Protection Program”; not verified execution.

  26. 32
    Action

    APP requires FIDO2 security keys for authentication

    Source-described action candidate under “Step 5: Enroll High-Risk Users in Advanced Protection Program”; not verified execution.

  27. 33
    Action

    APP blocks third-party app access unless explicitly approved

    Source-described action candidate under “Step 5: Enroll High-Risk Users in Advanced Protection Program”; not verified execution.

  28. 34
    Action

    APP provides enhanced scanning for Gmail and Drive downloads

    Source-described action candidate under “Step 5: Enroll High-Risk Users in Advanced Protection Program”; not verified execution.

  29. 35
    Action

    Step 6: Configure Email Authentication

    Source-described action candidate under “Step 6: Configure Email Authentication”; not verified execution.

  30. 36
    Action

    Publish SPF record: `v=spf1 include:spf.google.com all`

    Source-described action candidate under “Step 6: Configure Email Authentication”; not verified execution.

  31. 37
    Action

    Enable DKIM signing in Admin Console > Apps > Google Workspace > Gmail > Authenticate email

    Source-described action candidate under “Step 6: Configure Email Authentication”; not verified execution.

  32. 38
    Action

    Configure DMARC with monitoring: `v=DMARC1; p=none; rua=mailto:[email protected]`

    Source-described action candidate under “Step 6: Configure Email Authentication”; not verified execution.

  33. 39
    Action

    Progress DMARC to enforcement per organizational readiness

    Source-described action candidate under “Step 6: Configure Email Authentication”; not verified execution.

  34. 40
    Action

    Tools & Resources

    Source-described action candidate under “Tools & Resources”; not verified execution.

  35. 41
    Action

    Validation

    Source-described action candidate under “Validation”; not verified execution.

Potential risk surfaces

Static findings identify points to inspect before installation. They do not establish that a skill is safe, malicious, or effective.

Items warrant review

20 deterministic lexical finding(s) require review across the collected text. Findings can occur in documentation and do not prove execution or exploitability; binary-only files were not scanned.

Network accessObserved
File writesObserved
Credential useNot observed
Medium

Network access is mentioned

6 occurrences

A URL or network client appears in this source line. Review destinations, data sent, and trust boundaries; static text cannot establish actual network activity. This rule matched 6 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Note

File modification is described or implemented

14 occurrences

This line contains a possible file-write or redirection operation. Check destination paths and overwrite behavior; the static review did not write any file. This rule matched 14 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Where context can be spent

Discovery, activation, and resource layers have different meanings. Exact values appear only when the official token-counting method was run with a named model.

Exact token counts unavailable

All token values, including per-file inventory, are null until the pipeline performs an official exact count with an explicit model.

No token measurement was recorded with the required official method. This dossier does not substitute character counts, file sizes, or estimates.

Controlled evaluation

No controlled evaluation

This skill has only the evidence identified above. No task success, token efficiency, latency, or quality advantage is claimed.

Not tested

Use with the source in view

Install command
Inspect the pinned source at https://github.com/mukul975/Anthropic-Cybersecurity-Skills/blob/54a798831d2266a3ca61ce68a7acb80b81160d57/skills/implementing-google-workspace-phishing-protection/SKILL.md and follow the source repository's installation instructions. No installation was performed or verified by this static analyzer. Source license: Apache-2.0.

Prerequisites

  • Static analysis cannot assess runtime behavior, command success, network reachability, or model output quality.
  • No commands, scripts, network requests, model calls, or controlled skill executions were performed.
  • Category, tags, capabilities, workflows, and bilingual editorial summaries are deterministic candidates pending human review, not verified outcomes.
  • Exact token counts are unavailable until a later pipeline performs and records an official model-specific count.

Example prompts

Not provided

A decision, with its limits attached

Strengths

  • The snapshot contains 8 collected file(s), 5 Markdown file(s), and 2 script file(s), enabling source-level inspection. [Evidence: skills/implementing-google-workspace-phishing-protection/SKILL.md:L1]

Considerations

  • No functional, security, or model-quality result has been established. Human review must inspect source context and all cited findings before installation or publication.
Research conclusion

Provisional deterministic static inventory only; pending human editorial review and, separately, controlled evaluation. No install recommendation, security assurance, or effectiveness claim is made.

Traceable by construction

The dossier is a time-bound reading of a public artifact, not an endorsement. Use the source link to inspect the exact upstream material.

mukul975Anthropic-Cybersecurity-Skillsskills/implementing-google-workspace-phishing-protection
Source type
Community
Commit
54a798831d2266a3ca61ce68a7acb80b81160d57
Collected
20 Nov 2026
Last checked
20 Nov 2026
Upstream license
Apache-2.0
Repository stars
36,446
Content basis

Deterministic lexical parsing, YAML frontmatter validation, file inventory, source-described workflow extraction, and heuristic provisional classification of the supplied files only. Generated by machine; no LLM, execution, dynamic testing, or human editorial approval.