Hello,

We want to inform you about a new change in the presentation of elements within our Attack Resistance Management (ARM).

This time, we created a small dropdown menu placed in the upper right corner of the ARM. There, as you can see in the image, you will find part of the user's information and the API and Log out buttons, previously located in the left side menu.

At Fluid Attacks, we recognize that proper arrangement of information can make your navigation through the ARM easy and enjoyable.

All features are the product of a team effort. You can be part of it and contribute by leaving your comments here in this post or sending them to help@fluidattacks.com.

Hi there!

A few days ago, we announced a new daily email: Daily Digest.

Now a related improvement is here.

We're talking about a new 'Config' menu where you will find many more options later. For now, it will allow you to enable or disable the Daily Digest emails.

All features are the product of a team effort. You can be part of it and contribute by leaving your comments here in this post or sending them to help@fluidattacks.com.

We are deeply committed to making our users' activities within the Attack Resistance Management (ARM) more comfortable at Fluid Attacks.

It was time to modify the table of findings, which had many fixed columns with important information.

In this new presentation, as you can see in the following image, we have a cleaner table where the user can observe the descriptions and various details about the findings within drop-down lists.

All features are the product of a team effort. You can be part of it and contribute by leaving your comments here in this post or sending them to help@fluidattacks.com.

At Fluid Attacks, we are committed to facilitating our customers' activities within the Attack Resistance Management (ARM).

This time we wanted to enlarge the working area, so we decided to collapse the left bar of the ARM so that it would take up less space.

As you can see, the bar returns to its original size if you need to access any menu item.

All features are the product of a team effort. You can be part of it and contribute by leaving your comments here in this post or sending them to help@fluidattacks.com.

What happened

• Due to a recent feature implementation in our AI engine, we launched a new job that made a very huge set of parallel calls to our API, degrading its performance for a while.

What we’ve done

• We immediately stopped the involved job and committed a first fix (https://gitlab.com/fluidattacks/product/-/commit/395ca6b2070382fcc76f764922520e5999836b65).

What’s the impact

• Accessing the ARM was not possible for a few minutes.

What we are doing to help

• We are currently ensuring we don't overload our API with lots of intermittent expensive calls and also optimizing how our AI engine communicates with the ASM.

Coming soon is one of several new changes that will replace many of the ways we provide you with information.

You can see in the following image what data you will be able to access day by day through the new Daily Digest:

All features are the product of a team effort. You can be part of it and contribute by leaving your comments here in this post or sending them to help@fluidattacks.com.

Everything has a place in the world. The help button is not an exception.

From now on, you will find the help button in the upper-right corner.

From there, you can request our help at any time.

All features are the product of a team effort. You can be part of it and contribute by leaving your comments here in this post or sending them to help@fluidattacks.com.

In the last few days, we changed our comment component.

We did this, intending always to use secure and up-to-date components.

While for us, it implied a significant change at the platform level, for you, it is only a visual change.

We hope this change is to your liking, and we will be attentive to our support channel help@fluidattacks.com for any questions that may arise.

As part of our evolution towards having more control over the information published in our app, it is now possible to know which vulnerabilities belong to each repository.

This is the first step into a new world of possibilities. For now, the only control implemented is that only GIT Roots that do not have vulnerabilities linked to them can be deactivated.

If you see this error, don't worry. It means that the GIT Root you are trying to deactivate has vulnerabilities linked to it.

In order to deactivate it, close or eternally accept these vulnerabilities.

We will be adding more controls and use cases in the coming weeks, so stay alert for upcoming announcements.

Tracking the source code and why any portion of the software is excluded from Fluid Attacks analysis should be major issues in group management.

Therefore, if you are going to deactivate a GIT Root, you must declare why you are going to do so.

For now, the options are the following:

• Out of scope
• Registered by mistake

But we are going to add more options in the coming weeks.