[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6HECTYAM02AH3RDXJKE8C0E":3,"skill-same:01M6HECTYAM02AH3RDXJKE8C0E":124},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":23,"publishedAt":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":67,"commitSha":68,"skillDirectory":69,"forksCount":70,"repositoryHtmlUrl":71,"repositoryHomepageUrl":6,"ownerHtmlUrl":72,"ownerBlogUrl":6,"ownerDescription":73,"updatedAt":74,"install":75,"resources":88},"01M6HECTYAM02AH3RDXJKE8C0E","detecting-spearphishing-with-email-gateway",null,"Spearphishing targets specific individuals using personalized, researched content that bypasses generic spam filters. Email security gateways (SEGs) like Microsoft Defender for Office 365, Proofpoint,","HenriqueMC17\u002Fagente-core","HenriqueMC17","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F206460478?v=4","01M6HB63HBBF18AC4H09XTB549","Henrique Monteiro Cardoso","01M6HB63NGSQXWKWCFWW2B20W0",1,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fdetecting-spearphishing-with-email-gateway\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000005","邮件与沟通","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"gateway","email","detecting","spearphishing","with","detecting spearphishing with email gateway","t1566","at","spam","co","de","social","filters","cm","security","email-gateway","defense","dmarc","defender","cybersecurity","2026-11-10 10:12:30",false,"---\nname: detecting-spearphishing-with-email-gateway\ndescription: Spearphishing targets specific individuals using personalized, researched content that bypasses generic spam filters. Email security gateways (SEGs) like Microsoft Defender for Office 365, Proofpoint,\ndomain: cybersecurity\nsubdomain: phishing-defense\ntags:\n- phishing\n- email-security\n- social-engineering\n- dmarc\n- awareness\n- spearphishing\n- email-gateway\nversion: '1.0'\nauthor: mahipal\nlicense: Apache-2.0\nnist_csf:\n- PR.AT-01\n- DE.CM-09\n- RS.CO-02\n- DE.AE-02\nmitre_attack:\n- T1566.001\n- T1566.002\n- T1204.001\n- T1204.002\ncategory: detecting-spearphishing-with-email-gateway\n---\n# Detecting Spearphishing with Email Gateway\n\n## Overview\nSpearphishing targets specific individuals using personalized, researched content that bypasses generic spam filters. Email security gateways (SEGs) like Microsoft Defender for Office 365, Proofpoint, Mimecast, and Barracuda provide advanced detection capabilities including behavioral analysis, URL detonation, attachment sandboxing, and impersonation detection. This skill covers configuring these gateways to detect and block targeted phishing attacks.\n\n\n## When to Use\n\n- When investigating security incidents that require detecting spearphishing with email gateway\n- When building detection rules or threat hunting queries for this domain\n- When SOC analysts need structured procedures for this analysis type\n- When validating security monitoring coverage for related attack techniques\n\n## Prerequisites\n- Access to email security gateway admin console\n- Understanding of email flow architecture (MX records, transport rules)\n- Familiarity with SPF\u002FDKIM\u002FDMARC authentication\n- Knowledge of common spearphishing techniques and pretexts\n\n## Key Concepts\n\n### Spearphishing Characteristics\n- **Targeted recipients**: Specific individuals, often executives or finance staff\n- **Researched pretexts**: References to real projects, colleagues, or events\n- **Impersonation**: Spoofs trusted senders (CEO, vendor, partner)\n- **Low volume**: Few emails to avoid pattern-based detection\n- **Urgent tone**: Creates pressure to act quickly\n\n### Gateway Detection Layers\n1. **Reputation filtering**: IP\u002Fdomain\u002FURL reputation scoring\n2. **Authentication checks**: SPF, DKIM, DMARC validation\n3. **Content analysis**: NLP-based analysis of email body\n4. **Impersonation detection**: Display name and domain similarity matching\n5. **URL analysis**: Real-time URL detonation and redirect following\n6. **Attachment sandboxing**: Behavioral analysis of attachments in isolated environments\n7. **Behavioral analytics**: Anomaly detection in communication patterns\n\n## Workflow\n\n### Step 1: Configure Impersonation Protection\n```\nMicrosoft Defender for Office 365:\n  Security > Anti-phishing policies > Impersonation settings\n  - Enable user impersonation protection for VIPs\n  - Enable domain impersonation protection\n  - Add protected users (CEO, CFO, HR Director)\n  - Set action: Quarantine message\n\nProofpoint:\n  Email Protection > Impostor Classifier\n  - Enable display name spoofing detection\n  - Configure lookalike domain detection\n  - Set Impostor threshold sensitivity\n```\n\n### Step 2: Configure URL Protection\n- Enable Safe Links \u002F URL rewriting\n- Enable time-of-click URL detonation\n- Block newly registered domains (\u003C 30 days)\n- Enable URL redirect chain following\n\n### Step 3: Configure Attachment Sandboxing\n- Enable Safe Attachments \u002F attachment sandboxing\n- Configure dynamic delivery (deliver body, hold attachments)\n- Set sandbox detonation timeout to 60+ seconds\n- Block macro-enabled Office documents from external senders\n\n### Step 4: Create Custom Detection Rules\nUse the `scripts\u002Fprocess.py` to analyze email gateway logs, identify spearphishing patterns, and generate custom detection rules.\n\n### Step 5: Configure Alert and Response Actions\n- Real-time alerts for impersonation attempts\n- Automatic quarantine for high-confidence detections\n- User notification with safety tips\n- Integration with SIEM for correlation\n\n## Tools & Resources\n- **Microsoft Defender for Office 365**: https:\u002F\u002Fsecurity.microsoft.com\n- **Proofpoint Email Protection**: https:\u002F\u002Fwww.proofpoint.com\u002Fus\u002Fproducts\u002Femail-security\n- **Mimecast Email Security**: https:\u002F\u002Fwww.mimecast.com\u002Fproducts\u002Femail-security\u002F\n- **Barracuda Email Protection**: https:\u002F\u002Fwww.barracuda.com\u002Fproducts\u002Femail-protection\n\n## Validation\n- Impersonation protection correctly identifies spoofed VIP display names\n- URL detonation catches malicious links in test phishing emails\n- Attachment sandboxing detects weaponized documents\n- Custom rules trigger on known spearphishing patterns\n- SIEM integration receives gateway alerts\n","# Detecting Spearphishing with Email Gateway\n\n## Overview\nSpearphishing targets specific individuals using personalized, researched content that bypasses generic spam filters. Email security gateways (SEGs) like Microsoft Defender for Office 365, Proofpoint, Mimecast, and Barracuda provide advanced detection capabilities including behavioral analysis, URL detonation, attachment sandboxing, and impersonation detection. This skill covers configuring these gateways to detect and block targeted phishing attacks.\n\n\n## When to Use\n\n- When investigating security incidents that require detecting spearphishing with email gateway\n- When building detection rules or threat hunting queries for this domain\n- When SOC analysts need structured procedures for this analysis type\n- When validating security monitoring coverage for related attack techniques\n\n## Prerequisites\n- Access to email security gateway admin console\n- Understanding of email flow architecture (MX records, transport rules)\n- Familiarity with SPF\u002FDKIM\u002FDMARC authentication\n- Knowledge of common spearphishing techniques and pretexts\n\n## Key Concepts\n\n### Spearphishing Characteristics\n- **Targeted recipients**: Specific individuals, often executives or finance staff\n- **Researched pretexts**: References to real projects, colleagues, or events\n- **Impersonation**: Spoofs trusted senders (CEO, vendor, partner)\n- **Low volume**: Few emails to avoid pattern-based detection\n- **Urgent tone**: Creates pressure to act quickly\n\n### Gateway Detection Layers\n1. **Reputation filtering**: IP\u002Fdomain\u002FURL reputation scoring\n2. **Authentication checks**: SPF, DKIM, DMARC validation\n3. **Content analysis**: NLP-based analysis of email body\n4. **Impersonation detection**: Display name and domain similarity matching\n5. **URL analysis**: Real-time URL detonation and redirect following\n6. **Attachment sandboxing**: Behavioral analysis of attachments in isolated environments\n7. **Behavioral analytics**: Anomaly detection in communication patterns\n\n## Workflow\n\n### Step 1: Configure Impersonation Protection\n```\nMicrosoft Defender for Office 365:\n  Security > Anti-phishing policies > Impersonation settings\n  - Enable user impersonation protection for VIPs\n  - Enable domain impersonation protection\n  - Add protected users (CEO, CFO, HR Director)\n  - Set action: Quarantine message\n\nProofpoint:\n  Email Protection > Impostor Classifier\n  - Enable display name spoofing detection\n  - Configure lookalike domain detection\n  - Set Impostor threshold sensitivity\n```\n\n### Step 2: Configure URL Protection\n- Enable Safe Links \u002F URL rewriting\n- Enable time-of-click URL detonation\n- Block newly registered domains (\u003C 30 days)\n- Enable URL redirect chain following\n\n### Step 3: Configure Attachment Sandboxing\n- Enable Safe Attachments \u002F attachment sandboxing\n- Configure dynamic delivery (deliver body, hold attachments)\n- Set sandbox detonation timeout to 60+ seconds\n- Block macro-enabled Office documents from external senders\n\n### Step 4: Create Custom Detection Rules\nUse the `scripts\u002Fprocess.py` to analyze email gateway logs, identify spearphishing patterns, and generate custom detection rules.\n\n### Step 5: Configure Alert and Response Actions\n- Real-time alerts for impersonation attempts\n- Automatic quarantine for high-confidence detections\n- User notification with safety tips\n- Integration with SIEM for correlation\n\n## Tools & Resources\n- **Microsoft Defender for Office 365**: https:\u002F\u002Fsecurity.microsoft.com\n- **Proofpoint Email Protection**: https:\u002F\u002Fwww.proofpoint.com\u002Fus\u002Fproducts\u002Femail-security\n- **Mimecast Email Security**: https:\u002F\u002Fwww.mimecast.com\u002Fproducts\u002Femail-security\u002F\n- **Barracuda Email Protection**: https:\u002F\u002Fwww.barracuda.com\u002Fproducts\u002Femail-protection\n\n## Validation\n- Impersonation protection correctly identifies spoofed VIP display names\n- URL detonation catches malicious links in test phishing emails\n- Attachment sandboxing detects weaponized documents\n- Custom rules trigger on known spearphishing patterns\n- SIEM integration receives gateway alerts\n",{"name":5,"tags":49,"author":54,"domain":43,"license":15,"version":55,"category":5,"nist_csf":56,"subdomain":61,"description":7,"mitre_attack":62},[50,51,52,41,53,27,39],"phishing","email-security","social-engineering","awareness","mahipal","1.0",[57,58,59,60],"PR.AT-01","DE.CM-09","RS.CO-02","DE.AE-02","phishing-defense",[63,64,65,66],"T1566.001","T1566.002","T1204.001","T1204.002","main","5eea5b3296f4673b5f481e8bcc1ba76281149f16","modules\u002Fdetecting-spearphishing-with-email-gateway",0,"https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core","https:\u002F\u002Fgithub.com\u002FHenriqueMC17","Qualquer tecnologia suficientemente avançada é indistinguível da mágica.","2026-09-28 22:40:38",{"source":8,"skillName":5,"commands":76,"prompt":86,"zipAvailable":87},[77,80,83],{"tool":78,"command":79},"npx","npx skills add HenriqueMC17\u002Fagente-core --skill detecting-spearphishing-with-email-gateway",{"tool":81,"command":82},"bunx","bunx skills add HenriqueMC17\u002Fagente-core --skill detecting-spearphishing-with-email-gateway",{"tool":84,"command":85},"pnpm","pnpm dlx skills add HenriqueMC17\u002Fagente-core --skill detecting-spearphishing-with-email-gateway","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fdetecting-spearphishing-with-email-gateway\u002FSKILL.md",true,[89,95,100,106,110,114,120],{"path":90,"resourceType":91,"resourceTypeDesc":92,"sizeBytes":93,"sourceHtmlUrl":94},"assets\u002Ftemplate.md","ASSET","资产文件",1928,"https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fdetecting-spearphishing-with-email-gateway\u002Fassets\u002Ftemplate.md",{"path":96,"resourceType":96,"resourceTypeDesc":97,"sizeBytes":98,"sourceHtmlUrl":99},"LICENSE","许可证",11255,"https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fdetecting-spearphishing-with-email-gateway\u002FLICENSE",{"path":101,"resourceType":102,"resourceTypeDesc":103,"sizeBytes":104,"sourceHtmlUrl":105},"references\u002Fapi-reference.md","REFERENCE","参考文档",2296,"https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fdetecting-spearphishing-with-email-gateway\u002Freferences\u002Fapi-reference.md",{"path":107,"resourceType":102,"resourceTypeDesc":103,"sizeBytes":108,"sourceHtmlUrl":109},"references\u002Fstandards.md",2489,"https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fdetecting-spearphishing-with-email-gateway\u002Freferences\u002Fstandards.md",{"path":111,"resourceType":102,"resourceTypeDesc":103,"sizeBytes":112,"sourceHtmlUrl":113},"references\u002Fworkflows.md",3813,"https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fdetecting-spearphishing-with-email-gateway\u002Freferences\u002Fworkflows.md",{"path":115,"resourceType":116,"resourceTypeDesc":117,"sizeBytes":118,"sourceHtmlUrl":119},"scripts\u002Fagent.py","SCRIPT","脚本",5768,"https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fdetecting-spearphishing-with-email-gateway\u002Fscripts\u002Fagent.py",{"path":121,"resourceType":116,"resourceTypeDesc":117,"sizeBytes":122,"sourceHtmlUrl":123},"scripts\u002Fprocess.py",21603,"https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fdetecting-spearphishing-with-email-gateway\u002Fscripts\u002Fprocess.py",[125,154,179,201,217,235],{"skillNo":126,"name":127,"nameZh":6,"description":128,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":129,"categories":130,"keywords":134,"publishedAt":44},"01M6HPFF0RCN0X6WT5EBSV71GY","validating-backup-integrity-for-recovery","Validate backup integrity through cryptographic hash verification, automated restore testing, corruption detection, and recoverability checks to ensure backups are reliable for disaster recovery and ransomware response scenarios.","https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fvalidating-backup-integrity-for-recovery\u002FSKILL.md",[131],{"categoryNo":132,"categoryName":133,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",[135,136,137,138,139,140,43,141,142,143,144,145,146,147,148,149,150,151,152,153],"integrity","backup","recovery","validating backup integrity for recovery","for","testing","validate","verification","hash-verification","incident-response","ransomware","detection","t1078","t1490","disaster-recovery","restore","incident","disaster recovery","ransomware response",{"skillNo":155,"name":156,"nameZh":6,"description":157,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":158,"categories":159,"keywords":160,"publishedAt":44},"01M6HPFAWJVFK25Q33K3T7WQ8G","triaging-vulnerabilities-with-ssvc-framework","Triage and prioritize vulnerabilities using CISA's Stakeholder-Specific Vulnerability Categorization (SSVC) decision tree framework to produce actionable remediation priorities.","https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Ftriaging-vulnerabilities-with-ssvc-framework\u002FSKILL.md",[],[161,162,163,164,28,43,165,166,167,168,169,170,171,172,173,174,175,176,177,178],"vulnerabilities","framework","ssvc","triaging vulnerabilities with ssvc framework","triage and prioritize","CISA","vulnerability-management","risk-management","cvss","remediation","vulnerability","prioritization","decision-tree","prioritize","decision","priorities","actionable","tree",{"skillNo":180,"name":181,"nameZh":6,"description":182,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":183,"categories":184,"keywords":185,"publishedAt":44},"01M6HPF6JS9X72WP59094H3ASQ","triaging-security-incident","Performs initial triage of security incidents to determine severity, scope, and required response actions using the NIST SP 800-61r3 and SANS PICERL frameworks. Classifies incidents by type, assigns priority based on business impact, and routes...","https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Ftriaging-security-incident\u002FSKILL.md",[],[38,186,151,43,187,188,189,147,148,190,191,192,193,194,195,196,197,198,199,200],"triaging security incident","actions","soc","NIST","analysis","severity-classification","incident-triage","SANS-PICERL","SOC-operations","picerl","conversion","isolation","scope","impact","consistency",{"skillNo":202,"name":203,"nameZh":6,"description":204,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":205,"categories":206,"keywords":207,"publishedAt":44},"01M6HPF2EX6ZYNYYHKBRJN7GEF","triaging-security-incident-with-ir-playbook","Classify and prioritize security incidents using structured IR playbooks to determine severity, assign response teams, and initiate appropriate response procedures.","https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Ftriaging-security-incident-with-ir-playbook\u002FSKILL.md",[],[38,208,209,186,151,28,43,210,188,144,211,212,147,148,213,191,174,214,215,216],"playbook","triaging security incident with ir playbook","teams","IR-playbook","severity","classification","classify","incidents","initiate",{"skillNo":218,"name":219,"nameZh":6,"description":220,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":221,"categories":222,"keywords":223,"publishedAt":44},"01M6HPEY9XPGE7X95AG4XJFQAW","triaging-security-alerts-in-splunk","Triages security alerts in Splunk Enterprise Security by classifying severity, investigating notable events, correlating related telemetry, and making escalation or closure decisions using SPL queries and the Incident Review dashboard. Use when...","https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Ftriaging-security-alerts-in-splunk\u002FSKILL.md",[],[38,224,225,226,227,228,43,229,230,231,188,232,147,30,233,234,194,37,151,34],"security alerts","splunk","triaging security alerts in splunk","alerts","review","siem","dashboard","search","correlation-search","notable-events","incident-review",{"skillNo":236,"name":237,"nameZh":6,"description":238,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":239,"categories":240,"keywords":241,"publishedAt":44},"01M6HPET6XGEPEJPN7V032JGZ0","tracking-threat-actor-infrastructure","Threat actor infrastructure tracking involves monitoring and mapping adversary-controlled assets including command-and-control (C2) servers, phishing domains, exploit kit hosts, bulletproof hosting, a","https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Ftracking-threat-actor-infrastructure\u002FSKILL.md",[],[242,243,244,245,43,246,247,248,249,250,251,30,252,253,37,254,34,255,256,257],"infrastructure","tracking threat actor infrastructure","tracking","threat","monitoring","mitre-attack","threat-actor","threat-intelligence","command-and-control","dns","command","exploit","intelligence","domains","kit","hosts"]