Gateway.Management is a next-generation content filter and Internet gateway designed with a purposeful architecture to maximize on-premise performance with cloud-based intelligence. DNS, as a fundamental building block of the Internet, is at the core of this software along with strategic and dynamic firewall rules designed to allow a homeowner, a business owner, or an enterprise IT team to enforce desired policies without the use of proxies, SSL inspection, or other traditional techniques.

Gateway Management Community gives you granular control over each user’s Internet experience. The following features can be applied network wide, or on a device by device basis:

• Block inappropriate content
• Block phishing and identify theft attempts
• Block ads (even on mobile devices connected to WiFi)
• Block behavioural profiling
• Manage shared and custom lists

To maintain speed, Gateway Management Community performs all filtering on your ClearOS box. It is controlled with a Cloud based interface. For extended information see the Gateway.Management website for more details.

<div classes #id width uk-grid :language> <div classes #id width uk-width-medium-3-1 :language><div classes #id width pdflink :language>PDF</div> </div><div classes #id width uk-width-medium-3-2 :language> Product Overview and Availability </div> </div>

Before you begin the installation, you will want to document the following items that will help you with your deployment and configuration:

• Document all your internal domains on your local area network(s) (eg. mycompany.local)
• Document all external domains for the purpose of split DNS administration. (eg. remote.example.com)
• Document your current DHCP range(s) and statically assigned devices (eg. 192.168.5.100-200)
• Document all your reverse DNS zones (eg. 5.168.192.in-addr.arpa)
• Document your internal DNS servers (eg. 192.168.5.2, 192.168.5.3)
• Document all your internal Active Directory and Samba Directory Servers if you have them (eg. 192.168.5.4, 192.168.5.5)
• Document any proxy servers in use (if any)
• List all your core business applications which require Internet access (eg. accounting, banking, and applications with their own Internet update mechanisms)
• Verify you have layer 2 visibility of the machines under management from the gateway devices
• Document your IPv4 and IPv6 configurations and setting on your network.

<div classes #id width uk-grid :language> <div classes #id width uk-width-medium-3-1 :language><div classes #id width pdflink :language>PDF</div> </div><div classes #id width uk-width-medium-3-2 :language> Procurement, Introduction and pre-installation </div> </div>

To deploy this app you will need to make arrangements with your IT staff to decommission certain services and functions that may be running. The following items should be done to accomplish the transition to Gateway.Management:

• If this is an additional gateway, you will want to stop the DHCP services on the original gateway.
• Start the DHCP server on the same server that is running Gateway.Management assuming that this is the new, single gateway for your network. If this does not describe your network configuration, you may need to contact support or visit the forums for assistance and recommendations.
• Install and activate the software. Follow the steps below for finding the app in the Marketplace and navigating to that app. Once the installation is complete, enable the app and then start the app. Unless the IP address listed in the 'Block Page IP' conflicts with network resources in your LAN, or Enterprise, please use that IP listed by default. If you need to change it, you may need to contact technical support.
• Check the email account on record if this is your first installation. Then validate the software status and verify that your gateway device is online at the Gateway.Management portal
• Run through the Quality Assurance steps which include:
  • Edit the list for your device to ensure that you can view all logs
    • Confirm this with the Who Am I tool
    • Verify that the dashboards are links in the log files
  • Verify that the 'MyBox' tool links back to your device locally. (eg. https://192.168.5.1:81)
  • Validate an end-user device
    • Make sure that the MAC address is correct. If not, you likely don't have layer 2 visibility to all your devices from your gateway.

Plan on a maintenance window of 30-60 minutes for the deployment and initial configuration of this app.

<div classes #id width uk-grid :language> <div classes #id width uk-width-medium-3-1 :language><div classes #id width pdflink :language>PDF</div> </div><div classes #id width uk-width-medium-3-2 :language> Installation and deployment </div> </div>

If your system does not have this app available, you can install it via the Marketplace.

When installed and configured, an email will be sent to the account of record for the registration of your ClearOS server. If you are unsure about what email address this is, please log into your ClearSDN portal for your account.

You can find this feature in the menu system at the following location:

<navigation>Gateway | Filtering | Gateway Management Community</navigation>

Once you have Gateway Management Community installed on the server, it is time to configure and initialize the service.

The Box ID is a unique identifier used by the Gateway Management cloud system. You may need this information if you re-provision your ClearOS system.

When a web page is blocked, Gateway Management displays a block page. This allows you to select from which IP that page will be displayed. This IP must NOT be on the same subnet as the LAN interface and it must not be in use. You typically want to use the IP address given by default unless that address lies in a range already used by your environment.

The Gateway Management dashboard controls all of your related settings.

After completing the setup, visiting the Gateway Management Community page in your ClearOS web-based configuration tool will give you a link to open your cloud dashboard.

You can also visit https://dashboard.gateway.management directly.

Key to the management of your new gateway's management is the use of policies that you will create. These lists include authoritative lists, black lists, white lists, and rainbow lists. The following order of operations exists for all policies:

• Authoritative
• Rainbow
• Black
• White

Once a match has been achieved, the other policy rules are disregarded for a particular DNS request.

<div classes #id width uk-grid :language> <div classes #id width uk-width-medium-3-1 :language><div classes #id width pdflink :language>PDF</div> </div><div classes #id width uk-width-medium-3-2 :language> Lists Rule Sets and Devices </div> </div>

One important additional security feature provided by Gateway.Management is the “Don't Talk to Strangers” feature (or DTTS.) This feature makes it so that connections that do not have a DNS resolution are proactively blocked by the gateway. This means that a number of applications and services that try to circumvent DNS (like many Bittorrents, unauthorized VPNs, botnets, et al.) will be blocked.

To create bypass rules, look for the DTTS Bypass feature.

<div classes #id width uk-grid :language> <div classes #id width uk-width-medium-3-1 :language><div classes #id width pdflink :language>PDF</div> </div><div classes #id width uk-width-medium-3-2 :language> Don’t Talk To Strangers (DTTS) </div> </div>

The more you customize your environment the more difficult it will be for internet abusers to circumvent or exploit your network.

<div classes #id width uk-grid :language> <div classes #id width uk-width-medium-3-1 :language><div classes #id width pdflink :language>PDF</div> </div><div classes #id width uk-width-medium-3-2 :language> Customization and Tailoring </div> </div>

If you are using Active Directory in your environment, you will want to customize and tailor the mechanisms of your DNS resolution to properly configure Gateway.Management and AD DNS to work together.

Please see this DNSThingy support article for setting up Gateway management in an Active Directory domain.

You can edit the device names of devices behind your gateway to make them more manageable and to increase visibility in reporting. In the Devices section, click the 'edit' button to manage individual devices.

You can also add devices manually if layer 3 discovery is not in place. Simply add the device.

Tags can be used to group larger networks for more efficient management

The Block Page Assistant is a plugin for Google Chrome that allows your secure browser to give a descriptive block message instead of a security warning.

Users who are blocked can request unblocks from their block page. These will queue in your 'Unblock Requests' page in the Gateway.Management portal. You can manually or automatically whitelist the requests.

You can only auto-whitelist as long as the page is:

• Listed under Google SafeBrowsing
• In an acceptable Category site
• Is not adult content
• Is of known good reputation

You can add Managers so that additional people can manage your whitelists and unblock requests can be processed by multiple trusted individuals.

• MyTools.Management - Starting point for end users and new admins to the system

You can customize your block page in the interface. Don't forget to whitelist your block page!!!

• Product Overview and Availability
• Procurement, Introduction and pre-installation
• Installation and deployment
• Lists, Rule Sets and Devices
• Don’t Talk To Strangers
• Customization and Tailoring
• AdamNetworks (formerly DNSThingy) Knowledgebase

• Features
• FAQ
• Sign In to Gateway.Management

search?q=clearos%2C%20clearos%20content%2C%20gateway.management%2C%20app-gateway-management-community%2C%20clearos7%2C%20userguide%2C%20categorygateway%2C%20subcategoryfiltering%2C%20maintainer_dloper&amp;btnI=lucky