detecting-business-email-compromise-with-ai
Deploy AI and NLP-powered detection systems to identify business email compromise attacks by analyzing writing style, behavioral patterns, and contextual anomalies that evade traditional rule-based filters.
What this skill does
# Detecting Business Email Compromise with AI ## Overview AI-powered BEC detection uses machine learning, NLP, and behavioral analytics to identify sophisticated impersonation attacks that contain no malicious links or attachments. Traditional rule-based filters miss these attacks because BEC relies purely on social engineering. Modern AI approaches analyze writing style, tone, vocabulary, grammatical patterns, and behavioral context to determine if an email genuinely comes from the stated sender. BERT-based models achieve 98.65% accuracy in BEC detection, and AI-enhanced platforms show a 25% increase in phishing identification over keyword-based rules. ## When to Use - When investigating security incidents that require detecting business email compromise with ai - When building detection rules or threat hunting queries for this domain - When SOC analysts need structured procedures for this analysis type - When validating security monitoring coverage for related attack techniques ## Prerequisites - AI-powered email security platform (Abnormal Security, Tessian, Microsoft Defender) - Historical email data for baseline training (minimum 30 days) - Integration with email platform (Microsoft 365 or Google Workspace) - SIEM for alert correlation and investigation - Understanding of BEC attack types (FBI IC3 classification) ## Workflow ### Step 1: Deploy AI Email Security Platform - Select API-based solution (Abnormal Security, Tessian, Ironscales) or enhance existing SEG - Connect to Microsoft Graph API or Google Workspace API - Allow 48-hour baseline learning period on historical email data - Configure integration to scan inbound, outbound, and internal email - Verify API permissions for message access and remediation ### Step 2: Configure Behavioral Baselines - AI learns normal communication patterns: who emails whom, frequency, tone - Establish writing style profiles for each user (vocabulary, sentence structure) - Map typical request types per role (finance processes payments, HR handles PII) - Baseline email metadata: typical sending times, devices, locations - Flag deviations from established baselines as anomalous ### Step 3: Train NLP Models for BEC Detection - Deploy transformer-based models (BERT, GPT) for email content analysis - Detect urgency and manipulation language patterns - Identify mismatches between sender identity and writing style - Analyze sentiment shifts indicating social engineering pressure - Classify email intent: information request, payment request, credential request ### Step 4: Configure Detection Policies - VIP impersonation: AI compares new email against known executive communication patterns - Vendor impersonation: detect payment change requests from vendor lookalike domains - Account compromise: detect sudden changes in employee email behavior - Supply chain BEC: monitor for impersonation of trusted partners - Configure confidence thresholds for auto-block vs. warning banner vs. analyst review ### Step 5: Integrate with Response Workflow - Auto-quarantine high-confidence BEC detections - Add warning banners for moderate-confidence detections - Route suspicious emails to SOC analyst queue for review - Integrate with SOAR for automated response playbooks - Feed BEC verdicts back into training data for model improvement ## Tools & Resources - **Abnormal Security**: API-based AI email security with behavioral analysis - **Microsoft Defender for O365**: Built-in AI anti-BEC with Impostor Classifier - **Tessian (Proofpoint)**: AI-powered email security with human layer protection - **Ironscales**: AI + human-in-the-loop BEC detection - **Darktrace Email**: Self-learning AI for email threat detection ## Validation - AI detects test BEC email with no malicious indicators (pure social engineering) - Writing style analysis identifies impersonation of known executive - Behavioral baseline flags unusual payment request from compromised account - NLP correctly classifies urgency manipulation in test scenario - False positive rate below 0.05% after baseline training - Detection rate exceeds traditional rule-based filters by 25%+
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.