Limit Each Client to Its Own Site
Limit users, API keys and credentials to each client's site, and keep each daemon scanning only its own network.
With each client network on its own site, as in Planning Sites, limit access to each site and keep each daemon scanning only its own network.
Limit users, API keys and credentials to a site
Users, API keys and credentials belong to the organization. Limit each one to the sites it is for:
- Users: when you invite a user in Platform > Users, select the sites they may access. All data they query is filtered to those sites.
- API keys: create the key in Platform > API Keys with Specific sites. See API Keys.
- Credentials: assign each one only to the sites or hosts it is for. A new site is assigned the organization's site-wide default credentials, so check a new site's credentials and remove any that belong to another network. See Credentials.
Keep a daemon inside its network
A daemon belongs to the site chosen when you create it, and scans subnets on that site only. Within that site, two settings limit what it scans.
- Interfaces: by default the daemon scans every subnet its host has an interface on. When the host is attached to more than one network, set Interfaces on the daemon to the interfaces of its own network. See Scanning Isolated Networks from One Host.
- The scan's subnet list: a scan covers exactly the subnets in its list in Discovery > Scans. Remove any subnet the daemon shouldn't scan. See Managing Scan Targets.
When several networks are attached to one host, run one daemon per network, each created on that network's site with its own Interfaces setting.
Organizations and separate servers share nothing
An organization shares no users, sites, credentials or API keys with another, and a user belongs to exactly one organization. Scanopy Cloud creates an organization for each account that registers without an invite. A self-hosted Community, Standard or Plus license includes one organization.
Each self-hosted server has its own database, users and license.