[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71DA2BYMSP46WJTJP2C4BYP":3,"skill-same:01M71DA2BYMSP46WJTJP2C4BYP":61},{"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":29,"linkOnly":30,"markdownContent":31,"markdownBody":32,"frontMatter":33,"refName":34,"commitSha":35,"skillDirectory":36,"forksCount":14,"repositoryHtmlUrl":37,"repositoryHomepageUrl":6,"ownerHtmlUrl":38,"ownerBlogUrl":6,"ownerDescription":39,"updatedAt":40,"install":41,"resources":54},"01M71DA2BYMSP46WJTJP2C4BYP","email-phishing-proofpoint",null,"Email Phishing Proofpoint.","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-phishing-proofpoint\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000005","邮件与沟通","SCENARIO","使用场景",[24,25,26,27,28],"email","phishing","proofpoint","email phishing proofpoint","cybersecurity","2026-11-10 10:12:30",false,"---\nname: email-phishing-proofpoint\ndescription: \"Email Phishing Proofpoint.\"\ndomain: cybersecurity\n---\n\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","|\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,"domain":28,"description":7},"main","a91f1293287ffa9f4f1b8f486cd6e835a1568c84","skills\u002Femail-phishing-proofpoint","https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace","https:\u002F\u002Fgithub.com\u002FDCx7C5","#Python","2026-09-01 11:21:00",{"source":8,"skillName":5,"commands":42,"prompt":52,"zipAvailable":53},[43,46,49],{"tool":44,"command":45},"npx","npx skills add DCx7C5\u002Fai-marketplace --skill email-phishing-proofpoint",{"tool":47,"command":48},"bunx","bunx skills add DCx7C5\u002Fai-marketplace --skill email-phishing-proofpoint",{"tool":50,"command":51},"pnpm","pnpm dlx skills add DCx7C5\u002Fai-marketplace --skill email-phishing-proofpoint","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace\u002Fblob\u002Fmain\u002Fskills\u002Femail-phishing-proofpoint\u002FSKILL.md",true,[55],{"path":56,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":59,"sourceHtmlUrl":60},"index.json","REFERENCE","参考文档",500,"https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace\u002Fblob\u002Fmain\u002Fskills\u002Femail-phishing-proofpoint\u002Findex.json",[62,87,110,132,154,170],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":29},"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",[],[69,70,71,72,73,74,75,76,77,78,79,80,81,82,83,84,85,28,86],"services","detect","services wmi persistence detect","wmi","persistence","de","cm","process","activescript","event","subscriptions","commandline-consumer","repository","subscription","event-subscription","t1546.003","forensics","process-forensics",{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":29},"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",[],[94,69,95,72,96,97,98,28,99,100,101,102,103,104,74,105,106,107,108,109],"exploit","services wmi exec exploit","exec","remote","traffic","Bash","analysis","team","across","crackmapexec","native","command","lateral movement","read","lateral-movement","Impacket",{"skillNo":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":114,"categories":115,"keywords":116,"publishedAt":29},"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",[],[117,118,119,120,121,122,28,99,123,100,124,125,74,107,126,127,128,129,130,131],"artifact","registry","registry artifact extract","extract","evidence-collection","artifact-analysis","collection","analyze","uncover","software","activity","digital-forensics","windows-registry","regripper","sonnet",{"skillNo":133,"name":134,"nameZh":6,"description":135,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":136,"categories":137,"keywords":138,"publishedAt":29},"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",[],[70,139,140,141,142,143,144,75,145,28,86,146,147,148,149,150,151,152,153,74],"processes token impersonate detect","token","processes","attacks","windows","escalation","techniques","privilege-escalation","seimpersonate","token-impersonation","printspoofer","exploitation","potato","impersonation","via",{"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":29},"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",[],[161,162,70,163,141,143,164,75,165,145,28,86,100,166,167,168,169,153,74,76],"thread","processes thread injection detect","injection","memory","process-injection","api","apc-injection","thread-injection","nt-api",{"skillNo":171,"name":172,"nameZh":6,"description":173,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":174,"categories":175,"keywords":176,"publishedAt":29},"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",[],[177,70,141,178,164,75,179,180,28,86,181,182,183,184,185,186,74,76,187,188],"processes hollow technique detect","tree","memory-forensics","process-hollow","peb","runpe","image","pe-header","in memory","with","mismatched","headers"]