Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
roc-dns [2020/10/29 08:35] 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. | + | ==== Access Privatise ROC-DNS ==== |
+ | |||
+ | To get access to ROC-DNS, you must provision a ROC and then login to the Threat Detection dashboard | ||
+ | |||
+ | 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 " | ||
+ | |||
+ | You will now be brought to the Privatise DNS Threat Analysis Dashboard login page. Enter the password you copied above and login. | ||
+ | |||
+ | {{:: | ||
+ | |||
+ | ---- | ||
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 |
{{:: | {{:: | ||
Line 20: | Line 39: | ||
{{: | {{: | ||
+ | |||
+ | ---- | ||
+ | |||
=== Allow & Disallow / Whitelisting & Blacklisting === | === Allow & Disallow / Whitelisting & Blacklisting === | ||
Line 35: | Line 57: | ||
{{: | {{: | ||
+ | |||
+ | ---- | ||
+ | |||
=== Audit Logs, Query Lists, Debugging === | === Audit Logs, Query Lists, Debugging === | ||
Line 46: | Line 71: | ||
=== DNS Filtering when using Active Directory on LAN === | === DNS Filtering when using Active Directory on LAN === | ||
- | You can use Privatise DNS filtering in conjunction with your Active Directory on the local network. | + | You can use Privatise DNS filtering in conjunction with your Active Directory on the local network. |
+ | |||
+ | ---- | ||
+ | |||
+ | === Custom Fully Qualified Domain Names === | ||
+ | |||
+ | You can attach Fully Qualified Domain Names to an individual IP if it's static. To do so: | ||
+ | |||
+ | 1. Go to Local DNS Records | ||
+ | |||
+ | 2. Add a Fully Qualified Domain Name on the left, and static IP of the Privatise agent you want to connect to. | ||
+ | |||
+ | 3. Alternatively, | ||
+ | |||
+ | {{:: | ||
+ | |||
+ | === 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: | ||
+ | |||
+ | {{:: | ||
+ | |||
+ | Applying the new policy: | ||
+ | |||
+ | {{:: | ||
+ | |||
+ | === Custom DNS === | ||
+ | |||
+ | If you want to use your own custom DNS, you can upstream from your own DNS provider. See image below: | ||
+ | {{:: | ||