Back to catalog
Static reviewDevelopment

Skill dossier

implementing-mimecast-targeted-attack-protection

Source declaration

Deploys and configures Mimecast Targeted Threat Protection (TTP) modules -- URL Protect (click-time URL rewriting/analysis), Attachment Protect (sandbox detonation), Impersonation Protect (BEC/whaling detection), and Internal Email Protect -- for Microsoft 365 or Google Workspace. Use when defending against phishing, spearphishing, or business email compromise, or configuring TTP policies in the Mimecast Administration Console.

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

Deploys and configures Mimecast Targeted Threat Protection (TTP) modules -- URL Protect (click-time URL rewriting/analysis), Attachment Protect (sandbox detonation), Impersonation Protect (BEC/whaling detection), and Internal Email Protect -- for Microsoft 365 or Google Workspace. Use when defending against phishing, spearphishing, or business email compromise, or configuring TTP policies in the Mimecast Administration Console.

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.

Deploys and configures Mimecast Targeted Threat Protection (TTP) modules -- URL Protect (click-time URL rewriting/analysis), Attachment Protect (sandbox detonation), Impersonation Protect (BEC/whaling detection), and Internal Email Protect -- for Microsoft 365 or Google Workspace. Use when defending against phishing, spearphishing, or business email compromise, or configuring TTP policies in the Mimecast Administration Console. 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-mimecast-targeted-attack-protection/SKILL.md:L102]
  • Step 1: Configure URL Protect Policy [Source statement; provisional, not tested. Evidence: skills/implementing-mimecast-targeted-attack-protection/SKILL.md:L104]
  • Step 2: Configure Attachment Protect Policy [Source statement; provisional, not tested. Evidence: skills/implementing-mimecast-targeted-attack-protection/SKILL.md:L112]
  • Step 3: Configure Impersonation Protect [Source statement; provisional, not tested. Evidence: skills/implementing-mimecast-targeted-attack-protection/SKILL.md:L120]
  • Step 4: Enable Internal Email Protect [Source statement; provisional, not tested. Evidence: skills/implementing-mimecast-targeted-attack-protection/SKILL.md:L128]
  • Step 5: Create Test Group and Validate [Source statement; provisional, not tested. Evidence: skills/implementing-mimecast-targeted-attack-protection/SKILL.md:L135]
  • Step 6: Deploy Organization-Wide and Tune [Source statement; provisional, not tested. Evidence: skills/implementing-mimecast-targeted-attack-protection/SKILL.md:L142]

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-mimecast-targeted-attack-protection/SKILL.md:L1-L61]

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

File inventory

PathTypeBytes
skills/implementing-mimecast-targeted-attack-protection/assets/template.mdReference1.3 KB
skills/implementing-mimecast-targeted-attack-protection/LICENSEOther11 KB
skills/implementing-mimecast-targeted-attack-protection/references/api-reference.mdReference1.4 KB
skills/implementing-mimecast-targeted-attack-protection/references/standards.mdReference1.7 KB
skills/implementing-mimecast-targeted-attack-protection/references/workflows.mdReference2.2 KB
skills/implementing-mimecast-targeted-attack-protection/scripts/agent.pyScript6.1 KB
skills/implementing-mimecast-targeted-attack-protection/scripts/process.pyScript12.1 KB
skills/implementing-mimecast-targeted-attack-protection/SKILL.mdInstruction6.9 KB

SKILL.md frontmatter

{
  "name": "implementing-mimecast-targeted-attack-protection",
  "description": "Deploys and configures Mimecast Targeted Threat Protection (TTP) modules -- URL Protect (click-time URL rewriting/analysis), Attachment Protect (sandbox detonation), Impersonation Protect (BEC/whaling detection), and Internal Email Protect -- for Microsoft 365 or Google Workspace. Use when defending against phishing, spearphishing, or business email compromise, or configuring TTP policies in the Mimecast Administration Console.",
  "domain": "cybersecurity",
  "subdomain": "phishing-defense",
  "tags": [
    "mimecast",
    "email-security",
    "targeted-threat-protection",
    "url-protect",
    "impersonation",
    "attachment-sandboxing",
    "phishing"
  ],
  "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"
  ],
  "mitre_f3": {
    "version": "1.1",
    "tactics": [
      "initial-access",
      "reconnaissance",
      "stealth",
      "resource-development"
    ],
    "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": "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

    Key Concepts

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

  4. 04
    Action

    Workflow

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

  5. 05
    Action

    Step 1: Configure URL Protect Policy

    Source-described action candidate under “Step 1: Configure URL Protect Policy”; not verified execution.

  6. 06
    Action

    Navigate to Administration > Gateway > Policies > Targeted Threat Protection - URL Protect

    Source-described action candidate under “Step 1: Configure URL Protect Policy”; not verified execution.

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

    Create URL Protect definition with rewriting enabled for inbound messages

    Source-described action candidate under “Step 1: Configure URL Protect Policy”; not verified execution.

  2. 08
    Action

    Enable URL Pre-Delivery Action set to "Hold" for maximum protection

    Source-described action candidate under “Step 1: Configure URL Protect Policy”; not verified execution.

  3. 09
    Action

    Configure scan mode: aggressive for high-risk users, moderate for general population

    Source-described action candidate under “Step 1: Configure URL Protect Policy”; not verified execution.

  4. 10
    Action

    Set action for malicious URLs: block page with user notification

    Source-described action candidate under “Step 1: Configure URL Protect Policy”; not verified execution.

  5. 11
    Action

    Enable URL logging for all click events

    Source-described action candidate under “Step 1: Configure URL Protect Policy”; not verified execution.

  6. 12
    Action

    Step 2: Configure Attachment Protect Policy

    Source-described action candidate under “Step 2: Configure Attachment Protect Policy”; not verified execution.

  7. 13
    Action

    Navigate to Administration > Gateway > Policies > Targeted Threat Protection - Attachment Protect

    Source-described action candidate under “Step 2: Configure Attachment Protect Policy”; not verified execution.

  8. 14
    Action

    Create Attachment Protect definition for inbound email

    Source-described action candidate under “Step 2: Configure Attachment Protect Policy”; not verified execution.

  9. 15
    Action

    Select sandbox mode: "Safe File" (converts to safe format) or "Dynamic Configuration" (full sandbox)

    Source-described action candidate under “Step 2: Configure Attachment Protect Policy”; not verified execution.

  10. 16
    Action

    Configure attachment types to scan: executables, Office documents, PDFs, archives

    Source-described action candidate under “Step 2: Configure Attachment Protect Policy”; not verified execution.

  11. 17
    Action

    Set timeout for sandbox analysis (default: up to 7 minutes for complex files)

    Source-described action candidate under “Step 2: Configure Attachment Protect Policy”; not verified execution.

  12. 18
    Action

    Enable pre-emptive sandboxing for attachments from unknown senders

    Source-described action candidate under “Step 2: Configure Attachment Protect Policy”; not verified execution.

  13. 19
    Action

    Step 3: Configure Impersonation Protect

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

  14. 20
    Action

    Create Default Impersonation Protect Definition (Hit 3) for all inbound email

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

  15. 21
    Action

    Create VIP Impersonation Protect Definition (Hit 1) for executive protection

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

  16. 22
    Action

    Build VIP list: CEO, CFO, CTO, board members, finance leadership

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

  17. 23
    Output

    Configure detection identifiers: display name, domain similarity, newly observed sender

    Source-described output candidate under “Step 3: Configure Impersonation Protect”; not verified execution.

  18. 24
    Action

    Set actions: quarantine high-confidence impersonation, tag moderate confidence

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

  19. 25
    Action

    Enable end-user warning banners for flagged messages

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

  20. 26
    Action

    Step 4: Enable Internal Email Protect

    Source-described action candidate under “Step 4: Enable Internal Email Protect”; not verified execution.

  21. 27
    Action

    Configure journaling from Microsoft 365/Google Workspace to Mimecast

    Source-described action candidate under “Step 4: Enable Internal Email Protect”; not verified execution.

  22. 28
    Action

    Enable URL scanning for internal emails

    Source-described action candidate under “Step 4: Enable Internal Email Protect”; not verified execution.

  23. 29
    Action

    Enable attachment scanning for internal emails

    Source-described action candidate under “Step 4: Enable Internal Email Protect”; not verified execution.

  24. 30
    Action

    Configure alerts for internal account compromise indicators

    Source-described action candidate under “Step 4: Enable Internal Email Protect”; not verified execution.

  25. 31
    Action

    Set up detection for internal phishing (compromised account sending malware)

    Source-described action candidate under “Step 4: Enable Internal Email Protect”; not verified execution.

  26. 32
    Action

    Step 5: Create Test Group and Validate

    Source-described action candidate under “Step 5: Create Test Group and Validate”; not verified execution.

  27. 33
    Action

    Create pilot group of 50-100 users across departments

    Source-described action candidate under “Step 5: Create Test Group and Validate”; not verified execution.

  28. 34
    Action

    Apply TTP policies to pilot group first

    Source-described action candidate under “Step 5: Create Test Group and Validate”; not verified execution.

  29. 35
    Action

    Send test emails with known-safe test URLs and EICAR test files

    Source-described action candidate under “Step 5: Create Test Group and Validate”; not verified execution.

  30. 36
    Action

    Verify URL rewriting, attachment sandboxing, and impersonation detection

    Source-described action candidate under “Step 5: Create Test Group and Validate”; not verified execution.

  31. 37
    Action

    Monitor false positive rate for 1-2 weeks before organization-wide deployment

    Source-described action candidate under “Step 5: Create Test Group and Validate”; not verified execution.

  32. 38
    Action

    Step 6: Deploy Organization-Wide and Tune

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

  33. 39
    Action

    Extend TTP policies to all users

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

  34. 40
    Action

    Monitor Mimecast Threat Dashboard for detection metrics

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

  35. 41
    Action

    Review and whitelist legitimate applications triggering false positives

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

  36. 42
    Action

    Tune impersonation sensitivity based on false positive feedback

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

  37. 43
    Action

    Configure exception policies for automated systems and mailing lists

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

  38. 44
    Action

    Tools & Resources

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

  39. 45
    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

24 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

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

Note

File modification is described or implemented

17 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 17 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-mimecast-targeted-attack-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-mimecast-targeted-attack-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-mimecast-targeted-attack-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.