roc-dns

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision 		Previous revision
roc-dns [2021/03/09 11:55]
rafi 		roc-dns [2023/01/09 15:32] (current)
rafi
Line 1: Line 1:
 ==== Managing ROC-DNS ==== ==== Managing ROC-DNS ====
  
-To get access to ROC-DNS, you must provision a ROC and then login to the Threat Detection dashboard. If you haven't done so yet, please check the guide on [[https://kb.privatise.com/doku.php?id=groupsettings#provisioning_a_roc|provisioning a ROC.]]+==== Access Privatise ROC-DNS ==== 
 + 
 +To get access to ROC-DNS, you must provision a ROC and then login to the Threat Detection dashboard from the ROC-DNS Control menu page. 
 + 
 +Once on the ROC-DNS Control page, to login: 
 + 
 +1. Click on the eye to show the password. 
 + 
 +2. Copy the password. Make sure to disable your password manager if you have one, as it might overwrite this password and give you the wrong one. 
 + 
 +3. Click the button where it says "Access ROC-DNS Dashboard" 
 + 
 +You will now be brought to the Privatise DNS Threat Analysis Dashboard login page. Enter the password you copied above and login. 
 + 
 +{{::privatise-dns-login.png?400|}} 
 + 
 +----
  
 Our enterprise level ROC-DNS is based on state of the art threat detection to ensure that your endpoints are protected. It uses its threat algorithm analysis to block malicious or suspicious domains. It is made up of a combination of opensource and proprietary solutions. Our enterprise level ROC-DNS is based on state of the art threat detection to ensure that your endpoints are protected. It uses its threat algorithm analysis to block malicious or suspicious domains. It is made up of a combination of opensource and proprietary solutions.
 +
 +----
 +
  
 === Getting Started with DNS Management === === Getting Started with DNS Management ===
Line 13: Line 32:
 === Query Logging === === Query Logging ===
  
-You will be able to see specific queries. The Privatise VPN agent makes the data anonymous, but you will be able to break it down on a per group or per company basis. +You will be able to see specific queries and break it down to the device level.
  
 {{::query-log.png?400|}} {{::query-log.png?400|}}
Line 20: Line 39:
  
 {{:disable-query-logging.png?400|}} {{:disable-query-logging.png?400|}}
 +
 +----
 +
  
 === Allow & Disallow / Whitelisting & Blacklisting === === Allow & Disallow / Whitelisting & Blacklisting ===
Line 35: Line 57:
  
 {{:whitelisting.png?400|}} {{:whitelisting.png?400|}}
 +
 +----
 +
  
 === Audit Logs, Query Lists, Debugging ===  === Audit Logs, Query Lists, Debugging === 
Line 47: Line 72:
  
 You can use Privatise DNS filtering in conjunction with your Active Directory on the local network. Please see our guide to [[remote-access|Remote Access]] for more information. You can use Privatise DNS filtering in conjunction with your Active Directory on the local network. Please see our guide to [[remote-access|Remote Access]] for more information.
 +
 +----
  
 === Custom Fully Qualified Domain Names === === Custom Fully Qualified Domain Names ===
Line 59: Line 86:
  
 {{::custom-hostnames.png?400|}} {{::custom-hostnames.png?400|}}
 +
 +=== Category Filtering === 
 +
 +Category Filtering is based off of open source lists. You can enable category filtering under Groups -> Adlists. You simply enable the category then go to tools -> update gravity and click the update button to apply the new policies.
 +
 +Enabling a new category: 
 +
 +{{::category_filtering.png?600|}}
 +
 +Applying the new policy:
 +
 +{{::update_gravity.png?600|}}
 +
 +=== Custom DNS === 
 +
 +If you want to use your own custom DNS, you can upstream from your own DNS provider. See image below:
 +
 +{{::custom_dns.png?600|}}
  
  • roc-dns.1615290947.txt.gz
  • Last modified: 2021/03/09 11:55
  • by rafi