CertaDNS
Skip to lesson

Sustaining It · lesson 1 of 3

What decays, and how fast

After this lesson you can

Give each control a review cadence derived from how quickly it goes wrong.

Assumes you have read The ones worth skipping.

Every control has a decay rate, and the review cadence should be derived from it rather than from a calendar convention. Some things go wrong in hours; some take years and then matter enormously.

Decay rates

WhatGoes wrong inSo check
DNSSEC signaturesDays — a stopped signer is a cliff at the expiryHourly, from a validating resolver
MTA-STS policy host certificateWhenever the renewal process forgets a host serving one fileDaily, on days remaining
TLSA digests against the served keyEvery renewal that rotates the key — as often as every 60 daysHourly, by comparison
SPF lookup countWhenever a vendor grows their include, with no change on your sideWeekly
DMARC pass rateWhenever a platform changes its signing or a gateway starts rewritingPer report, per sending source
Dangling recordsWhenever a service is decommissioned by somebody who does not own DNSQuarterly, and at every offboarding
Unaccounted-for DKIM selectorsWhenever a vendor relationship endsQuarterly
Registrar lock state and contactsWhen somebody clears a lock, or a contact leavesMonthly
Domain expiryOnce, catastrophicallyMonthly, plus auto-renew
The estate list itselfContinuously, as domains are registered by people outside the teamQuarterly, against registrar accounts

The pattern

Fast decay   = something else changed
   vendor includes, vendor keys, certificate renewals,
   signer processes. All outside your control, all
   silent. These need automated checks.

Slow decay   = somebody in your organisation did
               something reasonable
   cancelled a subscription, offboarded a vendor,
   registered a domain, left. These need a checklist
   at the moment of the action, and a quarterly sweep
   because the checklist will be missed.

Neither category is caught by an annual review, which is the cadence most organisations actually run. The fast ones need monitoring; the slow ones need a sweep attached to a process rather than to a date.

Attach the slow checks to events, not to the calendar

“Remove the DKIM selector, the SPF include and any CNAME” belongs on the vendor offboarding checklist, where somebody is already doing something. A quarterly sweep is the backstop for when that checklist is missed — it is not the primary control, and treating it as one means finding things a quarter late.

Last reviewed