[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6AFBBQ536P402BMTJ4V53PW":3,"skill-same:01M6AFBBQ536P402BMTJ4V53PW":158},{"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":29,"publishedAt":50,"linkOnly":51,"markdownContent":52,"markdownBody":53,"frontMatter":54,"refName":99,"commitSha":100,"skillDirectory":101,"forksCount":102,"repositoryHtmlUrl":103,"repositoryHomepageUrl":104,"ownerHtmlUrl":105,"ownerBlogUrl":106,"ownerDescription":107,"updatedAt":108,"install":109,"resources":122},"01M6AFBBQ536P402BMTJ4V53PW","implementing-proofpoint-email-security-gateway",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.","mukul975\u002FAnthropic-Cybersecurity-Skills","mukul975","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F42860185?v=4","01M6ADEQR8T5M4EEG6C67BQCWF","Mahipal","01M6ADJPMYWG1E5GM1FWBE3128",35925,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fimplementing-proofpoint-email-security-gateway\u002FSKILL.md",[18,23,26],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000005","邮件与沟通","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000011","运维与部署",{"categoryNo":27,"categoryName":28,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49],"implementing proofpoint email security gateway","gateway","email","proofpoint","security","defense","email-filtering","anti-malware","anti-spam","secure-email-gateway","t1566","initial-access","email-gateway","malware","messages","secure","official","change","customer","cybersecurity","2026-11-10 10:12:30",false,"---\nname: implementing-proofpoint-email-security-gateway\ndescription: Deploy and configure Proofpoint Email Protection as a secure email gateway\n  to detect and block phishing, malware, BEC, and spam before messages reach user\n  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\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\n- T1598\n- T1534\n- T1036\n- T1027\nmitre_f3:\n  version: '1.1'\n  tactics:\n  - reconnaissance\n  - initial-access\n  - stealth\n  - positioning\n  techniques:\n  - id: T1598\n    name: Phishing for Information\n    tactic: reconnaissance\n    source: attack\n  - id: T1660\n    name: Phishing\n    tactic: initial-access\n    source: attack\n  - id: T1672\n    name: Email Spoofing\n    tactic: stealth\n    source: attack\n  - id: F1032\n    name: Impersonate Official\n    tactic: initial-access\n    source: f3\n  - id: F1029\n    name: Gather Customer Information\n    tactic: reconnaissance\n    source: f3\n  - id: F1005.006\n    name: 'Account Manipulation: Change of Payment Details'\n    tactic: positioning\n    source: f3\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":55,"author":59,"domain":49,"license":15,"version":60,"mitre_f3":61,"nist_csf":88,"subdomain":93,"description":7,"mitre_attack":94},[56,33,39,57,38,37,58,36],"email-security","phishing","bec","mahipal","1.0",{"tactics":62,"version":66,"techniques":67},[63,41,64,65],"reconnaissance","stealth","positioning","1.1",[68,72,75,78,82,85],{"id":69,"name":70,"source":71,"tactic":63},"T1598","Phishing for Information","attack",{"id":73,"name":74,"source":71,"tactic":41},"T1660","Phishing",{"id":76,"name":77,"source":71,"tactic":64},"T1672","Email Spoofing",{"id":79,"name":80,"source":81,"tactic":41},"F1032","Impersonate Official","f3",{"id":83,"name":84,"source":81,"tactic":63},"F1029","Gather Customer Information",{"id":86,"name":87,"source":81,"tactic":65},"F1005.006","Account Manipulation: Change of Payment Details",[89,90,91,92],"PR.AT-01","DE.CM-09","RS.CO-02","DE.AE-02","phishing-defense",[95,69,96,97,98],"T1566","T1534","T1036","T1027","main","54a798831d2266a3ca61ce68a7acb80b81160d57","skills\u002Fimplementing-proofpoint-email-security-gateway",4384,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills","https:\u002F\u002Fmahipal.engineer\u002FAnthropic-Cybersecurity-Skills\u002F","https:\u002F\u002Fgithub.com\u002Fmukul975","Mahipal.engineer","🔐 Cybersecurity | 💻 Dev | 📷 Street Photographer\r\n🎓 MSc | 📚 Research & AI Security","2026-08-31 12:32:44",{"source":8,"skillName":5,"commands":110,"prompt":120,"zipAvailable":121},[111,114,117],{"tool":112,"command":113},"npx","npx skills add mukul975\u002FAnthropic-Cybersecurity-Skills --skill implementing-proofpoint-email-security-gateway",{"tool":115,"command":116},"bunx","bunx skills add mukul975\u002FAnthropic-Cybersecurity-Skills --skill implementing-proofpoint-email-security-gateway",{"tool":118,"command":119},"pnpm","pnpm dlx skills add mukul975\u002FAnthropic-Cybersecurity-Skills --skill implementing-proofpoint-email-security-gateway","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fimplementing-proofpoint-email-security-gateway\u002FSKILL.md",true,[123,129,134,140,144,148,154],{"path":124,"resourceType":125,"resourceTypeDesc":126,"sizeBytes":127,"sourceHtmlUrl":128},"assets\u002Ftemplate.md","ASSET","资产文件",1739,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fimplementing-proofpoint-email-security-gateway\u002Fassets\u002Ftemplate.md",{"path":130,"resourceType":130,"resourceTypeDesc":131,"sizeBytes":132,"sourceHtmlUrl":133},"LICENSE","许可证",11255,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fimplementing-proofpoint-email-security-gateway\u002FLICENSE",{"path":135,"resourceType":136,"resourceTypeDesc":137,"sizeBytes":138,"sourceHtmlUrl":139},"references\u002Fapi-reference.md","REFERENCE","参考文档",5181,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fimplementing-proofpoint-email-security-gateway\u002Freferences\u002Fapi-reference.md",{"path":141,"resourceType":136,"resourceTypeDesc":137,"sizeBytes":142,"sourceHtmlUrl":143},"references\u002Fstandards.md",1750,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fimplementing-proofpoint-email-security-gateway\u002Freferences\u002Fstandards.md",{"path":145,"resourceType":136,"resourceTypeDesc":137,"sizeBytes":146,"sourceHtmlUrl":147},"references\u002Fworkflows.md",2727,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fimplementing-proofpoint-email-security-gateway\u002Freferences\u002Fworkflows.md",{"path":149,"resourceType":150,"resourceTypeDesc":151,"sizeBytes":152,"sourceHtmlUrl":153},"scripts\u002Fagent.py","SCRIPT","脚本",8392,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fimplementing-proofpoint-email-security-gateway\u002Fscripts\u002Fagent.py",{"path":155,"resourceType":150,"resourceTypeDesc":151,"sizeBytes":156,"sourceHtmlUrl":157},"scripts\u002Fprocess.py",11351,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fimplementing-proofpoint-email-security-gateway\u002Fscripts\u002Fprocess.py",[159,185,209,237,263,290],{"skillNo":160,"name":161,"nameZh":6,"description":162,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":163,"categories":164,"keywords":166,"publishedAt":50},"01M6AGDM3HJXTKXX15ZZ0ZVCJ3","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\u002FCD before deploying artifacts, when consuming third-party attestations, establishing a SLSA Build L3 pipeline, or confirming provenance during incident response or admission control.","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fverifying-build-provenance-with-slsa-sigstore\u002FSKILL.md",[165],{"categoryNo":27,"categoryName":28,"taxonomyType":21,"taxonomyTypeDesc":22},[167,168,169,170,34,49,171,172,173,174,175,176,177,178,179,180,181,182,183,184],"sigstore","provenance","slsa","verifying build provenance with slsa sigstore","incident response","identity","pr","code","artifacts","ci","supply-chain","pipeline","supply-chain-security","t1195","attestation","code-signing","cosign","keyless",{"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":192,"publishedAt":50},"01M6AGDGBPWYVZ2F11GFKJ4HZ9","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\u002Ftpm2_checkquote), and sealing secrets to a PCR policy. Use to confirm a system booted trusted firmware\u002Fkernel for Zero Trust device posture, detect boot-chain tampering via PCR drift, or build a golden-value baseline for fleet attestation.","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fvalidating-tpm-measured-boot-attestation\u002FSKILL.md",[191],{"categoryNo":27,"categoryName":28,"taxonomyType":21,"taxonomyTypeDesc":22},[193,181,194,195,34,196,49,173,197,198,199,200,201,202,203,204,205,206,207,208],"boot","TPM","validating tpm measured boot attestation","policy","verification","ZeRO","firmware","Tools","measured-boot","PCR","integrity","secrets","remote-attestation","tpm2-tools","integrity-verification","trusted-computing",{"skillNo":210,"name":211,"nameZh":6,"description":212,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":213,"categories":214,"keywords":219,"publishedAt":50},"01M6AGDCW0Y4FXZ3362GT1941M","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\u002Fair-gapped backups for silent corruption or tampering.","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fvalidating-backup-integrity-for-recovery\u002FSKILL.md",[215,218],{"categoryNo":216,"categoryName":217,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":27,"categoryName":28,"taxonomyType":21,"taxonomyTypeDesc":22},[203,220,221,222,223,49,224,225,197,226,227,228,229,230,231,232,233,234,235,236],"backup","recovery","validating backup integrity for recovery","testing","infrastructure","validation","compliance","hash-verification","incident-response","ransomware","cryptocurrency","detection","t1078","t1490","immutable","disaster-recovery","restore-testing",{"skillNo":238,"name":239,"nameZh":6,"description":240,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":241,"categories":242,"keywords":244,"publishedAt":50},"01M6AGD9GBG2KZ336AE763J3WH","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\u002Ftriage when full disk imaging is impractical but a defensible, parseable Windows artifact set is needed quickly, including at-scale remote collection.","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Ftriaging-windows-with-kape\u002FSKILL.md",[243],{"categoryNo":27,"categoryName":28,"taxonomyType":21,"taxonomyTypeDesc":22},[245,246,247,49,248,249,250,251,252,253,254,255,256,257,258,259,200,260,261,262],"windows","kape","triaging windows with kape","registry","browser","logs","windows-forensics","dfir","mft","mftecmd","data","prefetch","eric-zimmerman","digital-forensics","SET","collection","pecmd","artifact-collection",{"skillNo":264,"name":265,"nameZh":6,"description":266,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":267,"categories":268,"keywords":270,"publishedAt":50},"01M6AGD5PW5J4EVZM958WD74ZQ","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\u002FTrack*\u002FAttend\u002FAct decisions. Use when prioritizing vulnerability scan results (OpenVAS, Nessus, Qualys) for remediation planning beyond raw CVSS scores.","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Ftriaging-vulnerabilities-with-ssvc-framework\u002FSKILL.md",[269],{"categoryNo":27,"categoryName":28,"taxonomyType":21,"taxonomyTypeDesc":22},[271,272,273,49,274,275,276,277,278,279,280,281,282,283,284,285,286,287,288,289],"vulnerabilities","framework","triaging vulnerabilities with ssvc framework","status","planning","CISA","vulnerability-management","risk-management","nessus","qualys","openvas","cvss","remediation","risk","vulnerability","api","prioritization","ssvc","decision-tree",{"skillNo":291,"name":292,"nameZh":6,"description":293,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":294,"categories":295,"keywords":297,"publishedAt":50},"01M6AGD24TTQQM4CXG69E3B9TJ","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\u002FEDR alert needs human classification, concurrent alerts must be prioritized, or a user report or threat-intel IOC match requires initial incident categorization.","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Ftriaging-security-incident\u002FSKILL.md",[296],{"categoryNo":27,"categoryName":28,"taxonomyType":21,"taxonomyTypeDesc":22},[34,298,49,299,300,301,302,303,304,305,306,232,307,233,308,309,310,311,312,313],"triaging security incident","siem","file","ioc","soc","NIST-800-61","NIST","severity","edr","execution","analysis","classification","severity-classification","incident-triage","SANS-PICERL","SOC-operations"]