返回技能目录
静态审阅软件开发

技能研究档案

performing-dmarc-policy-enforcement-rollout

来源声明

Execute a phased DMARC rollout by inventorying sending sources, configuring SPF/DKIM 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.

保留作者的英文原始描述。它表达设计意图,不代表已验证的实际效果。

Execute a phased DMARC rollout by inventorying sending sources, configuring SPF/DKIM 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.

developmentreferencesscripts

研究摘要

机器生成分析,等待人工复核

以下观察来自确定性源码解析,不代表人工安全审查或受控任务评估。

来源描述:Execute a phased DMARC rollout by inventorying sending sources, configuring SPF/DKIM 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. 此双语摘要由所收集的源文本和文件结构确定性地生成,等待人工编辑复核。

审阅范围

对所收集的 SKILL.md 及辅助文本/代码进行确定性静态分析。机器辅助候选和发现等待人工编辑复核;不评估动态行为或效果。

可观察能力

  • Workflow[来源陈述;暂定,未测试。证据:skills/performing-dmarc-policy-enforcement-rollout/SKILL.md:L82]
  • Step 1: Inventory All Sending Sources (Week 1-2)[来源陈述;暂定,未测试。证据:skills/performing-dmarc-policy-enforcement-rollout/SKILL.md:L84]
  • Step 2: Configure SPF and DKIM (Week 2-4)[来源陈述;暂定,未测试。证据:skills/performing-dmarc-policy-enforcement-rollout/SKILL.md:L90]
  • Step 3: Deploy DMARC in Monitoring Mode (Week 4-6)[来源陈述;暂定,未测试。证据:skills/performing-dmarc-policy-enforcement-rollout/SKILL.md:L97]
  • Step 4: Move to Quarantine with pct Tag (Week 6-12)[来源陈述;暂定,未测试。证据:skills/performing-dmarc-policy-enforcement-rollout/SKILL.md:L104]
  • Step 5: Advance to Reject Policy (Week 12-20)[来源陈述;暂定,未测试。证据:skills/performing-dmarc-policy-enforcement-rollout/SKILL.md:L111]
  • Step 6: Ongoing Monitoring and Maintenance[来源陈述;暂定,未测试。证据:skills/performing-dmarc-policy-enforcement-rollout/SKILL.md:L118]

限制与范围

  • 静态分析无法评估运行时行为、命令是否成功、网络可达性或模型输出质量。
  • 未执行任何命令、脚本、网络请求、模型调用或受控技能测试。
  • 类别、标签、能力、工作流程和双语编辑摘要均为待人工复核的确定性候选,并非已验证结果。
  • 在后续管线实际执行并记录官方模型专用计数之前,无法提供精确 token 数。

适用读者

  • 评估是否检查并安装该来源技能的实践者;此受众由产品语境推断,并非测量得到的使用情况。[证据:skills/performing-dmarc-policy-enforcement-rollout/SKILL.md:L1-L33]

技能包含哪些内容

文件清单来自记录提交中的采集源码。路径与大小属于结构观察,不代表质量评价。

个文件
8
Markdown 文件
5
个脚本
2
个引用
4
大小
41 KB
结构复杂度
低

文件清单

路径类型字节
skills/performing-dmarc-policy-enforcement-rollout/assets/template.md引用1.5 KB
skills/performing-dmarc-policy-enforcement-rollout/LICENSE其他11 KB
skills/performing-dmarc-policy-enforcement-rollout/references/api-reference.md引用907 B
skills/performing-dmarc-policy-enforcement-rollout/references/standards.md引用1.7 KB
skills/performing-dmarc-policy-enforcement-rollout/references/workflows.md引用2.7 KB
skills/performing-dmarc-policy-enforcement-rollout/scripts/agent.py脚本5.4 KB
skills/performing-dmarc-policy-enforcement-rollout/scripts/process.py脚本11.7 KB
skills/performing-dmarc-policy-enforcement-rollout/SKILL.md指令6.1 KB

SKILL.md 前置元数据

{
  "name": "performing-dmarc-policy-enforcement-rollout",
  "description": "Execute a phased DMARC rollout by inventorying sending sources, configuring SPF/DKIM 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.",
  "domain": "cybersecurity",
  "subdomain": "phishing-defense",
  "tags": [
    "dmarc",
    "spf",
    "dkim",
    "email-authentication",
    "anti-spoofing",
    "phishing",
    "dns",
    "email-security"
  ],
  "version": "1.0",
  "author": "mahipal",
  "license": "Apache-2.0",
  "nist_csf": [
    "PR.AT-01",
    "DE.CM-09",
    "RS.CO-02",
    "DE.AE-02"
  ],
  "mitre_attack": [
    "T1566",
    "T1598",
    "T1534",
    "T1036"
  ]
}

对运行顺序的一种解读

此工作流根据源码材料重建表面顺序。除非明确记录受控评估,否则它属于暂定解读,而非真实运行轨迹。

  1. 01
    操作

    Overview

    来源描述的步骤候选,位于“Overview”;未经执行验证。

  2. 02
    判断

    When to Use

    来源描述的决策候选,位于“When to Use”;未经执行验证。

  3. 03
    操作

    Key Concepts

    来源描述的步骤候选,位于“Key Concepts”;未经执行验证。

  4. 04
    操作

    Workflow

    来源描述的步骤候选,位于“Workflow”;未经执行验证。

  5. 05
    操作

    Step 1: Inventory All Sending Sources (Week 1-2)

    来源描述的步骤候选,位于“Step 1: Inventory All Sending Sources (Week 1-2)”;未经执行验证。

  6. 06
    操作

    Audit all systems sending email as your domain (marketing, CRM, ticketing, transactional)

    来源描述的步骤候选,位于“Step 1: Inventory All Sending Sources (Week 1-2)”;未经执行验证。

查看全部工作流候选节点 (41 个候选步骤)
  1. 07
    操作

    Document third-party services: Salesforce, Mailchimp, SendGrid, Zendesk, etc.

    来源描述的步骤候选,位于“Step 1: Inventory All Sending Sources (Week 1-2)”;未经执行验证。

  2. 08
    操作

    Identify internal mail servers, applications, and relay hosts

    来源描述的步骤候选,位于“Step 1: Inventory All Sending Sources (Week 1-2)”;未经执行验证。

  3. 09
    操作

    Check for shadow IT email sending (departments using unauthorized services)

    来源描述的步骤候选,位于“Step 1: Inventory All Sending Sources (Week 1-2)”;未经执行验证。

  4. 10
    操作

    Step 2: Configure SPF and DKIM (Week 2-4)

    来源描述的步骤候选,位于“Step 2: Configure SPF and DKIM (Week 2-4)”;未经执行验证。

  5. 11
    操作

    Consolidate SPF record with all legitimate sending IPs and includes

    来源描述的步骤候选,位于“Step 2: Configure SPF and DKIM (Week 2-4)”;未经执行验证。

  6. 12
    操作

    Ensure SPF record stays under 10 DNS lookup limit

    来源描述的步骤候选,位于“Step 2: Configure SPF and DKIM (Week 2-4)”;未经执行验证。

  7. 13
    输入

    Generate and publish DKIM keys for each sending source

    来源描述的步骤候选,位于“Step 2: Configure SPF and DKIM (Week 2-4)”;未经执行验证。

  8. 14
    操作

    Verify DKIM signing works for all outbound mail paths

    来源描述的步骤候选,位于“Step 2: Configure SPF and DKIM (Week 2-4)”;未经执行验证。

  9. 15
    操作

    Test with MX Toolbox or dmarcian SPF/DKIM validators

    来源描述的步骤候选,位于“Step 2: Configure SPF and DKIM (Week 2-4)”;未经执行验证。

  10. 16
    操作

    Step 3: Deploy DMARC in Monitoring Mode (Week 4-6)

    来源描述的步骤候选,位于“Step 3: Deploy DMARC in Monitoring Mode (Week 4-6)”;未经执行验证。

  11. 17
    操作

    Publish initial DMARC record: `v=DMARC1; p=none; rua=mailto:[email protected]; fo=1`

    来源描述的步骤候选,位于“Step 3: Deploy DMARC in Monitoring Mode (Week 4-6)”;未经执行验证。

  12. 18
    操作

    Wait 1-2 weeks to collect representative aggregate reports

    来源描述的步骤候选,位于“Step 3: Deploy DMARC in Monitoring Mode (Week 4-6)”;未经执行验证。

  13. 19
    操作

    Analyze reports to identify unauthorized senders and alignment failures

    来源描述的步骤候选,位于“Step 3: Deploy DMARC in Monitoring Mode (Week 4-6)”;未经执行验证。

  14. 20
    操作

    Fix SPF/DKIM for all legitimate sources showing failures

    来源描述的步骤候选,位于“Step 3: Deploy DMARC in Monitoring Mode (Week 4-6)”;未经执行验证。

  15. 21
    操作

    Iterate until all legitimate mail passes DMARC

    来源描述的步骤候选,位于“Step 3: Deploy DMARC in Monitoring Mode (Week 4-6)”;未经执行验证。

  16. 22
    操作

    Step 4: Move to Quarantine with pct Tag (Week 6-12)

    来源描述的步骤候选,位于“Step 4: Move to Quarantine with pct Tag (Week 6-12)”;未经执行验证。

  17. 23
    操作

    Update to quarantine at 10%: `v=DMARC1; p=quarantine; pct=10; rua=...`

    来源描述的步骤候选,位于“Step 4: Move to Quarantine with pct Tag (Week 6-12)”;未经执行验证。

  18. 24
    操作

    Monitor for false positives (legitimate mail being quarantined)

    来源描述的步骤候选,位于“Step 4: Move to Quarantine with pct Tag (Week 6-12)”;未经执行验证。

  19. 25
    操作

    Increase pct gradually: 10% -> 25% -> 50% -> 75% -> 100%

    来源描述的步骤候选,位于“Step 4: Move to Quarantine with pct Tag (Week 6-12)”;未经执行验证。

  20. 26
    操作

    Each increase: wait 1-2 weeks and review reports before advancing

    来源描述的步骤候选,位于“Step 4: Move to Quarantine with pct Tag (Week 6-12)”;未经执行验证。

  21. 27
    操作

    Fix any remaining alignment issues discovered at each stage

    来源描述的步骤候选,位于“Step 4: Move to Quarantine with pct Tag (Week 6-12)”;未经执行验证。

  22. 28
    操作

    Step 5: Advance to Reject Policy (Week 12-20)

    来源描述的步骤候选,位于“Step 5: Advance to Reject Policy (Week 12-20)”;未经执行验证。

  23. 29
    操作

    After stable quarantine at 100%, move to reject at 10%: `v=DMARC1; p=reject; pct=10; rua=...`

    来源描述的步骤候选,位于“Step 5: Advance to Reject Policy (Week 12-20)”;未经执行验证。

  24. 30
    操作

    Gradually increase pct: 10% -> 25% -> 50% -> 100%

    来源描述的步骤候选,位于“Step 5: Advance to Reject Policy (Week 12-20)”;未经执行验证。

  25. 31
    操作

    Monitor closely for legitimate mail being rejected

    来源描述的步骤候选,位于“Step 5: Advance to Reject Policy (Week 12-20)”;未经执行验证。

  26. 32
    操作

    Establish emergency rollback procedure (revert to quarantine)

    来源描述的步骤候选,位于“Step 5: Advance to Reject Policy (Week 12-20)”;未经执行验证。

  27. 33
    操作

    Apply subdomain policy: `sp=reject` for subdomains

    来源描述的步骤候选,位于“Step 5: Advance to Reject Policy (Week 12-20)”;未经执行验证。

  28. 34
    操作

    Step 6: Ongoing Monitoring and Maintenance

    来源描述的步骤候选,位于“Step 6: Ongoing Monitoring and Maintenance”;未经执行验证。

  29. 35
    操作

    Continuously monitor DMARC aggregate reports

    来源描述的步骤候选,位于“Step 6: Ongoing Monitoring and Maintenance”;未经执行验证。

  30. 36
    操作

    Add new sending sources before they start sending

    来源描述的步骤候选,位于“Step 6: Ongoing Monitoring and Maintenance”;未经执行验证。

  31. 37
    操作

    Review forensic reports for spoofing attempts

    来源描述的步骤候选,位于“Step 6: Ongoing Monitoring and Maintenance”;未经执行验证。

  32. 38
    操作

    Maintain SPF record as sending infrastructure changes

    来源描述的步骤候选,位于“Step 6: Ongoing Monitoring and Maintenance”;未经执行验证。

  33. 39
    操作

    Rotate DKIM keys annually

    来源描述的步骤候选,位于“Step 6: Ongoing Monitoring and Maintenance”;未经执行验证。

  34. 40
    操作

    Tools & Resources

    来源描述的步骤候选,位于“Tools & Resources”;未经执行验证。

  35. 41
    操作

    Validation

    来源描述的步骤候选,位于“Validation”;未经执行验证。

潜在风险面

静态发现用于提示安装前需要检查的位置,不能证明一项技能安全、恶意或有效。

有需要复核的项目

收集的文本中有 33 项确定性词法发现需要复核。发现可能仅位于文档中,不证明已执行或可被利用;仅含二进制的文件未扫描。

网络访问已观察到
文件写入已观察到
凭据使用未观察到
提示

文本描述或实现了文件修改

31 次命中

此行包含可能的文件写入或重定向操作。应检查目标路径和覆盖行为;静态审查没有写入任何文件。 该规则在收集文本中命中 31 处;此处列出 3 个代表位置。命中文本可能只是文档,分析器没有执行它。

上下文可能消耗在哪里

发现、激活与资源层具有不同含义。只有使用指定官方方法并记录模型的运行时,才显示精确数值。

精确 token 计数不可用

在管线使用明确模型执行官方精确计数之前,包括文件清单在内的所有 token 值均为 null。

未使用要求的官方方法记录 token 测量。本档案不会用字符数、文件大小或估计值替代。

受控评估

没有受控评估

该技能仅具备以上标明的证据。不声称任何任务成功率、token 效率、延迟或质量优势。

尚未测试

在源码可见的情况下使用

安装命令
Inspect the pinned source at https://github.com/mukul975/Anthropic-Cybersecurity-Skills/blob/54a798831d2266a3ca61ce68a7acb80b81160d57/skills/performing-dmarc-policy-enforcement-rollout/SKILL.md and follow the source repository's installation instructions. No installation was performed or verified by this static analyzer. Source license: Apache-2.0.

前置条件

  • 静态分析无法评估运行时行为、命令是否成功、网络可达性或模型输出质量。
  • 未执行任何命令、脚本、网络请求、模型调用或受控技能测试。
  • 类别、标签、能力、工作流程和双语编辑摘要均为待人工复核的确定性候选,并非已验证结果。
  • 在后续管线实际执行并记录官方模型专用计数之前,无法提供精确 token 数。

示例提示词

未提供

附上限制条件的判断

优势

  • 快照包含 8 个收集文件、5 个 Markdown 文件和 2 个脚本文件,可进行源代码级检查。[证据:skills/performing-dmarc-policy-enforcement-rollout/SKILL.md:L1]

注意事项

  • 尚未确立功能、安全或模型质量结果。安装或发布前,人工复核必须检查源代码上下文和所有引用发现。
研究结论

仅为暂定的确定性静态清单;等待人工编辑复核以及独立的受控评估。不构成安装建议、安全保证或有效性声明。

从结构上保持可追溯

档案是对公开工件的限时阅读,而非背书。请通过来源链接检查确切的上游材料。

mukul975Anthropic-Cybersecurity-Skillsskills/performing-dmarc-policy-enforcement-rollout
来源类型
社区
提交
54a798831d2266a3ca61ce68a7acb80b81160d57
采集时间
2026年11月20日
最近核查
2026年11月20日
上游许可证
Apache-2.0
仓库星标
36,446
内容依据

仅对提供的文件进行确定性词法解析、YAML frontmatter 校验、文件清单、来源描述的工作流程提取和启发式暂定分类。由机器生成;无 LLM、执行、动态测试或人工编辑批准。