CertaDNS
Skip to lesson

Automation and Judgement · lesson 1 of 2

What automates well

After this lesson you can

Identify the stages of the programme that should be fully automated.

Assumes you have read When nobody answers.

Most of a brand protection programme is mechanical, repeated many times a day, and should never involve a person. The parts that should are few and specific.

The split

StageAutomate?Why
Generating the permutation spaceFullyDeterministic, and regenerating it when the brand changes is free.
Consuming registration and certificate feedsFullyContinuous, high volume, no judgement involved.
Matching against the watchlistFullyA string comparison, once normalisation is right.
Resolving DNS and checking for MXFullyCheap, and it is the escalation trigger.
Fetching and hashing site assetsFullyComparison against known hashes is exact.
Capturing the evidence packageFullyIt must happen at detection, which is faster than any human.
Ranking the queueFullyFrom the signals above, with published weights.
Deciding what a finding isNoThe four-way classification needs context a checker does not have.
Deciding to reportNoThe cost of being wrong falls on a third party.
Writing the reportPartlyTemplate it, and have a person confirm the content and send it.
EscalatingNoJudgement about which route, and when to stop.

The pattern

Everything up to and including “here is a ranked queue with complete evidence attached” should be automatic. Everything from “this is what it is” onward should not.

Automated:   detect -> enrich -> capture -> rank
Human:       classify -> decide -> report -> escalate

The handoff is a queue item with the gathering done,
so the person spends their time on judgement rather
than on collecting.

Automating capture is the highest-value piece

  • It must happen within minutes of detection, and no rota achieves that.
  • It is entirely mechanical, so there is nothing lost by automating it.
  • It preserves the option to report later, for findings you initially close.
  • It is the difference between a reportable finding and a recollection.

Automate enrichment, never conclusions

A pipeline that attaches the DNS, RDAP, certificate and asset-hash comparison to every finding makes a person five times faster. A pipeline that attaches a verdict makes them stop reading, and the verdict is the part it is worst at.

Last reviewed