Policy Across Customers
What each estate's resolver blocks, allows and answers by default, and the one decision you can take for a whole book at once.
Policy Across Customers Documentation
Policy in the portal is held on the customer it belongs to, and applies across that customer's account rather than to one endpoint. There are four kinds, and one decision you can take for the whole book at once.
The resolver policy
Each customer's resolver has a default answer and two lists: the names it blocks and the names it allows. An entry covers the name and everything beneath it, and an explicit allow wins over a block. A mode setting says how far the resolver leans on the graph before it forwards a lookup.
The portal edits the same document the customer's own account edits, so there is one policy per estate and no separate partner copy to drift. Resolver policy holds the field list.
Zone policy
A customer can have a dedicated resolver address of their own, and can hand a domain over for Whisper to serve authoritatively.
Zone rules sit on top of that: they change the answer a name gets in that zone when the graph scores it malicious. A zone rule takes effect once it is promoted, so you can write one and read it back before it changes an answer anyone depends on. Authoritative DNS covers the serving side.
Mesh
Mesh is which of a customer's nodes may reach each other.
Holding a node leaves its address, its DNS and its egress in place and takes away east-west reach, which contains lateral movement without taking the machine off the internet or off your screens. The access document is the same document the portal edits, and it narrows rather than widens.
Footprint
Footprint is what the sensor is allowed to cost the person sitting at the machine: how often it works, how far it spreads that work, and the ceiling it holds under.
It belongs with policy because the right answer differs by customer, and because the person at the keyboard is the one whose experience tells you whether you chose it well. What the sensor costs describes the governor itself.
One decision for the whole book
Pushing a verdict from shared infrastructure is the exception: one name blocked as a resolver rule for every customer you apply it to.
Everything else above is edited on the customer it belongs to. That is deliberate. A change in one estate is never a change in another, so a setting tuned for a customer with unusual traffic cannot quietly become the setting for the rest of the book.