Skip to main content

Use the platform

The Fluid Attacks platform offers comprehensive features designed to manage all your applications and vulnerabilities detected in these. To access the platform, click here.

Browser compatibility

We support the following web browsers, as well as any browser that is compatible with the ECMAScript 2019 standard.

Firefox60, 68, 78, 81, 82, 83, 88, 89, 91, 92, 93, 94, 95, 96, 97, 98, 99, 100, 101, 102, 103, 104, 105
Chrome71, 75, 80, 81, 83, 84, 85, 86, 87, 88, 89, 90, 91, 92, 93, 94, 95, 96, 98, 99, 100, 101, 102, 103, 104, 105, 106
Edge84, 89, 90, 91, 92, 93, 94, 95, 96, 97, 98, 99, 100, 101, 102, 103, 104, 105
Safari12.1, 13.1, 14, 14.1, 15, 15.1, 15.2, 15.3, 15.4, 15.5, 15.6,16
Opera78, 79, 80, 81, 82, 83, 84, 85, 86, 87, 88, 89, 90
Chrome iOS90, 93, 94, 95, 96, 97, 98, 99, 100, 101, 102, 103, 105


To sign up to the platform, go to and follow the prompts. For the steps, read the page section Sign up to Fluid Attacks.

You may sign up only with a valid Google, Azure or Bitbucket corporate account and will need to provide a Git repository to test.

Your use of all the Essential plan features is free for 21 days. During your trial, or when it is over, you may subscribe to a paid plan.

Login authentication

To login on Fluid Attacks' platform, go to

During the process, you are required to enter a one-time password (OTP) sent to your email. This step is designed to strengthen the security of the authentication process, providing an additional layer of protection. By using it, Fluid Attacks can prevent unauthorized access and protect your information.

When entering the OTP, you can check the box to indicate Fluid Attacks to trust the device you are using. Enabling this option, you will not be asked to give an OTP for the following 180 days.

Trust device

Read the page section Manage your trusted devices to better understand what this option involves and learn where to remove these devices.

Platform sections

Below, you will find a concise overview of all the sections that constitute our platform. Each section features links that will take you to their main page. We invite you to explore these links to understand each section better.


All customer data is consolidated in this section of the platform. Each organization has a data bucket that only users of that organization can access.

In this section, you will find the following subsections:


Within the Analytics section, you can view tables and different types of graphs, which offer valuable information about how your software is performing in detecting and resolving identified vulnerabilities.

Information presented, among others, includes the following:


You might have multiple apps within your organization, and it's likely that you want to keep separate their respective vulnerabilities.

You can create as many groups as needed. You have the option of having one group for each application or several groups for a single application; the choice is yours.

Within the "Groups" section, you will discover:


One of the primary sections within the platform is where you can access all the confirmed security issues related to your application. This feature is located in the "Vulnerabilities" section.

This section is divided as follows:


In this section, you will see the list of vulnerabilities, each accompanied by its specific location. In addition, you have the possibility to perform actions such as requesting a reattack, change the treatment, assign a vulnerability to a specific coworker, among other available options.

We invite you to enter here if you want to discover more about this section.


The "Description" tab offers technical insights about the vulnerability type, encompassing its nature, non-compliant security requisites, potential risks, and recommended remedial actions. For a deeper understanding, follow the provided link.


In the Severity section, you will find information about the level of severity of the vulnerability. This metric is determined using the Common Vulnerability Scoring System (CVSS) version 3.1.


This section provides supporting evidence regarding the existence and exploitation of the specific type of vulnerability reported. The evidence can come in the form of images or videos. For more information, please click here.


The detailed history information of each vulnerability is provided in the Tracking tab section. Here, you will see the entire vulnerability process.


Records tab, you will find a table with data obtained by our ethical hackers after exploiting the vulnerability in your system. Here, you can see sensitive and relevant information for your organization. For more details, click here.

Consulting in the vulnerability

Consulting should be used to communicate with us when a problem is related to any of the reported vulnerabilities or to validate the executed reattacks.

Note: Consulting in the vulnerability view is available for users with the Essential plan in view mode.

Group analytics

Within Group-level analytics, you'll discover graphs, tables, and metrics tailored to your specific group.


Fluid Attacks platform includes an agent that is present in the CI pipelines and can break the build for open vulnerabilities. This section shows the result of recent executions and more information such as the following:

  • Execution date
  • Execution status (secure or vulnerable)
  • Checked vulnerabilities
  • Strictness (Tolerant/Strict)
  • Type (SAST/DAST)


In this section, you can view events our analysts open when they cannot access the inputs. Events can be opened for various reasons; to learn more about these, click here.


In this section you will find a field where you can add comments, questions or doubts you may have about the group in general.

Note: This section is only for the Advanced plan.

Group members

You have group access control here to define who and what they can do. When you give access to the group, there are three role options available:

To get more information about it, check the Roles page.


The authors section gives you a list of git users that commit code to checked repositories.


The surface tab gives more information about the Target of Evaluation (ToE). This ToE is the result of repositories, environments and languages specified in the scope in roots section.


You need to define the surface that the Fluid Attacks team will check. The following information is required to enable the testing service:

  • Roots: Git repositories where you version the application’s source code.
  • Environments: URLs where applications are deployed.
  • Files: Any information that could help the service.
  • Tags: Keywords to build portfolios and get information and analytics for groups that share the tag.
  • Services: Active services for the group.
  • Deletion: Function to safely delete all group data.

If you want to see more of this section of scope, you can enter it here.


In the Analytics subsection, you have the data of all your groups. But if you want analytics for only a subset, you can go to the Portfolios subsection (we employ the same charts and indicators).

Please check the tags in Scope for more information.

Organization members

Some users can access your organization's data, but this permission does not guarantee access to groups or vulnerabilities, only access to organization-level analytics and policies.

Explore more of this section by clicking on this link.


You can use vulnerability treatments to plan remediation. To control the correct use of them, you can define rules that will apply to all groups in your organization. To explore this section further click here.


This section refers to repositories that are not yet associated with any group on the platform, which can consult with the credentials available in the Credentials tab. To learn more about this section, you can enter here.


In this section, you can create, edit and delete credentials at the Organization level and use them in all the groups that compose that. These credentials help us to have access to the ToE


Compliance shows the compliance of all standards validated by Fluid Attacks at the Organization and group level.

Platform version

When the platform was last deployed, because of new features or improvements to old features, is not top secret information we are keeping from our clients. You can see this information by clicking on the icon with the letter i on the platform's top-right menu.

Commit Hash Id

Upon clicking, you will see the commit hash ID (a commit’s unique identifier) that corresponds to the update. Below, you will see the update deployment date and time. You can click on the commit hash to see on GitLab the specific lines of code that were changed, the developer who made the change, what was removed and added, and on what file.

Note: This page is under development. Come back later for the full content.

free trial

Search for vulnerabilities in your apps for free with Fluid Attacks' automated security testing! Start your 21-day free trial and discover the benefits of the Continuous Hacking Essential plan. If you prefer the Advanced plan, which includes the expertise of Fluid Attacks' hacking team, fill out this contact form.