Back to catalog
Static reviewDevelopment

Skill dossier

performing-dmarc-policy-enforcement-rollout

Source declaration

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.

The author's original description, preserved in English. It describes intent, not verified performance.

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

Research summary

Machine-generated analysis; pending human review

These observations come from deterministic source parsing, not a human security review or controlled task evaluation.

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. This bilingual summary is generated deterministically from collected source text and file structure; it is pending human editorial review.

Review scope

Deterministic static analysis of collected SKILL.md and supporting text/code. Machine-assisted candidates and findings await human editorial review; no dynamic behavior or effect is assessed.

Observable capabilities

  • Workflow [Source statement; provisional, not tested. Evidence: skills/performing-dmarc-policy-enforcement-rollout/SKILL.md:L82]
  • Step 1: Inventory All Sending Sources (Week 1-2) [Source statement; provisional, not tested. Evidence: skills/performing-dmarc-policy-enforcement-rollout/SKILL.md:L84]
  • Step 2: Configure SPF and DKIM (Week 2-4) [Source statement; provisional, not tested. Evidence: skills/performing-dmarc-policy-enforcement-rollout/SKILL.md:L90]
  • Step 3: Deploy DMARC in Monitoring Mode (Week 4-6) [Source statement; provisional, not tested. Evidence: skills/performing-dmarc-policy-enforcement-rollout/SKILL.md:L97]
  • Step 4: Move to Quarantine with pct Tag (Week 6-12) [Source statement; provisional, not tested. Evidence: skills/performing-dmarc-policy-enforcement-rollout/SKILL.md:L104]
  • Step 5: Advance to Reject Policy (Week 12-20) [Source statement; provisional, not tested. Evidence: skills/performing-dmarc-policy-enforcement-rollout/SKILL.md:L111]
  • Step 6: Ongoing Monitoring and Maintenance [Source statement; provisional, not tested. Evidence: skills/performing-dmarc-policy-enforcement-rollout/SKILL.md:L118]

Limitations & scope

  • Static analysis cannot assess runtime behavior, command success, network reachability, or model output quality.
  • No commands, scripts, network requests, model calls, or controlled skill executions were performed.
  • Category, tags, capabilities, workflows, and bilingual editorial summaries are deterministic candidates pending human review, not verified outcomes.
  • Exact token counts are unavailable until a later pipeline performs and records an official model-specific count.

Relevant for

  • Practitioners evaluating whether to inspect and install the source skill; this audience is inferred from the product context, not measured usage. [Evidence: skills/performing-dmarc-policy-enforcement-rollout/SKILL.md:L1-L33]

What ships with the skill

The file inventory comes from the collected source at the recorded commit. Paths and sizes are structural observations, not a measure of quality.

files
8
Markdown files
5
scripts
2
references
4
Size
41 KB
Structural complexity
Low

File inventory

PathTypeBytes
skills/performing-dmarc-policy-enforcement-rollout/assets/template.mdReference1.5 KB
skills/performing-dmarc-policy-enforcement-rollout/LICENSEOther11 KB
skills/performing-dmarc-policy-enforcement-rollout/references/api-reference.mdReference907 B
skills/performing-dmarc-policy-enforcement-rollout/references/standards.mdReference1.7 KB
skills/performing-dmarc-policy-enforcement-rollout/references/workflows.mdReference2.7 KB
skills/performing-dmarc-policy-enforcement-rollout/scripts/agent.pyScript5.4 KB
skills/performing-dmarc-policy-enforcement-rollout/scripts/process.pyScript11.7 KB
skills/performing-dmarc-policy-enforcement-rollout/SKILL.mdInstruction6.1 KB

SKILL.md frontmatter

{
  "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"
  ]
}

A reading of the operating sequence

This workflow reconstructs the apparent sequence from source material. Unless controlled evaluation is explicitly recorded, it is provisional—not an observed trace.

  1. 01
    Action

    Overview

    Source-described action candidate under “Overview”; not verified execution.

  2. 02
    Decision

    When to Use

    Source-described decision candidate under “When to Use”; not verified execution.

  3. 03
    Action

    Key Concepts

    Source-described action candidate under “Key Concepts”; not verified execution.

  4. 04
    Action

    Workflow

    Source-described action candidate under “Workflow”; not verified execution.

  5. 05
    Action

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

    Source-described action candidate under “Step 1: Inventory All Sending Sources (Week 1-2)”; not verified execution.

  6. 06
    Action

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

    Source-described action candidate under “Step 1: Inventory All Sending Sources (Week 1-2)”; not verified execution.

Inspect all extracted workflow candidates (41 candidate steps)
  1. 07
    Action

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

    Source-described action candidate under “Step 1: Inventory All Sending Sources (Week 1-2)”; not verified execution.

  2. 08
    Action

    Identify internal mail servers, applications, and relay hosts

    Source-described action candidate under “Step 1: Inventory All Sending Sources (Week 1-2)”; not verified execution.

  3. 09
    Action

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

    Source-described action candidate under “Step 1: Inventory All Sending Sources (Week 1-2)”; not verified execution.

  4. 10
    Action

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

    Source-described action candidate under “Step 2: Configure SPF and DKIM (Week 2-4)”; not verified execution.

  5. 11
    Action

    Consolidate SPF record with all legitimate sending IPs and includes

    Source-described action candidate under “Step 2: Configure SPF and DKIM (Week 2-4)”; not verified execution.

  6. 12
    Action

    Ensure SPF record stays under 10 DNS lookup limit

    Source-described action candidate under “Step 2: Configure SPF and DKIM (Week 2-4)”; not verified execution.

  7. 13
    Input

    Generate and publish DKIM keys for each sending source

    Source-described input candidate under “Step 2: Configure SPF and DKIM (Week 2-4)”; not verified execution.

  8. 14
    Action

    Verify DKIM signing works for all outbound mail paths

    Source-described action candidate under “Step 2: Configure SPF and DKIM (Week 2-4)”; not verified execution.

  9. 15
    Action

    Test with MX Toolbox or dmarcian SPF/DKIM validators

    Source-described action candidate under “Step 2: Configure SPF and DKIM (Week 2-4)”; not verified execution.

  10. 16
    Action

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

    Source-described action candidate under “Step 3: Deploy DMARC in Monitoring Mode (Week 4-6)”; not verified execution.

  11. 17
    Action

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

    Source-described action candidate under “Step 3: Deploy DMARC in Monitoring Mode (Week 4-6)”; not verified execution.

  12. 18
    Action

    Wait 1-2 weeks to collect representative aggregate reports

    Source-described action candidate under “Step 3: Deploy DMARC in Monitoring Mode (Week 4-6)”; not verified execution.

  13. 19
    Action

    Analyze reports to identify unauthorized senders and alignment failures

    Source-described action candidate under “Step 3: Deploy DMARC in Monitoring Mode (Week 4-6)”; not verified execution.

  14. 20
    Action

    Fix SPF/DKIM for all legitimate sources showing failures

    Source-described action candidate under “Step 3: Deploy DMARC in Monitoring Mode (Week 4-6)”; not verified execution.

  15. 21
    Action

    Iterate until all legitimate mail passes DMARC

    Source-described action candidate under “Step 3: Deploy DMARC in Monitoring Mode (Week 4-6)”; not verified execution.

  16. 22
    Action

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

    Source-described action candidate under “Step 4: Move to Quarantine with pct Tag (Week 6-12)”; not verified execution.

  17. 23
    Action

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

    Source-described action candidate under “Step 4: Move to Quarantine with pct Tag (Week 6-12)”; not verified execution.

  18. 24
    Action

    Monitor for false positives (legitimate mail being quarantined)

    Source-described action candidate under “Step 4: Move to Quarantine with pct Tag (Week 6-12)”; not verified execution.

  19. 25
    Action

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

    Source-described action candidate under “Step 4: Move to Quarantine with pct Tag (Week 6-12)”; not verified execution.

  20. 26
    Action

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

    Source-described action candidate under “Step 4: Move to Quarantine with pct Tag (Week 6-12)”; not verified execution.

  21. 27
    Action

    Fix any remaining alignment issues discovered at each stage

    Source-described action candidate under “Step 4: Move to Quarantine with pct Tag (Week 6-12)”; not verified execution.

  22. 28
    Action

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

    Source-described action candidate under “Step 5: Advance to Reject Policy (Week 12-20)”; not verified execution.

  23. 29
    Action

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

    Source-described action candidate under “Step 5: Advance to Reject Policy (Week 12-20)”; not verified execution.

  24. 30
    Action

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

    Source-described action candidate under “Step 5: Advance to Reject Policy (Week 12-20)”; not verified execution.

  25. 31
    Action

    Monitor closely for legitimate mail being rejected

    Source-described action candidate under “Step 5: Advance to Reject Policy (Week 12-20)”; not verified execution.

  26. 32
    Action

    Establish emergency rollback procedure (revert to quarantine)

    Source-described action candidate under “Step 5: Advance to Reject Policy (Week 12-20)”; not verified execution.

  27. 33
    Action

    Apply subdomain policy: `sp=reject` for subdomains

    Source-described action candidate under “Step 5: Advance to Reject Policy (Week 12-20)”; not verified execution.

  28. 34
    Action

    Step 6: Ongoing Monitoring and Maintenance

    Source-described action candidate under “Step 6: Ongoing Monitoring and Maintenance”; not verified execution.

  29. 35
    Action

    Continuously monitor DMARC aggregate reports

    Source-described action candidate under “Step 6: Ongoing Monitoring and Maintenance”; not verified execution.

  30. 36
    Action

    Add new sending sources before they start sending

    Source-described action candidate under “Step 6: Ongoing Monitoring and Maintenance”; not verified execution.

  31. 37
    Action

    Review forensic reports for spoofing attempts

    Source-described action candidate under “Step 6: Ongoing Monitoring and Maintenance”; not verified execution.

  32. 38
    Action

    Maintain SPF record as sending infrastructure changes

    Source-described action candidate under “Step 6: Ongoing Monitoring and Maintenance”; not verified execution.

  33. 39
    Action

    Rotate DKIM keys annually

    Source-described action candidate under “Step 6: Ongoing Monitoring and Maintenance”; not verified execution.

  34. 40
    Action

    Tools & Resources

    Source-described action candidate under “Tools & Resources”; not verified execution.

  35. 41
    Action

    Validation

    Source-described action candidate under “Validation”; not verified execution.

Potential risk surfaces

Static findings identify points to inspect before installation. They do not establish that a skill is safe, malicious, or effective.

Items warrant review

33 deterministic lexical finding(s) require review across the collected text. Findings can occur in documentation and do not prove execution or exploitability; binary-only files were not scanned.

Network accessObserved
File writesObserved
Credential useNot observed
Note

File modification is described or implemented

31 occurrences

This line contains a possible file-write or redirection operation. Check destination paths and overwrite behavior; the static review did not write any file. This rule matched 31 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Medium

Network access is mentioned

2 occurrences

A URL or network client appears in this source line. Review destinations, data sent, and trust boundaries; static text cannot establish actual network activity. This rule matched 2 location(s) in the collected text; 2 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Where context can be spent

Discovery, activation, and resource layers have different meanings. Exact values appear only when the official token-counting method was run with a named model.

Exact token counts unavailable

All token values, including per-file inventory, are null until the pipeline performs an official exact count with an explicit model.

No token measurement was recorded with the required official method. This dossier does not substitute character counts, file sizes, or estimates.

Controlled evaluation

No controlled evaluation

This skill has only the evidence identified above. No task success, token efficiency, latency, or quality advantage is claimed.

Not tested

Use with the source in view

Install command
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.

Prerequisites

  • Static analysis cannot assess runtime behavior, command success, network reachability, or model output quality.
  • No commands, scripts, network requests, model calls, or controlled skill executions were performed.
  • Category, tags, capabilities, workflows, and bilingual editorial summaries are deterministic candidates pending human review, not verified outcomes.
  • Exact token counts are unavailable until a later pipeline performs and records an official model-specific count.

Example prompts

Not provided

A decision, with its limits attached

Strengths

  • The snapshot contains 8 collected file(s), 5 Markdown file(s), and 2 script file(s), enabling source-level inspection. [Evidence: skills/performing-dmarc-policy-enforcement-rollout/SKILL.md:L1]

Considerations

  • No functional, security, or model-quality result has been established. Human review must inspect source context and all cited findings before installation or publication.
Research conclusion

Provisional deterministic static inventory only; pending human editorial review and, separately, controlled evaluation. No install recommendation, security assurance, or effectiveness claim is made.

Traceable by construction

The dossier is a time-bound reading of a public artifact, not an endorsement. Use the source link to inspect the exact upstream material.

mukul975Anthropic-Cybersecurity-Skillsskills/performing-dmarc-policy-enforcement-rollout
Source type
Community
Commit
54a798831d2266a3ca61ce68a7acb80b81160d57
Collected
20 Nov 2026
Last checked
20 Nov 2026
Upstream license
Apache-2.0
Repository stars
36,446
Content basis

Deterministic lexical parsing, YAML frontmatter validation, file inventory, source-described workflow extraction, and heuristic provisional classification of the supplied files only. Generated by machine; no LLM, execution, dynamic testing, or human editorial approval.