Back to catalog
Static reviewDevelopment

Skill dossier

implementing-email-sandboxing-with-proofpoint

Source declaration

Email sandboxing detonates suspicious attachments and URLs in isolated environments to detect zero-day malware and evasive phishing payloads. Proofpoint Targeted Attack Protection (TAP) is an industry

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

Email sandboxing detonates suspicious attachments and URLs in isolated environments to detect zero-day malware and evasive phishing payloads. Proofpoint Targeted Attack Protection (TAP) is an industry

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.

Email sandboxing detonates suspicious attachments and URLs in isolated environments to detect zero-day malware and evasive phishing payloads. Proofpoint Targeted Attack Protection (TAP) is an industry 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

  • Attachment sandboxing: Detonates files in virtual machines (Windows, macOS, Android) [Source statement; provisional, not tested. Evidence: skills/implementing-email-sandboxing-with-proofpoint/SKILL.md:L53]
  • URL Defense: Rewrites URLs, detonates at time-of-click [Source statement; provisional, not tested. Evidence: skills/implementing-email-sandboxing-with-proofpoint/SKILL.md:L54]
  • Threat Intelligence: Proofpoint's NexusAI threat intelligence integration [Source statement; provisional, not tested. Evidence: skills/implementing-email-sandboxing-with-proofpoint/SKILL.md:L55]
  • TAP Dashboard: Real-time visibility into threats targeting the organization [Source statement; provisional, not tested. Evidence: skills/implementing-email-sandboxing-with-proofpoint/SKILL.md:L56]
  • Campaign correlation: Groups related attacks into campaigns [Source statement; provisional, not tested. Evidence: skills/implementing-email-sandboxing-with-proofpoint/SKILL.md:L57]
  • Very Attacked People (VAP): Identifies most-targeted individuals [Source statement; provisional, not tested. Evidence: skills/implementing-email-sandboxing-with-proofpoint/SKILL.md:L58]
  • Workflow [Source statement; provisional, not tested. Evidence: skills/implementing-email-sandboxing-with-proofpoint/SKILL.md:L68]
  • Step 1: Configure TAP in Proofpoint [Source statement; provisional, not tested. Evidence: skills/implementing-email-sandboxing-with-proofpoint/SKILL.md:L70]
  • Step 2: Tune Attachment Policies [Source statement; provisional, not tested. Evidence: skills/implementing-email-sandboxing-with-proofpoint/SKILL.md:L76]
  • Step 3: Configure URL Defense [Source statement; provisional, not tested. Evidence: skills/implementing-email-sandboxing-with-proofpoint/SKILL.md:L85]
  • Step 4: Set Up TAP Dashboard Monitoring [Source statement; provisional, not tested. Evidence: skills/implementing-email-sandboxing-with-proofpoint/SKILL.md:L92]
  • Step 5: Integrate with SIEM [Source statement; provisional, not tested. Evidence: skills/implementing-email-sandboxing-with-proofpoint/SKILL.md:L98]

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-email-sandboxing-with-proofpoint/SKILL.md:L1-L30]

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

File inventory

PathTypeBytes
skills/implementing-email-sandboxing-with-proofpoint/assets/template.mdReference1.2 KB
skills/implementing-email-sandboxing-with-proofpoint/LICENSEOther11 KB
skills/implementing-email-sandboxing-with-proofpoint/references/api-reference.mdReference1.5 KB
skills/implementing-email-sandboxing-with-proofpoint/references/standards.mdReference1.4 KB
skills/implementing-email-sandboxing-with-proofpoint/references/workflows.mdReference1.7 KB
skills/implementing-email-sandboxing-with-proofpoint/scripts/agent.pyScript5.3 KB
skills/implementing-email-sandboxing-with-proofpoint/scripts/process.pyScript9 KB
skills/implementing-email-sandboxing-with-proofpoint/SKILL.mdInstruction4.2 KB

SKILL.md frontmatter

{
  "name": "implementing-email-sandboxing-with-proofpoint",
  "description": "Email sandboxing detonates suspicious attachments and URLs in isolated environments to detect zero-day malware and evasive phishing payloads. Proofpoint Targeted Attack Protection (TAP) is an industry",
  "domain": "cybersecurity",
  "subdomain": "phishing-defense",
  "tags": [
    "phishing",
    "email-security",
    "social-engineering",
    "dmarc",
    "awareness",
    "sandboxing",
    "proofpoint"
  ],
  "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"
  ]
}

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

    Attachment sandboxing: Detonates files in virtual machines (Windows, macOS, Android)

    Source-described action candidate under “Proofpoint TAP Capabilities”; not verified execution.

  5. 05
    Action

    URL Defense: Rewrites URLs, detonates at time-of-click

    Source-described action candidate under “Proofpoint TAP Capabilities”; not verified execution.

  6. 06
    Action

    Threat Intelligence: Proofpoint's NexusAI threat intelligence integration

    Source-described action candidate under “Proofpoint TAP Capabilities”; not verified execution.

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

    TAP Dashboard: Real-time visibility into threats targeting the organization

    Source-described action candidate under “Proofpoint TAP Capabilities”; not verified execution.

  2. 08
    Action

    Campaign correlation: Groups related attacks into campaigns

    Source-described action candidate under “Proofpoint TAP Capabilities”; not verified execution.

  3. 09
    Action

    Very Attacked People (VAP): Identifies most-targeted individuals

    Source-described action candidate under “Proofpoint TAP Capabilities”; not verified execution.

  4. 10
    Action

    Workflow

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

  5. 11
    Action

    Step 1: Configure TAP in Proofpoint

    Source-described action candidate under “Step 1: Configure TAP in Proofpoint”; not verified execution.

  6. 12
    Action

    Enable TAP for inbound email policy

    Source-described action candidate under “Step 1: Configure TAP in Proofpoint”; not verified execution.

  7. 13
    Action

    Configure sandbox profiles (attachment types to detonate)

    Source-described action candidate under “Step 1: Configure TAP in Proofpoint”; not verified execution.

  8. 14
    Action

    Set URL Defense rewriting policy

    Source-described action candidate under “Step 1: Configure TAP in Proofpoint”; not verified execution.

  9. 15
    Action

    Configure quarantine actions for malicious verdicts

    Source-described action candidate under “Step 1: Configure TAP in Proofpoint”; not verified execution.

  10. 16
    Action

    Step 2: Tune Attachment Policies

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

  11. 17
    Action

    Step 3: Configure URL Defense

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

  12. 18
    Action

    Enable URL rewriting for all inbound email

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

  13. 19
    Action

    Set time-of-click detonation

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

  14. 20
    Action

    Block access to malicious URLs

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

  15. 21
    Action

    Show warning page for suspicious (not confirmed malicious) URLs

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

  16. 22
    Action

    Configure allowed domains bypass list

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

  17. 23
    Action

    Step 4: Set Up TAP Dashboard Monitoring

    Source-described action candidate under “Step 4: Set Up TAP Dashboard Monitoring”; not verified execution.

  18. 24
    Action

    Configure daily threat digest emails to security team

    Source-described action candidate under “Step 4: Set Up TAP Dashboard Monitoring”; not verified execution.

  19. 25
    Action

    Set up real-time alerts for targeted attacks

    Source-described action candidate under “Step 4: Set Up TAP Dashboard Monitoring”; not verified execution.

  20. 26
    Output

    Monitor VAP report for high-risk users

    Source-described output candidate under “Step 4: Set Up TAP Dashboard Monitoring”; not verified execution.

  21. 27
    Action

    Review campaign clusters for coordinated attacks

    Source-described action candidate under “Step 4: Set Up TAP Dashboard Monitoring”; not verified execution.

  22. 28
    Action

    Step 5: Integrate with SIEM

    Source-described action candidate under “Step 5: Integrate with SIEM”; not verified execution.

  23. 29
    Output

    Configure syslog/API export to SIEM

    Source-described output candidate under “Step 5: Integrate with SIEM”; not verified execution.

  24. 30
    Action

    Create correlation rules for TAP alerts

    Source-described action candidate under “Step 5: Integrate with SIEM”; not verified execution.

  25. 31
    Action

    Set up automated response workflows

    Source-described action candidate under “Step 5: Integrate with SIEM”; not verified execution.

  26. 32
    Action

    Tools & Resources

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

  27. 33
    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

41 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

14 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 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.

Note

File modification is described or implemented

24 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 24 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

3 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 3 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-email-sandboxing-with-proofpoint/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-email-sandboxing-with-proofpoint/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-email-sandboxing-with-proofpoint
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.