implementing-mimecast-targeted-attack-protection
Deploy Mimecast Targeted Threat Protection including URL Protect, Attachment Protect, Impersonation Protect, and Internal Email Protect to defend against advanced phishing and spearphishing attacks.
What this skill does
# Implementing Mimecast Targeted Attack Protection ## Overview Mimecast Targeted Threat Protection (TTP) is a suite of advanced email security services designed to protect against sophisticated phishing, spearphishing, and targeted attacks. TTP consists of four core modules: URL Protect (real-time URL rewriting and click-time analysis), Attachment Protect (sandbox detonation of suspicious attachments), Impersonation Protect (BEC and whaling detection), and Internal Email Protect (scanning internal/outbound email for threats). As of November 2025, Mimecast enabled URL Pre-Delivery Action with Hold setting for all customers by default. ## When to Use - When deploying or configuring implementing mimecast targeted attack 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 - Mimecast Email Security license with TTP add-on - Administrative access to Mimecast Administration Console - Microsoft 365 or Google Workspace environment - MX records configured to route through Mimecast - Understanding of email authentication (SPF, DKIM, DMARC) ## Key Concepts ### TTP Module Overview | Module | Function | Key Capability | |---|---|---| | URL Protect | Rewrites and scans URLs at click time | Real-time sandbox, pre-delivery hold | | Attachment Protect | Sandboxes suspicious attachments | Static + dynamic analysis | | Impersonation Protect | Detects BEC/whaling attacks | VIP name matching, header analysis | | Internal Email Protect | Scans internal/outbound email | Lateral phishing detection | ### Impersonation Protection Scenarios - **Hit 3 (Default)**: Flags emails matching 3+ impersonation indicators - **Hit 1 (VIP)**: Flags emails matching 1+ indicator for designated VIP users - Key identifiers: display name similarity, domain similarity, reply-to mismatch, newly registered domains ### URL Protect Modes - **Rewrite**: URLs rewritten to route through Mimecast proxy at click time - **Pre-Delivery Action (Hold)**: URLs checked before message delivery; held if suspicious - **Pre-Delivery Action (None)**: URLs checked pre-delivery but not held ## Workflow ### Step 1: Configure URL Protect Policy - Navigate to Administration > Gateway > Policies > Targeted Threat Protection - URL Protect - Create URL Protect definition with rewriting enabled for inbound messages - Enable URL Pre-Delivery Action set to "Hold" for maximum protection - Configure scan mode: aggressive for high-risk users, moderate for general population - Set action for malicious URLs: block page with user notification - Enable URL logging for all click events ### Step 2: Configure Attachment Protect Policy - Navigate to Administration > Gateway > Policies > Targeted Threat Protection - Attachment Protect - Create Attachment Protect definition for inbound email - Select sandbox mode: "Safe File" (converts to safe format) or "Dynamic Configuration" (full sandbox) - Configure attachment types to scan: executables, Office documents, PDFs, archives - Set timeout for sandbox analysis (default: up to 7 minutes for complex files) - Enable pre-emptive sandboxing for attachments from unknown senders ### Step 3: Configure Impersonation Protect - Create Default Impersonation Protect Definition (Hit 3) for all inbound email - Create VIP Impersonation Protect Definition (Hit 1) for executive protection - Build VIP list: CEO, CFO, CTO, board members, finance leadership - Configure detection identifiers: display name, domain similarity, newly observed sender - Set actions: quarantine high-confidence impersonation, tag moderate confidence - Enable end-user warning banners for flagged messages ### Step 4: Enable Internal Email Protect - Configure journaling from Microsoft 365/Google Workspace to Mimecast - Enable URL scanning for internal emails - Enable attachment scanning for internal emails - Configure alerts for internal account compromise indicators - Set up detection for internal phishing (compromised account sending malware) ### Step 5: Create Test Group and Validate - Create pilot group of 50-100 users across departments - Apply TTP policies to pilot group first - Send test emails with known-safe test URLs and EICAR test files - Verify URL rewriting, attachment sandboxing, and impersonation detection - Monitor false positive rate for 1-2 weeks before organization-wide deployment ### Step 6: Deploy Organization-Wide and Tune - Extend TTP policies to all users - Monitor Mimecast Threat Dashboard for detection metrics - Review and whitelist legitimate applications triggering false positives - Tune impersonation sensitivity based on false positive feedback - Configure exception policies for automated systems and mailing lists ## Tools & Resources - **Mimecast Administration Console**: Policy configuration and management - **Mimecast Threat Dashboard**: Real-time threat visibility and analytics - **Mimecast Awareness Training**: Integrated security awareness platform - **Mimecast API**: Programmatic access to logs and threat data - **Message Center**: Quarantine management for admins and users ## Validation - URL Protect rewrites URLs in test messages and blocks known-malicious at click - Attachment Protect sandboxes test file and returns verdict within SLA - Impersonation Protect flags test BEC email impersonating VIP - Internal Email Protect detects test lateral phishing scenario - Pre-delivery hold catches weaponized URL before reaching inbox - False positive rate below organizational threshold after tuning
Related in Cloud & DevOps
appbuilder-action-scaffolder
IncludedCreate, implement, deploy, and debug Adobe Runtime actions with consistent layout, validation, and error handling. Use this skill whenever the user needs to add actions to an App Builder project, understand action structure (params, response format, web/raw actions), configure actions in the manifest, use App Builder SDKs (State, Files, Events, database), deploy and invoke actions via CLI, debug action issues, or implement patterns such as webhook receivers, custom event providers, journaling consumers, large payload redirects, action sequence pipelines, and Asset Compute workers. Also trigger when users mention serverless functions in Adobe context, action logging, IMS authentication for actions, or cron-style scheduled actions.
orchestrating-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. Use this skill when the user needs a multi-step Data Cloud pipeline, cross-phase troubleshooting, or data space and data kit management. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase sf data360 workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching phase-specific skill), the task is STDM/session tracing/parquet telemetry (use observing-agentforce), standard CRM SOQL (use querying-soql), or Apex implementation (use generating-apex).
github-project-automation
IncludedAutomate GitHub repository setup with CI/CD workflows, issue templates, Dependabot, and CodeQL security scanning. Includes 12 production-tested workflows and prevents 18 errors: YAML syntax, action pinning, and configuration. Use when: setting up GitHub Actions CI/CD, creating issue/PR templates, enabling Dependabot or CodeQL scanning, deploying to Cloudflare Workers, implementing matrix testing, or troubleshooting YAML indentation, action version pinning, secrets syntax, runner versions, or CodeQL configuration. Keywords: github actions, github workflow, ci/cd, issue templates, pull request templates, dependabot, codeql, security scanning, yaml syntax, github automation, repository setup, workflow templates, github actions matrix, secrets management, branch protection, codeowners, github projects, continuous integration, continuous deployment, workflow syntax error, action version pinning, runner version, github context, yaml indentation error
sf-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase `sf data360` workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching sf-datacloud-* skill), the task is STDM/session tracing/parquet telemetry (use sf-ai-agentforce-observability), standard CRM SOQL (use sf-soql), or Apex implementation (use sf-apex).
fabric-cli
IncludedUse this skill for Fabric.so CLI workflows with the `fabric` terminal command: diagnose/install/login, search or browse a Fabric library, save notes/links/files, create folders, ask the Fabric AI assistant, manage tasks/workspaces, generate shell completion, check subscription usage, produce JSON output, and use Fabric as persistent agent memory. Do not use for Microsoft Fabric/Azure/Power BI `fab`, Daniel Miessler's Fabric framework, Python Fabric SSH, Fabric.js, or textile/fashion fabric.
lark
IncludedLark/Feishu CLI skills: lark-cli operations for docs, markdown, sheets, base, calendar, im, mail, task, okr, drive, wiki, slides, whiteboard, apps, approval, attendance, contact, vc, minutes, event. Use when the user needs to operate Lark/Feishu resources via lark-cli, send messages, manage documents, spreadsheets, calendars, tasks, OKRs, deploy web pages, or any Feishu/Lark workspace operations.