Securing the Core Service net.tcp endpoints

Clients that connect to the Core Service through its net.tcp endpoints are typically custom code running in the context of the Content Manager Explorer Web site or the Experience Manager Web site (as part of a GUI extension). Such code is assumed to be running on the same machine as the Core Service itself. As a result, by default, the net.tcp port is closed on your firewall to prevent all net.tcp connections from outside.