Mikey @DNSFilter
launched
Mikey @DNSFilter
Hello voters, we now have a working Chrome Extension and have a significant improvement release scheduled for next week. You can find out more in our docs. The extension was developed for a specific partnership that we are working on with Lenovo's LanSchool and does have some limitations. Most notably, it can only be deployed via MDM and is not available in the Chrome store. We'll continue to improve the extension and hope you find it valuable.
Kyle
Mikey @DNSFilter: by MDM do you mean any MDM or just gsuite or something else?
What are the other limitations?
Any advantages on non chromebooks?
Can we manually install the extension file into chrome "sideload" so to speak.
Mikey @DNSFilter
Hi Kyle, theoretically the extension could be deployed using any MDM, however, we have not tested any other than Gsuite.
Another limitation is the absence of Yandex safe search which is a feature in our other roaming clients.
A feature I forgot to mention is user reporting. You will see the user's email in our reports, which we are working to improve in the near future.
"Sideloading" is not supported at this time.
Nathan
Thanks, Mikey @DNSFilter! I'm looking forward to next week's update!
Will each Chromebook have just one roaming client instance show up in the roaming clients list or one instance for each user on the device?
Mikey @DNSFilter
Nathan: You will install just one Chrome Extension on each Chromebook but we will "assign" the traffic to the logged-in user. So you can have a single Chromebook servicing multiple users and the reporting will distinguish between the users based on who is logged in at the time traffic is sent.
Nathan
Mikey @DNSFilter: Would the following scenarios (eventually) be true, then?
Reporting Category (Data Explorer in particular)
* Requests by user will show all requests by that user regardless of device.
* Requests by roaming client will show all requests on that Chromebook regardless of user.
Deployments Category
* Roaming client section will show just one entry per Chromebook so policies/block pages can be assigned to device regardless of user.
* Users section will show individual Chromebook users so policies/block pages can be assigned to individual users regardless of device (override device policy/block page).
Mikey @DNSFilter
Nathan: I'll contact you directly via email.
Mikey @DNSFilter
Nathan
It looks like they are working on one here (https://docs.dnsfilter.com/docs/chrome-extension-roaming-client). It is still early in development, but it is in progress.
help
Yes!
Jesse
YES PLEASE!!!!
Matthew
Good one! I had a similar post just deleted in favor of using this one "Build a toolbar like Google's Suspicious Site Reporter that let's DNSFilter users submit malicious sites. It can send referrer chain + screenshots w/ full URLs to feed the AI instead of only getting the base domain. Also, show global correlation stats about domains so admins can make decisions about them on-the-fly in the toolbar.
* Let the user select an area of the screen, fill out a form that identifies which company is being spoofed, and then feed that to the AI for maximum context. Also, you could capture where the user interacted with it 'popup' 'email', etc.
* Access to stats for your own machine in the toolbar. i.e., We've blocked 550 sites for your machine. We've improved your requests an average of 58% over Comcast provider DNS averages for your region
* Network Status in the toolbar or a link to it for monitoring of the global Anycast network
* Admin capability of running searches out of the toolbar
* One click access to the portal w/ SSO from the toolbar login"
-Matthew
FixFinder
Kyle
the chromeos part is already a thing https://dnsfilter.canny.io/feature-requests/p/chromebook-roaming-client
Nathan
Kyle: This is just an Android client that can run on Chromebooks. It is not an extension.
Kyle
Nathan: in the end of the day I'm not sure what the advantage would be to having a chrome extension. Having a app would secure the Chromebook system wide not just chrome browser with a extension
Nathan
Kyle: I agree that the goal should be to secure the Chromebook system wide. The Android app currently must be activated for each user on each device manually, though. I don't know if that is a limitation of Android apps on Chromebooks or if the app just needs to be reprogrammed.