Find out if Control D blocked it, and allow it.
Neo checks whether Control D blocked a site and why, allowlists it, and reports blocked queries.
What Neo does with Control D.
Domain Test
Neo asks a customer's endpoint whether it blocks a domain, and which rule did.
Allowlisting
Neo adds a bypass or block rule for a domain on the customer's profile.
Blocked-query reports
Neo counts blocked queries by domain, filter and service per customer.
Concrete work Neo handles in Control D.
"A site is blocked" tickets
Neo confirms Control D blocked the site and names the filter.
Allowlist with approval
Neo adds the bypass rule once a technician approves it.
Security in the QBR
Neo reports a customer's blocked threats and top blocked domains.
Set it up with Neo.
Connect Control D
Enter the credentials the Control D card on Neo's Integrations page asks for. The setup guide shows where to find each one.
Start from a use case
Open the Control D card's "What Neo can do" tab and press Set up with Neo on the job you want.
Build it with Neo Support
Neo Support picks the tools and the Control D access the job needs, and builds the agent with you.
Questions about the Control D integration.
What does Neo need to connect to Control D?+
The credentials the Control D card on Neo's Integrations page asks for, from your Control D account. The setup guide shows where to find each one.
How do I set up one of these use cases?+
Connect Control D, open its "What Neo can do" tab in the Neo dashboard and press Set up with Neo on the use case. Neo Support builds the agent with you.