Support Library
DNSSEC Failures (Broken vs Missing)
Missing DNSSEC reduces authenticity assurance; broken DNSSEC causes immediate validation outages.
Threat Model
Missing DNSSEC reduces authenticity assurance; broken DNSSEC causes immediate validation outages.
Attack Path
Broken states come from stale DS, bad rollovers, expired signatures, or DNSKEY mismatches.
Detection Techniques
Compare validating/non-validating resolver behavior and verify DS-DNSKEY-RRSIG alignment.
Mitigation Strategies
Treat missing as informational improvement; treat broken validation as urgent outage remediation.
Scoring Impact (tie to Panopticon scoring model)
Missing DNSSEC is informational; broken DNSSEC is critical.
How DNS Panopticon Detects This
- Relevant checks: Delegation integrity, resolver consistency, DNSSEC health, and suspicious record-pattern checks.
- Severity mapping: Informational, medium/high, or critical based on exploitability and user impact.
- Score impact: Reliability and security scoring dimensions are reduced according to blast radius.
- Related findings users will see: NS drift, validation failure, orphaned CNAMEs, wildcard exposure, and policy misconfiguration alerts.
Operator Checklist
- Verify behavior from at least two public resolvers and one resolver inside your own network before making changes.
- Make one change at a time, capture before/after query output, and wait for TTL windows to clear so you can confirm impact.
- Document the root cause and the final fix in your runbook to shorten future incidents.