Skip to content

SecureTransit for MSPs: Digital Privacy Without Another Tool to Manage

Listen to this article instead
3:46

 

MSPs need to boost client security without sacrificing efficiency or margin. Every extra tool, console, or license just adds overhead and slows down service delivery.

Privacy is a classic example. Clients want their remote and hybrid users protected from the networks they connect through and the trackers profiling them, but most solutions add another siloed tool and more operational work.

SecureTransit lets MSPs deliver digital privacy through the DNSFilter Roaming Client, managed from the same dashboard already used for DNS-layer protection, content policies, and user activity intelligence. It encrypts traffic before it leaves the device and blocks the trackers and data brokers profiling your clients' users, on any network including the client's own. Here's a deeper look at how SecureTransit works.

The problem with separate privacy tools

Separate privacy tools mean more to maintain. Technicians end up provisioning credentials, documenting new processes, and troubleshooting connection issues. End users are often left to configure connections themselves, which leads to misconfigurations and missed steps.

For MSPs with multiple clients, this quickly turns into a service delivery problem. Clients need encrypted access, but if it adds too much operational complexity, it eats into margins and support capacity.

SecureTransit keeps encrypted access inside the DNSFilter workflow. MSPs manage it from the same console, apply it by policy, and skip adding another endpoint app to the client stack.

Worth being precise about what this is not. SecureTransit is not a VPN replacement, and it is not ZTNA. It does not control who can reach which internal applications, and it does not inspect content. It handles observation: What the local network can see, and what the trackers can collect. If a client already runs a VPN, the more useful question to ask them is whether they can prove it is actually on.

A billable add-on for clients that need it

SecureTransit is a per-device add-on. MSPs can only where it's needed, without licensing every endpoint.

Client needs aren’t one-size-fits-all. Some only need encrypted privacy for executives or traveling staff. Others need it for a wider group of remote users. Many devices don’t need it at all.

Per-device licensing lets MSPs target SecureTransit to the right users and devices. It’s easier to package as an add-on and align the cost to the client’s real use case.

Managed from the DNSFilter platform

SecureTransit is managed directly in the DNSFilter platform. MSPs can set it to Always On, Manual, or Disabled by organization or device.

Always On enforces protection for users and devices that need it. Manual mode lets users connect when needed. Disabled keeps SecureTransit off for devices that don’t require it.

Your technicians and your clients' admins keep the same DNS query visibility they have today, so there are no blind spots to explain to a client.

Removing setup for users

Credentials are provisioned server-side, so users never have to configure connections themselves.

Fewer manual steps mean fewer support tickets. That’s critical for MSPs supporting remote users on home, hotel, airport, or shared networks.

SecureTransit gives MSPs a practical way to offer encrypted access as a scalable add-on service without increasing operational overhead. Apply it where clients need it, manage it from the DNSFilter platform, and keep service delivery simple. Start offering SecureTransit with a 14-day free trial.

SecureTransit is available today on the Windows Roaming Client, with support for our other platforms coming, and it requires a Plus subscription.

 

Search
  • There are no suggestions because the search field is empty.
Latest posts
SecureTransit for MSPs: Digital Privacy Without Another Tool to Manage SecureTransit for MSPs: Digital Privacy Without Another Tool to Manage

MSPs need to boost client security without sacrificing efficiency or margin. Every extra tool, console, or license just adds overhead and slows down service delivery.

Privacy is a classic example. Clients want their remote and hybrid users protected from the networks they connect through and the trackers profiling them, but most solutions add another siloed tool and more operational work.

How Black Hat Proved DNSFilter is on the Right Expansion Path How Black Hat Proved DNSFilter is on the Right Expansion Path

By Ken Carnesi, CEO & Co-Founder, DNSFilter

I've been going to Black Hat for years, and I can tell you plainly: This year was different.

Shadow AI and AI governance are top of mind now, an evolution from what we were hearing at RSA earlier this year. In an AI era, taking a DNS First approach to cybersecurity isn't optional, and we're built to solve exactly that problem.

Explore More Content

Ready to brush up on something new? We've got even more for you to discover.