Back to catalog
Static reviewDevelopment

Skill dossier

implementing-proofpoint-email-security-gateway

Source declaration

Deploy and configure Proofpoint Email Protection as a secure email gateway to detect and block phishing, malware, BEC, and spam before messages reach user inboxes.

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

Deploy and configure Proofpoint Email Protection as a secure email gateway to detect and block phishing, malware, BEC, and spam before messages reach user inboxes.

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.

Deploy and configure Proofpoint Email Protection as a secure email gateway to detect and block phishing, malware, BEC, and spam before messages reach user inboxes. 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-proofpoint-email-security-gateway/SKILL.md:L108]
  • Step 1: Plan Mail Flow Architecture [Source statement; provisional, not tested. Evidence: skills/implementing-proofpoint-email-security-gateway/SKILL.md:L110]
  • Step 2: Configure Proofpoint Policies [Source statement; provisional, not tested. Evidence: skills/implementing-proofpoint-email-security-gateway/SKILL.md:L117]
  • Step 3: Deploy Email Authentication [Source statement; provisional, not tested. Evidence: skills/implementing-proofpoint-email-security-gateway/SKILL.md:L124]
  • Step 4: Enable Advanced Threat Protection [Source statement; provisional, not tested. Evidence: skills/implementing-proofpoint-email-security-gateway/SKILL.md:L130]
  • Step 5: Migrate MX Records [Source statement; provisional, not tested. Evidence: skills/implementing-proofpoint-email-security-gateway/SKILL.md:L137]
  • Step 6: Tune and Optimize [Source statement; provisional, not tested. Evidence: skills/implementing-proofpoint-email-security-gateway/SKILL.md:L144]

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-proofpoint-email-security-gateway/SKILL.md:L1-L63]

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
48.3 KB
Structural complexity
Low

File inventory

PathTypeBytes
skills/implementing-proofpoint-email-security-gateway/assets/template.mdReference1.7 KB
skills/implementing-proofpoint-email-security-gateway/LICENSEOther11 KB
skills/implementing-proofpoint-email-security-gateway/references/api-reference.mdReference5.1 KB
skills/implementing-proofpoint-email-security-gateway/references/standards.mdReference1.7 KB
skills/implementing-proofpoint-email-security-gateway/references/workflows.mdReference2.7 KB
skills/implementing-proofpoint-email-security-gateway/scripts/agent.pyScript8.2 KB
skills/implementing-proofpoint-email-security-gateway/scripts/process.pyScript11.1 KB
skills/implementing-proofpoint-email-security-gateway/SKILL.mdInstruction6.9 KB

SKILL.md frontmatter

{
  "name": "implementing-proofpoint-email-security-gateway",
  "description": "Deploy and configure Proofpoint Email Protection as a secure email gateway to detect and block phishing, malware, BEC, and spam before messages reach user inboxes.",
  "domain": "cybersecurity",
  "subdomain": "phishing-defense",
  "tags": [
    "email-security",
    "proofpoint",
    "secure-email-gateway",
    "phishing",
    "anti-spam",
    "anti-malware",
    "bec",
    "email-filtering"
  ],
  "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",
      "initial-access",
      "stealth",
      "positioning"
    ],
    "techniques": [
      {
        "id": "T1598",
        "name": "Phishing for Information",
        "tactic": "reconnaissance",
        "source": "attack"
      },
      {
        "id": "T1660",
        "name": "Phishing",
        "tactic": "initial-access",
        "source": "attack"
      },
      {
        "id": "T1672",
        "name": "Email Spoofing",
        "tactic": "stealth",
        "source": "attack"
      },
      {
        "id": "F1032",
        "name": "Impersonate Official",
        "tactic": "initial-access",
        "source": "f3"
      },
      {
        "id": "F1029",
        "name": "Gather Customer Information",
        "tactic": "reconnaissance",
        "source": "f3"
      },
      {
        "id": "F1005.006",
        "name": "Account Manipulation: Change of Payment Details",
        "tactic": "positioning",
        "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

    Key Concepts

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

  4. 04
    Action

    MX-Based Gateway (Traditional SEG): All mail routes through Proofpoint via MX record changes; intercepts threats before delivery

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

  5. 05
    Action

    API-Based Integration: Connects directly to Microsoft 365 or Google Workspace via API; no MX changes required; can be operational within 48 hours

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

  6. 06
    Action

    Hybrid Deployment: Combines gateway and API for layered protection

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

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

    Workflow

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

  2. 08
    Action

    Step 1: Plan Mail Flow Architecture

    Source-described action candidate under “Step 1: Plan Mail Flow Architecture”; not verified execution.

  3. 09
    Action

    Document current MX records and mail flow path

    Source-described action candidate under “Step 1: Plan Mail Flow Architecture”; not verified execution.

  4. 10
    Action

    Identify all legitimate sending sources (marketing platforms, CRM, ticketing systems)

    Source-described action candidate under “Step 1: Plan Mail Flow Architecture”; not verified execution.

  5. 11
    Action

    Map inbound connectors and transport rules in Microsoft 365 or Google Workspace

    Source-described action candidate under “Step 1: Plan Mail Flow Architecture”; not verified execution.

  6. 12
    Action

    Plan IP allowlisting for Proofpoint egress IPs on receiving infrastructure

    Source-described action candidate under “Step 1: Plan Mail Flow Architecture”; not verified execution.

  7. 13
    Action

    Configure SPF record to include Proofpoint: `v=spf1 include:spf.protection.outlook.com include:spf-a.proofpoint.com -all`

    Source-described action candidate under “Step 1: Plan Mail Flow Architecture”; not verified execution.

  8. 14
    Action

    Step 2: Configure Proofpoint Policies

    Source-described action candidate under “Step 2: Configure Proofpoint Policies”; not verified execution.

  9. 15
    Action

    Create organizational units matching business structure

    Source-described action candidate under “Step 2: Configure Proofpoint Policies”; not verified execution.

  10. 16
    Action

    Define inbound mail policies: anti-spam, anti-virus, impostor detection

    Source-described action candidate under “Step 2: Configure Proofpoint Policies”; not verified execution.

  11. 17
    Action

    Configure Smart Search quarantine with end-user digest notifications

    Source-described action candidate under “Step 2: Configure Proofpoint Policies”; not verified execution.

  12. 18
    Action

    Set up Proofpoint Encryption for sensitive outbound messages

    Source-described action candidate under “Step 2: Configure Proofpoint Policies”; not verified execution.

  13. 19
    Action

    Enable Targeted Attack Protection (TAP) for URL and attachment sandboxing

    Source-described action candidate under “Step 2: Configure Proofpoint Policies”; not verified execution.

  14. 20
    Action

    Step 3: Deploy Email Authentication

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

  15. 21
    Action

    Configure DKIM signing through Proofpoint for outbound messages

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

  16. 22
    Action

    Set DMARC policy to monitor mode initially: `v=DMARC1; p=none; rua=mailto:[email protected]`

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

  17. 23
    Action

    Enable inbound DMARC enforcement to reject spoofed messages

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

  18. 24
    Action

    Configure anti-spoofing rules for executive impersonation protection

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

  19. 25
    Action

    Step 4: Enable Advanced Threat Protection

    Source-described action candidate under “Step 4: Enable Advanced Threat Protection”; not verified execution.

  20. 26
    Action

    Activate URL Defense with rewriting enabled for all inbound messages

    Source-described action candidate under “Step 4: Enable Advanced Threat Protection”; not verified execution.

  21. 27
    Action

    Configure Attachment Defense sandbox policies (safe attachment mode)

    Source-described action candidate under “Step 4: Enable Advanced Threat Protection”; not verified execution.

  22. 28
    Action

    Enable Threat Response Auto-Pull (TRAP) for post-delivery remediation

    Source-described action candidate under “Step 4: Enable Advanced Threat Protection”; not verified execution.

  23. 29
    Action

    Set up TAP Dashboard alerts for targeted attack campaigns

    Source-described action candidate under “Step 4: Enable Advanced Threat Protection”; not verified execution.

  24. 30
    Action

    Configure Supplier Risk monitoring for vendor email compromise

    Source-described action candidate under “Step 4: Enable Advanced Threat Protection”; not verified execution.

  25. 31
    Action

    Step 5: Migrate MX Records

    Source-described action candidate under “Step 5: Migrate MX Records”; not verified execution.

  26. 32
    Action

    Lower MX record TTL to 300 seconds 48 hours before cutover

    Source-described action candidate under “Step 5: Migrate MX Records”; not verified execution.

  27. 33
    Action

    Update MX records to point to Proofpoint: `company-com.mail.protection.proofpoint.com`

    Source-described action candidate under “Step 5: Migrate MX Records”; not verified execution.

  28. 34
    Action

    Configure connector restrictions in Microsoft 365 to accept mail only from Proofpoint IPs

    Source-described action candidate under “Step 5: Migrate MX Records”; not verified execution.

  29. 35
    Action

    Monitor mail flow through Proofpoint Message Trace for 48-72 hours

    Source-described action candidate under “Step 5: Migrate MX Records”; not verified execution.

  30. 36
    Action

    Verify no legitimate mail is being blocked or delayed

    Source-described action candidate under “Step 5: Migrate MX Records”; not verified execution.

  31. 37
    Action

    Step 6: Tune and Optimize

    Source-described action candidate under “Step 6: Tune and Optimize”; not verified execution.

  32. 38
    Action

    Review quarantine and false positive/negative rates weekly for first month

    Source-described action candidate under “Step 6: Tune and Optimize”; not verified execution.

  33. 39
    Action

    Adjust spam thresholds based on organizational tolerance

    Source-described action candidate under “Step 6: Tune and Optimize”; not verified execution.

  34. 40
    Action

    Add approved senders and safe lists for legitimate bulk mail

    Source-described action candidate under “Step 6: Tune and Optimize”; not verified execution.

  35. 41
    Action

    Configure data loss prevention (DLP) rules for outbound sensitive content

    Source-described action candidate under “Step 6: Tune and Optimize”; not verified execution.

  36. 42
    Action

    Enable email warning banners for external sender identification

    Source-described action candidate under “Step 6: Tune and Optimize”; not verified execution.

  37. 43
    Action

    Tools & Resources

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

  38. 44
    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.

Attention recommended

21 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 useObserved
Medium

Network access is mentioned

12 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 12 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

High

Credential or secret material is referenced

2 occurrences

This line resembles a credential literal or reads a sensitive environment value. Do not expose its contents; verify whether it is a placeholder, required secret, or accidentally committed material. This rule matched 2 location(s) in the collected text; 2 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Note

File modification is described or implemented

7 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 7 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-proofpoint-email-security-gateway/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-proofpoint-email-security-gateway/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-proofpoint-email-security-gateway
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.