Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

The following ports should be opened:

ComponentSource IPDestination IPDestination PortprotocolReasonremarks

Bastion - Reverse Proxy Server

AnyBastion Server443HTTPSReverse Proxy listening portSphereshield for SFB
Bastion -Forward Proxy ServerTeams ClientsBastion Server80*httpForward Proxy listening portSphereshield for Teams
Bastion - Proxy ServerBastion'sSQL server1433TCPTo allow the Bastion's filters to pull configurations which will determine the behavior of the filters
Access PortalAccess Portal'sSQL server1433TCPTo allow the Access Portal website access to the SQL DB where it is used to modify settings and preferences
CASB AdapterCASB Adapter'sSQL server1433TCPTo allow the CASB Adapter to get users and groups..
Bastion, CASB Adapter, and Admin PortalBastion, CASB Adapter, and Admin Portal

Office 365 IPs

*.agatcloud.com 

443
Communication Between Proxy and Team servers

Skype for Business Online and Microsoft Teams (TCP)


Admins and BastionAdmin Portal443
Management Console and API
Webhook ListenerWebhook Listener serverSQL server1433TCPInsert messages in DB
Webhook ListenerMicrosoft IP'sWebhook Listener server443
Get Webhook notifications from Microsoft
Clients PC'sClient's*.agatcloud.com 443HTTPSTo get static scripts for clients

Microsoft GraphPlease refer to: Which URL's Should Be Opened for SphereShield when using Microsoft Graph for MS Teams

...

Firewall requirements for implementing eDiscovery using API 

Note:
When implementing API for eDiscovery, there is no importance for real-time activity, and therefore, eDiscovery via API doesn't require real-time responsiveness.  Hence the product does not need webhooks and not or the listener site. The only network traffic needed is calling graph API from the adapter   Rather, it uses a polling method whereby our adapter process calls Microsoft's Graph API.  This involves HTTPS traffic from the internal network to Microsoft's network