Network egress policy
Decide where Bot computers may connect: everything, the usual places plus your list, or only your list, for the whole organization or for one group.
3 min read
Where the policy is setCopy link to this section
Administrators set it in the admin console under Enterprise controls, in the Network section. It applies to the browser and commands on every Bot computer, and to the workspace's own outgoing calls for connectors and workflow steps. A saved change reaches running computers within seconds, without a restart, and is recorded in the audit trail.
With no policy at all, Bot computers may reach anything. Members cannot change the policy; they can ask for a site to be allowed (below).
The three modesCopy link to this section
- Allow all network access: a Bot computer may reach anything.
- Defaults plus team allowlist: the hosts a computer needs to install packages and fetch source code, plus your own Allowlist. A new policy starts here.
- Team allowlist only: nothing but your Allowlist.
Note
To give a Bot no network at all, switch off Cloud network access under Capabilities on the same page, for the people or groups who own it. A Bot computer that has been quarantined also gets no network.
Writing the allowlistCopy link to this section
One entry per line. For example:
example.com
*.corp.example
10.0.0.0/8 443,5432example.comallows the domain and all its subdomains.*.corp.exampleallows only its subdomains, notcorp.exampleitself.10.0.0.0/8 443,5432allows an address range on the ports listed. A name is allowed by a range only when every address it resolves to falls inside it.
Entries are checked when you save: a domain, range or port list that is not valid is refused with the reason.
Addresses that are always refusedCopy link to this section
Whatever the mode, even Allow all network access, Bot computers can never reach the link-local and cloud metadata addresses, such as 169.254.0.0/16, where a server keeps its own credentials.
When a Bot opens a page in its browser, only web addresses are accepted, and internal, private and local addresses are refused before the computer is asked.
Group policies and the lockCopy link to this section
Add a group policy gives one group its own Group network policy. It is used instead of the Organization network policy for Bots whose owner is in that group. If the owner is in several groups with a policy, the group whose name comes first alphabetically is used.
On the organization policy, Lock: groups may not replace this policy makes the organization's policy apply to everyone, whatever their groups' policies say. Only the organization policy has a lock. Remove policy deletes a policy; with a group's removed, its Bots fall back to the organization's.
Building an allowlist from what Bots really useCopy link to this section
In the admin console under Security:
- Egress log shows which hosts a Bot's computer contacted and whether each was allowed, never the content.
- Propose an allowlist lists where one Bot's computer went. Untick anything that should not be there and add the rest to the organization's allowlist; the mode is not changed, so you can switch to an allowlist mode once you are content.
- Test an address against egress policies shows, for each Bot, whether it may reach an address and why. Nothing is opened.
When a page a Bot needs is refused, a member can ask for it. The request appears under Site requests on the admin console's Computers page; approving it adds the site to the organization's allowlist.
Last updated