Sites

By default, your account includes a single organization, which itself contains a single site, named Primary. If the only site in an organization is deleted, a replacement will be created automatically. Similarly, if the last organization is removed, a replacement will be created. You can rename organizations and sites at any time.

Every organization has at least one site, but may have multiple sites. A site represents a distinct network segment, usually defined by addressing or accessibility. Sites in runZero do not necessarily correspond to physical sites or locations.

All analysis actions within runZero occur at the site level. This allows for multiple sites to use the same RFC1918 space, something common in retail, while still being possible to differentiate their assets within the inventory.

Use cases for sites

For flat networks, where every IP address can reach any other address on the network, a single site is usually enough, and avoids the possibility of accidentally creating duplicate assets by scanning the same devices from multiple sites. Sites are recommended for complicated, sprawling, and highly-segmented environments.

Two circumstances that could lead to multiple sites:

  • Overlapping IP space: sites will allow you to differentiate identical IPs that are actually different machines if you have overlapping IP space.
  • Highly complex network: sites would not be required in this case, but they can be used as an organizational tool.

Creating sites

To create a new site, you click the “New Site” button on the top of the sites page.

Site configurations

  • Name: the name of your site.
  • Description: the description can help keep track of what this site is used for.
  • Default scan scope: the default scan scope will be pre-populate when creating scans for this site.
  • Default scan exclusions: the default scan exclusions will be pre-populate when creating scans for this site.
  • Registered subnets: registered subnets can be used to automatically tag assets that fall within each subnet.

Sites and Explorers

Sites can be tied to specific Explorers, which can help limit traffic between low-bandwidth segments. The site configuration allows a default scan scope to be defined, along with an optional list of excluded scan scopes. These fields can be used to set the scan scope for scans of the site.

If you would like to tie an Explorer to a site, navigate to the Explorers page, click the Explorer you would like to tie to the site, and then click configure. After that, you will see a dropdown with your site options.