DNS Profile Rule Updates

Control D lets an organization set filtering rules per device profile, such as blocking ad domains on one profile and malware domains on all of them. A Beam agent reads a change request, such as adding a new category of sites to block, applies the approved rule for which profiles it should apply to, and updates the relevant Control D profiles. It confirms the change took effect rather than leaving it unverified. Requests that would loosen a security rule, like removing a malware block, are routed to a human before anything is changed.

Blocked Query Review

Control D logs every DNS query it blocks, which builds up into a record of attempted threats and unwanted content across an organization's devices. A Beam agent reads the block log on a schedule, applies the approved rule for what counts as routine, such as known ad domains, and closes those entries out without further action needed. It notes anything that repeats often or spikes unexpectedly against the recent baseline. Patterns that suggest a new threat source, an unfamiliar domain category, or a device that's compromised are routed to a human to investigate further before any policy changes.

Device Policy Assignment

Devices connected to Control D need to be assigned the right filtering profile, whether that's a standard policy or a stricter one for a specific team or location. A Beam agent reads new devices as they connect, applies the approved rule for which profile fits, such as matching by device group or location, and assigns it in Control D. It notes the assignment so the change is auditable. Devices that don't match any existing group, or that request an exception to standard policy, are routed to a human to assign manually.