Network Controls

Test securely through IP restrictions. Enforce org-wide monitoring, logging and security.

Network controls enable organizations to test securely through their IP access restrictions. Organizations can whitelist a range of BrowserStack IPs for all inbound and outbound traffic from our remote devices. It enables administrators to enforce org-wide monitoring and ensure that all traffic from BrowserStack cloud can be resolved through org’s network, for each of its user.

Outbound IP Whitelisting

Outbound IP Whitelisting allows your org’s users to connect to the BrowserStack domain (browserstack.com) through any corporate firewalls or proxy setups. This option is most frequently used when the security settings of organizations prevent connections from their internal computers to external endpoints. When enabled, your network team will whitelist access from your local machines to BrowserStack’s IP addresses, allowing your users to make outbound connections to BrowserStack.

How to Enable

  1. BrowserStack will provide a list of IP addresses representing our domain.
  2. Your network and security teams can whitelist the BrowserStack IP addresses in your firewall or proxy settings to allow outbound connections from your machines to our domain. Organization users will be able to access the BrowserStack cloud successfully.
Note:
  • Contact support to enable IP Whitelisting for your organization on BrowserStack.
  • Outbound IP Whitelisting will not allow BrowserStack remote terminals to reach your private staging environments. For that use case, you will need to use either Local testing or Inbound IP Whitelisting.

Inbound IP Whitelisting

Inbound IP Whitelisting allows the remote BrowserStack terminals to access your private staging environments. There are multiple implementations of Inbound IP Whitelisting, you can choose the best option based on your network and environment settings. Learn more about how BrowserStack’s inbound IP Whitelisting feature works.

There are four inbound whitelisting configurations. They each provide slightly different levels of access to your websites/applications:

Configuration Details
Dedicated Static IP Address Route traffic from BrowserStack’s remote terminals through a private static IP address that can be whitelisted to access your IP-restricted pre-production sites.
Dedicated Static IP Address + Local Testing Route traffic from BrowserStack’s remote terminals through a private static IP address that can be whitelisted to access your IP-restricted pre-production sites and use Local Testing to access private sites only accessible via your internal network.
Shared IP Addresses Route traffic from BrowserStack’s remote terminals through our shared infrastructure’s IP addresses that can be whitelisted to access your IP-restricted pre-production sites.
Shared IP Addresses + Local Testing Route traffic from BrowserStack’s remote terminals through our shared infrastructure’s IP addresses that can be whitelisted to access your IP-restricted pre-production sites and use Local Testing to access private sites only accessible via your internal network.
Note:
  • Contact support to enable IP Whitelisting for your organization on BrowserStack.
  • To use any of the inbound whitelisting configurations with the Automate or App Automate products, you need to enabled local tetsing connection by including the below capability in your test configuration: browserstack.local: true

Centralized local testing

Centralized local testing allows organizations to maintain a single local testing connection for all its users. This enables IT teams to ensure a single configuration and prevent any unauthorized access to their internal environments. This is very useful setting if IP whitelisting and running apps/binaries are restricted within your organization.

Implementation

  • Your IT or Systems team will stand up a dedicated internal server that runs the BrowserStack Local Testing binary and maintains an open Local testing connection using the WSS protocol.
  • BrowserStack will enable the Centralized local testing feature for your account (Contact support for the same). Once enabled, all Local testing traffic will be routed through the central connection and prevent other users within your account from launching Local testing connections with their own API keys.
  • Your users will initiate tests on BrowserStack with Local testing enabled. If the BrowserStack test needs to reach any non-public URLs, the HTTP request will be routed through the central Local testing connection and will be resolved from the internal server.
Note: Please ensure the internal server running the Local Testing connection has the necessary permissions to access the AUT. Any URLs not accessible to the internal server will be unreachable from BrowserStack tests. This includes the individual users’ localhost environments.

Forcing force local

Organizations can choose to enable force local for all their users on BrowserStack. When this setting is enabled, all tunnel connections initiated by any of their users will ensure that all traffic is forcefully routed via the organization network setup.

  • Ensure that the websites accessed via local testing are network compliant.
  • Test on websites behind VPNs or proxies that allow access only from restricted IP addresses.
Note:

Tunnel connection management

Network Panel enables the Owner to get a birds eye view of all the tunnel connections that have been started within the organization.

  • Monitor all the open connections along with details such as force local, duration etc.
  • Kill a single/all tunnel connections if any discrepancies are observed.

Network Panel

View network panel

  1. In BrowserStack, visit Account.
  2. Click Network Panel.
  3. You can view the active tunnel connections within your organization.
Note: Network panel can be accessed only by members with Owner or Organization Admin role.

We're sorry to hear that. Please share your feedback so we can do better







Contact our Support team for immediate help while we work on improving our docs.

We're continuously improving our docs. We'd love to know what you liked






Thank you for your valuable feedback

Is this page helping you?

Yes
No

We're sorry to hear that. Please share your feedback so we can do better







Contact our Support team for immediate help while we work on improving our docs.

We're continuously improving our docs. We'd love to know what you liked






Thank you for your valuable feedback!

Talk to an Expert
Talk to an Expert