[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71DBQQC17CD1REJNWVRQC8G":3,"skill-same:01M71DBQQC17CD1REJNWVRQC8G":98},{"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":26,"publishedAt":47,"linkOnly":48,"markdownContent":49,"markdownBody":50,"frontMatter":51,"refName":71,"commitSha":72,"skillDirectory":73,"forksCount":14,"repositoryHtmlUrl":74,"repositoryHomepageUrl":6,"ownerHtmlUrl":75,"ownerBlogUrl":6,"ownerDescription":76,"updatedAt":77,"install":78,"resources":91},"01M71DBQQC17CD1REJNWVRQC8G","phishing-proofpoint-detect",null,"Deploy and configure Proofpoint Email Protection as a secure email gateway to detect and block phishing, malware, BEC, and spam before messages reach user inboxes.","DCx7C5\u002Fai-marketplace","DCx7C5","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F42419559?v=4","01M71C01G2AZV3NTNGWAWSHJPP","DC","01M71C01GQW6G50S2BYMS7PP3E",0,"MIT","https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace\u002Fblob\u002Fmain\u002Fskills\u002Femail\u002Fphishing\u002Fproofpoint\u002Fdetect\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000005","邮件与沟通","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000011","运维与部署",[27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46],"phishing","detect","phishing proofpoint detect","proofpoint","secure","read","at","co","email-filtering","anti-malware","de","anti-spam","secure-email-gateway","Bash","configure","cybersecurity","spam","messages","cm","t1566","2026-11-10 10:12:30",false,"---\nname: phishing-proofpoint-detect\ndescription: Deploy and configure Proofpoint Email Protection as a secure email gateway to detect and block phishing, malware, BEC, and spam before messages reach user inboxes.\ndomain: cybersecurity\nsubdomain: phishing-defense\ntags:\n- email-security\n- proofpoint\n- secure-email-gateway\n- phishing\n- anti-spam\n- anti-malware\n- bec\n- email-filtering\nnist_csf:\n- PR.AT-01\n- DE.CM-09\n- RS.CO-02\n- DE.AE-02\nmodel: sonnet\nmaxTurns: 20\ntools: [Read, Bash, Glob, Grep]\nmitre_attack:\n- T1059\n- T1566\ncapec: []\n---\n\n# Implementing Proofpoint Email Security Gateway\n\n## Overview\nProofpoint Email Protection is a cloud-native secure email gateway (SEG) that acts as a security checkpoint where all inbound and outbound mail traffic routes through the gateway before reaching user inboxes. It combines signature-based detection for known malware, machine learning algorithms for emerging threats, real-time threat intelligence feeds, URL rewriting with time-of-click sandboxing, and behavioral analysis for BEC detection. Proofpoint processes over 2.8 billion emails daily and blocks over 1 million extortion attempts per day.\n\n\n## When to Use\n\n- When deploying or configuring implementing proofpoint email security gateway capabilities in your environment\n- When establishing security controls aligned to compliance requirements\n- When building or improving security architecture for this domain\n- When conducting security assessments that require this implementation\n\n## Prerequisites\n- Proofpoint Email Protection license (PPS on-premises or Proofpoint on Demand cloud)\n- Administrative access to DNS management for MX record changes\n- Microsoft 365 or Google Workspace email environment\n- Understanding of mail flow architecture and SPF\u002FDKIM\u002FDMARC\n- Network firewall rules permitting Proofpoint IP ranges\n\n## Key Concepts\n\n### Deployment Models\n1. **MX-Based Gateway (Traditional SEG)**: All mail routes through Proofpoint via MX record changes; intercepts threats before delivery\n2. **API-Based Integration**: Connects directly to Microsoft 365 or Google Workspace via API; no MX changes required; can be operational within 48 hours\n3. **Hybrid Deployment**: Combines gateway and API for layered protection\n\n### Core Detection Technologies\n- **Impostor Classifier**: ML model detecting BEC\u002Fimpersonation with no malicious URLs or attachments\n- **URL Defense**: Rewrites URLs and performs real-time sandboxing at time of click\n- **Attachment Defense**: Sandboxes suspicious attachments in virtual environments\n- **Nexus Threat Graph**: Cross-customer threat intelligence correlation engine\n- **Supplier Threat Detection**: Identifies compromised vendor email accounts\n\n### Protection Layers\n| Layer | Technology | Threat Type |\n|---|---|---|\n| Connection | IP reputation, rate limiting | Spam botnets |\n| Authentication | SPF, DKIM, DMARC enforcement | Spoofing |\n| Content | ML classifiers, NLP analysis | BEC, phishing |\n| URL | Rewriting + time-of-click sandbox | Credential theft |\n| Attachment | Static + dynamic sandboxing | Malware, ransomware |\n| Post-delivery | TRAP (auto-retraction) | Weaponized after delivery |\n\n## Workflow\n\n### Step 1: Plan Mail Flow Architecture\n- Document current MX records and mail flow path\n- Identify all legitimate sending sources (marketing platforms, CRM, ticketing systems)\n- Map inbound connectors and transport rules in Microsoft 365 or Google Workspace\n- Plan IP allowlisting for Proofpoint egress IPs on receiving infrastructure\n- Configure SPF record to include Proofpoint: `v=spf1 include:spf.protection.outlook.com include:spf-a.proofpoint.com -all`\n\n### Step 2: Configure Proofpoint Policies\n- Create organizational units matching business structure\n- Define inbound mail policies: anti-spam, anti-virus, impostor detection\n- Configure Smart Search quarantine with end-user digest notifications\n- Set up Proofpoint Encryption for sensitive outbound messages\n- Enable Targeted Attack Protection (TAP) for URL and attachment sandboxing\n\n### Step 3: Deploy Email Authentication\n- Configure DKIM signing through Proofpoint for outbound messages\n- Set DMARC policy to monitor mode initially: `v=DMARC1; p=none; rua=mailto:dmarc@company.com`\n- Enable inbound DMARC enforcement to reject spoofed messages\n- Configure anti-spoofing rules for executive impersonation protection\n\n### Step 4: Enable Advanced Threat Protection\n- Activate URL Defense with rewriting enabled for all inbound messages\n- Configure Attachment Defense sandbox policies (safe attachment mode)\n- Enable Threat Response Auto-Pull (TRAP) for post-delivery remediation\n- Set up TAP Dashboard alerts for targeted attack campaigns\n- Configure Supplier Risk monitoring for vendor email compromise\n\n### Step 5: Migrate MX Records\n- Lower MX record TTL to 300 seconds 48 hours before cutover\n- Update MX records to point to Proofpoint: `company-com.mail.protection.proofpoint.com`\n- Configure connector restrictions in Microsoft 365 to accept mail only from Proofpoint IPs\n- Monitor mail flow through Proofpoint Message Trace for 48-72 hours\n- Verify no legitimate mail is being blocked or delayed\n\n### Step 6: Tune and Optimize\n- Review quarantine and false positive\u002Fnegative rates weekly for first month\n- Adjust spam thresholds based on organizational tolerance\n- Add approved senders and safe lists for legitimate bulk mail\n- Configure data loss prevention (DLP) rules for outbound sensitive content\n- Enable email warning banners for external sender identification\n\n## Tools & Resources\n- **Proofpoint TAP Dashboard**: Real-time threat visibility and campaign tracking\n- **Proofpoint TRAP**: Automated post-delivery email retraction\n- **Proofpoint SER (Spam\u002FEnd-user Release)**: Self-service quarantine management\n- **Proofpoint Closed-Loop Email Analysis (CLEAR)**: Phishing report button integration\n- **MX Toolbox**: DNS record verification and mail flow testing\n\n## Validation\n- All inbound email routes through Proofpoint (verify MX records and message headers)\n- TAP Dashboard shows threat detections and blocked campaigns\n- URL Defense rewrites links in test messages and sandboxes at click time\n- Attachment Defense detonates test malware samples in sandbox\n- TRAP successfully retracts test phishing message from inboxes post-delivery\n- False positive rate below 0.1% after initial tuning period\n- DMARC\u002FSPF\u002FDKIM authentication passes for all legitimate outbound mail\n","# Implementing Proofpoint Email Security Gateway\n\n## Overview\nProofpoint Email Protection is a cloud-native secure email gateway (SEG) that acts as a security checkpoint where all inbound and outbound mail traffic routes through the gateway before reaching user inboxes. It combines signature-based detection for known malware, machine learning algorithms for emerging threats, real-time threat intelligence feeds, URL rewriting with time-of-click sandboxing, and behavioral analysis for BEC detection. Proofpoint processes over 2.8 billion emails daily and blocks over 1 million extortion attempts per day.\n\n\n## When to Use\n\n- When deploying or configuring implementing proofpoint email security gateway capabilities in your environment\n- When establishing security controls aligned to compliance requirements\n- When building or improving security architecture for this domain\n- When conducting security assessments that require this implementation\n\n## Prerequisites\n- Proofpoint Email Protection license (PPS on-premises or Proofpoint on Demand cloud)\n- Administrative access to DNS management for MX record changes\n- Microsoft 365 or Google Workspace email environment\n- Understanding of mail flow architecture and SPF\u002FDKIM\u002FDMARC\n- Network firewall rules permitting Proofpoint IP ranges\n\n## Key Concepts\n\n### Deployment Models\n1. **MX-Based Gateway (Traditional SEG)**: All mail routes through Proofpoint via MX record changes; intercepts threats before delivery\n2. **API-Based Integration**: Connects directly to Microsoft 365 or Google Workspace via API; no MX changes required; can be operational within 48 hours\n3. **Hybrid Deployment**: Combines gateway and API for layered protection\n\n### Core Detection Technologies\n- **Impostor Classifier**: ML model detecting BEC\u002Fimpersonation with no malicious URLs or attachments\n- **URL Defense**: Rewrites URLs and performs real-time sandboxing at time of click\n- **Attachment Defense**: Sandboxes suspicious attachments in virtual environments\n- **Nexus Threat Graph**: Cross-customer threat intelligence correlation engine\n- **Supplier Threat Detection**: Identifies compromised vendor email accounts\n\n### Protection Layers\n| Layer | Technology | Threat Type |\n|---|---|---|\n| Connection | IP reputation, rate limiting | Spam botnets |\n| Authentication | SPF, DKIM, DMARC enforcement | Spoofing |\n| Content | ML classifiers, NLP analysis | BEC, phishing |\n| URL | Rewriting + time-of-click sandbox | Credential theft |\n| Attachment | Static + dynamic sandboxing | Malware, ransomware |\n| Post-delivery | TRAP (auto-retraction) | Weaponized after delivery |\n\n## Workflow\n\n### Step 1: Plan Mail Flow Architecture\n- Document current MX records and mail flow path\n- Identify all legitimate sending sources (marketing platforms, CRM, ticketing systems)\n- Map inbound connectors and transport rules in Microsoft 365 or Google Workspace\n- Plan IP allowlisting for Proofpoint egress IPs on receiving infrastructure\n- Configure SPF record to include Proofpoint: `v=spf1 include:spf.protection.outlook.com include:spf-a.proofpoint.com -all`\n\n### Step 2: Configure Proofpoint Policies\n- Create organizational units matching business structure\n- Define inbound mail policies: anti-spam, anti-virus, impostor detection\n- Configure Smart Search quarantine with end-user digest notifications\n- Set up Proofpoint Encryption for sensitive outbound messages\n- Enable Targeted Attack Protection (TAP) for URL and attachment sandboxing\n\n### Step 3: Deploy Email Authentication\n- Configure DKIM signing through Proofpoint for outbound messages\n- Set DMARC policy to monitor mode initially: `v=DMARC1; p=none; rua=mailto:dmarc@company.com`\n- Enable inbound DMARC enforcement to reject spoofed messages\n- Configure anti-spoofing rules for executive impersonation protection\n\n### Step 4: Enable Advanced Threat Protection\n- Activate URL Defense with rewriting enabled for all inbound messages\n- Configure Attachment Defense sandbox policies (safe attachment mode)\n- Enable Threat Response Auto-Pull (TRAP) for post-delivery remediation\n- Set up TAP Dashboard alerts for targeted attack campaigns\n- Configure Supplier Risk monitoring for vendor email compromise\n\n### Step 5: Migrate MX Records\n- Lower MX record TTL to 300 seconds 48 hours before cutover\n- Update MX records to point to Proofpoint: `company-com.mail.protection.proofpoint.com`\n- Configure connector restrictions in Microsoft 365 to accept mail only from Proofpoint IPs\n- Monitor mail flow through Proofpoint Message Trace for 48-72 hours\n- Verify no legitimate mail is being blocked or delayed\n\n### Step 6: Tune and Optimize\n- Review quarantine and false positive\u002Fnegative rates weekly for first month\n- Adjust spam thresholds based on organizational tolerance\n- Add approved senders and safe lists for legitimate bulk mail\n- Configure data loss prevention (DLP) rules for outbound sensitive content\n- Enable email warning banners for external sender identification\n\n## Tools & Resources\n- **Proofpoint TAP Dashboard**: Real-time threat visibility and campaign tracking\n- **Proofpoint TRAP**: Automated post-delivery email retraction\n- **Proofpoint SER (Spam\u002FEnd-user Release)**: Self-service quarantine management\n- **Proofpoint Closed-Loop Email Analysis (CLEAR)**: Phishing report button integration\n- **MX Toolbox**: DNS record verification and mail flow testing\n\n## Validation\n- All inbound email routes through Proofpoint (verify MX records and message headers)\n- TAP Dashboard shows threat detections and blocked campaigns\n- URL Defense rewrites links in test messages and sandboxes at click time\n- Attachment Defense detonates test malware samples in sandbox\n- TRAP successfully retracts test phishing message from inboxes post-delivery\n- False positive rate below 0.1% after initial tuning period\n- DMARC\u002FSPF\u002FDKIM authentication passes for all legitimate outbound mail\n",{"name":5,"tags":52,"capec":55,"model":56,"tools":57,"domain":42,"maxTurns":61,"nist_csf":62,"subdomain":67,"description":7,"mitre_attack":68},[53,30,39,27,38,36,54,35],"email-security","bec",[],"sonnet",[58,40,59,60],"Read","Glob","Grep",20,[63,64,65,66],"PR.AT-01","DE.CM-09","RS.CO-02","DE.AE-02","phishing-defense",[69,70],"T1059","T1566","main","a91f1293287ffa9f4f1b8f486cd6e835a1568c84","skills\u002Femail\u002Fphishing\u002Fproofpoint\u002Fdetect","https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace","https:\u002F\u002Fgithub.com\u002FDCx7C5","#Python","2026-09-01 11:21:00",{"source":8,"skillName":5,"commands":79,"prompt":89,"zipAvailable":90},[80,83,86],{"tool":81,"command":82},"npx","npx skills add DCx7C5\u002Fai-marketplace --skill phishing-proofpoint-detect",{"tool":84,"command":85},"bunx","bunx skills add DCx7C5\u002Fai-marketplace --skill phishing-proofpoint-detect",{"tool":87,"command":88},"pnpm","pnpm dlx skills add DCx7C5\u002Fai-marketplace --skill phishing-proofpoint-detect","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace\u002Fblob\u002Fmain\u002Fskills\u002Femail\u002Fphishing\u002Fproofpoint\u002Fdetect\u002FSKILL.md",true,[92],{"path":93,"resourceType":94,"resourceTypeDesc":95,"sizeBytes":96,"sourceHtmlUrl":97},"index.json","REFERENCE","参考文档",652,"https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace\u002Fblob\u002Fmain\u002Fskills\u002Femail\u002Fphishing\u002Fproofpoint\u002Fdetect\u002Findex.json",[99,121,142,163,185,201],{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":47},"01M71HAPZ01KQ30RKTB0FFSQ05","services-wmi-persistence-detect","Detect WMI event subscription persistence by enumerating ActiveScriptEventConsumer, CommandLineEventConsumer, and permanent subscriptions in the WMI repository.","https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace\u002Fblob\u002Fmain\u002Fskills\u002Fwindows\u002Fservices\u002Fwmi\u002Fpersistence\u002Fdetect\u002FSKILL.md",[],[106,28,107,108,109,37,45,110,111,112,113,114,115,116,117,118,119,42,120],"services","services wmi persistence detect","wmi","persistence","process","activescript","event","subscriptions","commandline-consumer","repository","subscription","event-subscription","t1546.003","forensics","process-forensics",{"skillNo":122,"name":123,"nameZh":6,"description":124,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":125,"categories":126,"keywords":127,"publishedAt":47},"01M71HAK6JTTTS229T17WJMMCG","services-wmi-exec-exploit","Perform lateral movement across Windows networks using WMI-based remote execution techniques including Impacket wmiexec.py, CrackMapExec, and native WMI commands for stealthy post-exploitation during red team engagements.","https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace\u002Fblob\u002Fmain\u002Fskills\u002Fwindows\u002Fservices\u002Fwmi\u002Fexec\u002Fexploit\u002FSKILL.md",[],[128,106,129,108,130,131,132,42,40,133,134,135,136,137,37,138,139,32,140,141],"exploit","services wmi exec exploit","exec","remote","traffic","analysis","team","across","crackmapexec","native","command","lateral movement","lateral-movement","Impacket",{"skillNo":143,"name":144,"nameZh":6,"description":145,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":146,"categories":147,"keywords":148,"publishedAt":47},"01M71HAG6MHKNQV8KDZKMT4886","registry-artifact-extract","Extract and analyze Windows Registry hives to uncover user activity, installed software, autostart entries, and evidence of system compromise.","https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace\u002Fblob\u002Fmain\u002Fskills\u002Fwindows\u002Fregistry\u002Fartifact\u002Fextract\u002FSKILL.md",[],[149,150,151,152,153,154,42,40,155,133,156,157,37,32,158,159,160,161,162,56],"artifact","registry","registry artifact extract","extract","evidence-collection","artifact-analysis","collection","analyze","uncover","software","activity","digital-forensics","windows-registry","regripper",{"skillNo":164,"name":165,"nameZh":6,"description":166,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":167,"categories":168,"keywords":169,"publishedAt":47},"01M71HACR4A8XTWTTSXK4124AA","processes-token-impersonate-detect","Detect Windows token impersonation and privilege abuse including SeImpersonatePrivilege exploitation via Potato attacks and token stealing techniques.","https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace\u002Fblob\u002Fmain\u002Fskills\u002Fwindows\u002Fprocesses\u002Ftoken\u002Fimpersonate\u002Fdetect\u002FSKILL.md",[],[28,170,171,172,173,174,175,45,176,42,120,177,178,179,180,181,182,183,184,37],"processes token impersonate detect","token","processes","attacks","windows","escalation","techniques","privilege-escalation","seimpersonate","token-impersonation","printspoofer","exploitation","potato","impersonation","via",{"skillNo":186,"name":187,"nameZh":6,"description":188,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":189,"categories":190,"keywords":191,"publishedAt":47},"01M71HAABSB4Z6QFSXEG00R4RK","processes-thread-injection-detect","Detect Windows thread injection techniques including CreateRemoteThread, QueueUserAPC, NtCreateThreadEx, and thread hijacking via process memory analysis.","https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace\u002Fblob\u002Fmain\u002Fskills\u002Fwindows\u002Fprocesses\u002Fthread\u002Finjection\u002Fdetect\u002FSKILL.md",[],[192,193,28,194,172,174,195,45,196,176,42,120,133,197,198,199,200,184,37,110],"thread","processes thread injection detect","injection","memory","process-injection","api","apc-injection","thread-injection","nt-api",{"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":47},"01M71HA7H311V5G14WMX58HQSS","processes-hollow-technique-detect","Detect process hollowing (RunPE) by identifying processes with mismatched image paths between PEB and VAD tree, or unmapped PE headers in memory.","https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace\u002Fblob\u002Fmain\u002Fskills\u002Fwindows\u002Fprocesses\u002Fhollow\u002Ftechnique\u002Fdetect\u002FSKILL.md",[],[208,28,172,209,195,45,210,211,42,120,212,213,214,215,216,217,37,110,218,219],"processes hollow technique detect","tree","memory-forensics","process-hollow","peb","runpe","image","pe-header","in memory","with","mismatched","headers"]