SecureTrack topology map: dealing with separated sites

With multiple devices in SecureTrack and SecureChange, correct topology is essential for many different tasks: risk analysis, point to point connectivity checks, zone definitions, automatic target suggestions in SC, etc.

When you start building up the system, in most of the cases you have to fine tune your topology map. For example, if you have several geographical locations interconnected through WAN or Internet, they will most probably appear as on the map as separate isolated networks. Each one of these networks would have one or even several "clouds" representing external uplinks.

To interconnect these multiple sites one might want to set up a generic routing instance. Although this approach works, there is an easier one. You might just use cloud joining approach.

Go to Topology Map and open one of those external clouds. Go to Join Cloud menu and choose the corresponding cloud from the other site. Save the change. Now you have your separated sites linked.

Sometimes we have multiple links between the sites, for example the main Internet link and a backup link. In this case one has to merge couds twice, for the main and for backup links.