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.
- License 许可
- Apache-2.0
- 最近更新
- 2026-08-31
- Stars
- ★ 3.6w
- Forks
- 4.4k
01 前言 Front Matter
- name
- detecting-business-email-compromise-with-ai
- tags
- [ "bec", "ai", "nlp", "machine-learning", "email-security", "behavioral-analytics", "impersonation", "fraud-detection" ]
- author
- mahipal
- domain
- cybersecurity
- license
- Apache-2.0
- version
- 1.0
- mitre_f3
- { "tactics": [ "initial-access", "stealth", "positioning", "monetization" ], "version": "1.1", "techniques": [ { "id": "T1660", "name": "Phishing", "source": "attack", "tactic": "initial-access" }, { "id": "T1672", "name": "Email Spoofing", "source": "attack", "tactic": "stealth" }, { "id": "F1032", "name": "Impersonate Official", "source": "f3", "tactic": "initial-access" }, { "id": "F1005.006", "name": "Account Manipulation: Change of Payment Details", "source": "f3", "tactic": "positioning" }, { "id": "F1022", "name": "Delete Relevant Emails", "source": "f3", "tactic": "stealth" }, { "id": "F1025.003", "name": "Electronic Funds Transfer: Wire Transfer", "source": "f3", "tactic": "monetization" } ] }
- nist_csf
- [ "PR.AT-01", "DE.CM-09", "RS.CO-02", "DE.AE-02" ]
- subdomain
- phishing-defense
- description
- 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.
- nist_ai_rmf
- [ "GOVERN-6.2", "MAP-5.2", "GOVERN-6.1", "MEASURE-2.7", "MEASURE-2.5" ]
- mitre_attack
- [ "T1566.002", "T1534", "T1114.002", "T1657", "T1078.004" ]
- atlas_techniques
- [ "AML.T0073", "AML.T0052", "AML.T0088" ]
- d3fend_techniques
- [ "Sender MTA Reputation Analysis", "Email Filtering", "Sender Reputation Analysis", "Homoglyph Detection", "Message Analysis" ]
02 资源文件 12
- 资产文件assets/template.md927 B
- 许可证LICENSE11.0 KB
- 参考文档references/api-reference.md2.2 KB
- 参考文档references/eloquent.md7.3 KB
- 参考文档references/livewire.md10.9 KB
- 参考文档references/queues.md9.2 KB
- 参考文档references/routing.md8.4 KB
- 参考文档references/standards.md1.3 KB
- 参考文档references/testing.md12.0 KB
- 参考文档references/workflows.md1.4 KB
- 脚本scripts/agent.py5.3 KB
- 脚本scripts/process.py10.8 KB
03 SKILL.md 正文
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%+
04 同仓库更多 Skills
verifying-build-provenance-with-slsa-sigstore
Verifies artifact signatures and SLSA provenance using Sigstore's cosign (verify, verify-attestation, verify-blob-attestation) and slsa-verifier (verify-artifact), enforcing keyless OIDC builder identity and source repo against SLSA Build levels. Use in CI/CD before deploying artifacts, when consuming third-party attestations, establishing a SLSA Build L3 pipeline, or confirming provenance during incident response or admission control.
validating-tpm-measured-boot-attestation
Verifies TPM 2.0 measured-boot integrity and remote attestation with tpm2-tools -- reading PCRs (tpm2_pcrread), replaying the boot event log, generating and checking signed quotes (tpm2_quote/tpm2_checkquote), and sealing secrets to a PCR policy. Use to confirm a system booted trusted firmware/kernel for Zero Trust device posture, detect boot-chain tampering via PCR drift, or build a golden-value baseline for fleet attestation.
validating-backup-integrity-for-recovery
Validates backup integrity through cryptographic hash verification, automated restore testing, corruption detection, and recoverability checks to confirm backups are reliable for disaster recovery and ransomware response. Use before relying on backups for recovery, when building post-backup validation pipelines, auditing backup infrastructure for compliance, or checking immutable/air-gapped backups for silent corruption or tampering.
triaging-windows-with-kape
Runs KAPE (Kroll Artifact Parser and Extractor) to collect targeted forensic artifacts (registry hives, $MFT, event logs, prefetch, browser data) via Targets and parse them with Modules wrapping Eric Zimmerman's EZ Tools (PECmd, MFTECmd, RECmd). Use during early incident containment/triage when full disk imaging is impractical but a defensible, parseable Windows artifact set is needed quickly, including at-scale remote collection.
triaging-vulnerabilities-with-ssvc-framework
Triages and prioritizes vulnerabilities with CISA's Stakeholder-Specific Vulnerability Categorization (SSVC) decision tree, weighing exploitation status (via the CISA KEV catalog and FIRST EPSS API), technical impact, automatability, and mission prevalence to output Track/Track*/Attend/Act decisions. Use when prioritizing vulnerability scan results (OpenVAS, Nessus, Qualys) for remediation planning beyond raw CVSS scores.
triaging-security-incident
Performs initial triage of security incidents using the NIST SP 800-61r3 and SANS PICERL frameworks, classifying incident type, assigning priority by business impact, and routing to the appropriate response team. Use when a SIEM/EDR alert needs human classification, concurrent alerts must be prioritized, or a user report or threat-intel IOC match requires initial incident categorization.