Feature Requests

Can you rename the CyberSight service? Calling it "CyberSight.BehaviorTracking.Console" let's end-users know that management is tracking them. ;)

It would be super helpful if there was a DNS Filter report that could show the distribution of requests from TLD's. Essentially a graph or pie chart, with counts, grouping by TLD. This way we can hunt for TLD's that should not be in use, and probably should be blocked.

It would be helpful if there were more audit logs

CyberSight user behavior analytics transformed visibility for Windows deployments—and we want to bring that same capability to macOS. Mac-heavy teams will now have the same depth of user-level visibility across their entire fleet, without gaps in coverage based on operating system. What This Means for You Visibility and user-level activity logs extended to macOS devices Consistent behavioral insight across mixed Windows and Mac environments Faster investigations and incident response without switching between tools

For schools running Chromebook fleets, meaningful visibility into user activity has been a gap—and CyberSight is how we plan to close it. We're working to bring the same user-level insight available on Windows to the DNSFilter ChromeOS extension, with education teams squarely in mind. What This Means for You Visibility and user-level activity logs extended to Chromebook deployments Deeper insight into student and teacher activity across your fleet Consistent behavioral visibility across mixed-OS environments No additional tools required—everything within DNSFilter

Would it be possible to have a scheduled report that showed a summary of blocked pages visited (Site/Domain, Category) that could be drilled down by User/Roaming Client?

Customizable scheduled report that shows number of requests to specific domains broken down by user. Ability to limit/select domains included on report shows total requests to domain(s) shows all users those requests came from

Summary Allow MSP administrators to control whether CyberSight is visible to client-level administrators within sub-organizations. Problem CyberSight provides visibility into user activity and application usage. Some MSP partners allow their clients to administer DNSFilter within their sub-organizations but do not want those client admins to access company-wide analytics that could expose sensitive user activity (e.g., CEO/CFO browsing or application usage). Currently, CyberSight data can only be controlled by enabling or disabling data collection for specific Roaming Clients. There is no option to hide the CyberSight dashboard or restrict access to its analytics for certain administrative roles. Requested Capability Allow MSP administrators to hide or disable the CyberSight dashboard for client-level admins. Provide MSP-level controls to determine which roles can view CyberSight analytics. Maintain CyberSight data collection while restricting visibility when needed. Optionally support role-based permissions (custom roles) to control access to analytics features. Customer Value Allows MSPs to provide dashboard access to clients without exposing sensitive user activity data. Supports privacy and internal policy requirements for organizations with executive or sensitive roles. Provides better role-based control for MSP-managed environments.

Some blocked applications generate large amounts of query log entries, creating noise in the logs that makes searching for other blocked sites (that we might want to allow) difficult.

When searching the DNS query log, it's easy to define a relative timeframe (ex: Last 4 hours). Once that timeframe is set though, when you click refresh it maintains the same 4 hour window from when that option was originally chosen. Clicking refresh should also refresh the 4 hour window to be NOW-4 hours from the time the refresh occured.