In this article
The Organization Settings page hosts settings for org-wide Two-Factor Authentication (2FA) and Single Sign-On (SSO), as well as settings to limit the display of personal data.
Two-Factor Authentication
Require 2FA for all users at the Organization to add an additional layer of security to the account. Enabling this setting triggers individual users to setup 2FA upon their next login.
Single Sign-On
Account users with Super Admin permissions or higher to configure SSO for all users within the organization. Configure SSO with any Identity Provider (IdP) that supports the generic OpenID Connect (OIDC) authentication process.
Limit Display of Personal Data
The Limit Display of Personal Data option will reduce the amount of data we display across the dashboard. Enabling this option disables the collection of some Roaming Client fields which may contain personally identifiable information (PII).
This menu and option is only visible to Owner level users.
Redacted information
The limit display of personal data option redacts information from these DNSFilter dashboard pages:
DNSFilter Dashboard Page | Removed Information |
DNS Query Log |
✍️ The Columns menu removes the option to add back these columns |
DNS Query Log Export |
|
Insights Reporting |
|
Users, Collections, and Sync Tools |
|
Roaming Client Management |
|
Limit display of personal data FAQs
Q. How does this feature affect my organization’s GDPR compliance?
A. Your organization’s compliance with GDPR is determined solely by your own legal counsel and your own internal requirements. This feature is designed to enhance certain privacy features of our service.
Q. Can I turn this feature on and off again?
A. Yes. If after enabling this option, you decide to disable it again, you must wait for each Roaming Client to check in with the DNSFilter dashboard before Client Name and Username data is available again.
Limit display of personal data troubleshooting
If the Limit Display of Personal Data option was enabled before entering a Friendly Name for each Roaming Client, it might be difficult to differentiate between devices within the DNSFilter dashboard.
To identify Roaming Clients after the data has been redacted, compare the ID of the Roaming Client within the dashboard with the Client ID of the device. Obtain the Client ID of the device using multiple methods:
Command line or terminal window. Run this command, which will return the client_id of the Roaming Client:
nslookup -type=txt debug.dnsfilter.com
Windows Registry. Lookup the agent on the local device:
HKEY_LOCAL_MACHINE\SOFTWARE\DNSAgent\Agent\ClientId
macOS Library Application file. Lookup the agent on the local device:
Standard Agent: cat /Library/Application\ Support/DNSFilter\ Agent/daemon.reg
MSP/Whitelabel Agent: cat /Library/Application\ Support/DNS\ Agent/daemon.reg
Comments
0 comments
Please sign in to leave a comment.