Connection mechanisms

Last updated: Sep 30, 2026


Secure connectivity to your source code and systems prevents unauthorized access. It protects sensitive data and keeps your operations continuous. Fluid Attacks gives three connectivity options for this.

Cloud

The Cloud connection is a direct and secure bridge to your resources. You interact with your assets through the Fluid Attacks platform. The access is secure, reliable, and fast.

Primary benefits of the Cloud connection:

  • Enhanced security: Strong security measures keep your data safe in transit and in storage.
  • Simplified access: You manage connections and access resources quickly.
  • High availability: Access to your assets is reliable and the same each time.

The Cloud connection page gives the details: architecture, requirements, and limitations.

Egress

With the Egress connection, Fluid Attacks accesses your resources from static public IP addresses. You whitelist these addresses on your firewall. This gives you a controlled and secure connection: only the listed addresses have access.

Primary benefits of the Egress connection:

  • Granular control: You control network access with a whitelist of specified IP addresses.
  • Firewall compatibility: It works with your current firewall configuration.

The Egress connection page gives the details: architecture, requirements, and limitations.

Connector

The Connector connection uses Zero Trust Network Access (ZTNA). You install a pivot agent in your private network. The agent is a secure access point. Fluid Attacks reaches only the resources that you authorize, and the remaining part of your network stays private.

Primary benefits of the Connector connection:

  • Enhanced security: It applies zero trust principles. Its control of network access is more granular than a VPN. This reduces the risk of unauthorized access.
  • Device security posture validation: It checks the endpoint of the user for security flaws, such as missing patches.
  • Enhanced monitoring: It records the actions of users and devices in traffic logs. This information supports security monitoring and audits.

The Connector connection page gives the details: architecture, requirements, installation steps, and limitations.

On this page