DNS protection + operational ownership
Managed DNS Services for Michigan businesses.
DNS helps devices find the services people use. CTS can help distinguish protective DNS filtering from the operational management of domain records, then scope the responsibilities your business needs.
The business question
Make DNS part of the security conversation.
A malicious destination and a broken business record are different problems. The first needs appropriate filtering and investigation; the second needs accurate records, change control and a clear owner.
A blocked site turns out to be a business dependency.
Employees need a route to request review. A useful exception process considers the destination and the business need rather than simply turning the protection off.
Define the service
What the relationship needs to cover.
The useful scope connects the technical capability with the people and operating work around it.
Protective DNS
Discuss controls that evaluate requested destinations against the selected service policies.
Records and ownership
Where included, define who maintains business DNS records and approves changes.
Visibility and exceptions
Establish how requests, blocked destinations and necessary exceptions are reviewed.
From discussion to operation
Make the next step explicit.
Start with the current environment, define the responsibility and agree on how the work will be reviewed.
- 01
Clarify the service
Decide whether the requirement is security filtering, authoritative record management or both.
- 02
Map the dependencies
Identify users, locations, domains and services affected by the design.
- 03
Operate deliberately
Define changes, review, exception handling and service escalation.
Protective DNS and authoritative DNS management are different services. Coverage for remote devices, encrypted queries and specific applications depends on the selected design.
Questions before you decide
Understand what you are buying.
These distinctions help make the service conversation more useful.
Does DNS filtering stop every malicious connection?
No. It is one layer and depends on how queries and connections are made.
Does this include our public domain records?
Only if record management is included in the agreed scope. Confirm that responsibility explicitly.
Can remote employees be covered?
Discuss roaming users, devices and query paths. The approach depends on the platform and deployment.
Part of the wider environment
Connect the responsibilities.
This service works alongside other parts of your IT and security operating model.
Useful reading
Keep exploring the question.
Related CTS articles offer background and practical perspectives.
How to Avoid and Recognize Phishing Scams
Read more about the operating decisions behind this service.
Read the articleAre SSL VPNs Still Secure? Why Businesses Are Moving Beyond Them
Read more about the operating decisions behind this service.
Read the articleStart with your environment
Talk through managed dns services with CTS.
Tell us what is changing, what concerns you and how the responsibility is handled today. We will help you identify a useful next step.