Protect
Apply agreed malicious-domain, phishing, command-and-control and category policy at the DNS layer.
Guardian DNS Protection applies managed filtering policy and presents blocked, allowed and monitored activity through participant, business and provider-safe views.
Guardian DNS Protection combines managed DNS security policy with customer-safe activity, user and device context, operational review and accountable follow-up.
The underlying filtering technology remains a connector. Customers work through Guardian rather than being required to interpret a raw vendor console.
Apply agreed malicious-domain, phishing, command-and-control and category policy at the DNS layer.
Show blocked and allowed activity with available domain, category, user and device context.
Investigate material activity and connect required follow-up to Guardian actions and reporting.
Managed filtering policy for approved users, devices, networks and customer scope.
Block known malicious, phishing and command-and-control destinations according to the selected policy and threat intelligence.
Apply agreed content and risk-category controls where required by the customer policy.
Search and review blocked, allowed and monitored events using customer-safe fields.
Use available identity and device mapping to explain who or what generated an event without exposing unrelated tenant data.
Providers can review authorised customer activity and status through provider-scoped views.
Material events can be assessed alongside endpoint, dark web, vulnerability, learning and Security Operations context.
Required policy, user, device or remediation work can be tracked through Guardian All Actions.
Summaries and activity records support customer reporting without exposing credentials or raw connector data.
Participants can review activity attributed to their approved identity and devices without seeing other users or customer data.
Business customers receive organisation-scoped protection status, activity and follow-up information.
Providers can review their own and authorised child-customer DNS Protection activity using provider-safe filtering and drilldowns.
Commercial quantity and deployment design may be based on protected users, devices, sites or an agreed customer estate. The applicable package schedule records the approved model.
Protection applies only where DNS traffic is routed through the approved service or the supported endpoint deployment is active. It does not inspect every application payload and is not represented as a replacement for endpoint security, firewalling or Security Operations.
Category policy, exclusions, roaming-device coverage, identity attribution and retention are confirmed before activation. No claim is made that every malicious domain or event will be detected.
We will confirm deployment, policy categories, exclusions, reporting, retention and operational follow-up for the selected scope.