Security
DNSFilter integration
Reads which client sites have a DNS filtering policy and which don't. View-only.
Setup steps are for connected customers — sign in to read them.
What we find in DNSFilter
Which client sites have no DNS-filtering policy attached — a fact the vendor reports directly. Blocked-threat volume not yet wired (Traffic Reports endpoint, unconfirmed response schema).
Every finding lands on your Client Upsell board as a named client with a number beside it — not a report you have to read.
What the DNSFilter connection does
Read — powers Client Upsell
Read your clients' stack
Who is actually protected: endpoints still onboarding, seats never deployed, sites with no filtering policy.
Read-only
We only ever read — we never change anything in DNSFilter
You make a view-only key using our setup steps. Our connection has no code that can write to DNSFilter, and your key is encrypted and only used to read.
DNSFilter integration — common questions
- What does the DNSFilter integration read?
- Reads which client sites have a DNS filtering policy and which don't. View-only.
- What does MSProspector find in DNSFilter?
- Which client sites have no DNS-filtering policy attached — a fact the vendor reports directly. Blocked-threat volume not yet wired (Traffic Reports endpoint, unconfirmed response schema).
- Is the DNSFilter connection read-only?
- Yes. We only ever read from DNSFilter — our DNSFilter connection has no code that can change anything, and an automated check on every change to our code blocks any that could. Please create a view-only key using the setup steps, so the key itself can't make changes either.