[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EPVNHKAPHAFNDEBE6B0ZWG":3,"skill-same:01M7EPVNHKAPHAFNDEBE6B0ZWG":83},{"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":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":47,"commitSha":48,"skillDirectory":49,"forksCount":50,"repositoryHtmlUrl":51,"repositoryHomepageUrl":6,"ownerHtmlUrl":52,"ownerBlogUrl":6,"ownerDescription":53,"updatedAt":54,"install":55,"resources":68},"01M7EPVNHKAPHAFNDEBE6B0ZWG","performing-dmarc-policy-enforcement-rollout",null,"Execute a phased DMARC rollout by inventorying sending sources, configuring SPF\u002FDKIM alignment, and progressing DNS policy from p=none monitoring through p=quarantine to p=reject enforcement, ensuring all legitimate email sources authenticate before unauthorized senders are blocked. Use when deploying or advancing an organization's DMARC anti-spoofing posture, or when meeting bulk-sender authentication requirements from Google and Yahoo.","lza6\u002FArmor-piercing-system-prompts","lza6","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F128880206?v=4","01M7EB3K7WPX5T28EJ2NVHE6EG","Chinese-tingfeng","01M7EB3K97E1KQ16QWKJMFNGX8",11,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F04-安全渗透\u002Fperforming-dmarc-policy-enforcement-rollout\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: performing-dmarc-policy-enforcement-rollout\ndescription: Execute a phased DMARC rollout by inventorying sending sources, configuring\n  SPF\u002FDKIM alignment, and progressing DNS policy from p=none monitoring through p=quarantine\n  to p=reject enforcement, ensuring all legitimate email sources authenticate before\n  unauthorized senders are blocked. Use when deploying or advancing an organization's\n  DMARC anti-spoofing posture, or when meeting bulk-sender authentication requirements\n  from Google and Yahoo.\ndomain: cybersecurity\nsubdomain: phishing-defense\ntags:\n- dmarc\n- spf\n- dkim\n- email-authentication\n- anti-spoofing\n- phishing\n- dns\n- email-security\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---\n# Performing DMARC Policy Enforcement Rollout\n\n## Overview\nDomain-based Message Authentication, Reporting and Conformance (DMARC) is the cornerstone of email anti-spoofing protection. A DMARC rollout progresses through three phases: monitoring (p=none), quarantine (p=quarantine), and full enforcement (p=reject). When configured at p=reject, any email that fails both SPF and DKIM checks is outright rejected. Google and Yahoo now require DMARC for bulk senders (5,000+ emails), driving a 65% reduction in unauthenticated messages. The rollout typically takes 3-6 months for safe deployment.\n\n\n## When to Use\n\n- When conducting security assessments that involve performing dmarc policy enforcement rollout\n- When following incident response procedures for related security events\n- When performing scheduled security testing or auditing activities\n- When validating security controls through hands-on testing\n\n## Prerequisites\n- Administrative access to DNS management for the domain\n- Understanding of SPF, DKIM, and DMARC protocols (RFC 7208, 6376, 7489)\n- Complete inventory of all legitimate email sending sources\n- DMARC reporting analysis tool (EasyDMARC, DMARCLY, Valimail, or dmarcian)\n- Email gateway with DMARC enforcement capability\n\n## Key Concepts\n\n### DMARC Policy Levels\n| Policy | Behavior | Use Case |\n|---|---|---|\n| p=none | Monitor only, no action on failures | Discovery phase |\n| p=quarantine | Send failing messages to spam\u002Fjunk | Transition phase |\n| p=reject | Block failing messages entirely | Full enforcement |\n\n### DMARC Record Anatomy\n```\nv=DMARC1; p=quarantine; pct=25; rua=mailto:dmarc-agg@company.com; ruf=mailto:dmarc-forensic@company.com; adkim=r; aspf=r; fo=1\n```\n- **p**: Policy for organizational domain\n- **sp**: Policy for subdomains\n- **pct**: Percentage of messages subject to policy (for gradual rollout)\n- **rua**: Aggregate report destination (daily XML reports)\n- **ruf**: Forensic report destination (per-failure reports)\n- **adkim**: DKIM alignment mode (r=relaxed, s=strict)\n- **aspf**: SPF alignment mode (r=relaxed, s=strict)\n- **fo**: Failure reporting options (0=both fail, 1=either fails)\n\n### SPF and DKIM Alignment\n- **SPF Alignment**: The domain in the Return-Path (envelope sender) must match the From header domain\n- **DKIM Alignment**: The d= domain in the DKIM signature must match the From header domain\n- **Relaxed**: Organizational domain match (sub.example.com matches example.com)\n- **Strict**: Exact domain match required\n\n## Workflow\n\n### Step 1: Inventory All Sending Sources (Week 1-2)\n- Audit all systems sending email as your domain (marketing, CRM, ticketing, transactional)\n- Document third-party services: Salesforce, Mailchimp, SendGrid, Zendesk, etc.\n- Identify internal mail servers, applications, and relay hosts\n- Check for shadow IT email sending (departments using unauthorized services)\n\n### Step 2: Configure SPF and DKIM (Week 2-4)\n- Consolidate SPF record with all legitimate sending IPs and includes\n- Ensure SPF record stays under 10 DNS lookup limit\n- Generate and publish DKIM keys for each sending source\n- Verify DKIM signing works for all outbound mail paths\n- Test with MX Toolbox or dmarcian SPF\u002FDKIM validators\n\n### Step 3: Deploy DMARC in Monitoring Mode (Week 4-6)\n- Publish initial DMARC record: `v=DMARC1; p=none; rua=mailto:dmarc@company.com; fo=1`\n- Wait 1-2 weeks to collect representative aggregate reports\n- Analyze reports to identify unauthorized senders and alignment failures\n- Fix SPF\u002FDKIM for all legitimate sources showing failures\n- Iterate until all legitimate mail passes DMARC\n\n### Step 4: Move to Quarantine with pct Tag (Week 6-12)\n- Update to quarantine at 10%: `v=DMARC1; p=quarantine; pct=10; rua=...`\n- Monitor for false positives (legitimate mail being quarantined)\n- Increase pct gradually: 10% -> 25% -> 50% -> 75% -> 100%\n- Each increase: wait 1-2 weeks and review reports before advancing\n- Fix any remaining alignment issues discovered at each stage\n\n### Step 5: Advance to Reject Policy (Week 12-20)\n- After stable quarantine at 100%, move to reject at 10%: `v=DMARC1; p=reject; pct=10; rua=...`\n- Gradually increase pct: 10% -> 25% -> 50% -> 100%\n- Monitor closely for legitimate mail being rejected\n- Establish emergency rollback procedure (revert to quarantine)\n- Apply subdomain policy: `sp=reject` for subdomains\n\n### Step 6: Ongoing Monitoring and Maintenance\n- Continuously monitor DMARC aggregate reports\n- Add new sending sources before they start sending\n- Review forensic reports for spoofing attempts\n- Maintain SPF record as sending infrastructure changes\n- Rotate DKIM keys annually\n\n## Tools & Resources\n- **EasyDMARC**: DMARC monitoring dashboard with aggregate\u002Fforensic report analysis\n- **DMARCLY**: SPF, DKIM, DMARC monitoring with auto-DNS updates\n- **dmarcian**: DMARC deployment and management platform\n- **Valimail**: Automated DMARC enforcement with hosted authentication\n- **MX Toolbox**: DNS record lookup and DMARC validator\n- **Google Admin Toolbox**: DMARC check and diagnostic tools\n\n## Validation\n- DMARC record published and resolving correctly at _dmarc.domain.com\n- All legitimate sending sources pass SPF and\u002For DKIM alignment\n- Aggregate reports show >99% legitimate mail passing DMARC\n- Spoofed messages from unauthorized senders are rejected\n- No legitimate mail blocked after full p=reject enforcement\n- Subdomain policy (sp=) also set to reject\n","# Performing DMARC Policy Enforcement Rollout\n\n## Overview\nDomain-based Message Authentication, Reporting and Conformance (DMARC) is the cornerstone of email anti-spoofing protection. A DMARC rollout progresses through three phases: monitoring (p=none), quarantine (p=quarantine), and full enforcement (p=reject). When configured at p=reject, any email that fails both SPF and DKIM checks is outright rejected. Google and Yahoo now require DMARC for bulk senders (5,000+ emails), driving a 65% reduction in unauthenticated messages. The rollout typically takes 3-6 months for safe deployment.\n\n\n## When to Use\n\n- When conducting security assessments that involve performing dmarc policy enforcement rollout\n- When following incident response procedures for related security events\n- When performing scheduled security testing or auditing activities\n- When validating security controls through hands-on testing\n\n## Prerequisites\n- Administrative access to DNS management for the domain\n- Understanding of SPF, DKIM, and DMARC protocols (RFC 7208, 6376, 7489)\n- Complete inventory of all legitimate email sending sources\n- DMARC reporting analysis tool (EasyDMARC, DMARCLY, Valimail, or dmarcian)\n- Email gateway with DMARC enforcement capability\n\n## Key Concepts\n\n### DMARC Policy Levels\n| Policy | Behavior | Use Case |\n|---|---|---|\n| p=none | Monitor only, no action on failures | Discovery phase |\n| p=quarantine | Send failing messages to spam\u002Fjunk | Transition phase |\n| p=reject | Block failing messages entirely | Full enforcement |\n\n### DMARC Record Anatomy\n```\nv=DMARC1; p=quarantine; pct=25; rua=mailto:dmarc-agg@company.com; ruf=mailto:dmarc-forensic@company.com; adkim=r; aspf=r; fo=1\n```\n- **p**: Policy for organizational domain\n- **sp**: Policy for subdomains\n- **pct**: Percentage of messages subject to policy (for gradual rollout)\n- **rua**: Aggregate report destination (daily XML reports)\n- **ruf**: Forensic report destination (per-failure reports)\n- **adkim**: DKIM alignment mode (r=relaxed, s=strict)\n- **aspf**: SPF alignment mode (r=relaxed, s=strict)\n- **fo**: Failure reporting options (0=both fail, 1=either fails)\n\n### SPF and DKIM Alignment\n- **SPF Alignment**: The domain in the Return-Path (envelope sender) must match the From header domain\n- **DKIM Alignment**: The d= domain in the DKIM signature must match the From header domain\n- **Relaxed**: Organizational domain match (sub.example.com matches example.com)\n- **Strict**: Exact domain match required\n\n## Workflow\n\n### Step 1: Inventory All Sending Sources (Week 1-2)\n- Audit all systems sending email as your domain (marketing, CRM, ticketing, transactional)\n- Document third-party services: Salesforce, Mailchimp, SendGrid, Zendesk, etc.\n- Identify internal mail servers, applications, and relay hosts\n- Check for shadow IT email sending (departments using unauthorized services)\n\n### Step 2: Configure SPF and DKIM (Week 2-4)\n- Consolidate SPF record with all legitimate sending IPs and includes\n- Ensure SPF record stays under 10 DNS lookup limit\n- Generate and publish DKIM keys for each sending source\n- Verify DKIM signing works for all outbound mail paths\n- Test with MX Toolbox or dmarcian SPF\u002FDKIM validators\n\n### Step 3: Deploy DMARC in Monitoring Mode (Week 4-6)\n- Publish initial DMARC record: `v=DMARC1; p=none; rua=mailto:dmarc@company.com; fo=1`\n- Wait 1-2 weeks to collect representative aggregate reports\n- Analyze reports to identify unauthorized senders and alignment failures\n- Fix SPF\u002FDKIM for all legitimate sources showing failures\n- Iterate until all legitimate mail passes DMARC\n\n### Step 4: Move to Quarantine with pct Tag (Week 6-12)\n- Update to quarantine at 10%: `v=DMARC1; p=quarantine; pct=10; rua=...`\n- Monitor for false positives (legitimate mail being quarantined)\n- Increase pct gradually: 10% -> 25% -> 50% -> 75% -> 100%\n- Each increase: wait 1-2 weeks and review reports before advancing\n- Fix any remaining alignment issues discovered at each stage\n\n### Step 5: Advance to Reject Policy (Week 12-20)\n- After stable quarantine at 100%, move to reject at 10%: `v=DMARC1; p=reject; pct=10; rua=...`\n- Gradually increase pct: 10% -> 25% -> 50% -> 100%\n- Monitor closely for legitimate mail being rejected\n- Establish emergency rollback procedure (revert to quarantine)\n- Apply subdomain policy: `sp=reject` for subdomains\n\n### Step 6: Ongoing Monitoring and Maintenance\n- Continuously monitor DMARC aggregate reports\n- Add new sending sources before they start sending\n- Review forensic reports for spoofing attempts\n- Maintain SPF record as sending infrastructure changes\n- Rotate DKIM keys annually\n\n## Tools & Resources\n- **EasyDMARC**: DMARC monitoring dashboard with aggregate\u002Fforensic report analysis\n- **DMARCLY**: SPF, DKIM, DMARC monitoring with auto-DNS updates\n- **dmarcian**: DMARC deployment and management platform\n- **Valimail**: Automated DMARC enforcement with hosted authentication\n- **MX Toolbox**: DNS record lookup and DMARC validator\n- **Google Admin Toolbox**: DMARC check and diagnostic tools\n\n## Validation\n- DMARC record published and resolving correctly at _dmarc.domain.com\n- All legitimate sending sources pass SPF and\u002For DKIM alignment\n- Aggregate reports show >99% legitimate mail passing DMARC\n- Spoofed messages from unauthorized senders are rejected\n- No legitimate mail blocked after full p=reject enforcement\n- Subdomain policy (sp=) also set to reject\n",{"name":5,"tags":24,"author":33,"domain":34,"license":15,"version":35,"nist_csf":36,"subdomain":41,"description":7,"mitre_attack":42},[25,26,27,28,29,30,31,32],"dmarc","spf","dkim","email-authentication","anti-spoofing","phishing","dns","email-security","mahipal","cybersecurity","1.0",[37,38,39,40],"PR.AT-01","DE.CM-09","RS.CO-02","DE.AE-02","phishing-defense",[43,44,45,46],"T1566","T1598","T1534","T1036","main","d69096e239f2a89aabc2cd078c47664a9d3b1e11","04-安全渗透\u002Fperforming-dmarc-policy-enforcement-rollout",3,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts","https:\u002F\u002Fgithub.com\u002Flza6","个人vx：Tf00798\r\n个人✈：@TFGY999","2026-10-08 14:29:22",{"source":8,"skillName":5,"commands":56,"prompt":66,"zipAvailable":67},[57,60,63],{"tool":58,"command":59},"npx","npx skills add lza6\u002FArmor-piercing-system-prompts --skill performing-dmarc-policy-enforcement-rollout",{"tool":61,"command":62},"bunx","bunx skills add lza6\u002FArmor-piercing-system-prompts --skill performing-dmarc-policy-enforcement-rollout",{"tool":64,"command":65},"pnpm","pnpm dlx skills add lza6\u002FArmor-piercing-system-prompts --skill performing-dmarc-policy-enforcement-rollout","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F04-安全渗透\u002Fperforming-dmarc-policy-enforcement-rollout\u002FSKILL.md",true,[69,75,79],{"path":70,"resourceType":71,"resourceTypeDesc":72,"sizeBytes":73,"sourceHtmlUrl":74},"references\u002Fapi-reference.md","REFERENCE","参考文档",907,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F04-安全渗透\u002Fperforming-dmarc-policy-enforcement-rollout\u002Freferences\u002Fapi-reference.md",{"path":76,"resourceType":71,"resourceTypeDesc":72,"sizeBytes":77,"sourceHtmlUrl":78},"references\u002Fstandards.md",1708,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F04-安全渗透\u002Fperforming-dmarc-policy-enforcement-rollout\u002Freferences\u002Fstandards.md",{"path":80,"resourceType":71,"resourceTypeDesc":72,"sizeBytes":81,"sourceHtmlUrl":82},"references\u002Fworkflows.md",2772,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F04-安全渗透\u002Fperforming-dmarc-policy-enforcement-rollout\u002Freferences\u002Fworkflows.md",[84,93,98,105,112,119],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":88,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":92},"01M7FFG485KY83TD6HSC4YPCMC","obsidian-clipper-template-creator","Guide for creating templates for the Obsidian Web Clipper. Use when you want to create a new clipping template, understand available variables, or format clipped content.","MIT","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator\u002FSKILL.md",[],[],"2026-11-16 10:05:34",{"skillNo":94,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":88,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":92},"01M7FFG0T6AZ0STEJPSB3CX84K","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator-antigravity-awesome-skills-main\u002FSKILL.md",[],[],{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":88,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":92},"01M7FFFY0QEM14SKWPDYGMXM2P","python-api","Programmatic Object-Detection-Metrics API guidance for BoundingBox, BoundingBoxes, Evaluator, enums, coordinate conversion, AP\u002FmAP semantics, and source-style import diagnostics.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Fpython-api\u002FSKILL.md",[],[],{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":88,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":111,"publishedAt":92},"01M7FFFVZQZ2GJ0C0TGP7JHD20","file-evaluation","Folder-based PASCAL VOC AP\u002FmAP evaluation from ground-truth and detection text files.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Ffile-evaluation\u002FSKILL.md",[],[],{"skillNo":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":88,"licenseFileUrl":6,"sourceHtmlUrl":116,"categories":117,"keywords":118,"publishedAt":92},"01M7FFFSFNYSE77SJ6PE1CK2DA","object-detection-metrics","Guides legacy Object-Detection-Metrics PASCAL VOC AP\u002FmAP evaluation from detection text folders and direct Python API classes.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002FSKILL.md",[],[],{"skillNo":120,"name":121,"nameZh":6,"description":122,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":88,"licenseFileUrl":6,"sourceHtmlUrl":123,"categories":124,"keywords":125,"publishedAt":92},"01M7FFFP0GCK1RVXBCPQ8APBMT","nx-workspace-patterns","Configure and optimize Nx monorepo workspaces. Use when setting up Nx, configuring project boundaries, optimizing build caching, or implementing affected commands.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fnx-workspace-patterns\u002FSKILL.md",[],[]]